public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Aurelien Degremont <aurelien.degremont@cea.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/stderr gets unlinked 8]
Date: Tue, 14 Mar 2006 15:11:27 +0200	[thread overview]
Message-ID: <200603141511.27965.vda@ilport.com.ua> (raw)
In-Reply-To: <200603141308.OAA25709@styx.bruyeres.cea.fr>

On Tuesday 14 March 2006 15:07, Aurelien Degremont wrote:
> > Can I make /dev/stderr non-unlink-able?
> 
> Take a look to
> 
> $ man chattr
> # chattr +i /dev/stderr
> 
> if you are using a ext2/3 filesystem. If not, maybe your filesystem has 
> some similar functionality.

I have ramfs based /dev, which I mount early over /dev (from initrd, in fact).
On-disk /dev/ is empty.
--
vda

  reply	other threads:[~2006-03-14 13:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 10:12 /dev/stderr gets unlinked 8] Denis Vlasenko
2006-03-14 13:07 ` Aurelien Degremont
2006-03-14 13:11   ` Denis Vlasenko [this message]
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
     [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           ` Bodo Eggert
2006-03-19 16:57             ` Joshua Hudson

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=200603141511.27965.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=aurelien.degremont@cea.fr \
    --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