All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Montecchiani <luca.montecchiani@teamfab.it>
To: Chip Schweiss <chip@innovates.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18pre21 - IP kernel level autoconfiguration
Date: Thu, 16 Nov 2000 19:01:33 +0100	[thread overview]
Message-ID: <3A1420FD.528D2C41@teamfab.it> (raw)

> It seem somewhere between 2.2.17 and the current 2.2.18 kernel, IP 
> kernel level autoconfiguration has been broken. Upon kernel loading 
> the Ethernet card is detected and loaded properly, but the bootp code 
> never seems to be executed and mounting the root partion via NFS then 
> fails from lack of IP configuration. 
> I haven't had any luck tracing down the root of this problem. 
> Anyone else experience this problem or have a patch to fix it? 

Hi!

I've the same behavior here:

 server kernel : 2.2.17
 dhcpd         : 2.0b1pl29
 client kernel : 2.2.18-21
 client cmdline: root=/dev/nfs nfsroot=/foo/bar ip=bootp

After some quick tests seem that if you want bootp
you _need_ to compile the client's kernel with _only_ bootp,
if you have also dhcp, it doesn't work :(

Dhcp into kernel is COOL and I hope that someone is
porting on 2.4 ;), doesn't seem that hard

hope this help,
luca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-16 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16 18:01 Luca Montecchiani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-17 15:17 Re: 2.2.18pre21 - IP kernel level autoconfiguration chip
2000-11-17 15:32 ` Luca Montecchiani
2000-11-16 16:16 chip

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=3A1420FD.528D2C41@teamfab.it \
    --to=luca.montecchiani@teamfab.it \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chip@innovates.com \
    --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 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.