From: Roderich Schupp <rsch@ExperTeam.de>
To: linux-kernel@vger.kernel.org
Cc: rgooch@atnf.csiro.au, "H. Peter Anvin" <hpa@transmeta.com>
Subject: [PATCH] Make devfs create /dev/shm (was: Re: Trashing ext2 with hdparm) )
Date: Fri, 08 Dec 2000 09:46:09 +0100 [thread overview]
Message-ID: <200012080852.JAA19341@www1.ExperTeam.de> (raw)
In-Reply-To: Your message of "Thu, 07 Dec 2000 01:05:47 +0100." <F947C7609FCD02F0412569AD007A3EC0.000087C3412569AE@experteam.de>
Chris Meadors wrote:
>
> On 6 Dec 2000, H. Peter Anvin wrote:
>
> > <HARP>
> > Please don't use the path /var/shm... it was a really bad precedent
> > set when someone suggested it. Use /dev/shm.
> > </HARP>
>
> And I'll ask again... If this is now the recommend mount point, can we
> have devfs create this directory for us?
C'mon guys, this is just to easy:
--- 2.4.0-test11/ipc/shm.c.~1~ Thu Dec 7 22:32:47 2000
+++ 2.4.0-test11/lipc/shm.c Thu Dec 7 22:38:59 2000
@@ -221,6 +221,7 @@
#ifdef CONFIG_PROC_FS
create_proc_read_entry("sysvipc/shm", 0, 0, sysvipc_shm_read_proc, NULL);
#endif
+ devfs_mk_dir (NULL, "shm", NULL);
zero_id = ipc_addid(&shm_ids, &zshmid_kernel.shm_perm, 1);
shm_unlock(zero_id);
INIT_LIST_HEAD(&zshmid_kernel.zero_list);
Cheers, Roderich
--
When in trouble or in doubt,
run in circles, scream and shout.
Roderich Schupp mailto:rsch@ExperTeam.de
ExperTeam GmbH http://www.experteam.de/
Munich, Germany
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-12-08 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F947C7609FCD02F0412569AD007A3EC0.000087C3412569AE@experteam.de>
2000-12-08 8:46 ` Roderich Schupp [this message]
2000-12-18 15:23 ` [PATCH] Make devfs create /dev/shm (was: Re: Trashing ext2 with hdparm) ) Christoph Rohland
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=200012080852.JAA19341@www1.ExperTeam.de \
--to=rsch@experteam.de \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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;
as well as URLs for NNTP newsgroup(s).