[...]
> Actually, I view both existing LRP efforts, and a completely new base as
> within the pervue of the Leaf project. Short-term, I'd like to see an
> organized method of creating and distributing LRP based images, with the
> dual goal of making the images slightly more 'official' as well as building
> a structure that can be use to easily allow multiple folks to contribute to
> and/or maintain the same disk image. This will be vital (IMHO) to both
> existing LRP images, and any new-new things created by leaf.
Ok, good that we have the freedom to do something new. I'd like to see
the new base soon.
In relation to this, and your other post quoting Dave: I sort of agree with
Dave.
Disk images are fine but I'd like to see them include as little as possible
for the "official" ones. Only what's needed to make a secure packetfiltering
router. But I would like to see variations of these: different kernels, different
HW (i386,m68k,286(ELKS?),fpu, no fpu, "debian init" & "slack init", stuff like
that.
I'd much rather see a huge directory with packages
and an installer (running on linux, windows & others) to make small
distributions ("disk image wizard"). It should have the possibility to save the
configs you make, and name 'em. It should also know about disk image sizes
& stuff, and make recommandations (or show status) on what sort of media
you would need for the particular config. you are working on, as you add/remove
packages. This would be good for the pro: very little is forced upon them, and
good for the newbie: They'll get an (eventually) idiot proof way of making what
they need.
Now of course we would welcome prebuilt disk images for different purposes.
They could even be official, but I would then like to have them in their own
directory (The extended & the basic disk images). I would also like it to be a
requirment that if these images where to be official, the person making them
would have to join the LEAF team, and support them. Once he leaves, and no
one steps up to take over they are considered obsolete.
Also, if they have their own ways of setting them up, etc. One would have to
divide them further, into flavours IMO. They'd still be LEAF though.
Disk images from people not wanting to be part of LEAF team, and/or that
they don't intend to support could also be catered for in an incomeing or contrib
directory. And be part of the LEAF project that way.
No way we can guarantee these to be secure by default.
All would still be considerd LEAF
> Eventually, someone will create a new build environment for leaf, when the
> pressure to migrate to a 2.4.x kernel, use a smaller C library, have a build
> environment on a non-Slink platform, or some other factor motivates someone
> (or several someones) to do the work required. Even so, 'piggy-backing' on
> an existing distribution, particularly some of the embedded disto's with
> pre-rolled cross-compile environments, will probably save a lot of time and
> effort. Whether the new base is LRP or not, depends on what Dave C. turns
> Butterfly into, and how it compares with the other tiny linux disto's
> available.
I'd like to see this sooner, rather than later. And get it all right from the start :)
Anyway: I'm still having serious problems visualizing what you want LEAF to be.
Don't we need some sort of common base to build on, other than not agreeing
with Dave's dictatorlike control/leadership? Please spoonfeed me if necasery :)
Per
--
Per Gustav Ousdal <[EMAIL PROTECTED]>
SirCon DA, Postbox 12, 4440 Tonstad, Norway
Tlf: +47 38371111 Fax: +47 38371119
http://www.sircon.no
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-devel
