On 2/13/02 at 8:16 PM, Serge Caron <[EMAIL PROTECTED]> wrote:
> By formulating the concept of a default store and that of
> an exclusion list, here is _what_I_do_today_ : I boot from
> a CD which gives me all the storage I need for the job at
> hand. I define my default store to be on the _floppy_. So
> far, so good? Then I have this code snippet as part of the
> boot sequence:
Yeah! CODE! :)
> for pkg in /var/lib/lrpkg/*.list; do
> sed -e "/^etc/d" -e "/^[/]etc/d" -e "/^[.][/]etc/d" \
> ${pkg} > ${pkg}.light
> cmp -s ${pkg} ${pkg}.light
> if [ $? = 0 ]; then
> rm ${pkg}.light
> else
> echo ${pkg}
> mv ${pkg}.light ${pkg}
> fi
> done
How about this:
for pkg in /var/lib/lrpkg/*.list ; do
if grep -q "[./]*etc" ; then
sed '/[^\/]*etc/d' $pkg >$pkg.2
mv $pkg.2 $pkg
echo $pkg
fi
done
> Yes! Every package list that claimed anything in /etc is
> rewritten! When I want to backup, I simply remove the
> write protect tab on the floppy. I can assure you that it
> takes a lot of config data to fill 1.6Mb of compressed
> space. Further, if the floppy is lost or if something BAD
> happens, the machine still boots from the CD: removing the
> floppy is akin to a master reset on the memory, not the
> software. The entire experience is almost identical to
> running from ROM. Sharing it will only improve the
> process. For example, the enclosure can CREATE on the fly
> an empty package if the default store is not specified.
> See the discussion.img floppy that is idling somewhere.
How's this different from Oxygen and Dachstein and how they read their
configuration data from the floppy? I can create a package which
contains nothing but configuration files, put it onto a floppy disk,
and boot the Oxygen Bootable CDROM using that configuration....
And I DON'T have to rewrite all of the packages...
> I understand completely. The process of changing the way
> something is stored is usually referred to as a
> "conversion" and you will provide at a later date the
> conversion procedure for your RAM disk. Will you still be
> supporting the old LRP patches, eg, will Oxygen 1.9+
> support both the old tar.gz RAM disk and the new gz only
> RAM disk?
For booting purposes the use of root.lrp is dead; however, a script to
convert root.lrp to a root.gz is practically a neccessity. The LRP
patches can't be used on any kernel newer than 2.4.5 last I heard; so
this kills the use of a *.tar.gz file for booting.
> I am not certain I understand everything you wrote there,
> but I understand that you would be happy to include
> additional packages in your repository. I am correct?
One of the ways I felt I could help LEAF (or LRP) was to package up
everything I wanted - or everything in sight, which was about the same
thing :-)
The repository is one of two things. I've tried to make a repository
in that I've been gathering a lot of packages together, too. However,
a real Repository would be with hyperlinks, descriptions, home pages,
etc.... and requires a new package extension. I've not done as much
as I ought, but it mainly uses a new file /var/lib/lrpkg/<pkg>.desc
which contains all of the information....
This information is then read by the Lua script and converted to
HTML....
--
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
