[later]
From what I've seen in init, loading the additional SFS files starts from /dev/loop4, so I think it's in conflict with this:
Code: Select all
mount -r -t squashfs -o noatime /dev/loop4 /pup_z
Code: Select all
mount -r -t squashfs -o noatime /dev/loop4 /pup_z
What firmware did you delete?Why is this so big?
Firmware. I may trim that substantially -done.
Code: Select all
CNTLOOP=4 ; UMNTRO=""
Code: Select all
CNTLOOP=5 ; UMNTRO=""
Firstly .. wasn't on purpose of course. included wrong tarball . I'll upload a new kernel package soon, which will have an identical set of modules but the missing firmware will be back.peebee wrote:Also, think the removal of broadcom b43 wireless firmware (and others?) is a really retrograde step as it removes one of puppy's great strengths of wifi support OOTB - does the saving of a a few mb's in the iso size really matter these days????
Conflict in init. If you want to keep testing use the old init attached.. expand initrd.gz and replace init. OR try MHHP's suggestion above this post.SFR and peebee and others wrote:kernel panic on reboot if I install any sfs
Only thing remotely related is the removal of gtk-chtheme.. so it beats mezigbert wrote:Something has happened to gtk since the alpha
No, but changes are not that big in devx so a rename is safe enough, but you need to roll back init as mentioned to use it. OR, try MHHP's suggestion above.musher0 wrote:You just renamed the devx, right?
Tested with devx, libreoffice, adrv (gimp sfs renamed) and ydrv (jre by shino sfs renamed) and it all works.MinHundHettePerro wrote:Hello!
Changing line 1651 of initrd_/init fromtoCode: Select all
CNTLOOP=4 ; UMNTRO=""
solves the problem with kernel panic for BOOTCONFIGged sfs-files. (At least for me ...)Code: Select all
CNTLOOP=5 ; UMNTRO=""
Cheers / MHHP
SFR wrote:@Mick: what about those lsmod | grep '^aufs' tests?
I don't want to make any changes to the affected scripts, until we agree which procedure should be the standard from now on.
Greetings!
Unionfs hasn't worked properly in the kernel for over 4 years. They have shifted to a userspace model.2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).
I did the edit, loaded the devx and kernel source sfs with SFS-Load on-the-fly, then rebooted and everything is good.MinHundHettePerro wrote:Hello!
Changing line 1651 of initrd_/init fromtoCode: Select all
CNTLOOP=4 ; UMNTRO=""
solves the problem with kernel panic for BOOTCONFIGged sfs-files. (At least for me ...)Code: Select all
CNTLOOP=5 ; UMNTRO=""
Cheers / MHHP
Ok, done.01micko wrote:Unionfs hasn't worked properly in the kernel for over 4 years. They have shifted to a userspace model.2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).
I vote option 2.
It'll be OK. But FYI, see sfs_load-2.0.8 line 1836-1839, maybe taken from somewhere Barry's code.SFR wrote:2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).
Code: Select all
# aufs or unionfs?
#AUFS=$(lsmod | grep -w '^aufs')
# 11 Feb 2011 v0.7: see aufs even with no module(thanks to jemimah)
[ "$(mount -t aufs)" != "" ] && AUFS=aufs || AUFS=""
Yes, that's a good check, but academic now.shinobar wrote:It'll be OK. But FYI, see sfs_load-2.0.8 line 1836-1839, maybe taken from somewhere Barry's code.SFR wrote:2. Don't check for aufs at all (and additionaly remove all stuff related to unionfs, if we're sure the latter won't be used in the future).It needs only for backward compatibility.Code: Select all
# aufs or unionfs? #AUFS=$(lsmod | grep -w '^aufs') # 11 Feb 2011 v0.7: see aufs even with no module(thanks to jemimah) [ "$(mount -t aufs)" != "" ] && AUFS=aufs || AUFS=""
Code: Select all
# zarfy
(zarfy:21258): libglade-WARNING **: could not find glade file '/usr/share/zarfy/zarfy.glade'
Error opening glade xml file <üû¶
I made the pet using dir2pet on the package-zarfy directory in tmp/SBo01micko wrote:@Billtoo
zarfy misses the glade file?
Code: Select all
# zarfy (zarfy:21258): libglade-WARNING **: could not find glade file '/usr/share/zarfy/zarfy.glade' Error opening glade xml file <üû¶
Code: Select all
# tar xvf *zarf*pet
./package-zarfy-0.1.0/
./package-zarfy-0.1.0/pet.specs
./package-zarfy-0.1.0/install/
./package-zarfy-0.1.0/install/slack-desc
./package-zarfy-0.1.0/usr/
./package-zarfy-0.1.0/usr/doc/
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/zarfy.SlackBuild
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/README
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/NEWS
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/INSTALL
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/ChangeLog
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/COPYING
./package-zarfy-0.1.0/usr/doc/zarfy-0.1.0/AUTHORS
./package-zarfy-0.1.0/usr/bin/
./package-zarfy-0.1.0/usr/bin/zarfy