Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPLrYEQGNHdwdJyQ5=XY=G-4qyePUwAkHpzr1kxig_bscTv2-w@mail.gmail.com>
Date: Sun, 10 Jun 2012 20:38:57 +0200
From: Daniel Cegiełka <daniel.cegielka@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Re: Vision for new platform

>> Do we have some conclusions? systemd+udev is resource hungry, so the
>> question is, what next? Do we have to think about preparing a new
>> solution?
>
> The problem with systemd is that it is not only bloated
> all-in-pid-number-1 thing that depends on dbus, it *comes* from
> freedesktop, which reputation is not so good at software engineering.
> And udev is going to be merged with that codebase.
> And important thing: not to repeat already repeated mistakes.

I understand that and instead systemd I prefer to stay with
sysvinit+openrc... but the only solution is to prepare a new init
stuff from scratch (systemd+udev+dbus alternative). Do you see another
solution?

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.