kopia lustrzana https://gitlab.com/sane-project/website
69 wiersze
2.9 KiB
HTML
69 wiersze
2.9 KiB
HTML
<!-- received="Wed Aug 11 15:20:45 1999 PDT" -->
|
||
<!-- sent="Wed, 11 Aug 1999 23:22:01 +0100 (GMT)" -->
|
||
<!-- name="Nick Lamb" -->
|
||
<!-- email="njl98r@ecs.soton.ac.uk" -->
|
||
<!-- subject="Re: a few questions" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Pine.LNX.4.10.9908111950430.4506-100000@bastion.nl3155vj16.vanderkooij.org" -->
|
||
<title>sane-devel: Re: a few questions</title>
|
||
<h1>Re: a few questions</h1>
|
||
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
|
||
<i>Wed, 11 Aug 1999 23:22:01 +0100 (GMT)</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#102">[ date ]</a><a href="index.html#102">[ thread ]</a><a href="subject.html#102">[ subject ]</a><a href="author.html#102">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0103.html">Petter Reinholdtsen: "Re: SANE 1.0.1 under DEC UNIX 4.0"</a>
|
||
<li> <b>Previous message:</b> <a href="0101.html">Oliver Rauch: "Re: Discussion about SANE and TWAIN..."</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
On Wed, 11 Aug 1999, Petter Reinholdtsen wrote:<br>
|
||
<p>
|
||
<i>> </i><br>
|
||
<i>> > Load it with:</i><br>
|
||
<i>> > insmod sg</i><br>
|
||
<i>> </i><br>
|
||
<i>> You should use 'modprobe sg' instead to handle dependencies.</i><br>
|
||
<p>
|
||
On Wed, 11 Aug 1999, Hugo van der Kooij wrote:<br>
|
||
<i>> The `modprobe -a` at boot up does take of that allready.</i><br>
|
||
<i>> </i><br>
|
||
<i>> Hugo.</i><br>
|
||
<p>
|
||
modprobe -a? At boot up?<br>
|
||
<p>
|
||
Either you mean "depmod -a", which isn't necessary at bootup and is only<br>
|
||
done as a precaution in case you've rebuilt a modular kernel without<br>
|
||
reading the associated documentation... In which case NO, that doesn't<br>
|
||
take care of this at all, it just creates a dependency tree for later.<br>
|
||
<p>
|
||
Or you really do mean "modprobe -a", in which case this whole discussion<br>
|
||
was redundant because that loads ALL THE MODULES whether they are necessary<br>
|
||
or not, and the SCSI generic is already running. I doubt this is true,<br>
|
||
because it defeats half the point of a modular kernel.<br>
|
||
<p>
|
||
Regardless - Yes, just loading "sg.o" would likely work on most systems<br>
|
||
because SCSI core and SCSI mid are already loaded and running, but it<br>
|
||
is still best practise to always use "modprobe" unless you've a good<br>
|
||
reason not to do so.<br>
|
||
<p>
|
||
Nick.<br>
|
||
<p>
|
||
<p>
|
||
<pre>
|
||
--
|
||
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
||
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
||
</pre>
|
||
<!-- body="end" -->
|
||
<p>
|
||
<ul>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0103.html">Petter Reinholdtsen: "Re: SANE 1.0.1 under DEC UNIX 4.0"</a>
|
||
<li> <b>Previous message:</b> <a href="0101.html">Oliver Rauch: "Re: Discussion about SANE and TWAIN..."</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|