From kde-devel  Sat Jun 21 15:01:19 2003
From: Christian Mueller <cmueller () gmx ! de>
Date: Sat, 21 Jun 2003 15:01:19 +0000
To: kde-devel
Subject: Re: System Modules for Control Centre
X-MARC-Message: https://marc.info/?l=kde-devel&m=105620783730849
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============62310886710983526=="


--===============62310886710983526==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_PNH9+Bmz2HZl6+y";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_PNH9+Bmz2HZl6+y
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

Am Sonntag, 22. Juni 2003 16:40 schrieb Philip Scott:
> Greetings,
>
> > I was wondering what work people are doing to create Control Centre
> > modules for system administration tasks that have nothing to do with KDE
> > itself, like:
> >
> > - Start/Stop system services like cups, smb, cron etc
> > - insert/remove/list kernel modules, query/set module parameters
> > - configure ssh/telnet servers
> > - configure network devices
> > - configure scripts attached to hotplug events
> > - etc
>
> I think in principle, this is a marvellous idea, but the problem is, this
> is not nearly as simple as it sounds. Every distribution keeps its
> configuration files in a slightly different place, the boot scripts being
> the least standardised. A few distribitions do make some efforts to add
> modules like these; for example redhat includes an interface to configure
> it's ftp daemon. The kernel modules stuff could certainly work, and I thi=
nk
> is a good idea - and if you can find ways of achieving the rest in a
> non-distro specific way you are brighter than me!
>
> Perhaps it is time we tried to standardise these things across the linuxe=
s.
> (And rember, kde does not have to mean linux, so these tools would be
> redundant for a few users, albeit I assume a small minority)

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

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

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

Christian.

=2D-=20
Conservative, n.:
One who admires radicals centuries after they're dead.
		-- Leo C. Rosten

--Boundary-02=_PNH9+Bmz2HZl6+y
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+9HNPdKozh3+HUO4RAsi/AKDYqxo1ZLdoDtva67JyF40Cs9pDOgCdH/Ds
rUzvjFglGlB93G21E3Medwc=
=4T+Z
-----END PGP SIGNATURE-----

--Boundary-02=_PNH9+Bmz2HZl6+y--


--===============62310886710983526==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============62310886710983526==--