I have been able to mount the initrd file after uncompressing with gzip. Normally, I mount the uncompressed file with:
mount -t ext2 -o loop initrd /mnt/data
The above does work the Puppy 2.17 initrd. However, it does not work with Puppy 3.00. The Xfilemount utility by Sunburnt also dos not work. Any ideas on how to mount Puppy 3.00 initrd? Thanks in advance for any help.
Problem mounting Puppy 3.00 Initrd.gz
Problem mounting Puppy 3.00 Initrd.gz
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Read the release notes:
http://www.puppylinux.com/download/release-3.00.htm
http://www.puppylinux.com/download/release-3.00.htm
Thank you, Barry for the information. I am posting the process for anyone else who is interested and if someone searches for it:
For Puppy 3.00 initrd.gz is a cpio archive. The 'initrd' file no longer has a filesystem inside it, so cannot be mounted with a loop device. It is now a cpio archive, so has to be extracted somehing like this:
# gunzip initrd.gz
# mkdir puppy-init
# cd puppy-init
# cat ../initrd | cpio -d -i
To go the other way, that is, to create a initrd.gz file:
# cd puppy-init
# find . | cpio -o -H newc | gzip -9 > ../initrd.gz
For Puppy 3.00 initrd.gz is a cpio archive. The 'initrd' file no longer has a filesystem inside it, so cannot be mounted with a loop device. It is now a cpio archive, so has to be extracted somehing like this:
# gunzip initrd.gz
# mkdir puppy-init
# cd puppy-init
# cat ../initrd | cpio -d -i
To go the other way, that is, to create a initrd.gz file:
# cd puppy-init
# find . | cpio -o -H newc | gzip -9 > ../initrd.gz
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Barry picked this up as well - as did I
he is rolling cpio back from 2.6 to 2.5 as apparantly it is a known issue
Slackware 12 uses 2.5 probbaly for this reason
v2.6 apparantly has problems with the interpretation of symlinks and instead copies the busybox file instead
See Barry's Blog for a better explanation
George
he is rolling cpio back from 2.6 to 2.5 as apparantly it is a known issue
Slackware 12 uses 2.5 probbaly for this reason
v2.6 apparantly has problems with the interpretation of symlinks and instead copies the busybox file instead
See Barry's Blog for a better explanation
George
george