Lynn Avants wrote:
As I noted, this post is to submit where I am with
[snip]
Thoughts, comments, suggestions, or flames???
Nuts! That's my flame. Nuts. This whole idea I mean. Don't get me wrong... I'm all down for doinking around in a GUI to do some of the config, but ya'll are going about it wrong-like. What is needed imho, is preconfig. Preconfig means you burn Bering-1.0 onto a diskette, in Windows let's say. Then you run an app that can access the .tgz files on the diskette and insert the correct modules.o, the correct ip and dhcp basics, you know, enough to get your system functional, the first time you pop in Bering. Otherwise, you're sort of talking about redoing Bering from the ground up. In my suggestion, we don't touch her. In addition, Lynn lists the weblet's dependencies: back end, front end, new packaging system, new packages, precompiled binaries, etc. I suggest that the easiest of those tasks be started, not the global weblet idea that requires all of them to be done already. And besides, what's the goal here? Remote, secure admin of a functioning LEAF box? Can't we do that already with SSH/SCP? Matt ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
