Lynn Avants wrote:
But it's not secure. All remote admin should be encrypted.
Can't you tunnel http through SSH, zebedee, stunnel, <whatever> ?
Ok. You're right, you can tunnel through ssh easily enough.
Secondly, we need standards first, for files and manifests.
Absolutely!
Unfortunately I don't understand how a global config file
that they are talking about on the other config thread
helps us make a random package integrate.
I mean David D. has dozens of packages sitting in his subdirectories.
Does someone have to go in and rework those by hand to convert
them over to global database? Who will rework every new version of
a program as they are released in a never ending torrent?
Third, we've taken a massive step backwards when we didn't
implement a web based module configurator, like Cinege did,
for preconfig.
Absolutely, as was Coyote's sloppy that I have a copy of GPL'ed.
In regards of this being used on Linux, Win32, Mac, BeOS, Solaris,
<whatever> desktops; how do you suggest this be implemented
(ie.. tunneled, local disk, web-http, *.exe, *.sh, etc.....)?
The easiest cross platform module configurator application would
be a Java application, requiring the user to have a Java JRE
installed.
Doing this with a Java application is much better than doing
this using a web client and server cgi-scripts, because of
the load put on the server and trying to get images back and
forth, etc, like you mentioned below.
The other fellow said they are writing one for LINCE.
Steal theirs or write our own. I can do it.
I see this to work acceptably if a CD image was provided with
_everything_ on it, including the 'preconfig' script and tools for
making a floppy, cd, or HD image. Anybody want to make one?
Good idea. My java app idea would take the creation
of a standardized global-config file. That's much easier
to parse as suggested. Given that, I can write the app in
a week or two.
And finally, I don't want to presume what people need to deploy,
in terms of # of nics, type of nics, dhcp or not, etc. I just
want to make it easier. That's why I say *preconfig* is a better
task until 1 & 2 get done.
Excellent point. This has also been discussed before around a year
ago. Why not integrate the configuration system into the pre-config
system? I see both as being desired, but a pre-config _should_ depend
in part on system-config.
Don't bite off so much because it's too complicated to
make it all come together. Do two simple things, make
a standard global file for [1] and deploy a pre-config
java app. That proves the concept, makes life instantly
useful to people upgrading to CF/newer Bering, and gives
people time to work on making the whole system remotely
administerable. There's 100's of packages, that's my point.
Gives time to get feedback on Java app.
Best,
Matt
[1] /boot/etc/modules
/etc/modules
/etc/network/interfaces
/etc/resolv.conf
... and more?
-------------------------------------------------------
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
