public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Hudson" <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/stderr gets unlinked 8]
Date: Sun, 19 Mar 2006 08:57:02 -0800	[thread overview]
Message-ID: <bda6d13a0603190857p5cb466datd0395253ed263986@mail.gmail.com> (raw)
In-Reply-To: <E1FKmO8-000303-Ve@be1.lrz>

On 3/18/06, Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> wrote:
> linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
> > On Fri, 17 Mar 2006, Jan Engelhardt wrote:
>
> >> If not, you could write an LSM that prohibits unlinking /dev/stderr.
>
> > That symlink isn't even used -- at least by any sane program!
> > I don't have a clue why these things were created and what they
> > were for. The objects stdin, stdout, and stderr, are 'C' runtime
> > library pointers to opaque types associated with the file descriptors,
> > STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO. The presence of
> > these bogus sym-links in /dev represent some kind of obfuscation
> > and have no value except to confuse (or identify a RedHat distribution).
>
> Think about portable shell scripts. I remember /dev/std* longer than /proc.
They're from BSD (where they are real devices, with a major & minor number).

  reply	other threads:[~2006-03-19 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5QeND-31x-7@gated-at.bofh.it>
     [not found] ` <5QE55-6Td-9@gated-at.bofh.it>
     [not found]   ` <5R778-8fs-29@gated-at.bofh.it>
     [not found]     ` <5RgN2-5fi-3@gated-at.bofh.it>
     [not found]       ` <5RohF-7Oe-3@gated-at.bofh.it>
     [not found]         ` <5Rpnz-ZJ-39@gated-at.bofh.it>
2006-03-19  1:07           ` /dev/stderr gets unlinked 8] Bodo Eggert
2006-03-19 16:57             ` Joshua Hudson [this message]
2006-03-14 10:12 Denis Vlasenko
2006-03-14 13:07 ` Aurelien Degremont
2006-03-14 13:11   ` Denis Vlasenko
2006-03-14 13:11 ` Christian
2006-03-14 13:35   ` Denis Vlasenko
2006-03-15 11:02     ` Stefan Seyfried
2006-03-15 13:14       ` Andreas Schwab
2006-03-15 13:34         ` Denis Vlasenko
2006-03-15 14:23           ` linux-os (Dick Johnson)
2006-03-16  8:07             ` Denis Vlasenko
2006-03-16 20:11         ` Jan Engelhardt
2006-03-17  6:34           ` Denis Vlasenko
2006-03-17 14:32             ` Jan Engelhardt
2006-03-17 15:40               ` linux-os (Dick Johnson)
2006-03-15 13:30       ` Denis Vlasenko

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=bda6d13a0603190857p5cb466datd0395253ed263986@mail.gmail.com \
    --to=joshudson@gmail.com \
    --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