On 22 Jan 2001, at 19:10, [EMAIL PROTECTED] wrote:
> Can't mount 'em till etc.lrp is loaded; it might do to have it
> load ASAP, then deal with things like fstab, then load other
> packages.
Makes sense.
> Actually, modules.lrp should prolly be loaded sooner
> rather than later; then you're looking pretty much at a base
> LRP system loaded early followed by secondary packages loaded
> later.
I'm not sure what you meant by this, but it sounds like you are
refering to the requirements of modules to be loaded. In my
specific case (Oxygen) this is already handled by using
/var/boot/modules, and loading these modules even before
packages are loaded.
Theoretically, it would thus be possible to mount something before
any packages are loaded at all, given the right module.
> This is a good idea, actually: Package load priority.
Scary :-) This could be a good idea, but there seems to be some
trouble. For example, what is the priority of root.lrp?
Would have to think on this some more...
> Make a package containing scripts that run, mount the volume you're
> concerned with, and then load packages from it as you please.
This seems to be the basic idea, but here is some troubles I have...
1. What device should be mounted?
2. What is the path?
3. How are these specified?
Currently, PKGPATH specifies a device name. This is good as
long as these requirements are satisfied:
1. the device can be mounted by the kernel.
2. the packages are all at the root level.
For a floppy system, this is just fine. For a hard drive system,
custom-tailored for an individual system, it is probably just fine.
For a CDROM with a complete package repository on it, this could
be a problem.... you really want to load 100's of packages every
time you boot? :)
There could be an expanded form of the current Oxygen networking
setup - loading an Oxygen system over the network uses a
"lrp.conf" file with filenames of packages to load in it. However, on
a readonly system such as CDROMs, this won't work unless a
path to a file is specified - then you are stuck again.
Perhaps a (compatible) extension to PKGPATH is necessary to
specify the actual path that goes with a device to be loaded...?
--
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
