1 |
The issue your raising is completely different than the one posted. |
2 |
In your system you did compile support for modules, that's why the commands |
3 |
you've mentioned solved the problem. The original post is about a system in |
4 |
which modules support is disabled on purpose. In such a system |
5 |
modules-update will not help. In fact the script should not look for |
6 |
modules.dep since it is relevant for systems without modules support. |
7 |
|
8 |
System.map is a file which is generated when compiling the kernel. It is |
9 |
specific to each kernel being compiled. AFAIK It has to reside in the boot |
10 |
partition in order for the kernel to find it while loading. |
11 |
|
12 |
Asaf |
13 |
|
14 |
|
15 |
On 5/15/07, Darren Smith <dsmith@××××××××××××.ca> wrote: |
16 |
> |
17 |
> We were getting similar messages on a recently built machine including a |
18 |
> "FATAL: Could not load System.Map: Missing....." right after a message |
19 |
> about loading modules.dep. Didn't seem to affect proper function at all, |
20 |
> but any error is bothersome to me, so... |
21 |
> |
22 |
> This was fully resolved by the following set of commands: |
23 |
> |
24 |
> # env-update && source /etc/profile |
25 |
> # modules-update |
26 |
> # reboot |
27 |
> |
28 |
> Not sure if this issue is entirely similar... seems related though. |
29 |
> |
30 |
> -D |
31 |
> |
32 |
> > -----Original Message----- |
33 |
> > From: Charles Taylor [mailto:security@××××××.net] |
34 |
> > Sent: May 11, 2007 3:11 AM |
35 |
> > To: gentoo-hardened@l.g.o |
36 |
> > Subject: RE: [gentoo-hardened] Could not load modules.dep |
37 |
> > |
38 |
> > Don't mess with your scripts... Never know when it |
39 |
> > will break something... As root, simply: |
40 |
> > |
41 |
> > touch /lib/modules/kernel-hardened-2.18-r6/modules.dep |
42 |
> > |
43 |
> > Problem solves, and no config/script file tinkering! |
44 |
> > |
45 |
> > It's been working perfectly for me for months. |
46 |
> > |
47 |
> > Charles |
48 |
> > |
49 |
> > --- Clemente Aguiar |
50 |
> > <clemente.aguiar@××××××××××××××××.pt> wrote: |
51 |
> > |
52 |
> > > |
53 |
> > > See below some feedback on the suggestions given: |
54 |
> > > |
55 |
> > > > -----Mensagem original----- |
56 |
> > > > De: Igor Novgorodov [mailto:igor@××××.net] |
57 |
> > > > Enviada: quinta-feira, 10 de Maio de 2007 14:10 |
58 |
> > > > Para: Clemente Aguiar |
59 |
> > > > Assunto: Re: [gentoo-hardened] Could not load |
60 |
> > > modules.dep |
61 |
> > > > |
62 |
> > > > > Since a while ago I have been getting a series |
63 |
> > > of errors at |
64 |
> > > > start-up |
65 |
> > > > > on my servers, such as: |
66 |
> > > > |
67 |
> > > > > "FATAL: Could not load |
68 |
> > > > > |
69 |
> > > /lib/modules/kernel-hardened-2.18-r6/modules.dep: |
70 |
> > > > > No such file or directory" |
71 |
> > > > |
72 |
> > > > > I configured my hardened kernels with "loadable |
73 |
> > > module support" |
74 |
> > > > > disabled, so I think that modules.dep could |
75 |
> > > never exist. |
76 |
> > > > |
77 |
> > > > > First of all, I can see these messages "fly" by |
78 |
> > > the console at |
79 |
> > > > > start-up, but it seems that they are not logged |
80 |
> > > (I can't find them |
81 |
> > > > > anywhere). Shouldn't they get logged somewhere? |
82 |
> > > > You can try setting RC_BOOTLOG="yes" in |
83 |
> > > /etc/conf.d/rc |
84 |
> > > > Messages will be logged to /var/log/boot.msg |
85 |
> > > |
86 |
> > > I did as suggested and emerged |
87 |
> > > "app-admin/showconsole" as well (it is a |
88 |
> > > requirement for this to work), and most boot |
89 |
> > > messages where logged in |
90 |
> > > /varlog/boot.msg, but not all, and the ones I |
91 |
> > > mentioned where NOT |
92 |
> > > logged. |
93 |
> > > |
94 |
> > > |
95 |
> > > |
96 |
> > > > > Second, how can I get rid of the messages |
97 |
> > > altogether? |
98 |
> > > > Just do "rc-update del modules" to remove module |
99 |
> > > init script |
100 |
> > > > from startup |
101 |
> > > > |
102 |
> > > |
103 |
> > > I did as you suggested, but when I rebooted, a |
104 |
> > > warning was issued and |
105 |
> > > "modules" init script was automatically added back |
106 |
> > > to "boot". |
107 |
> > > |
108 |
> > > Any other suggestions? |
109 |
> > > |
110 |
> > > Clemente |
111 |
> > > -- |
112 |
> > > gentoo-hardened@g.o mailing list |
113 |
> > > |
114 |
> > > |
115 |
> > |
116 |
> > -- |
117 |
> > gentoo-hardened@g.o mailing list |
118 |
> |
119 |
> -- |
120 |
> gentoo-hardened@g.o mailing list |
121 |
> |
122 |
> |