public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: "J . A . Magallon" <jamagallon@able.es>,
	Linus Torvalds <torvalds@transmeta.com>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: Strange umount problem in latest 2.4.0 kernels
Date: 12 Jan 2001 09:05:53 +0100	[thread overview]
Message-ID: <qwwg0ipi49q.fsf@sap.com> (raw)
In-Reply-To: <UTC200101112234.XAA98877.aeb@ark.cwi.nl> <20010112002303.A905@werewolf.able.es>
In-Reply-To: <20010112002303.A905@werewolf.able.es>

On Fri, 12 Jan 2001, jamagallon@able.es wrote:
> Same cam be applied to shm ? Thus kernel Documentation/Changes
> should be changed:
[...]
> 
> none        /dev/shm    shm     defaults    0 0
> 
> to
> 
> shm        /dev/shm    shm     defaults    0 0
> 

Yes, I thought that I changed that :-( I always have the type as
device in my fstab. 

Linus, it is not really crucial, but still could be applied without
breaking anything for sure ;-) 

Greetings
		Christoph

--- 2.4.0/Documentation/Changes Mon Jan  1 19:00:04 2001
+++ linux/Documentation/Changes Fri Jan 12 09:03:35 2001
@@ -121,7 +121,7 @@
 memory. Adding the following line to /etc/fstab should take care of
 things:
 
-none           /dev/shm        shm             defaults        0 0
+shm            /dev/shm        shm             defaults        0 0
 
 Remember to create the directory that you intend to mount shm on if
 necessary (The entry is automagically created if you use devfs). You           
-
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/

  reply	other threads:[~2001-01-12  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 22:34 Strange umount problem in latest 2.4.0 kernels Andries.Brouwer
2001-01-11 22:46 ` Udo A. Steinberg
2001-01-11 23:23 ` J . A . Magallon
2001-01-12  8:05   ` Christoph Rohland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11 18:22 Udo A. Steinberg
2001-01-11 18:33 ` Daniel Phillips
2001-01-11 18:41   ` Alexander Viro
2001-01-11 19:24     ` Udo A. Steinberg
2001-01-11 19:32       ` Alexander Viro
2001-01-11 20:26         ` Udo A. Steinberg
2001-01-11 20:56       ` Udo A. Steinberg
2001-01-11 21:34         ` Alan Cox
2001-01-11 23:04         ` David Ford
2001-01-11 21:42       ` Andreas Dilger

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=qwwg0ipi49q.fsf@sap.com \
    --to=cr@sap.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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