4 ms·

Processes don't work quite the same. There's no sysv init or systemd. There's not good user separation within the shell (run all as root) and the file permissio

Processes don't work quite the same. There's no sysv init or systemd. There's not good user separation within the shell (run all as root) and the file permissions in places where the subsystem meet the PC are weird. Those were my first impressions. I'm cautiously optimistic about it though, and confident they'll work out the kinks with time. But right now it's still better to be on BSD/Mac if you like a unix-like development environment without running linux.

banashark 10y ago
I'm curious what your use case for those are. Are you needing to `init 1` or `systemctl isolate rescue.target`? Or is it perhaps a need to `systemctl status` on services? I might just not be that experienced with the wide use-cases for these applications, but what are your hypothetical use cases?
- matt_wulfeck 10y ago
  Really I just want a way to write simple service scripts and have the OS keep them alive. upstart, sysv init, systemd, whatever works... I don't like logging into my dev box and then manually starting one-off scripts for all of the services that I like running (docker, dnsmasq, apt-cache, foo.py, etc etc).
  - JdeBP 10y ago
    Then use the Ubuntu-packaged runit or daemontools; or port s6, perp, daemontools-encore, or nosh. * https://news.ycombinator.com/item?id=11416376 https://news.ycombinator.com/item?id=11416376 * http://jdebp.eu./FGA/daemontools-family.html http://jdebp.eu./FGA/daemontools-family.html I don't know whether the Debian-packaged nosh will install on Ubuntu as it stands. * http://jdebp.eu./Softwares/nosh/debian-binary-packages.html http://jdebp.eu./Softwares/nosh/debian-binary-packages.html
JdeBP 10y ago
Your first impressions did not include reading the release notes. (-: The authors made it very clear that it does not "run all as root". * http://askubuntu.com/a/754951/43344 http://askubuntu.com/a/754951/43344

banashark 10y ago

I'm curious what your use case for those are. Are you needing to `init 1` or `systemctl isolate rescue.target`? Or is it perhaps a need to `systemctl status` on services? I might just not be that experienced with the wide use-cases for these applications, but what are your hypothetical use cases?

matt_wulfeck 10y ago
Really I just want a way to write simple service scripts and have the OS keep them alive. upstart, sysv init, systemd, whatever works... I don't like logging into my dev box and then manually starting one-off scripts for all of the services that I like running (docker, dnsmasq, apt-cache, foo.py, etc etc).
- JdeBP 10y ago
  Then use the Ubuntu-packaged runit or daemontools; or port s6, perp, daemontools-encore, or nosh. * https://news.ycombinator.com/item?id=11416376 https://news.ycombinator.com/item?id=11416376 * http://jdebp.eu./FGA/daemontools-family.html http://jdebp.eu./FGA/daemontools-family.html I don't know whether the Debian-packaged nosh will install on Ubuntu as it stands. * http://jdebp.eu./Softwares/nosh/debian-binary-packages.html http://jdebp.eu./Softwares/nosh/debian-binary-packages.html

JdeBP 10y ago

Your first impressions did not include reading the release notes. (-: The authors made it very clear that it does not "run all as root". * http://askubuntu.com/a/754951/43344 http://askubuntu.com/a/754951/43344