mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Micallef <steven.micallef@world.net>
To: "'Ben Collins'" <bcollins@debian.org>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: chroot() breaks syslog() ?
Date: Mon, 4 Aug 2003 15:49:48 +1000	[thread overview]
Message-ID: <6416776FCC55D511BC4E0090274EFEF5080024AC@exchange.world.net> (raw)

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()?

Regards,

Steve.

> -----Original Message-----
> From: Ben Collins [mailto:bcollins@debian.org]
> Sent: Monday, 4 August 2003 3:19 PM
> To: Steven Micallef
> Cc: 'linux-kernel@vger.kernel.org'
> Subject: Re: chroot() breaks syslog() ?
> 
> 
> > connect(3, {sin_family=AF_UNIX, path="/dev/log"}, 16) = -1 
> ENOENT (No such
> > file or directory)
> > 
> > Is this intentional? If so, is there a work-around? I 
> discovered this when
> > debugging 'rwhod', but I imagine there are many more utils 
> that would be
> > affected too.
> 
> I don't know how it ever did work, if in fact it did for you. /dev/log
> is not a kernel device, it's just a normal socket created by syslogd.
> 
> Now, if you use devfs, and mount devfs under the chroot, it magically
> propogates /dev/log. But that's not the normal thing.
> 
> -- 
> Debian     - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> WatchGuard - http://www.watchguard.com/
> __________ Information from NOD32 1.449 (20030630) __________
> 
> This message was checked by NOD32 for Exchange e-mail monitor.
> http://www.nod32.com
> 
> 
> 
> 

             reply	other threads:[~2003-08-04  5:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04  5:49 Steven Micallef [this message]
2003-08-04  5:34 ` Ben Collins
2003-08-04  6:12   ` David Lang
2003-08-04  8:40   ` Wichert Akkerman
2003-08-04 13:33 ` Herbert Pötzl
2003-08-04 20:19   ` Olaf Titz
  -- strict thread matches above, loose matches on Subject: below --
2003-08-06 13:34 Oliver Pitzeier
2003-08-06  8:42 Oliver Pitzeier
2003-08-06 11:08 ` Herbert Pötzl
2003-08-04  7:30 Steven Micallef
2003-08-04  5:27 Steven Micallef
2003-08-04  5:19 ` Ben Collins
2003-08-04  7:23 ` Torsten Foertsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6416776FCC55D511BC4E0090274EFEF5080024AC@exchange.world.net \
    --to=steven.micallef@world.net \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®