4chan archive /g/ (index)
2012-11-12 01:53 29003932 Anonymous (autism_speaks.png 1600x1272 210kB)
https://www.archlinux.org/news/end-of-initscripts-support/ I'll need to move to something else then. What other distros have initscripts?

20 min later 29004323 Anonymous
>>29003932 What's wrong with systemd?

22 min later 29004369 Anonymous
>>29004323 It's not a config file like rc.conf.

23 min later 29004383 Anonymous
>>29004369 Do you edit your rc.conf all day every day?

23 min later 29004388 Anonymous (installgentoo.gif 170x113 1209kB)
>>29003932 install gentoo

23 min later 29004392 Anonymous
loled

24 min later 29004401 Anonymous
>>29003932 I will trade faster boot times and ease of use for 80mb of memory. Truly autism is what is stopping you.

24 min later 29004406 Apple
>>29004369 So?

26 min later 29004434 Anonymous
>>29004383 No. >>29004401 >Wanting things to be simple is autism. >>29004406 It makes things needlessly complex

27 min later 29004463 Apple
>>29004434 >It makes things needlessly complex How? Explain.

27 min later 29004466 Anonymous
>>29004434 Then what's your problem? Instead of shoving stuff into a list of daemons, you just run systemctl enable daemon. It's not that complicated.

28 min later 29004496 Anonymous
>>29004463 Instead of having everything in one nice simple file, they have to have multiple configs for th hostname and shit like that, and all these extra commands.

29 min later 29004511 Anonymous
>>29004496 Again, so what? It took me 5 minutes to figure out. You don't change your hostname and daemons all the time, so what's the problem?

31 min later 29004552 Anonymous
>>29004466 this, honestly. systemd is much more efficient and a hell of a lot faster >>29004496 its easier on arch than ever before, adapt or die you fucking pleb.

35 min later 29004623 Apple
>>29004496 Some of the files already existed anyway and were actually "synchronized" with the setting in rc.conf, which was retarded (for example /etc/hostname or /etc/localtime). It takes 5 minutes to make those files. There's a guide on the arch wiki for that. And then you don't edit those files so it's just one time. The only thing I was changing from time to time in rc.conf was DAEMONS array, which you do using systemctl now.

36 min later 29004655 Anonymous
I'm glad that they took out the installer and use a shittier le shit, it lets me soak up more of my worthless time. Why just the other day I finally got it all to work and had to reformat because I would have had to think about getting a job, or really just anything outside my linux video game.

37 min later 29004665 Anonymous
bsd style init scripts 4 lyfe

42 min later 29004786 Anonymous
>>29004623 It still seems pretty messy to have multiple systemctl commands instead of one DAEMONS = (daemon).

44 min later 29004816 Anonymous
>>29004655 The installer was an enormous piece of shit. The install scripts are actually a lot faster and easier.

44 min later 29004821 Anonymous
>>29004786 How? Enable enables a daemon. Disable disables a daemon. Start and stop do what you expect them to do. What's messy about it? I actually like it more. You can do everything from a console.

45 min later 29004844 Anonymous
>>29004786 you know what rc.conf didn't have? verbose output as to why a daemon failed to start. systemctl status daemon... so fucking useful.

48 min later 29004921 Anonymous
>>29004821 It's already easy to manage daemons from the command line. >>29004844 That's a fair point. I'm only bitching about startup, not interactive use.

57 min later 29005103 Anonymous
I installed Arch 2 days ago with the latest monthly CD, now that all that transitioning shit happened. The last time I installed an Arch system, was in the middle of reorganizing pacman - so I tried 3 or 4 times and yet couldn't manage to have a warning-free pacman. a lot of different pgp errors and shit, and a script to auto-add the basic pgp signatures DID NOT WORK. I had to add each of them by hand. Fucking awful. The second to last time, was even before that, so the transitions worked better actually. Anyway, my point is: I can't even think of more stuff to change, so maybe it's the end of a really turbulent year for Arch and the userbase. In the end, I think the changes were for the better. I can't express how glad I am with the faster boot, and the somewhat simpler "install" process. I liked it and it fits Arch's "build from a basic system" approach. I'm not really savvy, but I'm not afraid of the command line, and I didn't think systemd is hard compared to the .rc stuff at all.

58 min later 29005107 Apple
>>29004786 No, systemctl is much better. It's much faster to run systemctl enable daemon than to edit some file. And to know what's enabled, you can do systemctl, or ls /etc/systemd/system/multi-user.target.wants. As a bonus, systemd obsoletes a bunch of stuff, like consolekit. And service files are easier to make than rc scripts.

1 hours later 29005185 Anonymous
>>29005107 I know, I know. systemd sounds awesome for the most part, I just really liked the just werks approach to startup configuration that rc.conf provided. >And service files are easier to make than rc scripts. Example?

1 hours later 29005200 Anonymous
I liked a few things about Arch: It's ease of installation (with the old installer), the nice and easy config file (rc.conf) and It's package manager (pacman). That said I moved to debian testing since arch keeps shooting itself in the foot. Its like the community became too neurotypical for the jobless authistic neckbeards there so they decided to fuck everything.

1 hours later 29005258 Apple
>>29005185 >Example? [narf@rodentia ~]$ cat /usr/lib/systemd/system/sshd.service [Unit] Description=OpenSSH Daemon Wants=sshdgenkeys.service After=sshdgenkeys.service [Service] ExecStart=/usr/sbin/sshd -D ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=always [Install] WantedBy=multi-user.target # This service file runs an SSH daemon that forks for each incoming connection. # If you prefer to spawn on-demand daemons, use sshd.socket and sshd@.service. [narf@rodentia ~]$ cat /etc/rc.d/sshd #!/bin/bash . /etc/rc.conf . /etc/rc.d/functions . /etc/conf.d/sshd PIDFILE=/run/sshd.pid PID=$(cat $PIDFILE 2>/dev/null) if ! readlink -q /proc/$PID/exe | grep -q '^/usr/sbin/sshd'; then PID= rm $PIDFILE 2>/dev/null fi case "$1" in start) stat_busy 'Starting Secure Shell Daemon' /usr/bin/ssh-keygen -A [[ -z $PID ]] && /usr/sbin/sshd $SSHD_ARGS if [[ $? -gt 0 ]]; then stat_fail else add_daemon sshd stat_done fi ;; stop) stat_busy 'Stopping Secure Shell Daemon' [[ ! -z $PID ]] && kill $PID &> /dev/null if [[ $? -gt 0 ]]; then stat_fail else rm_daemon sshd stat_done fi ;; restart) $0 stop sleep 1 $0 start ;; *) echo "usage: $0 {start|stop|restart}" esac exit 0

1 hours later 29005428 Anonymous
>>29005258 Looks a lot more readable, honestly. How do you configure what daemons are started at boot, though? And view which ones are set to start?

1 hours later 29005573 Apple
>>29005428 >How do you configure what daemons are started at boot, though? systemctl enable/disable daemon >And view which ones are set to start? systemctl --no-pager list-units

0.758 0.078