Dachstein automatically *ALWAYS* includes the boot= device in the packagepath, while Bering seems to completely ignore the boot= device when loading packages (except for a 'hack' to get DoC working if PKGPATH is not defined).
Is this an oversight or the desired behavior?
I initialized the package path to the boot= device for the following reasons:
- Everything works as before if you don't include a PKGPATH setting in the kernel command line or provide a pkgpath.cfg file on the boot= device, ie: backwards compatability.
- There's no real need to specify the same device twice, which wastes kernel command line space (limited to 256 characters).
NOTE: The DoC 'hack' would *NOT* have been required, if the old Dachstein method of including the boot= device in the package path had been implemented.
Before I 'fix' this in the new linuxrc scripts I'm working on, I want to make sure it's not supposed to work the way it does for some reason I don't fully understand.
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
