Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CentOS 7 released on x86_64

lists.centos.org

Post reply on HN
Print view View original

111–120 of 123 posts

Re: CentOS 7 released on x86_64

#111

Post by mprovost »

vezzy-fnord wrote: post #23
netcraft wrote: post #17

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…

Slackware has always used BSD init scripts and it's one of the oldest distros. You used to be able to choose any init system you wanted but it seems that systemd is becoming entwined with "Linux" in some nasty ways. I wonder how long Slackware (or any other distro) will be able to avoid using it since software like Gnome is starting to require it.

Re: CentOS 7 released on x86_64

#112

Post by mackal »

beedogs wrote: post #74
mackal wrote: post #50

Earlier quoted context omitted.

I've never had issues with PulseAudio personally.

...said no one ever. The very first thing I used to do on any new Linux install (until most distros stopped including it) was to uninstall Pulse and all of its dependencies.

I did.

Re: CentOS 7 released on x86_64

#113

Post by jrslack »

ck2 wrote: post #72
nailer wrote: 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…

How do you do "configtest" and "graceful" with systemd/systemctl (trick question, you cannot, use old init.d scripts)

>trick question, you cannot

  [Unit]
  Description=The Apache HTTP Server
  After=remote-fs.target nss-lookup.target
  [Service]
  Type=notify
  EnvironmentFile=/etc/sysconfig/httpd
  ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
  ExecReload=/usr/sbin/httpd $OPTIONS -k graceful
  ExecStop=/usr/sbin/httpd $OPTIONS -k graceful-stop
  KillSignal=SIGCONT
  PrivateTmp=true
  [Install]
  WantedBy=multi-user.target
and 'apachectl configtest' or 'nginx -t' iirc

Re: CentOS 7 released on x86_64

#114

Post by sciurus »

heroprotagonist wrote: post #107
kureikain wrote: post #43

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…

Besides using third party repos, you can also use Red Hat Software Collections for the official Red Hat offering of more recent packages (requires RHN, not available for CentOS). https://access.redhat.com/documentation/en-US/Red_Hat_Softwa... As another approach to mitigating dependency hell, you might consider using Docker containers for your services.

Software Collections are available for CentOS.

http://wiki.centos.org/AdditionalResources/Repositories/SCL

Re: CentOS 7 released on x86_64

#115

Post by jrslack »

keeperofdakeys wrote: post #82
netcraft wrote: post #17

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?

Systemd isn't just replacing the init process and service manager, it encompasses many other boot and session related features. As an example, Gnome now uses parts of systemd for session management (replacing consoleskit, and others). While there are workarounds, this means no one can really use any other init system besides systemd, or things won't work correctly. This is what many people view un-unix like, a big de…

>though they view that they should be the only user of cgroups

And they're absolutely correct. There can only be one cgroups manager on the system. cgmanager isn't finished, either.

>As an example, Gnome now uses parts of systemd for session management (replacing consoleskit, and others). While there are workarounds, this means no one can really use any other init system besides systemd, or things won't work correctly.

Gnome requires logind, which is the successor to consolekit. Gnome has repeatedly stated that they're willing to work with the BSDs et al with workarounds. You can either use the old logind, which doesn't require systemd as PID1 (due to cgroups management changes) or you can develop your own replacement to logind, one that doesn't require systemd as PID1.

People criticize these decisions, but they have no suggestions on how to fix it and, for the most part, they have no inkling of why there's a requirement.

Re: CentOS 7 released on x86_64

#116

Post by michaelmike »

beedogs wrote: post #74
mackal wrote: post #50

Earlier quoted context omitted.

I've never had issues with PulseAudio personally.

...said no one ever. The very first thing I used to do on any new Linux install (until most distros stopped including it) was to uninstall Pulse and all of its dependencies.

I still uninstall it, even though I know it's improved a bit. I just can't get to the point of trusting it, or see the point for yet another layer of latency and bugs between programs generating audio and the sound card. They should have spent all that effort making a nice interface to dmix or something. Rather than bash ALSA for being "Linux only", then turn around and create systemd which is Linux only by design. I mean, we get it. You're the next Miguel de Icaza. The savior of Linux, coming to save us from the terror of text files, open standards, and clean dependencies. People must be forgetting the hell that was CORBA and Linux circa 2001 or so. You still can't install many apps without installing half of GNOME.

Re: CentOS 7 released on x86_64

#118

Post by scurvy »

tacticus wrote: post #88
scurvy wrote: post #83

Earlier quoted context omitted.

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.

GPT labelled disks don't have a limit on the number of primary partitions

Nice! Didn't know that.

Re: CentOS 7 released on x86_64

#119

Post by frio »

ck2 wrote: post #72
nailer wrote: 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…

How do you do "configtest" and "graceful" with systemd/systemctl (trick question, you cannot, use old init.d scripts)

Why would I do a `configtest` with a thing that starts or stops a service in the first place? That's what `apachectl configtest` or whatever is for.

I wouldn't expect to go to Windows' list of services, right click one and run arbitrary commands either.

Post reply on HN