control: reopen -1
[2018-11-09 01:09] alecfeld...@disroot.org
> Glancing over the changes, changing the runsvdir is a bad idea, since
> now stage 3 won't stop t he correct services.
>
> sv force-stop /etc/service/*
> sv exit /etc/service/*
Good catch. It need to be changed too. But I consider not stopping
`sulogin` a very minor issue.
> You set the service directory to /etc/runit/runsvdir/single if
> "single" kernel paramter is use d, so sulogin won't be properly
> stopped when shutting down.
Yeah, /etc/runit/3 need to be adjusted.
> Instead, the runsvchdir command addresses this problem. Just have
> /etc/service symlinked to /etc/runit/runsvdir/current. current is then
> symlinked to default (sorry for not being clearer on this matter). So,
> in simplistic terms: /etc/sv/<service> --> /etc/service -->
> /etc/runit/runsvdir/current --> /etc/runit/runsv dir/default
> (relative). When using "single", runsvchdir will switch the current
> symlink to /etc/runit/runsvdir/single.
And when it will be restored to point to default? And what about sudden
power outage? And what about /etc/runit/runsvdir/{foo,bar}, maintained
by local system administrator? Too many questions, too many corner
cases, too many moving parts.
> I'm not sure what you mean by virtual filesystems?
Everything under /proc, /sys and /dev. While I use Linux kernel, I
prefer to tie myself as little as possible to its features, unless
strictly necessery.
