On Mon, Jan 22, 2001 at 12:17:26PM -0600, David Douthitt scribbled:
> I've been wondering about this problem, and wondered what you all
> thought about it. The problem is this: a volume is typically
> mounted as one of the first parts of the system start process (in
> the rc scripts), and loading packages before this happens can be
> difficult.
>
> For example, you have packages in /hda/lrp/net/1/*.lrp and in
> /hda/lrp/net/2/*.lrp and you want them to load - but /hda isn't
> mounted until after all the packages are loaded - and /etc/fstab
> doesn't even exist until etc.lrp is loaded.
>
> What's more, there is two specifications here: a physical device
> and/or mount point (/hda, /hda5, whatever) and a path. How do you
> set this up?
Er...how do you set what up? Imagine you're running the command
yourself:
mount -t msdos /dev/hda1 /mnt
/dev/hda1 is the device, /mnt is the mountpoint, msdos is the fs type.
> Would it be enough to load packages from a path, and if the path is
> not found, mount a drive? Or should the "mount all drives" be done
> even earlier? Or what?
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. 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.
This is a good idea, actually: Package load priority. Maybe two
to five points in the boot process where packages can load,
labelled a, b, c, d, e, f; and then a priority of 0-x, so you
can control (within each letter-labelled time) the order that
packages are loaded. A package of priority a1 would load as
early as possible, which c5 would be relatively later on,
probably more like packages are loaded now.
> My thinking is muddled on this - I need some clarity.
I'm sure I just made it worse. That's what you get when you
start turning the gears inside my head.. <G>
> Here is another example - more true to life:
>
> A bootable CDROM with a LEAF project on it boots and then
> wants to load packages from /cdrom/lrp/pkgs/net1/ and
> /cdrom/lrp/pkgs/net2/ .... this is what got me thinking about this,
> but hard drives have the same potential problem.
>
> More than anything, it's the path that throws things off - the current
> way of doing things is to specify the physical device... What do
> you all think?
Well, without modifications to root.lrp, which might make it
easy, what about maybe something in syslinux.cfg that tells
it to mount something...
Wait a second, this is so easy...here it is:
Make a package containing scripts that run, mount the volume
you're concerned with, and then load packages from it as you
please.
Okay, I've just turned my brain to mush. Thank you, come again.
> --
> David Douthitt
> UNIX Systems Administrator
> HP-UX, Linux, Unixware
> [EMAIL PROTECTED]
--
rick -- A mind is like a parachute... it only works when it's open.
ICQ# 1590117 [EMAIL PROTECTED] (home)
Help with LRP: http://lrp.c0wz.com Home page: http://www.c0wz.com
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
