That's probably why they recommend that you not hand-edit the Grub2 config file.spandey wrote:There are some unprintable characters before word savefile. Hence entire savefile argument has become meaningless. Looks like they came up while copying and pasting Grub2 entries in the editor. A very good lesson for future !!!!
Fatdog64-610 testing 20 Nov 2012 (finished)
It's all there in http://puppylinux.org/wikka/Grub2. Anyway I am repeating it again.For the benefit of other Fatdog-Grub2 users, could you please post your 40-custom file along with some instructions on how you used it in Mint? Where do you put the file? What update command do you run? etc.
1. GRUB2 can't find frugal puppy install otherwise it picks up most other linux installed in the machine.
2. Just open the '/etc/grub.d/40_custom' with admin access and add the entries for puppy like lucid, fatdog etc.
3. Once done form terminal do 'sudo update-grub'. You are good to go.
Here are my sample '40_custom" file entries
Code: Select all
menuentry "Lucid Puppy 5.2.8" {
search --no-floppy --fs-uuid --set=root 672878ac-c0ca-453b-bc38-0de03ec38f63
linux /Luppuold/vmlinuz pmedia=atahd psubdir=Luppuold pfix=fsck
initrd /Luppuold/initrd.gz
}
menuentry "Precise 5.4.1" {
search --no-floppy --fs-uuid --set=root 672878ac-c0ca-453b-bc38-0de03ec38f63
linux /Precise/vmlinuz pmedia=atahd psubdir=Precise pfix=fsck
initrd /Precise/initrd.gz
}
menuentry "Fatdog 600" {
search --no-floppy --fs-uuid --set=root 672878ac-c0ca-453b-bc38-0de03ec38f63
linux /Fatdog/vmlinuz savefile='ram:device:sda5:/Fatdog/fd64save.ext4'
initrd /Fatdog/initrd
}
I had Linux Mint 13 on here until an update caused a boot failure, but grub2 is still working.
/etc/grub.d/41_custom reads like this.
So I place custom entries in /boot/grub/custom.cfg. With entries in that file it is unnecessary to update grub. Since Linux Mint doesn't boot anyway that is kind of handy.
Here is the entry for Fatdog64 610.
Here is one with no save file for Fatdog64 600
The UUID of a partition can be found by running the command:
One time I plugged in another hard drive and sda became sdb, but Fatdog64 still booted because grub2 read the UUID.
If entries are placed in /etc/grub.d/40_cutom instead of /boot/grub/custom.cfg, the command to update grub2 is:
Here is a link to a good tutorial on grub2:
http://ubuntuforums.org/showthread.php?t=1195275
Ubuntu has closed those types of how to's and now require them to go into there community wiki, so someday that link maybe dead.
/etc/grub.d/41_custom reads like this.
Code: Select all
#!/bin/sh
cat <<EOF
if [ -f \$prefix/custom.cfg ]; then
source \$prefix/custom.cfg;
fi
EOF
Here is the entry for Fatdog64 610.
Code: Select all
menuentry "Fatdog64 610" {
insmod part_msdos
insmod ext2
set root='(dev/sda,msdos2)'
search --no-floppy --fs-uuid --set=root 6fbee58b-cd48-4819-8d2b-ed06d7f00eea
linux /fatdog610/vmlinuz root=UUID=6fbee58b-cd48-4819-8d2b-ed06d7f00eea savefile=direct:device:sda2:/fatdog610/fd64save.ext4
initrd /fatdog610/initrd
}
Code: Select all
menuentry "Fatdog64 600 No Save" {
insmod part_msdos
insmod ext2
set root='(dev/sda,msdos2)'
search --no-floppy --fs-uuid --set=root 6fbee58b-cd48-4819-8d2b-ed06d7f00eea
linux /fatdog600/vmlinuz root=UUID=6fbee58b-cd48-4819-8d2b-ed06d7f00eea savefile=none
initrd /fatdog600/initrd
}
Code: Select all
blkid
If entries are placed in /etc/grub.d/40_cutom instead of /boot/grub/custom.cfg, the command to update grub2 is:
Code: Select all
sudo update-grub
http://ubuntuforums.org/showthread.php?t=1195275
Ubuntu has closed those types of how to's and now require them to go into there community wiki, so someday that link maybe dead.
Brief return to 64bit-land with an i3.4G. LiveCD, used my worst (p54) and best(zd1211) performing dongles along with a couple of others that rarely give problems. No problems finding base station, no problem connecting to ditto, but as soon as an attempt is made to use the connection for anything it drops out (message pops up in tray). e.g. load default browser, type in URL, - everything still stable - hit Enter and down it goes, new tray message pops up 'disconnected'. Few seconds later after stopping trying to access the connection, tray message often pops up with re-connect (but not always). This routine proceeds until patience runs out. Doesn't happen with any other distros on this machine or with those dongles on other machines/other distros, except, maybe, the Wistron which can be as much of a pig as Broadcoms. Didn't happen with FD600s. ???
Sage,
After it disconnects from your network, can you open a terminal and type:
and then attach those two files to this thread? I'm surprised it worked in 601 and quit working with 610. Thanks
After it disconnects from your network, can you open a terminal and type:
Code: Select all
lspci > /root/lspci.txt
dmesg > /root/dmesg.txt
Live media is NOT getting the session saved at Power-off
Hi all.
As has been traditional with my use of FATDOG since inception, I use its Live media feature for operations and management of the OS. Traditionally, after all tailoring is done and saved via saved session, the OS runs basically un-interrupted for in 1 case, year(s).
In testing the latest Beta; namely 610 I have run into an issue when trying to save the session back to the Live media. I do understand that there are several changes in the saved file(s) which represents the changes and the tailoring done while the system was running. I am positive on these changes as the architecture is very promising. But, unfortunately, I have run into some issues in trying to get my session saved.
To show the problem, here is a step by step that I followed which leads to the problem.
It surfaces as follows:
Also, my desktop configuration may be a little different from other desktops. There is no Floppy and there are 2 DVD burners on the system. And, as I may have mentioned, all local and remote mounts were umount'd prior to start of Power-off.
Here to help.
As has been traditional with my use of FATDOG since inception, I use its Live media feature for operations and management of the OS. Traditionally, after all tailoring is done and saved via saved session, the OS runs basically un-interrupted for in 1 case, year(s).
In testing the latest Beta; namely 610 I have run into an issue when trying to save the session back to the Live media. I do understand that there are several changes in the saved file(s) which represents the changes and the tailoring done while the system was running. I am positive on these changes as the architecture is very promising. But, unfortunately, I have run into some issues in trying to get my session saved.
To show the problem, here is a step by step that I followed which leads to the problem.
It surfaces as follows:
- Menu>Power-off
The Create Save File Window pops: click Yes (Do you want to create a savefile now?)
What follows is unexpected at end of desktop session - Create Save File windows text dialogue changes to set/reset the system hostname: Changed it to FATDOG610-testing and clicked Next
(this is unexpected because, all system changes including hostname changes should have occurred before reaching this point. Reason: Other system files and applications should have configured with hostname needs long before getting to this point in the system's use. This step really should be moved to system start and not at system end so that any tool that would utilize or need the final system hostname would have at their setups. But, I'm sure there are those who are going to argue this placement as a defensive.)
Again, the following, too, is unexpected at end of desktop session - Create Save File windows text dialogue changes to set/reset root's password: Changed it fatdog and clicked Next
(This also is unexpected placement. Shouldn't this be also done at system's initial start.)
Expected - Create Save File windows text dialogue changes to choose save session device: Changed it /dev/sr0 (where the Live media presently resides) clicked "Save as multisession" (this is an unknown for which there is no documentation or desktop help for this new shutdown parameter) and clicked Next
Expected - Create Save File windows text dialogue changes to show status of some prior entries for confirmation: Viewing shows my prior selections and clicked Next
Xdesktop is then exited and text terminal (console) continues with message that a fatdog ...sfs is being created. Immediately the system progresses with another message, then and within 15 seconds, the PC powers down without every saving of anything to the Live media.
Also, my desktop configuration may be a little different from other desktops. There is no Floppy and there are 2 DVD burners on the system. And, as I may have mentioned, all local and remote mounts were umount'd prior to start of Power-off.
Here to help.
Thank you, bug confirmed, I will look at it.gcmartin wrote:Xdesktop is then exited and text terminal (console) continues with message that a fatdog ...sfs is being created. Immediately the system progresses with another message, then and within 15 seconds, the PC powers down without every saving of anything to the Live media.
Procedure is correct.Could someone confirm the procedure
EDIT: Bug is fixed for the next release. Please note that even after you managed to save the session, at next boot you will have to type "fatdog savefile=direct:multi" if you boot from the first DVD drive. If you don't want to do this all the time you will need to remaster and ensure that you put this boot parameter into your customised isolinux.cfg.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Known problem: due to kernel bug, DVDs ejected with hardware button will stay shown on the Rox desktop. Right-click, then "eject" to remove it from the desktop.
This will be fixed in the next release (either we replace the kernel or we put back the userspace polling).
This will be fixed in the next release (either we replace the kernel or we put back the userspace polling).
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Nothing's ever straightforward is it?!
The feature reported has become variable - occasionally, every dongle is now connecting, sometimes some aren't and sometimes some drop out. Also aware of some ISP issues. Working to try to isolate each parameter before we send you up/down any blind alleys, kirk. I saw something about forcing a connection to be retained somewhere?
The feature reported has become variable - occasionally, every dongle is now connecting, sometimes some aren't and sometimes some drop out. Also aware of some ISP issues. Working to try to isolate each parameter before we send you up/down any blind alleys, kirk. I saw something about forcing a connection to be retained somewhere?
Well, kirk, sorted out the ISP, now getting stability with connections to the zd1211 and the p54 Wiston. The rt2800usb ( new Hama 300MHz) now comes up as 'not in list' which it didn't do previously and when added, doesn't connect, which it did! The other dongles are out on loan - an Atheros and a Broadcom. The former is rather older but often worked for its previous owner as well as for me, the Broadcom is fairly new but haven't used it much yet. I knew the router was OK because the on-board units on mobiles and laptops always connected.
Thanks for following up - will know what to do next time!
Later: Knew I'd seen it recently, it's from our own micko over on the Slacko thread:
Thanks for following up - will know what to do next time!
Later: Knew I'd seen it recently, it's from our own micko over on the Slacko thread:
Regarding your connection, Frisbee has an option that keeps the connection up if it's flakey.
SWAP partition is not picked up on initial Live media boot
Problem Scenario
Booted the Live media FATDOG610. There is a SWAP partition on the HDD.
But, the booting system is either not detecting/ignoring it. This is a new problem for booting PUPs.
Here to help
Booted the Live media FATDOG610. There is a SWAP partition on the HDD.
But, the booting system is either not detecting/ignoring it. This is a new problem for booting PUPs.
Here to help
Re: SWAP partition is not picked up on initial Live media boot
Fatdog requires manual configuration (by editing /etc/fstab) to activate the swap file.gcmartin wrote:Problem Scenario
Booted the Live media FATDOG610. There is a SWAP partition on the HDD.
But, the booting system is either not detecting/ignoring it. This is a new problem for booting PUPs.
Here to help
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Re: SWAP partition is not picked up on initial Live media boot
Thanks for your responses.jamesbond wrote: ... Fatdog requires manual configuration (by editing /etc/fstab) to activate the swap file.
If time permits, maybe this could be used by default with manual config step to turn it off or expand it if necessary. Just a thought. If useful, run with it.
Cheers
Re: SWAP partition is not picked up on initial Live media boot
EDIT: Fatdog requires manual configuration (by editing /etc/fstab) to activate the swap PARTITION, not swap file. Fatdog has a utility (in the Control Panel) to automatically create a swap file and mount it at boot.gcmartin wrote:Thanks for your responses.jamesbond wrote: ... Fatdog requires manual configuration (by editing /etc/fstab) to activate the swap file.
Well, if one is advanced enough to know about and create a swap partition, I'd assume that one knows how to edit /etc/fstab or at the very least be capable of using "swapon" command to use the swap partitionIf time permits, maybe this could be used by default with manual config step to turn it off or expand it if necessary. Just a thought. If useful, run with it.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I have a query related to default action of Fatdog or may be it's how all puppy's behave.
Using Fatdog, I opend a text file in some other linux partition using geany and without doing any changes just closed it. Will there be any changes to that file's attributes or attributes of any of it's parent directories?
Using Fatdog, I opend a text file in some other linux partition using geany and without doing any changes just closed it. Will there be any changes to that file's attributes or attributes of any of it's parent directories?
There shouldn't be. But geany does some hidden stuff that basic text editors like leafpad do not. So I wouldn't want to swear to it.spandey wrote:Using Fatdog, I opend a text file in some other linux partition using geany and without doing any changes just closed it. Will there be any changes to that file's attributes or attributes of any of it's parent directories?
Did you actually see something change?