I was thinking... If you make root.list contain specific files, and "move" the specification of "./" to another package, that raises some interesting things.... What if instead of gloming onto home.lrp, you create overflow.lrp or default.lrp?
One nice benefit would be that if that package grows, one would KNOW it.... and the root.lrp package in systems that still use it would not grow without bound if something is messed up. On 2/19/02 at 5:23 PM, Serge Caron <[EMAIL PROTECTED]> wrote: > Suppose that the system of partial backups is finely tuned > so that modified files always end up in write-enabled > storage. Suppose also that packages from read-only storage > are always loaded before packages from write-enabled > storage, eg, you don't loose modifications. Finaly, > presume the goodwill of the package developer, eg, package > xyz claims nothing out of its immediate territory. Oxygen already supports the use of config.lrp, which is a package containing ALL files listed in *.conf files and saved in package format - and this package is loaded *LAST* after all other packages. This means that you can update the conf files and then save them to a floppy which is used during a CDROM boot - in which case your configuration is used and the system is configured just how you want it. -- David Douthitt UNIX Systems Administrator HP-UX, Unixware, Linux [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
