[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: System Modules for Control Centre
From:       Dik Takken <D.H.J.Takken () phys ! uu ! nl>
Date:       2003-06-21 15:20:08
[Download RAW message or body]


\begin{quote}

You could try to handle that with distro / OS profiles that contain the
locations of those files. But you would also have to consider
distro and/or application *version numbers* because those things
tend to change from time to time.  This would require quite a few
maintenance work on top of the actual coding.

But there's something else:  The professional admins I know
tend to write/adapt their own init.d/* scripts so these new
modules should also be customisable and be able
to use the logic in the shell scripts.
BTW, they're not too fond of graphical tools anyway.
But that's a different matter ;-)

And you're absolutely correct, this is the classic area
where distro makers put their effort, so almost every distro has its
own incompatible set of config tools.  The question that'll come up
immediately is whether the KCC module plays together with those
tools (e.g. they can be used interchangeably and don't overwrite
each others' changes)

\end{quote}

I was actually thinking about 'home-sys-admins' like myself. Of course,
professional Linux Admins use pico/VI, but Linux newbies need easy to use
tools to manage their Linux box. Indeed, most tools provided by the distro
don't work with other distro's, and no single distro provides graphical
tools for all common tasks. It's still not possible to do certain things
without having to use command-line tools.

A graphical system administration tool should not do anything
distribution-specific, but invoke distro-specific bash scripts for
example. Just supply one set of scripts for each distro and you-re done.
The KDE part can be developed seperately.

Dik
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]