From: Bill Davidsen <davidsen@tmr.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Submissions for 2.4.19-pre [sdmany (Richard Gooch)] [Discuss :) ]
Date: Thu, 28 Feb 2002 22:07:17 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1020228220249.3310B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <E16gaRG-0001aR-00@the-village.bc.nu>
On Thu, 28 Feb 2002, Alan Cox wrote:
> > Hate to say it but 2.5 is not ready for any kind of production use, and
> > some people really need to connect more SCSI devices than are currently
> > supported. That's NOT ivory tower, it's real world "do it with Linux"
> > problem solving.
>
> I'd be interested to know if Al Viro considers devfs production use ready yet
I would say that is a fair question. I find it in the production kernel?
Good, so it was considered ready by someone. Seems to me one of the Redhat
kernels had devfs as a module, they seem to think so.
It's a good question, though, and I am assuming that the answer is "it's
in the stable kernel" which isn't yes or no.
If it's not stable then there simply is no Linux solution to large
storage. Given what vendors are doing I find that unintuitive.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2002-03-01 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 1:41 Michael Cohen
2002-02-26 2:40 ` Alan Cox
2002-02-26 3:24 ` Richard Gooch
2002-02-26 9:29 ` Alan Cox
2002-02-28 22:38 ` Bill Davidsen
2002-02-28 23:58 ` Alan Cox
2002-03-01 3:07 ` Bill Davidsen [this message]
2002-03-01 12:40 ` Alan Cox
2002-03-01 18:39 ` Bill Davidsen
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.LNX.3.96.1020228220249.3310B-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®