From: "Martin G. McCormick" <martin@dc.cis.okstate.edu>
To: blinux-list@redhat.com
Subject: Re: Still Having Fun with SCSI Emulation.
Date: Fri, 11 Jan 2002 09:58:04 -0600 [thread overview]
Message-ID: <200201111558.g0BFw4g75592@dc.cis.okstate.edu> (raw)
I have one last question before I dive back in to this
this weekend.
If the SCSI support is compiled in rather than modules,
does that change the need for the lilo.conf directive that
Janina is referring to?
There is nothing at all regarding SCSI in my lilo.conf.
My understanding of modules versus compiled is that it is
all supposed to function the same when up and running. The only
difference is that your kernel grows or shrinks by loading and
unloading portions of code as needed rather than just having them
sitting there unused part of the time.
Martin
Janina Sajka writes:
>I have it as modules, and I have had no dificulty with it since at least
>2.2.12. I have it on my IBM Thinkpad T20, where I have a swappable ide
>burner.
next 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=200201111558.g0BFw4g75592@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).