On 22 Jan 2001, at 23:19, [EMAIL PROTECTED] wrote:
> On Mon, Jan 22, 2001 at 04:15:11PM -0600, David Douthitt scribbled:
> > specific case (Oxygen) this is already handled by using
> > /var/boot/modules, and loading these modules even before
> > packages are loaded.
>
> Cool!
Oxygen also allows modules (*.o) to be placed on a disk and
loaded before any of the modules (on that disk) are loaded...
> > 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?
>
> Well, those two are specific to each user, and so should be just
> an option somewhere.
>
> > 3. How are these specified?
>
> Either in syslinux.cfg, or as in my idea, in a script or config
> file that the user can edit from lrcfg..
A config file implies that it has to be booted first to be edited, then
rebooted to get packages loaded - I prefer finding a way in
syslinux.cfg, though the options in Oxygen are starting to exceed
the 255 char limit :)
> > 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.
>
> Hence needing the modules loaded.
>
> > 2. the packages are all at the root level.
>
> Whaddyamean?
Any packages loaded by "PKGPATH=/dev/fd0u1680" have to be
located at / on the disk - packages in /lrp/pkgs will be missed...
> > 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? :)
>
> :)
>
> Nope..that's why you'd specify which packages you wanted to load.
Oxygen considers this obsolete, though it is still supported. All
packages on the boot medium and on the PKGPATH entries are
loaded automatically.
> > 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.
>
> Why don't you have to specify a path when loading via network?
Network loading is done via URL..... http://server/dir/to/lrp.conf or
tftp://server/dir/to/lrp.conf
> > Perhaps a (compatible) extension to PKGPATH is necessary to
> > specify the actual path that goes with a device to be loaded...?
>
> Maybe. What exactly do you mean by 'actual path that goes with a
> device to be loaded'?
Sample entry:
BOOT=/dev/fd0u1680 PKGPATH=/dev/fd0u1680,/dev/hda5
This loads all packages on two floppy disks (the boot disk and one
other) as well as all packages located on /dev/hda5 at the root
level. To break down the packages into subdirectories requires a
path of some kind.
--
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
