jim at winonacotter.org
Wed May 3 14:54:03 UTC 2006
> Along the lines of what Jim said below....I have some ideas.
> I can see essentially 3 or 4 (or 5) installation options for folks
> depending on their network setup....
This is sort of what I am thinking about. However I have a little different
take I believe on when to install it. Installs are already cluttered up with
options, and many users do not know what they want to do on initial
install..especially new users. I would like to see a "Configure Your Server"
app that can be called on at any time after installation. I say clear the
LTSP stuff completely from the Fedora installer. Just keep basics that make
it so you don't have to know crap to get it installed and show you a gui.
Then make it so the root user when logged in automatically gets the "Configure
Your Server" menu. This menu can have the checkbox for "don't show on
startup" and some instructions after checking it that say where to go in the
menu to find it later. Then this could be a dual paned menu app that had the
categories like for Application Server, Directory/Samba Server, LTSP Server,
DHCP Server, Home Directory Server, etc on the left. Then when the category
on the left is selected a wizard for configuration of that category appears on
the right. And give the many pieces that LTSP needs to work the wizard for
LTSP would ask "will this be the home directory server or would you like to
mount an existing one?", or "will this be the networks dhcp server or should I
use an existing one?", or "will this server be the Master Directory Server or
will this be a Sub Directory Server?" and if a Sub Directory Server is chosen,
ask the IP of the Master Directory server, or "will this be a single or
multiple NIC install?. You get the point. You could even put things under
the DHCP, Home Directory, and Directory Server sections that say "if you are
going to run an LTSP server, please configure these services in the LTSP
server section. And maybe even some failsafes that grey out these menu
choices if LTSP Server has already been configured to keep users from hosing
up the LTSP configuration.
I think this sort of tool is exactly what would be needed to get into larger
networks and really kick Windows/OSX out of the picture.
I would love to help design how this should look. I have zero knowledge on
the scripting/coding to achieve such a thing, but have enough interaction with
users that I think I know what would be needed.
This message has been scanned for viruses and
dangerous content by the Cotter Technology
Department, and is believed to be clean.
More information about the education