Re: Upgraded kmod, but --ignored linux & glibc, modules still in /lib - can I reboot safely?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]




On 7/15/2012 3:55 PM, C Anthony Risinger wrote:
On Sun, Jul 15, 2012 at 2:25 PM, David Benfell
<benfell@xxxxxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/15/12 08:07, Leonid Isaev wrote:
The kernel is not new, but the same with a changed location of the
modules. Why would you ever want to mask linux?

Those of us who are running Linodes may well all share this issue,
because Linode supplies the kernel. But isn't this what kmod is for (I
hope, I hope!)?
it's pretty easy to run a custom kernel on Linode -- that's what i do
with mine at least.

... prob not really an answer in your mind :-) but a possibility.

personally i'm curious why it's an issue at all -- if /lib/ is a
symlink, why can't modules in /usr/lib/ be found?  doesn't kmod follow
symlinks? ... all my stuff is working fine, but now i'm compelled to
seek the answer.

I am having no troubles at all using 3.4.2-linode44 on an i686 instance.



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux