mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
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, 3 Dec 2006 09:30:31 +0100	[thread overview]
Message-ID: <20061203083031.GB900@1wt.eu> (raw)
In-Reply-To: <1165129510.5745.14.camel@lade.trondhjem.org>

On Sun, Dec 03, 2006 at 02:05:10AM -0500, Trond Myklebust wrote:
> On Sun, 2006-12-03 at 07:02 +0100, Willy Tarreau wrote:
> 
> > That's a valid point, but in fact, building with NFS client and serial
> > port support in the kernel on some archs is as common as building with
> > IDE driver and VGA console in the kernel on x86. With some architectures
> > used in light networked workstations, it's very common to boot from the
> > network (sparc & parisc come to mind, sorry to those I forgot), hence
> > this common practise.
> 
> I have no influence over the distributions' choice of kernel compiler
> options. The fact is, though, that few of them support nfsroot out of
> the box. AFAICS FC-6 is one of those that appears not to.
> 
> > > As for the initramfs support, hpa has assured me that his klibc
> > > distribution already has a full solution for NFS mounting on current
> > > kernels.
> > 
> > That's again where we see the limits of this ever-developping 2.6.
> > I'm not saying that doing this from initramfs+tools is a bad solution,
> > since it solves lots of problems, it's just that it is *much* different
> > from what was previously done.
> > 
> > People who have installed a distro on their machines will not be
> > able to upgrade their kernel past a certain point by hand. Upgrading
> > distro packages in such environments is generally not always an
> > option (particularly boot packages such as boot loader and kernel),
> > because the boot server is not necessarily running on the same
> > OS/distro, and sometimes the kernel needs different build options.
> 
> Most people that run nfsroot systems do so because that makes
> provisioning of new machines easy: if you only have one system image,
> then upgrading it is less of a challenge.

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.

Willy


  reply	other threads:[~2006-12-03  8:30 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 [this message]
2006-12-03 11:04                 ` Jan Engelhardt
2006-12-03 16:59                 ` Trond Myklebust
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=20061203083031.GB900@1wt.eu \
    --to=w@1wt.eu \
    --cc=MrUmunhum@popdial.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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®