mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Schmidlkofer <menion@srci.iwpsd.org>
To: Wakko Warner <wakko@animx.eu.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.6 and netboot
Date: Thu, 19 Jul 2001 10:10:51 -0600	[thread overview]
Message-ID: <01071910105102.01826@widmers.oce.srci.oce.int> (raw)
In-Reply-To: <20010719082650.A26980@animx.eu.org>
In-Reply-To: <20010719082650.A26980@animx.eu.org>

On Thursday 19 July 2001 06:26 am, Wakko Warner wrote:
> I'm using a kernel that is dd'd to a floppy to net boot linux on random
> machines.  I noticed that 2.4.6 won't get it's IP from the server (it won't
> even attempt it).  2.4.4 works
>
> If any more info is needed, just ask.

Sine 2.4.4 I have been unable to make ipconfig automagically go, and I think 
that this configuration is not supported.   At least, with my limited 
knowledge of how ipconfig works  you must to pass: 'ipconfig=dhcp', or 
ipconfig='bootp' to the kernel at boot time.  I built a LILO disk, but
I think that syslinux would work.  Also, I did eventually successfully get an 
Xterminal running.

After 2.4.4 ipconfig was changed to the ipconfig= style of behaviour.  I 
don't know why, but someone does.  I think it has to do with implementation 
cahnges to allow for modularized NIC's to use ipautoconfig.   This seems 
insane that functionality was cut in order to do this.

Also, I have been unable to make bootp work for nfsboot, but I suspect my 
bootp server - not the kernel.

BACK to the point.  Since 2.4.5 I have had to use lilo, and add a line that 
says 'nfs=[all that stuff] ipconfig=dhcp'

good luck.

js


  parent reply	other threads:[~2001-07-19 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 12:26 Wakko Warner
2001-07-19 14:51 ` Ryan Sweet
2001-07-19 16:32   ` Wakko Warner
2001-07-19 16:10 ` Joshua Schmidlkofer [this message]
2001-07-19 16:35   ` Wakko Warner

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=01071910105102.01826@widmers.oce.srci.oce.int \
    --to=menion@srci.iwpsd.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wakko@animx.eu.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 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®