From: Oliver Feiler <kiza@gmx.net>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Removing files in devfs
Date: Mon, 21 Jan 2002 00:09:04 +0100 [thread overview]
Message-ID: <20020121000904.A23198@gmxpro.net> (raw)
In-Reply-To: <20020119094424.A239@gmxpro.net> <200201202255.g0KMtYh15207@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201202255.g0KMtYh15207@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Sun, Jan 20, 2002 at 03:55:34PM -0700
Richard Gooch wrote:
>
> What is "every other system"?
>
Sorry, the last mail didn't get a followup to the list... that should
explain it:
----forwarded mail----
>>>>> "oliver" == Oliver Feiler <kiza@gmxpro.net> writes:
oliver> Juan Quintela wrote:
>>
>> Since 2.4.16-preX, you can't remove a {file,symlink} in devfs created
>> by devfs :(
oliver> Hmm, that'll be it. Since the other systems I tried were both running
oliver> 2.4.17 kernels and I'm with .16 at the moment. Thanks for the hint.
this patch should make the trick (it is a workaround, but it is not
trivial to do it an easier way without still more incestuous
relations, Wating for Richard to do something to the respect.
Later, Juan.
diff -u linux/fs/super.c.orig linux/fs/super.c
--- linux/fs/super.c.orig Fri Jan 4 21:28:24 2002
+++ linux/fs/super.c Fri Jan 4 21:09:45 2002
@@ -1056,8 +1056,8 @@
putname(fs_names);
if (path_start >= 0) {
name = path + path_start;
- devfs_mk_symlink (NULL, "root", DEVFS_FL_DEFAULT,
- name + 5, NULL, NULL);
+// devfs_mk_symlink (NULL, "root", DEVFS_FL_DEFAULT,
+// name + 5, NULL, NULL);
memcpy (name, "/dev/", 5);
}
vfsmnt = alloc_vfsmnt();
----end forward----
--
Oliver Feiler kiza@gmx.net
http://www.lionking.org/~kiza/pgpkey PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/
prev parent reply other threads:[~2002-01-20 23:06 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
2002-01-20 22:55 ` Richard Gooch
2002-01-20 23:09 ` Oliver Feiler [this message]
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=20020121000904.A23198@gmxpro.net \
--to=kiza@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.