[Pkg-sysvinit-devel] Bug#626263: Clarification of §10.5 symlink wording needed
Carsten Hey
carsten at debian.org
Tue May 10 23:48:08 UTC 2011
* Carsten Hey [2011-05-11 01:06 +0200]:
> * Russ Allbery [2011-05-10 15:32 -0700]:
> > Carsten Hey <carsten at debian.org> writes:
> >
> > > Besides "/usr -> /", are symlinks to directories still supported as
> > > top-level directories and are there still people using such a setup?
> > > If nobody uses this anymore, the policy could be adapted to the year
> > > 2011.
> >
> > Is there any reason *not* to continue supporting them?
Actually, there is a bug that could be triggered by absolute symlinks.
bind9/sid contains the directory /var/run/named. If I run cdeboootstrap
(I assume the same is true for debootstrap if dpkg is not available) and
pass bind9 as extra package to install, tar (run by cdebootstrap) would
create /var/run/bind9 instead of $TARGET/var/run/bind9 if
$TARGET/var/run is an absolute symlink. #514015 contains a past example
that triggered this bug.
Carsten
More information about the Pkg-sysvinit-devel
mailing list