> yes, bootrc basicly does the same stuff as the c based /boot/boot
> did before. we found that the other 30 odd programs can come in handy.
> especially when you try to boot a kernel on a odd machines where
> theres no working disks (yet :-)).
Yes, I've found the same approach useful while developing an sd/mmc
card driver for the raspberry pi. I started with this inital boot.rc:
#!/boot/rc -m /boot/rcmain
/boot/echo boot...
/boot/bind -c /boot /bin
bind '#p' /proc
bind '#d' /fd
bind -a '#P' /dev
bind -a '#t' /dev
bind -a '#S' /dev
echo -n rpi >/dev/hostowner
echo fdisk...
fdisk -p /dev/sdM0/data >/dev/sdM0/ctl
cat /dev/sdM0/ctl
dossrv -f/dev/sdM0/dos
mount -c /srv/dos /mnt
exec /boot/rc -m/boot/rcmain -i
And for sd driver testing there's no need for a paqfs - a handful
of useful programs can just be stuck into /boot directly:
bootdir
boot.rc boot
/arm/bin/rc
/rc/lib/rcmain
/arm/bin/mount
/arm/bin/unmount
/arm/bin/bind
/arm/bin/echo
/arm/bin/cat
/arm/bin/cmp
/arm/bin/ls
/arm/bin/ps
/arm/bin/dd
/arm/bin/xd
/arm/bin/rm
/arm/bin/mkdir
/arm/bin/disk/fdisk
/arm/bin/dossrv
But all this is now obsolete [see next message].
