From: Bryan Whitehead <driver@jpl.nasa.gov>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: "Peter C. Norton" <spacey-linux-kernel@lenin.nu>,
Christoph Hellwig <hch@infradead.org>,
Ian Kent <raven@themaw.net>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 future
Date: Tue, 02 Dec 2003 13:56:50 -0800 [thread overview]
Message-ID: <3FCD0AA2.2030306@jpl.nasa.gov> (raw)
In-Reply-To: <20031202201800.GB2030@devserv.devel.redhat.com>
Arjan van de Ven wrote:
> On Tue, Dec 02, 2003 at 12:10:40PM -0800, Peter C. Norton wrote:
>
>>On Tue, Dec 02, 2003 at 12:54:54AM +0100, Arjan van de Ven wrote:
>>
>>>On Mon, 2003-12-01 at 22:36, Peter C. Norton wrote:
>>>`
>>>
>>>>encouraging the distros to get behind autofs4 (hint hint, redhat,
>>>>hint).
>>>
>>>I suspect you'll have a really hard time finding ANY distro that still
>>>wants to actively develop new products on a 2.4 codebase.
>>
>>Perhaps, but some rather large customers of AS2.1, would like it if
>>redhat could deliver the large outstanding automounting features for
>>their (mainly sun) environments. Since these environments resist
>>change, upgrading a kernel to include a newer autofs4 is more likely
>>than upgrading the whole system.
>
>
> and putting a feature into 2.4.23 is going to help/change that... how ?
From a sysadmin with rather large Solaris / Linux install base I'd love
to see a fully working autofs in 2.4. But I would loath running 2.6 on a
much needed production system... Hacking around the junk version of
autofs in 2.4 is a pain.
--
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
driver@jpl.nasa.gov
next prev parent reply other threads:[~2003-12-02 21:59 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 14:25 Linux 2.4 future Marcelo Tosatti
2003-12-01 15:04 ` Ian Kent
2003-12-01 15:33 ` Christoph Hellwig
2003-12-01 21:36 ` Peter C. Norton
2003-12-01 23:54 ` Arjan van de Ven
2003-12-02 1:11 ` Ian Kent
2003-12-02 20:13 ` Peter C. Norton
2003-12-02 20:10 ` Peter C. Norton
2003-12-02 20:18 ` Arjan van de Ven
2003-12-02 20:46 ` Peter C. Norton
2003-12-03 1:23 ` Ian Kent
2003-12-03 10:36 ` Matthias Andree
2003-12-03 14:49 ` Ian Kent
2003-12-03 15:00 ` Matthias Andree
2003-12-04 6:24 ` Ian Kent
2003-12-02 21:56 ` Bryan Whitehead [this message]
2003-12-02 8:17 ` Christoph Hellwig
2003-12-02 1:09 ` Ian Kent
2003-12-02 2:23 ` snpe
2003-12-02 6:39 ` Jan-Benedict Glaw
2003-12-02 18:04 ` Linus Torvalds
2003-12-02 18:45 ` Jan-Benedict Glaw
2003-12-02 19:09 ` Linus Torvalds
2003-12-02 19:13 ` Jan-Benedict Glaw
2003-12-02 19:39 ` Gene Heskett
2003-12-02 20:13 ` Jeff Garzik
2003-12-02 20:32 ` Stephan von Krawczynski
2003-12-02 21:48 ` Gene Heskett
2003-12-02 21:56 ` Linus Torvalds
2003-12-03 2:36 ` Harald Arnesen
2003-12-03 9:21 ` Helge Hafting
2003-12-02 19:59 ` snpe
2003-12-02 22:30 ` Mike Fedyk
2003-12-02 22:43 ` Arnaldo Carvalho de Melo
2003-12-03 14:08 ` snpe
2003-12-03 13:26 ` Christoph Hellwig
2003-12-02 8:18 ` Christoph Hellwig
2003-12-01 15:26 ` Norberto Bensa
2003-12-01 23:30 ` 2.6 security patches merged? was: " Mike Fedyk
2003-12-02 0:06 ` Chris Wright
2003-12-02 0:58 ` Måns Rullgård
2003-12-02 1:56 ` Chris Wright
2003-12-02 11:55 ` Marcelo Tosatti
2003-12-02 9:00 ` Matthias Andree
2003-12-02 11:54 ` Ionut Georgescu
2003-12-02 12:03 ` Arnaldo Carvalho de Melo
2003-12-02 13:13 ` Ionut Georgescu
2003-12-02 13:38 ` Ed Sweetman
2003-12-02 14:12 ` Arnaldo Carvalho de Melo
2003-12-02 16:01 ` Ionut Georgescu
2003-12-02 16:08 ` Jeff Garzik
2003-12-02 18:20 ` John Bradford
2003-12-02 20:19 ` Ville Herva
2003-12-02 21:40 ` Chris Wright
2003-12-02 20:09 ` Stephan von Krawczynski
2003-12-02 20:24 ` Arnaldo Carvalho de Melo
2003-12-02 20:45 ` Stephan von Krawczynski
2003-12-02 21:03 ` Arnaldo Carvalho de Melo
[not found] ` <Pine.LNX.4.58.0312021402360.17892@moje.vabo.cz>
[not found] ` <20031202131512.GU13388@conectiva.com.br>
[not found] ` <Pine.LNX.4.58.0312021433360.8417@moje.vabo.cz>
[not found] ` <20031202135423.GB13388@conectiva.com.br>
2003-12-02 20:21 ` Tomas Konir
2003-12-02 18:53 ` Mike Fedyk
2003-12-02 19:06 ` Valdis.Kletnieks
2003-12-02 23:13 ` Jose Luis Domingo Lopez
2003-12-03 18:22 ` bill davidsen
2003-12-04 1:24 ` jw schultz
2003-12-04 1:47 ` Mike Fedyk
2003-12-04 3:45 ` Tim Connors
2003-12-04 5:41 ` Willy Tarreau
2003-12-05 0:14 ` jw schultz
2003-12-01 15:56 ` Marcelo Tosatti
2003-12-01 21:02 ` David S. Miller
2003-12-03 21:26 ` Jan Rychter
2003-12-03 20:51 ` Jeff Garzik
2003-12-03 21:14 ` Willy Tarreau
2003-12-05 15:33 ` John Jasen
2003-12-05 22:23 ` Mike Fedyk
2003-12-06 15:49 ` Max Valdez
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 22:46 Ralf Baechle
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=3FCD0AA2.2030306@jpl.nasa.gov \
--to=driver@jpl.nasa.gov \
--cc=arjanv@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=raven@themaw.net \
--cc=spacey-linux-kernel@lenin.nu \
/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.