Another problem that comes to mind is the "Too many levels
of symbolic links" errors. If a symbolic link is added at
the beginning of a system path are we increasing the risk
that this error will be triggered?
$ grep MAX_NESTED_LINKS linux/namei.h
enum { MAX_NESTED_LINKS = 8 };
char *save
On Sat, 16 Apr 2011, Lars Wirzenius wrote:
> On pe, 2011-04-15 at 21:58 -0300, Henrique de Moraes Holschuh wrote:
> > Symlinks in system path components REALLY are best avoided.
>
> Out of curiosity: why?
Because not everything is blind to what it is transversing to get to the
inode a path refers
On Fri, Apr 15, 2011 at 09:58:58PM -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 16 Apr 2011, Roger Leigh wrote:
> > On Fri, Apr 15, 2011 at 08:59:01PM -0300, Henrique de Moraes Holschuh wrote:
> > > On Fri, 15 Apr 2011, Roger Leigh wrote:
> > > > { find var/run/ ! -type d -print0; \
> > > >
On Fri, Apr 15, 2011 at 09:58:58PM -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 16 Apr 2011, Roger Leigh wrote:
> > On Fri, Apr 15, 2011 at 08:59:01PM -0300, Henrique de Moraes Holschuh wrote:
> > > On Fri, 15 Apr 2011, Roger Leigh wrote:
> > > > { find var/run/ ! -type d -print0; \
> > > >
On pe, 2011-04-15 at 21:58 -0300, Henrique de Moraes Holschuh wrote:
> Symlinks in system path components REALLY are best avoided.
Out of curiosity: why?
--
Blog/wiki/website hosting with ikiwiki (free for free software):
http://www.branchable.com/
--
To UNSUBSCRIBE, email to debian-devel-req
On Sat, 16 Apr 2011, Roger Leigh wrote:
> On Fri, Apr 15, 2011 at 08:59:01PM -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 15 Apr 2011, Roger Leigh wrote:
> > > { find var/run/ ! -type d -print0; \
> > > find var/lock/ ! -type d -print0; } | xargs -0r $_CHROOT_SH rm
> > >
> > > I'm afra
On Fri, Apr 15, 2011 at 08:59:01PM -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 15 Apr 2011, Roger Leigh wrote:
> > { find var/run/ ! -type d -print0; \
> > find var/lock/ ! -type d -print0; } | xargs -0r $_CHROOT_SH rm
> >
> > I'm afraid this will need fixing in util-vserver(?) though.
On Fri, 15 Apr 2011, Roger Leigh wrote:
> { find var/run/ ! -type d -print0; \
> find var/lock/ ! -type d -print0; } | xargs -0r $_CHROOT_SH rm
>
> I'm afraid this will need fixing in util-vserver(?) though. We can't
> work around this in initscripts postinst, I'm afraid, since it worked
> cor
On Fri, Apr 15, 2011 at 02:39:40PM +0200, Adam Borowski wrote:
> On Fri, Apr 15, 2011 at 02:28:35PM +0200, Adam Borowski wrote:
> > On Fri, Apr 15, 2011 at 12:07:37PM +0100, Roger Leigh wrote:
> > > http://people.debian.org/~rleigh/run/sysvinit_2.88dsf-13.3.dsc
> > >
> > > Changes since last time:
On Fri, Apr 15, 2011 at 02:28:35PM +0200, Adam Borowski wrote:
> On Fri, Apr 15, 2011 at 12:07:37PM +0100, Roger Leigh wrote:
> > http://people.debian.org/~rleigh/run/sysvinit_2.88dsf-13.3.dsc
> >
> > Changes since last time:
> > - vserver environments should now upgrade correctly (autodetect and
On Fri, Apr 15, 2011 at 12:07:37PM +0100, Roger Leigh wrote:
> http://people.debian.org/~rleigh/run/sysvinit_2.88dsf-13.3.dsc
> http://people.debian.org/~rleigh/run/sysvinit_2.88dsf-13.3.patch
> http://people.debian.org/~rleigh/run/sysvinit_2.88dsf-13.3_amd64.changes
> http://people.debian.org/~rle
On Wed, Mar 30, 2011 at 11:20:45PM +0100, Roger Leigh wrote:
> On Wed, Mar 30, 2011 at 10:32:51PM +0200, Goswin von Brederlow wrote:
> > Tollef Fog Heen writes:
> >
> > > ]] Julien Cristau
> > >
> > > | On Wed, Mar 30, 2011 at 16:20:10 +0100, Roger Leigh wrote:
> > > |
> > > | > Given that Fedo
12 matches
Mail list logo
