Live data from Hacker News

CentOS 7 released on x86_64

lists.centos.org

51–60 of 123 posts

Re: CentOS 7 released on x86_64

#51
post #4

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…

Er 'low port' should be 'high port', ahem.

Re: CentOS 7 released on x86_64

#52
post #48
post #37

Earlier quoted context omitted.

1) Lennart Poettering 2) MAH FREEDOMS! There are technical reasons people don't like systemd that are valid, but usually the die hard anti-systemd people boil down to hating Lennart Poettering and complaining about how the US Constitution must some where say they never have to use systemd. There are some valid concerns (big scope, bloat, feature creep, etc) but they really haven't come to fruition, although are still…

Does "years of fucking with PulseAudio problems" count as its own item, or is that a subset of item 1?

s/pulseaudio/linux/

does that suck too?

Re: CentOS 7 released on x86_64

#53
post #31

Earlier quoted context omitted.

>Oh, an embedded HTTP server is loaded to read them. QR codes are served, as well. And outright falsehoods. systemd-journald-gatewayd is entirely optional. People keep harping on a packaging mistake when it was first pushed to Fedora for testing, but repeating it so many times doesn't make it true. >In fact, udev merged with systemd a long time ago systemd relies on udev and dbus, but udev doesn't pull in systemd as…

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…

From your [2]: Like for the kernel, there are options to fin-grain control systemd's logging behaviour; just do not use the generic term "debug" which is a convenience shortcut for the kernel AND the Base OS.

[2]: https://bugs.freedesktop.org/show_bug.cgi?id=76935

Re: CentOS 7 released on x86_64

#54

I always scare of CentOS/Fedora. Whenever I updated something, it will be very old packages. Leading to use 3rd repo, and without any kind of document, the next sysadmin will be in trouble. I used to install Gearman on Centos 5.9 and it was a nightmare: the original 3rd repo didn't have gearman and I have to use other repo which is complain about PHP-Common conflicting. Remi and webtactic did help at the end. It's ha…

Perhaps it's what you're familiar with and the intended use case. I personally can't stand the way APT won't let you override certain behavior. RHEL / CentOS have always favored stability over being bleeding-edge, and in my experience EPEL provides enough newer software to make the system usable for most cases, although if you're wanting the latest frameworks, etc.. I can see that being incompatible with your needs.…

I think the third-party frameworks issue can be solved with LXC / Docker. If app x requires library y and supporting utility z, this can all be put into a container without having to update the OS's versions of y and z.

Re: CentOS 7 released on x86_64

#55

Earlier quoted context omitted.

There are quite a few choices of lightweight Linux distro. This isn't aimed at that market

Oh, I know, but I've been happily using CentOS 6 on my 128MB box, and was looking forward to CentOS 7.

> I've been happily using CentOS 6 on my 128MB box

I used to do that too, but then I figured there's a constructive use I could give to my old desktops when any such system reaches the age of replacement - just max it out on RAM and declare it a "home server". Now I can run a Minecraft node for my kids on it - with 2GB of Java heap, no less.

I mean, my Raspberry Pi has more than 128 MB of RAM.

Lots of RAM - like chicken soup for your server.

Re: CentOS 7 released on x86_64

#56

I've never used RHEL. It doesn't seem prohibitively expensive. What advantages are there over Centos, other than support?

They'll prioritize fixing your bugs with their product management team, but that is basically support. You pay for RHEL for support, that is all it ever was for.

The code is 100% open source.

Re: CentOS 7 released on x86_64

#57

Earlier quoted context omitted.

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?

Linux did kind of get the short end of the stick with System V initialization. BSD rc scripts are also written in shell, but much cleaner (particularly when you make use of rcorder(8) dependencies). systemd's declarative unit file syntax is easier to reason with, but comes at the expense of having to memorize a ton of options and being fundamentally dependent on the toolbox provided to you by systemd, since you can't…

FWIW, systemd can also call scripts under /etc/init.d if that is really what floats your boat. It is fully backwards compatible, you just lose a lot of the flexibility of systemd when doing that. The redis-server package in RHEL7 (from EPEL) installs an init script and I know that systemctl starts it.

Re: CentOS 7 released on x86_64

#58
post #50
post #48

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.

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.

Re: CentOS 7 released on x86_64

#59
post #58
post #50

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.

Haven't had issues across multiple systems, even back when it first came out.
Post reply on HN