Viewing profile — skarnet
skarnet
HN member- Joined
- Fri, Jun 20, 2014, 6:02 PM UTC
- HN karma
- 23
- Public activity
- 16 items
- HN profile
- View on Hacker News ↗
About skarnet
Recent public activity
-
comment
Comment #36956796
Except it's... not quite correct. getent performs NSS resolution, not DNS resolution, so its output depends on the value of the hosts field in your /etc/nsswitch.conf, which could …
-
comment
Comment #32435294
Not at all. I'm referring to the structure of the Alpine packaging, especially around boot scripts, that hardcodes busybox in a number of places and makes it difficult to package a…
-
comment
Comment #32354931
And if you look under the hood, you will see that it's only possible because of a bunch of ad-hoc hacks, which is exactly what my proposal was about: level the playing field and ma…
-
comment
Comment #32354350
Your information is incorrect. "Avoiding spinning up new processes" is incorrect characterization of s6. Processes are not a scarce resource; spawning a process is not a costly ope…
-
comment
Comment #14011664
There is no good solution for servers that, mistakenly, background themselves; the practice of backgrounding itself comes from a time where supervision was not as widely known as i…
-
comment
Comment #14007937
You need to read the archives of the supervision mailing-list at list.skarnet.org, as well as http://skarnet.org/software/s6/overview.html - there is a lot of value in process supe…
-
comment
Comment #14006929
I agree with Jonathan on everything here, with the additional caveat that the Go runtime is particularly heavy, and thus not really suitable for low-level system software (which sh…
-
comment
Comment #13569851
Still in active development too. :) And no, Jonathan, I haven't heard anything from TrueOS people. Which is a shame, because if a distribution is being built today, with no existin…
-
comment
Comment #10527342
I see nothing there that can't be achieved by a simple supervision suite. s6, nosh, even runit provide those features; the extra complexity of systemd isn't needed at all. If even …
-
comment
Comment #10491592
Honestly, the people who use Busybox are probably aware of the problems - political as well as technical - with systemd, and most likely not using systemd in the first place becaus…
-
comment
Comment #10377265
But how would you go with restoring such an image? It won't be instant, there will still be a window where the service manager is continuing its work but the image hasn't been rest…
-
comment
Comment #10372182
You seem to dislike the idea of asking for notification support in the daemons themselves. Granted, it's impractical, but it's the only way to avoid race conditions which are rare …
-
comment
Comment #10372154
It's important to realize that "a replacement for systemd" is neither achievable nor desirable. systemd has grown fast and conquered large market shares because it was backed up by…
-
comment
Comment #10288157
As Jonathan said: the reason for the compilation phase is efficiency. The information in the compiled database is organized for fast loading and immediate access to the complete de…
-
comment
Comment #9809813
Yes, that was exactly the idea behind s6-fdholder-daemon: set up a central server to keep fds open when you need to restart a process. The old process stores the fd into the fdhold…
-
comment
Comment #7946492
Note that: - You do not have to follow the slashpackage convention to use or build s6. You can configure it out. - You do not have to write your init scripts in execline. Any scrip…