From: Oliver Feiler <kiza@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Removing files in devfs
Date: Sat, 19 Jan 2002 09:44:24 +0100 [thread overview]
Message-ID: <20020119094424.A239@gmxpro.net> (raw)
Hello,
Is this behaviour supposed to be?
9:36 root@kiza /dev# l null
crw-rw-rw- 1 root root 1, 3 Jan 1 1970 null
9:36 root@kiza /dev# rm null
removing `null'
9:36 root@kiza /dev# l null
ls: null: No such file or directory
9:36 root@kiza /dev#
I have kernel 2.4.16 with devfs and on every other system I tried I
only get "rm: cannot unlink `null': Operation not permitted" when trying to
delete something in devfs. And I cannot see any differences as far as devfs is
concerned on the systems I tried. devfs compiled in, mounted on boot time,
same version of devfsd.
Regards,
Oliver
--
Oliver Feiler kiza@gmx.net
http://www.lionking.org/~kiza/pgpkey PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/
next reply other threads:[~2002-01-19 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 8:44 Oliver Feiler [this message]
2002-01-19 20:54 ` Removing files in devfs Juan Quintela
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=20020119094424.A239@gmxpro.net \
--to=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