bkor

86 ms·

871.
by bkor 13y ago
I block ads, but I have a subscription on LWN. Probably would have done the same on h-online if their comment section would be a bit more integrated. I've been reading this site for various years, the reporting is pretty good.
872.
by bkor 13y ago
Suggest to read the previous articles by this Debian person (a comment on HN linked to the other ones). He wrote a document explaining that systemd is different daemons, utilities, etc. Further, some stuff is only done after forking (minimi
873.
by bkor 13y ago
Suggest to change the way you word things. For one, your post is attacking people indirectly by suggesting that systemd people are absurd and their idea is a cancer and that there is no need to change at all. That is what I see as the main
874.
by bkor 13y ago
Change happens by people doing work. There are at least 3 people actively working on systemd support. Meaning: they help out other packagers, file bugs, look at bugreports, coordinate with upstream, etc. For OpenRC, there is just one person
875.
by bkor 13y ago
Initscripts are specific to one distribution. A bug in an initscript in one distribution is not fixed in another distribution. This is practical real life example that has happened for 10+ years. With systemd, there is just a configuration
876.
by bkor 13y ago
You realistically expect BSD to ever use a GPL licensed init system? I don't see the point of systemd being able to run under BSD. BSD wants to get rid of every GPL licensed software, including GCC. You really expect them to consider s
877.
by bkor 13y ago
Try doing that reliably with loads of workers and cgi scripts. Maybe possible at one point, but systemd does that reliably by default.
878.
by bkor 13y ago
systemd contains a lot of different bits, each with a different task. Much like e.g. coreutils. Coreutils contains a lot of different utilities. If systemd is somehow bad for Linux, coreutils is as well.
879.
by bkor 13y ago
Loads of sysvinit scripts are distribution specific. With systemd, these are now shipped upstream. No clue what your problem is, but there are loads of benefits to systemd, suggest to try it out (and then recent version, not some old Fedora
880.
by bkor 13y ago
systemd supports /usr just fine. It is the other software that is broken. The systemd package on Gentoo was packaged wrongly, which made people think that the problem lied with systemd, not that is said that other software is broken. T
881.
by bkor 13y ago
systemd is not something that is intentionally put up to prevent Hurd or FreeBSD from being popular. When I asked about the Hurd of FreeBSD versions of Debian, it seems that stuff has to compile against it. Every Debian maintainer has to al
882.
by bkor 13y ago
systemd also logs stderr + stdout, so if some daemon fails to start up, you can easily see it in 'service $SERVICE status'. A lot of things could theoretically be done by putting that all in a sysvinit script. That means duplicati
883.
by bkor 13y ago
In practice, Gtk+ will have to deprecate a few things to better support Wayland. See https://wiki.gnome.org/Wayland/GTK%2B and https://wiki.gnome.org/Wayland/Gaps . Mir and Wayland seem to be prett
884.
by bkor 13y ago
So how would the Gtk+ developers be able to ensure that it works under Mir? Mir is distribution specific. Same for an application running under Mir. It creates lots of extra work for people who do not run Ubuntu. It will result in extra bug
885.
by bkor 13y ago
The focus within Mir is Unity, not anything else. Wayland wants to work with every desktop environment. Further in Mir they did not give a stability agreement, Wayland has. Software modularity is overrated, but in this case I think you got
886.
by bkor 13y ago
Unity was designed at the same hackfest that GNOME shell was discussed. However, the discussion of GNOME shell was in the open, Unity was secret. Note that Wayland is available in Fedora, Mageia, opensuse, etc.
887.
by bkor 13y ago
Wayland developers had to fix all kinds of things elsewere. The development is not slow. One of the Mir developers attributed the quicker speed of Mir to the work that the Wayland developers did. Further, a lot of stuff in Mir is copied&#x2
888.
by bkor 13y ago
Actually GNOME shell has a Wayland compositor for around as much time as when Mir was initiated (not when it was announced). The future was also clear. Whatever reason Canonical had to start Mir, it is not related to Wayland.
889.
by bkor 13y ago
When Mir was announed, Wayland was already past 1.0. About 60% of the GNOME applications currently run under Wayland. See https://live.gnome.org/Wayland/Applications . Note that Mir requires the exact same stuff. Just t
890.
by bkor 13y ago
That was working on Wayland before it was working on Mir.
891.
by bkor 13y ago
A lot of the Wayland developers are X developers. It basically is X12, just that calling it X results in a lot of unneeded steps (loads of people will have a say into the spec, etc). Daniel Stone explained this in a video.
892.
by bkor 13y ago
Wayland had Android driver support before Mir. Mir actually uses the same thing as wayland (libhybris or something).
893.
by bkor 13y ago
That's called client side window drawing and GTK has it. Needed for Wayland. Maybe good to investigate a little bit before saying things that aren't true.
894.
by bkor 13y ago
Nope, that is changing the wording to suit yourself. He started the project and is able to work full time on this. A Mageia packager contributed some very good patches towards systemd. He's not in the email on debian-devel, while he monitor
895.
by bkor 13y ago
Another layer of abstraction just results in more complicated code, more bugs, more difficulty testing the different code paths. Might be fine for a lot of projects, but this is just something to boot up your system.
896.
by bkor 13y ago
BSD doesn't support a bunch of stuff. How would you deal with that concretely. How would you ensure that all those different code paths are tested?
897.
by bkor 13y ago
Do you really think BSD would replace their init system with something not BSD licensed? Seems like a pointless exercise to slow down progress just for theoretical usecase.
898.
by bkor 13y ago
systemd can boot quite a bit faster than just 5 seconds. In any case, do you have any specific complaints? Your post is pretty long but lacks specifics.
899.
by bkor 13y ago
I didn't mean the openldap config. Sometimes the daemon just plainly does not start. You basically have to resort to using strace to figure out what is wrong with the thing. Systemd redirects stderr and stdout, highly useful IMO. Openldap g
900.
by bkor 13y ago
Just because I pointed out flaws in your arguments doesn't make it ok to respond like this. Please refute what I said based on clear references and without name calling such as "insanities". E.g. you said: "forced": prove it. Also, you didn

More ›