How to add sfs files to a FATDOG64 live CD/DVD? (Solved)

A home for all kinds of Puppy related projects
Post Reply
Message
Author
gcmartin

How to add sfs files to a FATDOG64 live CD/DVD? (Solved)

#1 Post by gcmartin »

@fatdog64kudos posted thisPosted: Today, August 3rd at 1:07 am
kirk,

I made another sfs/iso/CD without devx but with 8 additional sfs files included:
audio-all-in-one-amd64-7.sfs
fd64-32bit-libs.sfs
hugin-2010.0.0-amd64.sfs
jre160_amd64-3.sfs
skype_static-2.1.0.81.sfs
wine-1.2-rc5-i486-4.sfs
xcas-0.8.6-amd64.sfs
go-oo_32_amd64-3.sfs

Following your procedure a new sfs file of 560 MB was created and a new Fatdog64-500-extra.iso as well. burniso2cd was used to burn the iso and the system was rebooted using the new CD.

The same problem happened while booting the CD after the sfs was copied to RAM as detailed below.

BUT copying the new sfs file to a pen drive allowed the CD boot to boot successfully ( it found the sfs file on the pen drive and used it ) and all ran very well.

Also, booting via grub in the MBR of a pen drive with the sfs and other files copied to the pen drive booted nicely as well.

SO, as far as I can tell it is a size issue while booting solely from the CD. I was concerned that it might have been a devx associated problem, but now it seems not so.

ERRORS REPORTED:

Loading 'fd64-500.sfs' main file ... copying to ram done
Dumping last lines of /tmp/bootinit.log ...
mount: /dev/sr0 is write-protected, mounting read-only
writing '/mnt/tmpfs/fd64-500.sfs': No space left on device
mount: mounting /dev/loop0 on /pup_ro2 failed
mount: mounting unionfs on /pup_new failed

Dumping last lines of kernel log ...
<7> ISO 9660 Extensions: RRIP_1991A
<7> ISO 9660 Extensions: Microsoft Joliet Level 3
<7> ISO 9660 Extensions: RRID_1991A
<3> aufs test_add:226:mount[1743]: unsupported filesystem, /pup_ro2 (rootfs)
I. too, have this exact problem under different circumstances. My circumstances has involved several differing attempts to produce a LiveDVD by updating the booted LiveDVD at the end of a desktop session following procedures and steps I have found on the Puppy Sites. They have involve placing SFS files on the DVD and updating the BOOTCONFIG file using the Puppy provided utilities., then saving the session changes on reboot. All cases, whether manual, or using the BOOTMANAGER Bootup Configuration utility ends with this exact error. My only circumvention to get a FATDOG64 desktop session is to reboot the LiveDVD with puppy pfix=1 to get my desktop session. And this reboot does NOT have the SFS changes I was looking to have.

I am certain that there is either a lack of understanding on extending a LiveDVD or there is sort of a problem wtih what FATDOG64 was expecting at boot time as it tries to incorporate the additional SFS files.

Anyone with any ideas on where to look for resolution. Be aware that what I hit and what @fatdog64kudos hit, I believe are related.

gcmartin

Here's a listing of the LiveDVD's filesystem when attempting

#2 Post by gcmartin »

Many attempts were made to process directly on the LiveDVD. Puppy tools used in updating the LiveDVD were
  • normal shutdown and Save feature
  • growfsiso
  • BootManager Configure Bootup
LiveDVD Filelists

Code: Select all

9 files totaling 191292MB after burning on 07/07/10
-r--r--r-- 1 root root      2048 2010-07-01 20:36 boot.cat
-rwxr-xr-x 1 root root       105 2009-06-11 10:26 boot.msg
-rwx------ 1 root root 191397888 2010-07-01 20:25 fd64-500.sfs
-rwxr-xr-x 1 root root      1089 2010-04-23 00:19 help.msg
-rw-r--r-- 1 root root   1667619 2010-05-20 23:02 initrd.gz
-rwxr-xr-x 1 root root     14336 2010-06-30 21:12 isolinux.bin
-rwxr-xr-x 1 root root       138 2009-06-11 10:26 isolinux.cfg
-rwxr-xr-x 1 root root         0 2009-06-11 10:26 logo.16
-rw-r--r-- 1 root root   2797968 2010-05-20 16:49 vmlinuz

After saving session couple of times, this is the rebooted filelist
drwxrwxrwt 11 root root      2048 2010-07-08 20:08 2010-07-09-01-12
drwxrwxrwt 10 root root      4096 2010-07-09 01:40 2010-07-09-02-42
-r--r--r--  1 root root      2048 2010-07-01 20:36 boot.cat
-rwxr-xr-x  1 root root       105 2009-06-11 10:26 boot.msg
-rwx------  1 root root 191397888 2010-07-01 20:25 fd64-500.sfs
-rwxr-xr-x  1 root root      1089 2010-04-23 00:19 help.msg
-rw-r--r--  1 root root   1667619 2010-05-20 23:02 initrd.gz
-rwxr-xr-x  1 root root     14336 2010-06-30 21:12 isolinux.bin
-rwxr-xr-x  1 root root       138 2009-06-11 10:26 isolinux.cfg
-rwxr-xr-x  1 root root         0 2009-06-11 10:26 logo.16
-rw-r--r--  1 root root   2797968 2010-05-20 16:49 vmlinuz

