>Ingo, > >> Just trying to clear that up: As I understood it the problem was that >> the >> OBOSInstall jam rule was buggy and and the drivers were always >> installed on >> a `jam all' and not just on a `jam install-networking' (well, this >> part is >> a fact :-), which left people who just built the whole tree with no >> networking since the drivers installed from our tree were overriding >> (as >> opposed to overwriting) Be's, as they were installed in >> /boot/home/config/... > >Yeah, you're absolutly right! >And override is the word I should have used, yes. So, when I am testing, am I using our rtl8139 driver, or Be's? I have an rtl8139 driver in boot/home/config/kernel/drivers/bin I want to test against a "known good" driver, namely Be's, so I dont have to consider the driver to be at fault... Update: I removed the driver from /boot/home/config... and things still work ok. I am using Be's driver. That other driver may have been there from when I was last testing out the stack (in June) Brennan