public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Oliver Feiler <kiza@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Removing files in devfs
Date: 19 Jan 2002 21:54:57 +0100	[thread overview]
Message-ID: <m21ygmxdr2.fsf@trasno.mitica> (raw)
In-Reply-To: <20020119094424.A239@gmxpro.net>
In-Reply-To: <20020119094424.A239@gmxpro.net>

>>>>> "oliver" == Oliver Feiler <kiza@gmx.net> writes:

oliver> Hello,
oliver> Is this behaviour supposed to be?

oliver> 9:36 root@kiza /dev# l null 
oliver> crw-rw-rw-    1 root     root       1,   3 Jan  1  1970 null
oliver> 9:36 root@kiza /dev# rm null
oliver> removing `null'
oliver> 9:36 root@kiza /dev# l null
oliver> ls: null: No such file or directory
oliver> 9:36 root@kiza /dev#

oliver> I have kernel 2.4.16 with devfs and on every other system I tried I 
oliver> only get "rm: cannot unlink `null': Operation not permitted" when trying to 
oliver> delete something in devfs. And I cannot see any differences as far as devfs is 
oliver> concerned on the systems I tried. devfs compiled in, mounted on boot time, 
oliver> same version of devfsd.

oliver> Regards,

oliver> Oliver

Since 2.4.16-preX, you can't remove a {file,symlink} in devfs created
by devfs :(

That hit me hardly whith /dev/root.  I had to remove the code that
generate that link to get my system booting (where system is anything
booting with mkinitrd + devfs).

Later, Juan.


-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  reply	other threads:[~2002-01-19 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19  8:44 Removing files in devfs Oliver Feiler
2002-01-19 20:54 ` Juan Quintela [this message]
2002-01-20 22:55 ` Richard Gooch
2002-01-20 23:09   ` Oliver Feiler

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=m21ygmxdr2.fsf@trasno.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=kiza@gmx.net \
    --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