After following one set of Puppy SFS guidelines, this is the failed filelist
drwxrwxrwt 11 root root      2048 2010-07-08 20:08 2010-07-09-01-12
drwxrwxrwt 10 root root      4096 2010-07-09 01:40 2010-07-09-02-42
drwxrwxrwt 10 root root      4096 2010-07-09 03:33 2010-07-09-03-39
drwxrwxrwt  9 root root      2048 2010-07-08 23:06 2010-07-09-04-16
drwxrwxrwt 10 root root      2048 2010-07-09 11:50 2010-07-09-12-09
-r--r--r--  1 root root      2048 2010-07-01 20:36 boot.cat
-rw-r--r--  1 root root       132 2010-07-26 03:22 BOOTCONFIG
-rwxr-xr-x  1 root root       105 2009-06-11 10:26 boot.msg
-rwx------  1 root root 191397888 2010-07-01 20:25 fd64-500.sfs
-rwxr-xr-x  1 root root      1089 2010-04-23 00:19 help.msg
-rw-r--r--  1 root root   1667619 2010-05-20 23:02 initrd.gz
-rwxr-xr-x  1 root root     14336 2010-06-30 21:12 isolinux.bin
-rwxr-xr-x  1 root root       138 2009-06-11 10:26 isolinux.cfg
-rwxr-xr-x  1 root root         0 2009-06-11 10:26 logo.16
drwxr-xr-x  3 root root      2048 2010-07-09 11:52 mnt <=== SFSs here
-rw-r--r--  1 root root   2797968 2010-05-20 16:49 vmlinuz

After following 2nd set of Puppy SFS guidelines, and ONLY trying for OOo SFS, this is the failed filelist
drwxrwxrwt 11 root root      2048 2010-07-08 20:08 2010-07-09-01-12
drwxrwxrwt 10 root root      4096 2010-07-09 01:40 2010-07-09-02-42
drwxrwxrwt 10 root root      4096 2010-07-09 03:33 2010-07-09-03-39
drwxrwxrwt  9 root root      2048 2010-07-08 23:06 2010-07-09-04-16
drwxrwxrwt 10 root root      2048 2010-07-09 11:50 2010-07-09-12-09
drwxrwxrwt  9 root root      2048 2010-07-09 08:04 2010-07-09-14-23
drwxrwxrwt 11 root root      2048 2010-07-24 13:49 2010-07-25-02-45
drwxrwxrwt 10 root root      2048 2010-07-25 14:04 2010-07-25-23-14
drwxrwxrwt  9 root root      2048 2010-07-25 21:11 2010-07-26-02-47
drwxrwxrwt  9 root root      2048 2010-07-25 22:00 2010-07-26-03-28
-r--r--r--  1 root root      2048 2010-07-01 20:36 boot.cat
-rw-r--r--  1 root root       132 2010-07-26 03:22 BOOTCONFIG
-rwxr-xr-x  1 root root       105 2009-06-11 10:26 boot.msg
-rwx------  1 root root 191397888 2010-07-01 20:25 fd64-500.sfs
-rw-r--r--  1 spot spot 191352832 2010-07-08 05:53 go-oo_32_amd64-3.sfs
-rwxr-xr-x  1 root root      1089 2010-04-23 00:19 help.msg
-rw-r--r--  1 root root   1667619 2010-05-20 23:02 initrd.gz
-rwxr-xr-x  1 root root     14336 2010-06-30 21:12 isolinux.bin
-rwxr-xr-x  1 root root       138 2009-06-11 10:26 isolinux.cfg
-rwxr-xr-x  1 root root         0 2009-06-11 10:26 logo.16
drwxr-xr-x  3 root root      2048 2010-07-09 11:52 mnt
-rw-r--r--  1 root root   2797968 2010-05-20 16:49 vmlinuz
ALL attempts to have FATDOG64 boot and include SFS(s) failed with the error as indicated by @fatdog64kudos

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#3 Post by jamesbond »

Did a very quick test today. Combined devx and main sfs, I did it this way:
a) extract the content of main.sfs to a folder
b) extract the content of devx to another folder
c) use cpio -p to combine content of devx folder to the main sfs folder
d) mksquashfs to re-create the main.sfs folder
e) re-create the live-cd using mkisofs

All those are done on a harddisk with ext3 filesystem. If you have plenty of RAM you could probably do it on /tmp instead.

Oh yes, the that caused the crash is inside /init, so you have to extract initrd.gz, edit init and re-create the initrd.gz before step e).

The offending code is in line 1179

Code: Select all

SIZESFSK=$(($SIZESFSK + 1000)) #some slack.
.
Change 1000 there to at least 2000 or higher (2000 did the trick for me), so it should look like:

Code: Select all

SIZESFSK=$(($SIZESFSK + 2000)) #some slack. 
.
And then the new live-CD boots perfectly. I used 1GB RAM for testing this.

cheers!
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]

fatdog64kudos
Posts: 9
Joined: Sat 24 Jul 2010, 03:52

#4 Post by fatdog64kudos »

jamesbond,

Thank you very much for your time in finding the problem, solving it and testing it out as well :)

I will give it a try.

Thanks also for Fatdog in the first place !

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#5 Post by jamesbond »

No worries. gcmartin has asked me to upload the modified initrd.gz, it's on the "broken" folder on fatdog's ibiblio site.

cheers!
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]

gcmartin

Next relaese of FATDOG64

#6 Post by gcmartin »

@jamesbond
I heard rumor of an upcoming FATDOG64. Will this modification to init.gz be included?
Thanks in advance...
Edited 12-24-10: Bump

Post Reply