From: "Jason Perlow" <perlow@hotmail.com>
To: ilh@sls.lcs.mit.edu
Cc: redhat-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Adaptec 19160 Problems
Date: Mon, 08 Jan 2001 20:04:24 [thread overview]
Message-ID: <F1757dcLdZs3JcXu98s00012935@hotmail.com> (raw)
So you are saying this was fixed in 2.2.18? Which distro uses that by
default now?
We need to get the distros to come up with boot floppy images for this then
because 19160 is a very popular host adapter. Its not like its weirdo
hardware. Waiting for an updated distro is a real pain in the ass if this
can be fixed easily by just updating the boot disk images.
Jason
From: I Lee Hetherington <ilh@sls.lcs.mit.edu>
To: Jason Perlow <perlow@hotmail.com>
Subject: Re: Adaptec 19160 Problems
Date: Mon, 08 Jan 2001 14:45:26 -0500
Well, 2.2.18 is newer than what Red Hat 6.2 installer uses.
You could use Ghost or Drive Image to copy things over, or if you can
mount both simultaneously (booted from IDE), you can just make your SCSI
partition and cp -a everything over. That is, everything except for
/lost+found, /proc, and any other mount points.
I agree this is ugly, but what can you do when the Red Hat (or
otherwise) install kernel doesn't really support your hardware?
I suppose it is possible to update the install kernel or specific
modules, and I think I once succeeded in doing this, but it is even
uglier!
--Lee
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-08 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 20:04 Jason Perlow [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 18:46 Jason Perlow
2001-01-08 18:30 Jason Perlow
2001-01-08 18:39 ` I Lee Hetherington
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=F1757dcLdZs3JcXu98s00012935@hotmail.com \
--to=perlow@hotmail.com \
--cc=ilh@sls.lcs.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=redhat-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®