Note 1 :
I have put a removal of /var/tmp and /tmp gets moved to /var/tmp/ .
Note 2 :
Due to giving access to keyboard i have put in a lot of the module loading part of rc.sysinit .
Note 3 :
I am working on implementing other filesystem capabilities atm , reiserfs 3x first .

And even it has more than is needed for a simplified setup, as it makes
masses of links and has it`s app. loading / unloading method code.

I didn`t catch what your new init code does for Puppy...

The main purpose is to have an interactive and debugging mode .

Fsck -y automatically repair without questions can mess up things ie move a lot files to /lost+found like windows chkdsk to /found.000 .

On both OS Linux+Win these files get numbered names, so they become nearly impossible to recover correctly, especially the small files . 100 Mb files could be easily thought they may be some .sfs or .iso but how to recover /boot/grub for example if its files get named like

found_001.chk
found_002.chk
.
.
.

If you ever have experienced such on both OS like me you want to make a fsck -n or -i first to get an overview .

Parts of the code are also experimental mounting a sfs found somewhere on disk in case the needed binaries are corrupted too .

I have implemented a check for glibc version which might not be needed .

I could think of the whole put in an initrd.gz for full installs , where it would not need to check /lib for size, pivot_root and that all .

This /sbin/init is intended for people that want not much "Crunchbang" to their HDD .

I am on full installations mainly and there are so many Puppies out and Projects that it should be OK for me not to make a Derivate for now .

I am enjoying my adjustments which are different everywhere with their ugly debugging output . Not sure if that would be successful since such is not common .

I really do like busybox and i don't call it a "crippled whatsever" but ash has some disadvantages to bash :

no arrays
type has no -a option

for example .

Hardware that survived older Puppy versions rc.shutdown for example i think you can busybox poweroff without getting nightmares .

I am not the real minimalist , my RAM stated once with 320 MB . I have configured my kernels with both SATA and IDE inside and enjoing them .

There are some testers out there that complain about empty folders . Who needs them ?

But now i have problems with newer Hardware with Xorg for example . Some kernel configurations i thought would work don't work anymore and am regretting that i thrashed some kernels that did not work back then . My main kernel compiling machine died and i would have to setup a new one .

Today i struggled with testdisk for example after i accidentally did a cp /file /dev/hda which destroyed the MBR . The problem was the extended part of the partitions and after several attempts testdisk was able to dd the (two) partitions in question and the correct one was able to mount to recover but testdisk ordered my disordered physical/numbered partiton table and i had to get grub installed and find me a backup menu.lst and change the root (hdx,y) and root=/dev/hdaz entries .

Such things happen to me every day . Compiling can turn out very troublesome hunting dependencies, fixing the various [qic*]makes, fixing header structures, I mostly compile "./configure" that probably is not Puppy-like (i486) . Must say my HW started with i686 .

And for this particular /sbin/init i need a new HDD to experiment with other filesystems which could be possible since i was able to spare for two new ones; mail came yest/oday at least one can be picked up in some hours .

And i even think that is useless since it seems that really most people run Puppy frugally, which i can not understand since i once started with kernel 2.2 series suse-linux once when such loop mounting probably was not invented back then having had no telephone nor router .

And there is so many testing Puppy.iso ~ twice a week : enjoy them !

And for fsck : Because of my desaster today i had to fsck /dev/hda1 which got the superblock overwritten and for the record : Linux fsck names the files in lost+found "#NUMBER" without an extension .

Another idea i developed today is to add a mbr_backup.txt file to contain fdisk -l, date, and file output so i now which mbr.NUMBER is the one to be used; had grub4dos on hda1 and menu.lst was gone . I really like grub4dos but on toplevel of first drive I never really felt comfortable, and mostly stay with legacy grub .

Ever heard of indenting your code?? I could easily tell what your code is doing if it was formatted to be readable. But code like that makes me cringe -I won't even try to read a single line of that mess, hence I would never try it out either! You know, formatting would be helpful for you also -when you are debugging or three months from now when you look at that code again.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum