Re: Building driver loader from sources fails for FC5 kernel 2.6.18 + exponentially growing modprobe.conf

Henrik Nilsson <[email protected]> Tue, 31 Oct 2006 16:18:56 +0000
Newsgroups gmane.linux.kernel.driver-loader
Message-ID <[email protected]>
Hi Jonathan,

 > you mean that only saving the file with a text editor when the file
 > contains trailing comments is enough to trigger the problem?

No, not a text editor. Through the Fedora GUI tools for network
configuration, as stated in the first mail.

 > If this is the case, then it's very unlikely DriverLoader which is
 > making these changes. DriverLoader will only modify the file when:
 >
 > 1) DriverLoader was assigned to drive a new wireless device by the
 > kernel, this generally happen when the DriverLoader module is inserted
 > in the kernel in most cases.
 >
 > 2) When DriverLoader is uninstalled from the system.

Well, then it would seem that it's unlikely that driverloader is
involved, unless the GUI tools does do a bit of inserting and deletion
of modules. Which they might, I suppose.

 > Since most users are not affected by this problem and we never saw
 > this problem on our systems, it is quite possible that this is a
 > problem in a 3rd party software which is either not part of Fedora
 > Core or at least, not in the base install.

I don't have a terribly exotic setup though. Nothing beyond Fedora
in terms of network functionality beside driverloader. And no
non-standard drivers for anything else, either.

The system in question is a Dell Latitude D600, BTW. Might you know
what systems other users with similar systems are running?

 > You could perhaps attempt to find the problematic software on your
 > system with a SELinux rule for example.

That's a thought! Thanks!

Obviously, since I'm aware of the problem, it's not a huge issue for me
any more. Only puzzling and annoying. Hopefully this discussion will
save other people some trouble.

Best,

/Henrik

-- 
Henrik Nilsson
School of Computer Science and Information Technology
The University of Nottingham
[email protected]

This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.