Am 13.08.2014 um 21:05 schrieb Cristian Rodríguez:
El 13/08/14 a las #4, Tomas Cech escribió:
https://connect.opensuse.org/pg/polls/read/sleep_walker/45294/do-we-want-to-...
To whoever thinks this is a good idea (it is not)
I agree that this is not a good idea, but your questions are too funny (and too easy to answer) for me to skip the fun :-)
could you kindly answer the following questions ?
- What you will use to replace logind ? (and who is going to maintain that replacement...)
busybox
- What you will use when udev stops working without systemd ?
mdev
- What you will use as a cgroup writer process ? (google: "single cgroup writer")
Build a kernel with CONFIG_CGROUPS=n
- How you will convince various upstreams including but not limited to several freedesktop key components, plasma on wayland, gnome-session (?) to accept all the needed code that this effort necessarily entails ?
Well, probably it would be possible to just build *BSD userspace. There must be some software that runs without systemd. There are operating systems that do not use systemd :-) XFCE runs on BSD, so it is not necessary to have systemd for it to work.
- In the future.. what you will use to replace ..let's say.. avahi (aka. systemd-resolved) ?
I never had a use for avahi anyway, I am certainly not going to miss it.
I can use the rest of the evening writing a longer list of questions and detailing why this is a DOA idea for which you will find no support where it matters but I will just leave it there.
I could spend the rest of the evening writing "busybox" as an answer :-P
- "The journal is slow and uses X,Y amount of CPU and RAM" (this is a known, multi-faced problem that some people have reported that needs to be fixed)
This is my favorite bug, waiting for a solution since the first incantation of journald arrived. Now we have binary logs with abysmal performance and no program to read them. Too bad. :-) No matter how badly my mahchines crashed and how corrupted my /var/log/messages was, but there was always the possibility to skip over the bad spot in the logfile and read the messages before and / or after. The problem is: right now the forwarding to syslog-ng is broken again (even though the syslog-ng package did not change), so there is no reliable log at all on factory. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org