On Mon, 2004-08-23 at 08:37, Greg Wildman wrote: > Listman said the following on 23/08/2004 13:23: > > In Redhat 9 I would load like this... > > > > add above eth0 8021q > > /etc/modules.conf > > > modprobe.conf does not like this. > > Of course. modules.conf != modprobe.conf > Doing a man on modprobe.conf will show you the way. Look for the > 'install' command > > E.g. install <eth0 module name> /sbin/modprobe 8021q; /sbin/modprobe > --ignore-install <eth0 module name> > > > > Anyone know what the syntax is for loading 8021q in modprobe.conf? > > > > Google didn't turn anything up. > > > > FC2 2.6.8-1.521 and modutils-2.4.26-16. > > > > Having list issues so please disregard dup, seems my posts get lost. > > Hopefully unsubscribing and then subscribing again resolves :-) > > > > Thanks, > > Ted > > > > > > > -- > Redmond, we have a problem. Yes we do Redmond, using install does not work for 8021q. If you add an install line like so install 8021q /sbin/modprobe 8021q modprobe will repeat the command until the machine is toast. By experimenting I was able to use alias vlan 8021q that will load the module. Not sure where I am going wrong here or their is something a miss. Also something must have changed in the network start script, as naming an interface eth0.9 does not work the same as in Redhat 9. I have to manually use vconfig to create the vlan before issuing service network start. Will start a new thread on this. Ted
