Experiences with KDE-CVS at LinuxWorldExpo

[conhenne at gofree.indigo.ie]

On Monday 04 November 2002 15:06, Adam Treat wrote:
> > # 2 #
> > -----
> > "Fat" clients. A complete set of all programs are installed on the
> > clients. "Profiles" and home directories are on central file servers. The
> > profile is retrieved if the user logs in and decides about the subset of
> > programs the user is allowed to start and use.
>
> Ok, so you've narrowed it down to thin clients and workstations.  Does this
> GUI app work only with Linux or must it work with the *BSD's?  Is it
> responsible for the actual deployment and configuration of the non-KDE OS
> ie, does it need to configure X, kernel, printing system, network shares,
> ssh, mail server, etc, etc.  If so, then we are talking about a _huge_
> parameter space.  IMHO, the only way an app such as this could be
> successful is to narrow the scope considerably OR make choices for the
> system admin thereby limiting the situations where the tool could be used. 
> I'm really trying to understand what you are looking for ... ?
>
> I like the idea, but I fail to see how it could be executed successfully.

Maybe you should start from the position of what should already be setup and 
what needs to be added.
Also targetting this, is probably a really good idea e.g. start with smaller 
offices where there is a smaller likelyhood of experienced IT admin people.
However,. can you assume that the "server" is already setup with all the 
necessary components ( nfs, nis, firewall, dns, dhcp, printers ), by using
a vendors(SuSE/Redhat/Mandrake/etc) setup ?
After that it should be a matter of writing an app to *gather* the info
needed for client installations and "somehow" enable the clients to access
this info during installation/post-configuration.

CPH