vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am trying to setup aliass for eth0 on a slackware 9.1 box. I am confused as the init scripts have changed since slackware 9. What is the correct syntax for the rc.inet1.conf file. I have not been able to find any info about this file. Thanks Jeff Turley |
| |||
| On Wed, 07 Jan 2004 20:50:26 GMT, Jeff Turley <jaturley@sbcglobal.net> wrote: > What is the correct syntax for the rc.inet1.conf file. Have a look at the example file; it's commented very well, so it should be fairly easy to figure out what does what. The only thing that might not be immediately obvious is that the number in square brackets is the number of the interface (e.g '0' means 'eth0'). -- Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69 "We demand rigidly defined areas of doubt and uncertainty." - Douglas Adams |
| ||||
| In article <mi_Kb.21977$P%1.21218537@newssvr28.news.prodigy.c om>, Jeff Turley wrote: > I am trying to setup aliass for eth0 on a slackware 9.1 box. I am If you are referring to the alias for the NIC driver module, that would be done in /etc/modules.conf or /etc/modprobe.conf. > confused as the init scripts have changed since slackware 9. What is the The init scripts assume that the driver is already loaded. You can set an alias as above to do this, or have the driver explicitly loaded in /etc/rc.d/rc.netdevice. This file is generated by "netconfig" and has not changed in syntax: "/sbin/modprobe $DRIVER". > correct syntax for the rc.inet1.conf file. I have not been able to find It is a shell (bash) script which is sourced by rc.inet1. Variables set in rc.inet1.conf control what happens in rc.inet1. Read rc.inet1 and refer back to rc.inet1.conf. If it doesn't make sense, then you probably don't understand shell scripting very well, and you would not be advised to edit these init scripts directly. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |