On 2/4/02 at 2:24 PM, Serge Caron <[EMAIL PROTECTED]> wrote: > What [an enclosure] does promote is a facility for moving from > environment A to environment B, be it Oxygen or Dachstein > or whatever.
> There is no guarantee to Joe User that happens to like > Shorewall enough to build on it for his own needs that he > will be able to move his stuff to a cool new environment > like Oxygen. > > On the other hand, the ordinary sysadmin that can write a > script without feeling the urgency to rewrite the entire > LEAF effort will find the concept of an enclosure usefull. > After all, HER stuff is protected and she is one quick "cp > -a root.lrp ..." away from moving to something else. > Further, you can replace the ENTIRE set of files in the > enclosure without loosing the base concept. Note that Oxygen (now) uses root.gz - which is NOT a tar.gz file, but a gzipped filesystem image, just like the Linux kernel wants... > Finally, it does promote some social responsibility. If > LEAF provide a package repository, it creates a pull > effect, that is a center of attention were everybody can > go to find something. If it also provides "reference" kits > (bootdisk, kernels, modules, whatever) it suddently has a > broad offering as well as sharing the experience of > working with these different environment, be it glibc > 2.1.x or MacIntosh processors. If Charles, Jacques, or > David create a "distribution", it creates a push effort > that lacks the LEAF project synergy. Forgive me - you lost me there. Pull? Push effort? Project synergy? Reference kits? What? > Not only do I agree that POSIXness and silly kernel > patches must go, I expect people creating enclosures to > document each aspect of building of boot image in the > comfort of their user's computer. This is Linux and people > are also expected to work from source. Depending on the user's knowledge, you can do this: # fdformat /dev/fd0u1680 # dd if=my-leaf-disk.ima of=/dev/fd0u1680 Or you can look at the Linux From Scratch site (and HowTo) and read the Developer's Guide. > PacketFilter is just a network setup script designed to > drop IP traffic. Yet it is usefull enough to build a small > workstation, an unforeseen benefit. How do you create a workstation from a network shell script? > As I plainy wrote in the > documentation: "I do not intend to maintain an LRP > distribution just for the purpose of providing an > environment in which to run PacketFilter." I believe this > is clear enough. True. But one doesn't need to create a distribution to utilize shell script and create your own firewall scripts. That is how Seawall, Shorewall, and rcf came to be. All work without a specific distribution. It almost sounds as if you are suggesting that a distribution have a standard set of applications included and a standard set of functions and scripts so that script writers can depend on certain programs being there and not worry these same programs will turn up missing. -- 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
