From: orc <orc@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: Re: Vision for new platform
Date: Mon, 11 Jun 2012 02:58:13 +0800 [thread overview]
Message-ID: <20120611025813.282434d1@sibserver.ru> (raw)
In-Reply-To: <CAPLrYEQGNHdwdJyQ5=XY=G-4qyePUwAkHpzr1kxig_bscTv2-w@mail.gmail.com>
On Sun, 10 Jun 2012 20:38:57 +0200
Daniel Cegiełka <daniel.cegielka@gmail.com> wrote:
> >> 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?
Maybe new init stuff, maybe daemon that will control other daemons and
get launched from inittab for example.
I'm just trying to warn that this must not be a second systemd and
that's all. Sure that adequate non-bloated alternative should exist.
Maybe it should be developed as a part of new platform that we
all want to have, because as an alternative alone it will not be
accepted well.
next prev parent reply other threads:[~2012-06-10 18:58 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 1:06 Rich Felker
2012-05-18 3:11 ` Isaac Dunham
2012-05-18 3:26 ` Rich Felker
2012-05-19 1:28 ` Isaac Dunham
2012-05-18 6:07 ` Szabolcs Nagy
2012-05-21 20:05 ` aep
2012-05-21 20:17 ` Rich Felker
2012-05-21 20:51 ` nwmcsween
2012-05-21 20:59 ` Rich Felker
2012-05-21 21:18 ` Rich Felker
2012-05-21 21:51 ` aep
2012-05-21 22:25 ` Rich Felker
2012-05-22 0:53 ` aep
2012-05-22 1:54 ` Rich Felker
2012-05-22 12:55 ` Christoph Lohmann
2012-06-09 11:27 ` orc
2012-06-09 14:44 ` Isaac Dunham
2012-06-09 15:25 ` orc
2012-06-09 21:24 ` Rich Felker
2012-06-09 22:38 ` Christian Neukirchen
2012-06-10 12:53 ` Daniel Cegiełka
2012-06-10 13:22 ` Rich Felker
2012-06-10 14:52 ` orc
2012-06-10 14:55 ` orc
2012-06-10 15:13 ` Rich Felker
2012-06-10 15:51 ` orc
2012-06-10 16:33 ` Rich Felker
2012-06-10 17:53 ` orc
2012-06-10 18:03 ` Daniel Cegiełka
2012-06-10 18:26 ` orc
2012-06-10 18:38 ` Daniel Cegiełka
2012-06-10 18:58 ` orc [this message]
2012-06-10 19:19 ` Daniel Cegiełka
2012-06-10 19:33 ` Rich Felker
2012-06-10 20:13 ` Daniel Cegiełka
2012-06-11 7:24 ` orc
2012-06-11 12:54 ` Init system (Re: [musl] Re: Vision for new platform) aep
2012-06-12 0:59 ` Re: Vision for new platform Isaac Dunham
2012-06-12 1:48 ` Rich Felker
2012-06-12 5:37 ` idunham
2012-06-12 5:48 ` Kurt H Maier
2012-06-12 8:20 ` aep
2012-06-12 14:32 ` Rich Felker
2012-06-14 4:28 ` Isaac Dunham
2012-06-12 14:30 ` Rich Felker
2012-06-12 7:46 ` orc
2012-06-12 8:27 ` nwmcsween
2012-06-12 8:41 ` orc
2012-06-12 8:44 ` aep
2012-06-12 9:02 ` orc
2012-06-12 10:28 ` aep
2012-06-12 10:33 ` orc
2012-06-10 15:17 ` Daniel Cegiełka
2012-06-10 15:27 ` Rich Felker
2012-06-10 15:12 ` Jeremy Huntwork
2012-06-10 18:03 ` Kurt H Maier
2012-06-10 18:15 ` Jeremy Huntwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120611025813.282434d1@sibserver.ru \
--to=orc@sibserver.ru \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).