mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Raj <obelix123@toughguy.net>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	okir@monad.swb.de
Subject: Re: [TRIVIAL][PATCH]:/proc/fs/nfsd/
Date: Sat, 13 Mar 2004 18:26:39 +0100	[thread overview]
Message-ID: <20040313172639.GW14833@fs.tum.de> (raw)
In-Reply-To: <40485803.7060102@toughguy.net>

On Fri, Mar 05, 2004 at 04:05:47PM +0530, Raj wrote:
> Neil Brown wrote:
>...
> >Does it need fixing??
> >
> >If you remove this, then people who compile a kernel without nfsd
> >support, and then later decide to compile an nfsd module and load it,
> >will not be able to mount the nfsd filesystem at the right place.
> > 
> >
> 
> I guess choosing nfsd either builtin or as a module will cause a rebuild 
> of some components of the main kernel and hence a
> reboot is anyway need. Pls correct me if i am wrong.

You are wrong.

If choosing nfsd as a module, no component of the main kernel needs to 
be changed to load the module on i386.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-03-13 17:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05  9:09 [TRIVIAL][PATCH]:/proc/fs/nfsd/ Raj
2004-03-05 10:08 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Neil Brown
2004-03-05 10:35   ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Raj
2004-03-13 17:26     ` Adrian Bunk [this message]
2004-03-05  9:47 [TRIVIAL][PATCH]:/proc/fs/nfsd/ Petr Vandrovec
2004-03-05 11:28 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Neil Brown

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=20040313172639.GW14833@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=obelix123@toughguy.net \
    --cc=okir@monad.swb.de \
    /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®