From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Willy Tarreau <w@1wt.eu>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
William Estrada <MrUmunhum@popdial.com>,
linux-kernel@vger.kernel.org
Subject: Re: Mounting NFS root FS
Date: Sun, 03 Dec 2006 11:59:50 -0500 [thread overview]
Message-ID: <1165165190.711.57.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20061203083031.GB900@1wt.eu>
On Sun, 2006-12-03 at 09:30 +0100, Willy Tarreau wrote:
> It's one use, but another one is for diskless terminals, often built
> from old systems. In this case, it's to avoid the cost, noise, power
> consumption and failures associated to disks. It's quite often done
> one radically different archs/OS between the server and the clients,
> making the upgrade more complicated.
It is naive to believe that the only thing you need to keep up to date
is the kernel itself: if you are at all worried about security, then
upgrades are a fact of life. Depending on your choice of distribution,
then you can make that process easy or difficult.
As for the kernel, nobody has promised you that we would keep all
possible implementations of a given feature around forever. As and when
we develop better ways of implementing a set of features, we may want to
remove the old ways. You will be given advance notice in
Documentation/feature-removal-schedule.txt, and it will be your choice
whether or not you want to follow the upgrade path, or stick with your
existing setup.
What we will not do is to maintain a bunch of parallel kernel trees or
unduly bloat the kernel forever in order to support old systems: that is
the job of those distributions that promise you n years legacy support.
Trond
next prev parent reply other threads:[~2006-12-03 17:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 19:03 William Estrada
2006-12-02 19:07 ` Jan Engelhardt
2006-12-02 21:15 ` Willy Tarreau
2006-12-02 21:56 ` Jan Engelhardt
2006-12-02 22:55 ` Willy Tarreau
2006-12-03 2:37 ` Trond Myklebust
2006-12-03 6:02 ` Willy Tarreau
2006-12-03 7:05 ` Trond Myklebust
2006-12-03 8:30 ` Willy Tarreau
2006-12-03 11:04 ` Jan Engelhardt
2006-12-03 16:59 ` Trond Myklebust [this message]
2006-12-04 11:51 ` Janne Karhunen
2006-12-04 15:29 ` Trond Myklebust
2006-12-04 17:12 ` Janne Karhunen
2006-12-04 18:21 ` Trond Myklebust
2006-12-04 20:05 ` Janne Karhunen
2006-12-04 21:27 ` Trond Myklebust
2006-12-05 0:20 ` H. Peter Anvin
2006-12-04 20:03 ` Jan Engelhardt
2006-12-04 20:27 ` Janne Karhunen
2006-12-04 20:47 ` Trond Myklebust
2006-12-05 18:43 ` Jan Engelhardt
2006-12-05 19:37 ` Trond Myklebust
2006-12-05 19:59 ` Jan Engelhardt
2006-12-05 20:12 ` Trond Myklebust
2007-01-27 14:47 ` Jan Engelhardt
2006-12-07 22:27 ` Hans-Peter Jansen
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=1165165190.711.57.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=MrUmunhum@popdial.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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®