I'm not sure that the default route is being set in the following situation: Relevant portion of control file: ... </interfaces> <routing config:type="list" > <route> <destination>default</destination> <device>eth0</device> <gateway>192.168.0.1</gateway> <netmask>0.0.0.0</netmask> </route> </routing> </networking> I'm installing using DHCP to initially identify the host (was having trouble with ip=). The client does not use DHCP once it is installed. My config file specifies <BOOTPROTO>static</BOOTPROTO> for all NICs. I'm guessing that DHCLIENT_SET_DEFAULT_ROUTE="yes" is being left in /etc/sysconfig/network/dhcp due to DHCP being available during initial install, and that is also causing the <route> configuration above to not take. I'm going to use a <file_path>/etc/sysconfig/network/routes</file_path> workaround for now. Please let me know if there are any additional Profile Elements not documented at: http://www.suse.com/~nashif/autoinstall/autoyast2/index.html I like autoinstall/autoyast better than ALICE (which I was just recently trying to learn after a successful history with Solaris Jumpstart). I really appreciate Anas' and anyone else's work in creating this. Thanks! John
Hi, * John Young <john_young@sonic.net> [May 10. 2002 23:45]:
I'm not sure that the default route is being set in the following situation:
Relevant portion of control file: ... </interfaces> <routing config:type="list" > <route> <destination>default</destination> <device>eth0</device> <gateway>192.168.0.1</gateway> <netmask>0.0.0.0</netmask> </route> </routing> </networking>
I'm installing using DHCP to initially identify the host (was having trouble with ip=). The client does not use DHCP once it is installed. My config file specifies <BOOTPROTO>static</BOOTPROTO> for all NICs.
I'm guessing that DHCLIENT_SET_DEFAULT_ROUTE="yes" is being left in /etc/sysconfig/network/dhcp due to DHCP being available during initial install, and that is also causing the <route> configuration above to not take. I'm going to use a <file_path>/etc/sysconfig/network/routes</file_path> workaround for now.
Unfortunatly this seems to be a bug. It is fixed now. More infor can be found here: http://www.suse.de/~nashif/autoinstall/bugs.html ( will show up on web server soon)
Please let me know if there are any additional Profile Elements not documented at: http://www.suse.com/~nashif/autoinstall/autoyast2/index.html
Not really, what are you missing?
I like autoinstall/autoyast better than ALICE (which I was just recently trying to learn after a successful history with Solaris Jumpstart). I really appreciate Anas' and anyone else's work in creating this.
Thanks, Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
[route stuff deleted]
Unfortunatly this seems to be a bug. It is fixed now. More infor can be found here: http://www.suse.de/~nashif/autoinstall/bugs.html ( will show up on web server soon)
Thanks, Anas!
Please let me know if there are any additional Profile Elements not documented at: http://www.suse.com/~nashif/autoinstall/autoyast2/index.html
Not really, what are you missing?
Nothing really comes to mind right now, just wanting to learn more about autoyast2. I wondered a little about setting variables from rc.config, etc., but that is not important as I do that through another method. I also wondered about perhaps some sort of "include" directive which would allow one to make several files/components that the control file would call - but I am guessing that the classes approach does something like that. Also, I don't really need that as I am doing quite well with <script></script>. That hook enables one to then do pretty much anything. Nice job on autoyast2. I'm grateful you have created this tool. Thanks, John
* John Young <john_young@sonic.net> [May 13. 2002 22:18]:
[route stuff deleted]
Unfortunatly this seems to be a bug. It is fixed now. More infor can be found here: http://www.suse.de/~nashif/autoinstall/bugs.html ( will show up on web server soon)
Thanks, Anas!
Please let me know if there are any additional Profile Elements not documented at: http://www.suse.com/~nashif/autoinstall/autoyast2/index.html
Not really, what are you missing?
Nothing really comes to mind right now, just wanting to learn more about autoyast2. I wondered a little about setting variables from rc.config, etc., but that is not important as I do that through another method.
Well, this is possible, take a look at : http://w3.suse.de/~nashif/autoinstall/autoyast2/x712.html
I also wondered about perhaps some sort of "include" directive which would allow one to make several files/components that the control file would call - but I am guessing that the classes approach does something like that.
No, the classes work only 'offline' or before you have installed anything. I am currently looking into using some XML features which will allow including external entities (XInclude). Another feature that might be comeing is the usage of XML-RPC, but this still in the testing phase and you need to have an XML-RPC server running to serve data..
Also, I don't really need that as I am doing quite well with <script></script>. That hook enables one to then do pretty much anything.
Yep. scripts are always the last resort, but we are trying to provide as many configuration options as possible in a native way rather than let the user hack their own scripts
Nice job on autoyast2. I'm grateful you have created this tool.
Thanks again, Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
participants (2)
-
Anas Nashif -
John Young