From: Matt Domsch <Matt_Domsch@dell.com>
To: jlewis@lewis.org
Cc: Scott Long <scott_long@adaptec.com>, linux-raid@vger.kernel.org
Subject: Re: Adaptec aacraid
Date: Sun, 14 Mar 2004 22:28:48 -0600 [thread overview]
Message-ID: <20040315042848.GA3941@lists.us.dell.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0403142056490.1969@web1.mmaero.com>
On Sun, Mar 14, 2004 at 09:14:50PM -0500, jlewis@lewis.org wrote:
> I just took another look, and actually what it did was much worse. It
> looks at grub.conf and then rm's modules from /lib/modules for all kernels
> mentioned in grub.conf and then installs its own (if it has one). This
> left me with:
>
> # rpm -V kernel-smp-2.4.20-30.9
> .M...... /dev/shm
> missing /lib/modules/2.4.20-30.9smp/kernel/drivers/scsi/aacraid
> missing /lib/modules/2.4.20-30.9smp/kernel/drivers/scsi/aacraid/aacraid.o
>
> and no aacraid module anywhere in /lib/modules/2.4.20-30.9smp/.
>
> Fortunately, it didn't blow away the 2.4.20-30.9smp initrd, so I was able
> to extract the missing module from that, and put it back in place. I know
> the system would have booted just fine (since the module was in the
> initrd)...but man, that's _really_annoying_ behavior for an RPM. I
> haven't bothered reading the whole script (25kb), but AFAICT, it rm'd the
> modules and did not leave backup copies of them anywhere I've looked.
<shameless plug>
FWIW, this is *exactly* the reason DKMS exists - because every vendor
who offers a driver update does it a little differently. DKMS is
designed to standardize this, and make it really obvious when a given
driver has been updated, and to what version, for each kernel.
http://linux.dell.com/projects.shtml#dkms
</shameless plug>
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-03-15 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 23:10 Adaptec aacraid jlewis
2004-03-15 0:12 ` Scott Long
2004-03-15 0:39 ` jlewis
2004-03-15 1:00 ` Scott Long
2004-03-15 2:14 ` jlewis
2004-03-15 4:28 ` Matt Domsch [this message]
2004-03-15 4:50 ` ATA 100/133 Card Samuel Davidoff
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 14:51 Adaptec aacraid Salyzyn, Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040315042848.GA3941@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=jlewis@lewis.org \
--cc=linux-raid@vger.kernel.org \
--cc=scott_long@adaptec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.