That's great, thanks, but building them isn't the problem. I'm still new to
the Linux module structure, and I was wondering how to load a NIC module
after boot time so that TCP/IP recognises it on eth0 (I'm used to older Unix
kernels where everything had to be build it, or more recently, the Microsoft
structure from NT where you first load a NIC, then the other protocol layers
on top, and you can't slide lower-level protocols in either.)
I'll go back and look how "pcmcia start" does it, and also hunt through the
boot time code for where it uses the IP network parameters set up in
settings.s
---------------------------------------------------------------
|\ | o _ |/ Life's like a jigsaw
| \| | |_ |\ You get the straight bits
But there's something missing in the middle
Nick Brown, Strasbourg, France (Nick(dot)Brown(at)coe(dot)fr)
---------------------------------------------------------------
> -----Original Message-----
> From: Tom Oehser [SMTP:[EMAIL PROTECTED]]
> Sent: 09 April 1999 21:24
> To: BROWN Nick
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: [tomsrtbt] Other Ethernet cards - modules
>
>
> > 1. Get Tom's .config file and add the cards to the kernel (do you make
> the
> > .config file available, Tom ?)
> > 2. Build the modules myself (done) and load them with insmod, then use
> > ifconfig ("too much typing" !).
> > 3. Build the modules and have them load round about boot time;
> basically, so
> > that the card is there as eth0 when the rest of the network stuff needs
> it.
>
> You missed (4.), look in ftp://www.toms.net/rb/add-ons/. Most all of them
> are either included with the default tomsrtbt, or are already available
> for download. Then use unpack.s/buildit.s to put them in... -Tom
