81–90 of 123 posts
I can learn to adjust to systemd But wow I cannot stand grub2, what a mess.
Woo. Have been using the RHEL 7 Amazon AMI images, and it's nice not to worry about shell scripts / custom supervisord stuff for your web services anymore. My node app is deployed with a single `myapp.service` file thanks to systemd: [Service] ExecStart=/usr/local/bin/node --harmony /var/www/myapp/server.js Restart=always User=nobody Group=nobody Environment=PATH=/usr/bin:/usr/local/bin Environment=NODE_ENV=productio…
that looks so much cleaner than init.d scripts. I have heard some people refer to systemd as not very linux-esque - can someone comment on what that might mean?
This is what many people view un-unix like, a big dependency, that can't be replaced in the chain. The systemd developers also develop udev (which actually builds out of the same source tree as systemd), and there have been a few arguments about whether certain responsibilities are that of the kernel, or udev/userspace http://lwn.net/Articles/518942/, http://lwn.net/Articles/593676/. Systemd also touts its cgroup usage, though they view that they should be the only user of cgroups, since they are in a spot to "manage things properly" (which is partially true). (Some services have also started relying on systemd's cgroups to clean up orphan processes, which is bad for other init systems that don't do this).
So no one really hates how systemd works, just how its managed, and what it aims to do. If it were a simple init system and service manager, there would probably have been no arguments.
I can learn to adjust to systemd But wow I cannot stand grub2, what a mess.
CentOS 6 only required biosdevname=0
Earlier quoted context omitted.
I'd be very interested to see a qualified crypto expert on the "sealing" that journald uses. This is one of two indicators of a troubling level of arrogance from the developers. The crypto method used by journald to verify messages haven't been tampered with is called Forward Secure Sealing [0]. It's based on an invention of the brother of Lennart - the lead developer, and for a long time after first release even the…
I just can't agree with your [2] as a problem. The actual problem (an assertion failure in systemd) was fixed, several alternative workarounds are provided in case the user can't or doesn't want to upgrade systemd immediately, and functionality changes about when and where and how to log were going on on the mailing list, as they should be, and the reporters were directed there politely, even after violent vitriolic…
Their attitudes towards journal log corruption have been rather apathetic, as well, though I cannot find the particular bug report at the moment.
Earlier quoted context omitted.
And actually being able to call redhat can be very useful once in while when you are having a really bad day.
Given that the OP said "other than support", I'll assume you mean they're actually nice and supportive when call to complain about your day :)
Earlier quoted context omitted.
I've never had issues with PulseAudio personally.
It depends what sound hardware and software you use, what the memory layout of the PulseAudio daemon happens to end up like on your system, your tolerance for audio glitches, and how long you go between reboots. The code quality's awful but if you're lucky you can miss out on the worst of the issues.
I suspect, based on how few people seem to be upset about pulse audio (as opposed to what one might expect) that some subset of popular sound hw worked rather well. It's just not a subset I ever owned.
I can learn to adjust to systemd But wow I cannot stand grub2, what a mess.
Aye, and now grub2 requires a 1MB partition to boot a GPT labelled disk on a BIOS (non-EFI) system. Well, looks like we're out of primary partitions. Adios swap.
Earlier quoted context omitted.
Does "years of fucking with PulseAudio problems" count as its own item, or is that a subset of item 1?
I've never had issues with PulseAudio personally.
Earlier quoted context omitted.
Does "years of fucking with PulseAudio problems" count as its own item, or is that a subset of item 1?
I've never had issues with PulseAudio personally.
I still don't trust Lennart, even though systemd looks nice from what i've seen.