[01:55] Every time I have to install GNU Bash for some program it makes me think: this developer could have picked any programming language, with any amount of expressivity and capability, and they picked GNU Bash? [01:57] I tend to pick bash for simple tasks. It's always installed everywhere, so I don't need to worry about it being a dependency. [02:00] I don't have it installed on anything, so I tend not to use it. [02:08] i c [02:09] i don't install bash on openbsd [02:43] *** plett_ is now known as plett [04:03] Also not installed on FreeBSD. [04:04] *** mhoran_ is now known as mhoran [04:04] i think lots of ports depend on it in freebsd? [04:05] I guess I don't have any of those ports installed. [04:05] a lot of stuff needs gmake [04:05] bloody gnu [04:05] [mhoran@friction] ~% bash [04:05] zsh: correct 'bash' to 'hash' [nyae]? n [04:05] hahaha [04:05] you don't need hash [04:05] i installed zsh on opensolaris [04:06] I also uninstall gmake every time a port installs it for build, and generally use packages so long as they don't pull X11 or something else insane. [05:04] Yeah same. Switching to packages has helped remove any GNU dependencies. [06:30] *** qbit has quit IRC (Quit: WeeChat 1.5) [06:55] *** qbit has joined #arpnetworks [09:04] *** mkb has quit IRC (Remote host closed the connection) [09:14] *** mkb has joined #arpnetworks [09:30] I've come across a number of scripts that "relied on" bash only as far as calling it in the shabang, but didn't actually utilize bash-isms, the developer just didn't know any better to use /bin/sh :( [09:31] Or scripts with bash in the shebang but only so that they can declare functions using the GNU Bash syntax. [12:18] *** neish_ is now known as neish [17:11] https://www.facebook.com/owendelong/posts/10153204974284649 [17:36] someone correct me if I'm wrong.. but is the "service" command in Ubuntu Trusty part of Upstart, but on Xenial, it is systemd ? [17:37] mercutio: ^^ :) [17:37] Yup. [17:37] On debian it routes to systemd somefuckinghow. [17:37] I don't even understand how Linux works anymore. [17:37] up_the_irons: it can also link to init.d i think [17:38] well that's not confusing , is it [17:38] * up_the_irons facepalms [17:38] systemv started the confusion [17:38] it escalated from there [17:38] no wonder the etcd service script on my Xenial nodes don't work, yet the scripts are using it like upstart [17:39] i swear to god i'm going to make my own linux distro [17:39] systemd isn't actually too bad to use [17:39] up_the_irons: good luck :) [17:39] haha [17:39] ARP Linux™ LOL [17:39] I just have to learn all new tools that are different than the ones I've been using for 20 years. [17:39] yeah it's so annoying [17:39] then you can learn to love to hate autoconf, automake, etc. [17:39] ... and different from the tools that I have to use on other systems. [17:40] and you have to re-learn them every 2 years when the whole thing changes [17:40] Yup. [17:40] i haven't found much has changed really [17:40] rc.local vs systemd is the main thing [17:41] probably lots of things i'm missing [17:41] mercutio: so is /etc/init still used by systemd (was Upstart) [17:41] nope [17:41] but ubuntu has lots of legacy stuff [17:41] systemd isnt' too hard [17:42] Hard isn't the point. Unnecessary change is. [17:42] * mhoran hugs FreeBSD rc.d [17:42] systemctl start ssh.service [17:42] systemctl enable ssh.service [17:42] mhoran: yeah unnecessary changes are totally annoying [17:42] i think that kind of way of doing things is pretty easy [17:42] as is over-engineering [17:42] sure it's different, and seems really confusing at first [17:43] but it's not altogether bad [17:43] mercutio: OK, so if I have an Upstart file in /etc/init, and I want to port it to work with systemd, where's the systemd version of /etc/init ? [17:43] I still have to manage init.d scripts from services that haven't migrated, and then know to use systemctl vs /etc/init.d when I use different distros that haven't ugraded, and then balance that with FreeBSD /etc/rc.d ... and then OS X launchctl ... [17:44] https://wiki.ubuntu.com/SystemdForUpstartUsers [17:45] mercutio: thanks :) [17:45] /usr/lib/systemd/user i think [17:48] i use system/ though [17:50] ok [19:47] What's wrong with /etc/systemd/{system,user} or is that not "in" Ubuntu? [19:47] I've always left /usr/lib/systemd for packaged services (sockets, timers, etc) and put my own hand-rolled in /etc/systemd/ [20:25] *** dj_goku has quit IRC (Read error: Connection reset by peer) [20:25] well /etc is kind of meant to be local isn't it? [20:25] so if you want to have the units on multiple systems /usr seems to make sense [20:27] *** dj_goku has joined #arpnetworks [20:27] *** dj_goku has quit IRC (Changing host) [20:27] *** dj_goku has joined #arpnetworks [20:52] *** erratic_ has quit IRC (Ping timeout: 244 seconds) [21:38] I'd still argue that /usr/local/* would be better-suited. But I have no idea if systemd itself uses/recognizes /usr/local for anything. [21:38] i don't think it does. but yeh /usr/local was the standard [21:39] man hier seems to suggest that /usr/local isn't supported [21:40] According to systemd.unit(5) it's /{etc,run,lib}/systemd/ [21:40] Plus various user-level directories. [21:41] /etc/systemd/system │ Local configuration, /run/systemd/system │ Runtime units, /lib/systemd/system │ Units of installed packages [21:41] *** erratic has joined #arpnetworks [21:50] what's /run/systemd [21:50] damn i'm behind aren't i [21:50] /var/run is a symlink to /run these days [21:51] and /run is a tmpfs [21:51] (Manpage from Debian Jessie) [21:55] yeh i thought run had pid etc in it [21:55] so run having systemd units sounded strange [21:55] I guess "runtime units" means temporary in this context [21:59] does anyone here pay for lwn? [23:15] I do [23:16] HOORAY! Now that the console server is running a moderately recent OpenBSD, I can use ed25519 keys :D [23:23] :)