| 1 |
On 10/05/06, Devon Miller <devon.c.miller@×××××.com> wrote: |
| 2 |
> On 5/10/06, Paul B. Henson <henson@×××.org> wrote: |
| 3 |
> > Unless it has changed recently, the system I just installed last month |
| 4 |
> > actually looks for it in /usr/src/linux, not /boot. It still complains |
| 5 |
> > during boot even though I actually have one there, presumably it is |
| 6 |
> looking |
| 7 |
> > before filesystems are mounted. |
| 8 |
> > |
| 9 |
> |
| 10 |
> Ugh, then it's a duet between /sbin/module-update and /sbin/rc. Looking in |
| 11 |
> /usr/src/linux is just plain wrong. If for any reason I build a kernel, but |
| 12 |
> don't install it, then it's not just looking for data from an unmounted |
| 13 |
> filesystem (/boot or /usr) but it's also looking for the *wrong* System.map. |
| 14 |
> I'm going to file a bug on this. I can imagine cases where this might leave |
| 15 |
> a system hosed. |
| 16 |
|
| 17 |
I think the latest stable baselayout fixed this (i.e. I'm not getting |
| 18 |
this error at boot time anymore). It was reported some time ago: |
| 19 |
|
| 20 |
https://bugs.gentoo.org/show_bug.cgi?id=104288 |
| 21 |
|
| 22 |
-- |
| 23 |
Regards, |
| 24 |
Mick |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives