4.3.1 supports ext4, but the init script ignores ext4 drives

Please post any bugs you have found
Post Reply
Message
Author
User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

4.3.1 supports ext4, but the init script ignores ext4 drives

#1 Post by jemimah »

Add ext4 to this line in the init script to fix.

Code: Select all

PCPARTS0="`echo "$PCPARTSALL" | grep '^/dev/' | cut -f 1-2 -d '|'  | grep -E 'iso9660|ext2|ext3|reiserfs|msdos|vfat|minix|ntfs' | sed -e 's/\/dev\///g'`"

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#2 Post by BarryK »

Download Woof and get the latest 'init' script, has many more bug fixes.
[url]https://bkhome.org/news/[/url]

User avatar
c.cobb
Posts: 9
Joined: Thu 11 Feb 2010, 01:16
Location: Costa Rica

#3 Post by c.cobb »

Where exactly does the init script reside? I'd like to learn more about startup, but all I find for init is a symlink to busybox. I'm missing something basic! Also, which Woof package would contain new init? I tried downloading the busybox[...].pet package but same thing: init's just a symlink. (Rather not download all of Woof just yet.) Thanks!

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#4 Post by jemimah »

You have to open the initrd.

Code: Select all

mkdir initrddir
cp initrd.gz initrddir
cd initrddir
gunzip initrd.gz
cat initrd |cpio -id
rm initrd
To repack:

Code: Select all

cd initrddir
find . | cpio -H newc -o > ../initrd
cd ..
gzip -9 initrd
You can get the new script by building a puplet from woof and extracting it from the resulting initrd.

User avatar
c.cobb
Posts: 9
Joined: Thu 11 Feb 2010, 01:16
Location: Costa Rica

#5 Post by c.cobb »

Thank you very much. I thought that, after the pivot, the initrd fs was mounted under /initrd so was just looking under there. Lots to learn. Cheers,

Post Reply