> In the process of compiling a new kernel, I renamed my /lib/modules/2.2.17
> file. I won't take you along the convoluted process that made me think that
> that was a good idea. Anyway ...
>
> I can't boot up. I keep getting an endless series of messages that
> /lib/modules/2.2.17 can't be acc
> In the process of compiling a new kernel, I renamed my /lib/modules/2.2.17
> file. I won't take you along the convoluted process that made me think
that
> that was a good idea. Anyway ...
>
> I can't boot up. I keep getting an endless series of messages that
> /lib/modules/2.2.17 can't be acce
"Keith & Cecile Schooley" wrote:
>In the process of compiling a new kernel, I renamed my /lib/modules/2.2.17
>file. I won't take you along the convoluted process that made me think that
>that was a good idea. Anyway ...
>
>I can't boot up. I keep getting an endless series of messages t
In the process of compiling a new kernel, I renamed my /lib/modules/2.2.17
file. I won't take you along the convoluted process that made me think that
that was a good idea. Anyway ...
I can't boot up. I keep getting an endless series of messages that
/lib/modules/2.2.17 can't be accessed becaus
4 matches
Mail list logo