* Hella.Breitkopf(a)varetis.de <Hella.Breitkopf(a)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://184.108.40.206/x/suse8.0
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...
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
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
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 :-)
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
Anas Nashif <nashif(a)suse.com>om>, SuSE Linux AG
Montreal (Laval), Canada