On (15/07/04 20:18), Clive Menzies wrote: > On (15/07/04 20:40), Sven Luther wrote: > > On Thu, Jul 15, 2004 at 05:10:33PM +0100, Clive Menzies wrote: > > > On (15/07/04 18:00), Sven Luther wrote: > > > > > > > Ah! I don't have discover on my production system which is probably > > > > > why > > > > > they loaded out of sequence. I don't use firewire, so presumably I > > > > > could remove this module? > > > > > > > > Well, you just need to blacklist it in /etc/hotplug/blacklist. > > > Hmm...OK, I won't ask how ;) I'll just nip off to google and have a > > > look ;) > > > > Get the name of the module, and add it to the /etc/hotplug/blacklist > > file. It is a trivial thing to do, which is why i didn't explain more. > I'd already deduced that from the helpful comments in the blacklist > file ;) But thanks - nevertheless, having done that it didn't seem to > make any difference to where the sungem module was allocated - it's > still eth1. So I've left it at that - it's no big deal - just part of my > education ;) Hi Sven
Installing discover1 sorted the problem - the sungem is now at eth0 ;) I'm happy now ;) Thanks Clive -- http://www.clivemenzies.co.uk strategies for business
