From: Alexander Viro <viro@math.psu.edu>
To: "David L. Nicol" <david@kasey.umkc.edu>
Cc: Zack Brown <zbrown@tumblerings.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Will Mosix go into the standard kernel?
Date: Tue, 27 Feb 2001 16:37:06 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.21.0102271630300.4105-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <3A9C1A3A.8BC1BCF2@kasey.umkc.edu>
On Tue, 27 Feb 2001, David L. Nicol wrote:
> /proc/cluster/.... this would be standard root point for clustering stuff
>
> /proc/mosix would go away, become proc/cluster/mosix
>
> and the same with whatever bproc puts into /proc; that stuff would move to
> /proc/cluster/bproc
#include <std_rants/Thou_Shalt_Not_Shite_Into_Procfs>
Guys, if you want a large subtree in /proc - whack yourself over the head
until you realize that you want an fs of your own. I'll be more than
happy to help with both parts.
next prev parent reply other threads:[~2001-02-27 21:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:17 Will Mosix go into the standard kernel? Zack Brown
2001-02-27 21:20 ` David L. Nicol
2001-02-27 21:32 ` Rik van Riel
2001-02-28 23:06 ` Daniel Ridge
2001-02-28 23:58 ` Albert D. Cahalan
2001-03-01 0:53 ` Dan Hollis
2001-03-01 1:35 ` Daniel Ridge
2001-03-01 2:37 ` zbrown
2001-03-02 0:52 ` Pavel Machek
2001-02-27 21:37 ` Alexander Viro [this message]
2001-02-27 21:56 ` Zack Brown
2001-02-27 22:29 ` zbrown
2001-02-27 22:33 ` J . A . Magallon
2001-02-28 17:59 ` Ric Wheeler
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
[not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
[not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02 ` Tor Arntsen
2001-03-01 19:13 ` Tim Wright
2001-03-02 10:22 Tor Arntsen
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=Pine.GSO.4.21.0102271630300.4105-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=david@kasey.umkc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zbrown@tumblerings.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;
as well as URLs for NNTP newsgroup(s).