public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "Martin G. McCormick" <martin@dc.cis.okstate.edu>
To: blinux-list@redhat.com
Subject: Re: Still Having Fun with SCSI Emulation.
Date: Thu, 10 Jan 2002 15:30:13 -0600	[thread overview]
Message-ID: <200201102130.g0ALUDg83019@dc.cis.okstate.edu> (raw)

Janina Sajka writes:
>Do you reference ide-scsi in your lilo.conf?

	No, and if I was a gambler, I would bet that there in
lies the problem.

> I have it as:
>
>append = "hdc=ide-scsi hde=ide-scsi"

	I remember reading that directive in the HOWTO or
somewhere that dealt with this topic and I was kind of confused at
the time or maybe half asleep and thought that this was something
taken care of in the kernel configuration.

	Do you have the SCSI emulation and driver set up as
loadable modules or did you just reply  y  to having that module
become an integral part of the kernel?  That is how I have done
the SCSI configuration because it is something that will more
than likely get used all the time.  Except for the increase in
kernel size, it is probably more efficient to have things like
that compiled in.

	As I said, this may be the missing link that explains why
nothing seems to tie the SCSI support to what is actually
there.

	Again thanks for the reminder.  I certainly hope that
that is what's missing.  This system just isn't that unusual.

Martin




             reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Martin G. McCormick [this message]
 ` Janina Sajka
  -- strict thread matches above, loose matches on Subject: below --
 Martin McCormick
 Martin G. McCormick
 ` Willem van der Walt<vdwaltw@health.gov.za>
 Martin G. McCormick
 Martin G. McCormick
 ` Janina Sajka
 Martin G. McCormick
 ` Janina Sajka

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=200201102130.g0ALUDg83019@dc.cis.okstate.edu \
    --to=martin@dc.cis.okstate.edu \
    --cc=blinux-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).