[arch-general] My end-user $0.02 on /etc/rc.conf splitting.
Stephen E. Baker
baker.stephen.e at gmail.com
Tue Jul 24 11:53:49 EDT 2012
On 24/07/2012 11:08 AM, Leonid Isaev wrote:
> On Tue, 24 Jul 2012 16:07:50 +0200
> Heiko Baums <lists at baums-on-web.de> wrote:
>> Am Tue, 24 Jul 2012 23:40:51 +1000
>> schrieb Gaetan Bisson <bisson at archlinux.org>:
>> Yes, I don't like those Windoze like ini files of systemd, too.
> One thing I noticed is that the only people who usually bash Windows are those
> who don't develop or know very little about programming. What exactly is wrong
> with ini files and/or registry? Perhaps it is your misunderstanding...
I assure you, lots of developers, even (or maybe especially) Windows
developers bash windows. The key is not throwing the baby out with the
Ini style files are both easy to parse and easy to read - there's no
reason not to copy the format.
Certainly these systemd target files etc. are easier to read and manage
than the initscripts were.
It may take some getting use to not being able to see everything in
DAEMONS, but the benefits to the maintainers and to me if I ever need to
tweak something beyond what gets run in what order, more than offset that.
> Over time various linux projects took a lot from windows: gconf/dconf
> (~registry), KDE4 indexing services (~superfetch/desktop indexing),
> systemd-journald (~windows event viewer). This is real, get used to it.
The registry is more debatable. (Having all your config in one place is
nice, but when that one place is an inconsistent mess that can only be
managed by a mediocre special purpose tool it loses it's benefits.) I
think I would be very upset if they wanted to move rc.conf into a gconf
like interface. As is though I find it hard to complain.
I generally like Windows events except for some of the pointless make
work of registering each message ahead of time in your message.dll
(which .NET hacks around). That said I've never had any issue with
More information about the arch-general