linux-kernel - Re: Upgrading kernel across multiple machines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <C0FFAB00.89A2%brian@visionpro.com>
Date:	Wed, 09 Aug 2006 15:08:48 -0700
From:	Brian McGrew <brian@...ionpro.com>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	<linux-kernel@...r.kernel.org>
Subject: Re: Upgrading kernel across multiple machines

It would appear that way; but I assure you, the modules are in
/lib/modules/2.6.16.16/

:b!


On 8/9/06 3:03 PM, "Sam Ravnborg" <sam@...nborg.org> wrote:

> On Wed, Aug 09, 2006 at 02:52:41PM -0700, Brian McGrew wrote:
>> Hello,
>> 
>> I'm using a Dell PE1800 and I've built a new 2.6.16.16 kernel on the machine
>> that works fine.  However, if I tar up /lib/modules/2.6.16.16 and /boot and
>> move it onto another Dell PE1800 running the exact same software (FC3/Stock
>> install) the new kernel doesn't boot.
>> 
>> On machine #1 life is good but moving it to machine #2, I get
>> 
>> /lib/ata_piix.ko: -l unknown symbol in module.
> Looks like your kernel modules has ended up in /lib somehow.
> Cannot see why atm.
> 
> Sam


:b!

-- 
Brian McGrew    { brian@...ionpro.com || brian@...bledimenison.com }

> For economy reasons the light at the end of the tunnel has been turned off!

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/