1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
<!doctype linuxdoc system>
<article>
<title>Missing commands
<abstract>
<em/Linuxconf/ can't locate a command on your system. Some actions
are required.
</abstract>
<sect>Why something is missing
<p> There are different reasons why something may be missing from your
system.
<itemize>
<item>You did not install all the packages. Most <em/Linux/
distributions let you add the packages on the fly. On
<em/Debian/ systems, use the <tt/dselect/. On <em/Red Hat/
systems, use RPM or <tt/Gnome-RPM/. On <em/Slackware/ systems,
use <tt/pkgtool/.
<item>Your distribution has non-standard components. Most distributions
(for some time now) agree on the Filesystem Hierarchy Standard,
a document which describes where things should go. However,
sometimes things aren't exactly right. Some <em/Red Hat/ 3.0.3
CD-ROMs contained <tt>/usr/sbin/portmap</tt> and some contained
<tt>/usr/sbin/rpc.portmap</tt>. Most distributions contained the
latter.
Anyway, if you will have non-standard components, you'll need to
investigate and fix the path used by <em/Linuxconf/.
<item>You did not intend to run this package anyway, so you did
not install it.
</itemize>
<sect>What you can do
<p> If you select yes, a dialog will be opened allowing you to disable
this command or change the path. If you accept the change, Linuxconf
will retry the command and continue its normal processing.
If you decide to disable the command, you will be able to re-enable
it later using the option <tt/List all command and daemons/ from the
main menu. Further, in the Linuxconf log
(<tt>/var/run/netconf.log</tt>), <em/Linuxconf/ will remind you that
this command would have been started if <em/Linuxconf/ was allowed to.
It might be handy later if you decide to install the command after all.
</article>
|
