Anas Nashif <nashif@suse.de> [22.05.2002 04:45]:

* Hella.Breitkopf@varetis.de <Hella.Breitkopf@varetis.de> [May 21. 2002 23:12]:

...

Hi List, hi Anas,

Anas Nashif's great documentation of his tool AutoYast2 mentions this:

Putting this to the bootcd kernel commandline, I expected the use of network device "eth1" for network setup (with dhcp):

linux netdevice=eth1 install=nfs://1.2.3.4/x/suse8.0 autoyast=nfs://1.2.3.5/y/auto.xml

Unluckily the information of the "netdevice" keyword seems to be ignored: ----- Trying to activate eth0 Setting up localhost...done timed out waiting for a valid DHCP server response

Sending DHCP request to eth0... no/incomplete answer Ok, that didn't work; see if we can activate another network device... No further network cards found; giving up. -----

Does linuxrc in this case actually loads both network devices periot to sending the DHCP request...

Previous to the run with eth0 there is an "empty" run. There is no try with eth1. Since on my machines both devices are using the same module, the loading of the correct module means both devices are available .. IIRC we've no "ifconfig -a" at that moment, but /proc/net/dev shows both interfaces. (But eth1 is not up).

...

If I do a "manual Installation", I *can* choose between two network devices. And fetching dhcp information and the following installation from "eth1" works. (An installation over "eth0" works, too - if there is a cable. But there are good reasons to use eth1 in this case. )

Other parameters (I tried e.g. ip,netmask,gateway) work as expected, so

why

...

netdevice doesn't?

We are investigating....

...

Hella - my next boot cd should include that. (Somebody interested in a description, how to build a crude boot cd for network installation?)

Building a boot CD will be part of the next release and would be provided as a replacement for similar functionality available with alice.

Yes, that would quite nice and usefull.

Are you interested in a description or are you offering one...? If you have one, that might help me while putting the docs for next release :-)

I'm offering. I've to document the stuff I do, anyway. But it's a crude not very elegant solution. (So, yes, I'd be interested in a *better* description, too.)

Regards, Anas

Regards, Hella