[lkml]   [2004]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: insmod module-loading errors, Linux-2.6.9
On Mon, 08 Nov 2004 12:52:18 EST, linux-os said:

> There are certainly work-arounds for problems that shouldn't
> exist at all. So, every time I do something to a kernel, I
> have to change whatever the EXTRAVERSION field is? Then, when
> a customer demands that the kernel version be exactly the
> same that was shipped with Fedora or whatever, I'm screwed.

If you didn't have the foresight to keep that kernel version around,
there isn't much we can do to help you. Yes, this may mean you have
a big bunch of /usr/src/linux-2.6.* directories.

Note that you can *still* get screwed unless you keep the same
compiler toolchain around...

> They simply should not have removed the "-f" option of
> insmod. It's just that simple. This option allowed transient
> (possible) incompatibilities so that one could be productive
> and not spend a whole day reinstalling from a distribution
> CD because the new modules wouldn't work because somebody
> decided that their special VERMAGIC_STRING was so ")@*&#$%)"
> important that they preempted my work. Don't get me started....

Yes, instead you can spend a whole day reinstalling from a
distribution CD, and then restoring user files from backup,
because the new module you just 'insmod -f' had a different
number of parameters to some kernel call, and as a result your
stack got smashed and took the root filesystem with it....
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 14:07    [W:0.091 / U:2.568 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site