Messages in this thread | | | From | David Lang <> | Date | Sun, 3 Aug 2003 23:12:10 -0700 (PDT) | Subject | Re: chroot() breaks syslog() ? |
| |
if you need any devices in /dev after the chroot you can create anything you need in the appropriate directory.
with syslog you need to look at the -a option to syslogd to make things work the way you want them to.
David Lang
On Mon, 4 Aug 2003, Ben Collins wrote:
> Date: Mon, 4 Aug 2003 01:34:38 -0400 > From: Ben Collins <bcollins@debian.org> > To: Steven Micallef <steven.micallef@world.net> > Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org> > Subject: Re: chroot() breaks syslog() ? > > On Mon, Aug 04, 2003 at 03:49:48PM +1000, Steven Micallef wrote: > > You're right - my mistake, it doesn't actually work on 2.4.8 either, I think > > I was looking at the wrong thing when I thought it was actually working. > > > > Is it worth considering (optionally) making /dev available to chroot()'ed > > environments, or would that just defeat the whole purpose of chroot()? > > Enable devfs, and you can mount devfs anywhere, even in chroots, and it > will propogate things like /dev/log. > > Generally chroot environments don't want that though. > > -- > Debian - http://www.debian.org/ > Linux 1394 - http://www.linux1394.org/ > Subversion - http://subversion.tigris.org/ > WatchGuard - http://www.watchguard.com/ > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |