[Pkg-sysvinit-devel] Bug#630723: misc regressions on GNU/kFreeBSD

[Roger Leigh]

On Sun, Feb 10, 2013 at 02:06:40PM +0000, Steven Chamberlain wrote:
> Control: notfixed -1 2.88dsf-34
> Control: found -1 2.88dsf-41
> Control: tags -1 + patch
> 
> On Thu, 16 Jun 2011 16:41:57 +0200, Robert Millan wrote:
> >   mount: /run: unknown special file or file system
> 
> There are still some remaining errors like that:
> 
> > mount: /run: unknown special file or file system
> > mount: /run/lock: unknown special file or file system
> > mount: proc : Operation not supported
> > mount: sys : Operation not supported
> > mount: /run/shm: unknown special file or file system
> 
> These come from S08mtab.sh, in the "Add entries for mounts created in
> early boot" section.  The mount_filesystems function only knows about
> Linux-specific filesystems (proc, sysfs) and also uses the remount
> option not supported by kFreeBSD for these filesystems.
> 
> I don't think we even need to run S08mtab.sh on GNU/kFreeBSD, as
> /etc/mtab is only symlinked to /proc/mounts.  Maybe we could exit early
> with:
> 
> # Abort if /etc/mtab is a symlink to /proc/mounts (e.g. on GNU/kFreeBSD)
> [ "$(readlink /etc/mtab)" = "/proc/mounts" ] && exit 0
> 
> As far as I can tell the errors are harmless though.

We could certainly abort early.  mtab.sh is going to be removed for
jessie, where we will eliminate /etc/mtab as a file entirely and
require it to be a symlink to /proc/mounts.  Currently it's there
primarily as a fallback for any systems which can't transition for
some reason; currently this is Hurd users, and the odd Linux user
who is storing esoteric stuff in mtab which is not in /proc/mounts;
though the latter is now all gone to the best of my knowledge.

I think the reason you see the errors on kFreeBSD is that the Linux
mount makes all these mtab-updating mount commands into no-ops.
The others, which trigger a remount with the mount options from
the fstab entry, will have to be moved elsewhere.  I'm not sure if
these work with the kFreeBSD mount.

I'd like for the current sysvinit to migrate to testing, and if
possible fix this after that.  If it's not strictly RC, could this
wait until after the release?


Thanks,
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