[Pkg-sysvinit-devel] Bug#693398: Bug#693387: Pre-approval for unblock: sysvinit/2.88dsf-33

Roger Leigh rleigh at codelibre.net
Fri Nov 16 13:48:32 UTC 2012


On Fri, Nov 16, 2012 at 02:33:54PM +0100, Michael Biebl wrote:
> I'm redirecting this to #693398 since I don't want to spam the unblock
> request bug.
> 
> On 16.11.2012 11:37, Roger Leigh wrote:
> > On Fri, Nov 16, 2012 at 02:11:13AM +0100, Michael Biebl wrote:
> 
> >>
> >> As already mentioned on IRC: checkroot-bootclean is kinda odd.
> >> It cleans up /run/, /run/lock *after* the tmpfs has been mounted, so
> >> this cleanup looks entirely pointless.
> > 
> > The main point of this script was to clean /tmp prior to mounting a
> > tmpfs, as well as /lib/init/rw (for historical reasons).  It also
> > handles cleaning of /run and /run/lock; for platforms which don't
> > support a tmpfs, or where the admin has explicitly disabled tmpfs
> > mounting.
> 
> /run-on-tmpfs is not really optional (at least not on kfreebsd and
> Linux). So this only seems to be relevant for Hurd.
> Especially cleaning up /run/lock seems completely pointless, since we
> already cleanup /run.
> Also, keep in mind that clean_all is run *three* times during boot.
> So for all non-Hurd users, which probably make up 100% of our user base
> (minus rounding errors), we run those clean up rules unnecessarily.
> 
> While I could see the point of cleaning up /var/lock and /var/run, if
> you mount a tmpfs on those dirs, that is no longer what's happening with
> them being migrated to symlinks on upgrades.

While we don't expose a configuration option (RAMRUN) to disable
tmpfs on /run, we don't actively prevent users from disabling it by
e.g. commenting out the line in mountkernfs.  It's not supported,
and I certainly won't recommend anyone do that.  But there were
several requests to restore boot-time cleaning by people who were
doing that, and this covers that use case.

While I'm open to revisiting this for jessie, it costs very little
to do this, and I don't want to actively and intentionally break
this use case, even though it's nonstandard at this point in time.

Note that we do create flag files to prevent the clean being done
multiple times, so the overhead of the three scripts is in reality
very low.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800



More information about the Pkg-sysvinit-devel mailing list