[...]SysV init needed a replacement. And systemd can be that and much more. But your refusal to help make the transition easier, I consider laziness. You don't want to be bothered with a method of handling no cgroups. Debian's systemd-shim interface is filled with bugs (you're not directly responsible for that, but I blame you for its design). You do come across as arrogant and the my-way-or-the-highway approach is what is pissing so many people off. One thing I've learned from working in Open Source community for the last 16 years, is that people that say they know better than everyone else are the ones that are not treated well by the community. But those that are willing to collaborate, and listen to others before pushing their own methods are welcomed with open arms.[...]
duncangareth wrote:Apropos of systemd's documentation, I do not find it very helpful.
I think the developers of systemd need to read up on that which distinguishes UNIX and UNIX-derived systems like Linux distros from proprietary systems:
http://www.linfo.org/unix_philosophy.html
systemd is monolithic and obscure. Surely Mageia can do better!
syschuck wrote:So here is how you improve systemd. Dump the binary logs (it's not needed). Start the Virtual terminals early in the boot cycle. Enable some meaningful debugging (debug consoles?) If a daemon is waiting for a socket, I would like to know that it's waiting for a socket. When it's booting and going through it check lists, I would be nice to know if it's kernel related, daemon related, or application related. Allow of the boot to be interrupted. And document how systemd can be manipulated through the kernels startup command line.
syschuck wrote:I couldn't even find the system logs, not on the master nor on the leaf nodes.
I see no advantage to using 'journalctl' over 'cat'. Is there an equivalent to 'tail -f' ? Please tell me in journalctl speak.
OPTIONS
...
-f, --follow
Show only the most recent journal entries, and continuously print
new entries as they are appended to the journal.
martinw wrote:Note also that you don't have to use the journald service, you can install and use one of the old syslog packages, as mentioned in the /var/log/README file (admittedly I've not tried this myself, so can't vouch for whether it works in Mageia).
syschuck wrote:The second thing that got me was how the virtual terminals are activated at the very end of start-up.
If a daemon is waiting for a socket, I would like to know that it's waiting for a socket.
When it's booting and going through it check lists, I would be nice to know if it's kernel related, daemon related, or application related.
[Unit]
Description=Root Slice
Documentation=man:systemd.special(7)
DefaultDependencies=no
Before=slices.target
doktor5000 wrote:If you think Mageia can do better, feel free to send patches and take maintenance and development for whatever alternative you propose.
$ cd /usr/lib/systemd/system
grep Documenation *
grep: invalid option -- '.'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
MadmanRB wrote:another systemd topic, I hate these things.
Dont like systemd use slackware.
jiml8 wrote:MadmanRB wrote:another systemd topic, I hate these things.
Dont like systemd use slackware.
That comment is about as worthless as they come.
MadmanRB wrote:These systemd debates are the plague.
doktor5000 wrote:MadmanRB wrote:These systemd debates are the plague.
Yes they are - and you make that point even more valid.
doktor5000 wrote:And how do your posts in this thread help with this?
If you don't like systemd, then for gods sake keep using Slackware if that makes you happy. But don't bother others that are happy with it.
syschuck wrote:Directories. All of the startup is located in /usr/lib/systemd. [...]
And that is an improvement over init.d how? So if I add my own .service .target or whatever, it needs to be duplicated in multiple locations.
Second gripe; The filenames and directories don't make any sense and are not intuitive.
Here is another brain dead filename in systemd. -.slice!
MadmanRB wrote:No I dont care one way or the other with systemd, I am more sick of the debates then systemd itself.
I personally dont mind systemd
doktor5000 wrote:MadmanRB wrote:No I dont care one way or the other with systemd, I am more sick of the debates then systemd itself.
I personally dont mind systemd
You are sick of the debates, yet you still continue to feed them - so what's your point?
/usr This directory is usually mounted from a separate partition. It should hold only sharable, read-only data, so that it can be mounted by various machines running Linux.
dbus.ini cpupower.ini chronyd.ini cups.ini httpd.ini freshclam.ini saslauthd.ini
syschuck wrote:However, I think there is enough of a backlash to it, that people need to hear both sides of the debate.
Return to General discussions about Mageia
Users browsing this forum: No registered users and 1 guest