[Pkg-sysvinit-devel] /run transition

Roger Leigh rleigh at codelibre.net
Mon Apr 25 20:19:47 UTC 2011

On Sat, Apr 23, 2011 at 09:53:51AM +0100, Roger Leigh wrote:
> On Sat, Apr 23, 2011 at 10:07:28AM +1000, Kel Modderman wrote:
> > On Sat, 23 Apr 2011 04:27:00 AM Roger Leigh wrote:
> > > Hi Kel and other sysvinit developers,
> > > 
> > > I've attached a further update for your consideration, which fixes a
> > > few issues.  If it's OK with you, this could be uploaded to
> > > experimental (with your changes folded into the same version in the
> > > changelog) as 2.88dsf-13.5.  Unless you'd prefer to do a maintainer
> > > upload.
> > In my opnion: do not hesitate to upload this to experimental and continue the
> > improvement of the transition to /run.
> Thanks.
> Following discussion with the systemd folks, they would prefer it if we
> could deprecate /etc/default/tmpfs and migrate to using /etc/fstab
> directly.  This is because systemd can't make use of /etc/default/fstab
> directly, and if we both use fstab it's both more obvious for the user
> since it's in an expected place, and it can be shared with systemd.
> I've attached a proposed patch for this.  Note that this is tested, but
> not yet final.  I also attached a patch to tighten up mount options
> where possible.

I have attached a proposed tested and hopefully final patch for the
next NMU.

This is the same as the last patch, but with the addition of the
tested /etc/default/tmpfs deprecation/migration.  Note that
/etc/default/tmpfs continues to be functional, but (as was already
the case) continues to be overridden by the mount options in
/etc/fstab.  We migrate the existing settings from /etc/default/tmpfs
to /etc/fstab on package upgrade.

Is this OK to upload?


sysvinit (2.88dsf-13.5) experimental; urgency=low

  [ Roger Leigh ]
  * Non-maintainer upload.
  * Unify mount logic shared between mountkernfs.sh, mountdevsubfs.sh
    and mtab.sh
    - all functions use domount() from /lib/init/mount-functions.  This
      merges in the functionality of domtab() in mtab.sh, which was
      almost entirely identical.  domount is now capable of mounting and
      remounting (with and without mtab updates) as well as updating
    - mtab.sh calls mountkernfs.sh and mountdevsubfs with an "mtab"
      argument to do the mtab generation for early mounts.  This means
      that the mount logic is not needlessly duplicated, and does not
      require two copies to be kept exactly in sync.  This reduces the
      risk of problems as a consequence of subtle differences between
      the two scripts.
    - mount options may be specified in either /etc/default/tmpfs or
      in /etc/fstab, and will supersede hard coded defaults.  The
      the values in fstab (if any) will supersede those in
      /etc/default/tmpfs should an entry be present.  These values are
      also used for remounting, which means that filesystems mounted in
      an initramfs and moved onto the root filesystem prior to init
      starting will be remounted with the correct user-specified
    - Improve robustness of stat checks when comparing directories.
    - mountkernfs.sh and mountdevsubfs.sh are idempotent, so allow for
      repeated invocation.  This is needed to allow the same code to
      be used for mounting, remounting and mtab generation.
    - Enabling RAMLOCK, RAMSHM and RAMTMP in /etc/default/rcS is no longer
      required if the filesystems are present in /etc/fstab
  * /etc/default/tmpfs is deprecated
    - If changing the default size limits, adding an entry to /etc/fstab
      is preferred compared with editing /etc/default/tmpfs.  This also
      permits modifying the default mount options, and setting additional
      mount options.
    - If /etc/default/tmpfs has been modified from the defaults, any
      needed entries will be created in /etc/fstab on upgrade, to
      preserve the settings from /etc/default/tmpfs.  The entries in
      /etc/fstab will subsequently override the settings in
  * The mount options for /run are made stricter when possible.  For
    example, if /run/shm is a separate filesystem, it may be safely
    mounted with "noexec".
  * Compatibility symbolic links are relative, not absolute.  e.g.
    /var/lock is ../run/lock rather than /run/lock.  This means that if
    you're using a chroot from the host system, you'll always be using
    locations in the chroot, rather than the host, when following the
  * Updated documentation in initscripts README.Debian and rcS(5).

  [ Kel Modderman ]
  * Consider rpcbind as alternative to portmap in mountnfs ifupdown
    script. Thanks to Jamie Heilman and Arthur de Jong.
    (Closes: #620788)

 -- Roger Leigh <rleigh at debian.org>  Fri, 22 Apr 2011 15:25:25 +0100

  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sysvinit-run-nmu2.patch
Type: text/x-diff
Size: 40589 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20110425/4e7ce7a2/attachment-0001.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20110425/4e7ce7a2/attachment-0001.pgp>

More information about the Pkg-sysvinit-devel mailing list