On Mon, Jan 16, 2006 at 05:13:20AM -0800, hillbilly wrote:
>
> Chris Bannister wrote:
> > On Thu, Jan 12, 2006 at 01:08:13AM -0800, hillbilly wrote:
> > > Well, that works brilliantly!
> > > I created /etc/modprobe.conf/local and added to it the following
> > > lines...
> > >
> > > install parport
Chris Bannister wrote:
> On Thu, Jan 12, 2006 at 01:08:13AM -0800, hillbilly wrote:
> > Well, that works brilliantly!
> > I created /etc/modprobe.conf/local and added to it the following
> > lines...
> >
> > install parport /bin/true
> > install parport_pc /bin/true
> > install lp /bin/true
>
> We
On Thu, Jan 12, 2006 at 01:08:13AM -0800, hillbilly wrote:
> Well, that works brilliantly!
> I created /etc/modprobe.conf/local and added to it the following
> lines...
>
> install parport /bin/true
> install parport_pc /bin/true
> install lp /bin/true
Weird, why the reverse logic?
> and lo and
On 12 Jan 2006 00:45:10 -0800
"hillbilly" <[EMAIL PROTECTED]> wrote:
> Just a question to Marc Perrudin...
> In directory /etc/ only have a modprobe.d/ directory. Should the
> 'local' file be in there or should I create an /etc/modprobe.conf/
> directory as indicated in your response and place th
On Thu, Jan 12, 2006 at 12:45:10AM -0800, hillbilly wrote:
> Just a question to Marc Perrudin...
> In directory /etc/ only have a modprobe.d/ directory. Should the
> 'local' file be in there or should I create an /etc/modprobe.conf/
> directory as indicated in your response and place the 'local' f
Just one last point in case anyone is interested...
The file does not have to be called /etc/modprobe.d/local
It can be anything you like... such as /etc/modprobe.d/psychopath if
you like.
It seems that modprobe functions in such a manner as to scan and
process all files in the /etc/modprobe.d/ dir
Well, must modify that last claim that the modprobe.conf idea worked.
It did but the very presence of the /etc/modprobe.conf/local file (even
if empty) caused some other drivers to fail to load properly (or at
all, maybe). I discovered this when trying to access the floppy and
the system informed
Just a further note to Adam Porter in addition to my response on the
why and wherefore above, I discovered that the wierd behaviour with not
being able to access the status port appears to be specific to the
combination of Debian Sarge with the particular PC I was using. The
difficulty does not ap
Well, that works brilliantly!
I created /etc/modprobe.conf/local and added to it the following
lines...
install parport /bin/true
install parport_pc /bin/true
install lp /bin/true
and lo and behold, the drivers did not load.
Thank you, Marc and one and all for your responses.
--
To UNSUBSCRIBE
Just a question to Marc Perrudin...
In directory /etc/ only have a modprobe.d/ directory. Should the
'local' file be in there or should I create an /etc/modprobe.conf/
directory as indicated in your response and place the 'local' file in
that one instead?
--
To UNSUBSCRIBE, email to [EMAIL PROT
Thanks, I'll try that.
Please excuse the 'disorder' of my replies - something funny happened
when first loading the web page and I missed Marc's response.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I have a completely different use for the parport. However, 'why' is
irrelevant. If modules are only loadable, where's the flexibility?
What if you're fiddling around with various PCI cards or some such
experimentation? My application was previously run on RH9 and it was
easy to rmmod the lp, pa
OT, but how come you want to prevent it from loading?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hillbilly a écrit :
>Can ANYONE help?
>I am trying to prevent parport (and parport_pc, lp) from loading at
>bootup on Deb Sarge with no success short of brute force (hiding the
>actual module from the OS) which results in ugly messages about
>undefined symbols and is at best potentially dangerous
14 matches
Mail list logo
