61–70 of 102 posts
Earlier quoted context omitted.
No. Why would you want to? Upstart is inferior to systemd in every way and if Fedora supported both then it would have to test every package that contained a daemon twice.
Because upstart is easy and systemd is difficult.
systemd is not hard, it's just different. Those configuration files are a lot easier to generate and get working correctly.
Earlier quoted context omitted.
Because upstart is easy and systemd is difficult.
Removing upstart is a feature. systemd is not hard, it's just different. Those configuration files are a lot easier to generate and get working correctly .
It just baffles me whenever I look at it.
Earlier quoted context omitted.
Of course, I am nobody to criticize the sacred things, so there are few links to the people who are worth of paying attention to (and who gave us golang). http://harmful.cat-v.org/software/java http://harmful.cat-v.org/software/OO_programming
So with a handful of out of context citations and some rather retarded points of view (Greenspun WTF?) you are trying to convince people? Really? At least give it _some_ effort. This way it is rather boring...
Seeing the removal of syslogd, getting more than a bit grumpy here at the continuing direction Redhat is dragging the Linux world. Journald may serve the basic user well, it can't do half the stuff a good syslogd configuration can do; it can't pipe messages to other processes, it can't send messages to remote servers, it can't send messages to multiple places. If redhat had put in services to let journald do the thin…
One needs to look no further than what their plans for cgroups are to see the future. Not to mention the plans to get rid of /bin/login and VTs.
Earlier quoted context omitted.
Removing upstart is a feature. systemd is not hard, it's just different. Those configuration files are a lot easier to generate and get working correctly .
As a user, I can't tell what service is started when by which config file and where it should go. multi-user.target.wants? default.target.wants? Why are there windows-style .ini files and why are they all symlinks to /usr? Is it forbidden to make changes now? Really, RedHat? It just baffles me whenever I look at it.
Anyone has succeeded dual botting Fedora 20 with Windows 8.1 in a UEFI system with secure boot?
When I tried the beta it made Windows 8.1 unbootable.
"Syslog removed from default installation" and "Users accustomed to checking /var/log/messages for system logs should instead use journalctl." I'm sure I'm going to forget about that... I can't wait for the first WTF :)
It's quite an audacious release note. As if millions of users are suddenly going to forget about cat, head, tail, more, less, grep, awk, sed, fmt, etc. etc. that are only still useful if you learn how to journalctl and convert those binary logs back into plain text. I'd like to install Fedora 20 and use it as my main desktop, but both systemd and journald will somehow have to be avoided and worked around because I do…
Seeing the removal of syslogd, getting more than a bit grumpy here at the continuing direction Redhat is dragging the Linux world. Journald may serve the basic user well, it can't do half the stuff a good syslogd configuration can do; it can't pipe messages to other processes, it can't send messages to remote servers, it can't send messages to multiple places. If redhat had put in services to let journald do the thin…
It's an obvious power play by RedHat to force people to use SystemD which is nearly liblinux at this point. As the project subsumes other projects and adds more and more functions that directly rely on SystemD you'll be harder and harder pressed to run a system without it. One needs to look no further than what their plans for cgroups are to see the future. Not to mention the plans to get rid of /bin/login and VTs.
Anyway, your entire complaint is explained at every systemd presentation. The maintainers want to have something which can be used as the basic building block for Linux. Various other projects now rely on that.
So systemd is successful, but surely it is a conspiracy! hahaha
Earlier quoted context omitted.
I don't think the fragmentation claim stands up to scrutiny. It's so far been adopted by redhat, suse, arch, coreos and with some consideration by debian. The only big name not thinking about it is Ubuntu. I don't think that many of the journald drivers could have been solved by better syslogd configuration, for example journald cryptographically signs each log entry. Even if you get root on my box, you can't edit an…
Think bigger than Linux. Think those with freebsd boxes, netbsd boxes, solaris boxes, etc. They're all very much relevant, but left out in the cold by deliberate decisions of the systemd folks to eschew compatibility. Functionality-wise, journald has no way of acting on the messages it receives. With syslogd, it's fairly trivial to write a script that will send a nagios alert every time a service is restarted, for ex…
I don't get what you're complaining about, the fragmentation has been reduced :P
Earlier quoted context omitted.
I had similar sentiments when Arch made the move to systemd but I think I've come to like it. Things seem to be a lot more stable than with initscripts.
For me it looks like a fix for what wasn't broken. I think that the only reason to re-write something that is good-enough is to make it even simpler, more clear and, in some rare situations, more general (but what could be more general than text files and pipes?) Imagines someone in physics would say "this equation is not clever-enough, it lacks linear algebra, let's rewrite it using vector notation". Guys in physics…
Cool that you didn't run into the various issues that systemd makes easy. But various others have. Suggest giving it a try.