> > As I'm mainly looking for a stable replacement to my Eiger series disks,
and
> > the overall size of the distribution has shrunk considerably already,
I'm
> > going to stick with ctar for package creation. I'm hoping this will be
the
> > last of the primarily LRP based releases, with new stuff using an
updated
> > packaging format, likely some version of your apkg application.
>
> What do you mean by "last of the primarily LRP based releases"?
The last of the releases I plan that will include a substantial portion of
code from LRP systems. Major LRP chunks and their planned replacements:
Kernel Patches: I'd like for these to go away...the work you're doing with
removing things from root.lrp helps here, as what I'd like to see is a
fairly small conventional ramdisk image that rarely (if ever) needs to be
altered. No more funky LRP kernel patches to mess with...use any kernel
you've got space for on your boot disk.
POSIXness: Mainly replaced by busybox, but there will probably be a few
script based applets.
Network init scripts: I think something more graceful can be done here.
The 'mountain' images already share very little network.conf code with 2.9.x
releases.
Script based package system: Replaced with apkg, modified apkg, or possibly
something completely different.
Firewall scripts: Not a part of LRP 2.9.x at all, but will be replaced by
something like SeaWall, rcf, &c.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
