From: Michael Meissner <meissner@spectacle-pond.org>
To: Ookhoi <ookhoi@dds.nl>
Cc: Michael Meissner <meissner@spectacle-pond.org>,
linux-kernel@vger.kernel.org
Subject: Re: The advantage of modules?
Date: Mon, 8 Jan 2001 14:05:21 -0500 [thread overview]
Message-ID: <20010108140521.C11682@munchkin.spectacle-pond.org> (raw)
In-Reply-To: <20010105225020.A1188@evaner.penguinpowered.com> <20010108114734.A11682@munchkin.spectacle-pond.org> <20010108192601.J3680@ookhoi.dds.nl>
In-Reply-To: <20010108192601.J3680@ookhoi.dds.nl>; from ookhoi@dds.nl on Mon, Jan 08, 2001 at 07:26:01PM +0100
On Mon, Jan 08, 2001 at 07:26:01PM +0100, Ookhoi wrote:
> > 3) Having drivers as modules means that you can remove them and
> > reload them. When I was working in an office, I had one scsi
> > controller that was a different brand (Adaptec) than the main scsi
> > controller (TekRam), and I hung a disk in a removable chasis on the
> > scsi chain in addition to a tape driver and cd-rom. When I was
> > about to go home, I would copy all of the data to the disk, unmount
> > it, and then unload the scsi device driver. I would take the disk
> > out, and reload the scsi device driver to get the tape/cd-rom. I
> > would then take the disk to my home computer. I would reverse the
> > process when I came in the morning.
>
> You don't need modules for this to work.
Quoting from drivers/scsi/scsi.c:
/*
* Usage: echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi
* with "0 1 2 3" replaced by your "Host Channel Id Lun".
* Consider this feature BETA.
* CAUTION: This is not for hotplugging your peripherals. As
* SCSI was not designed for this you could damage your
* hardware !
* However perhaps it is legal to switch on an
* already connected device. It is perhaps not
* guaranteed this device doesn't corrupt an ongoing data transfer.
*/
so my take is unless you explicitly use hotplug devices (I wasn't), that it is
much safer to unload the driver, unattach/attach scsi devices, and then reload
the driver (which will scan the scsi bus for devices), which you need modules
for.
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482
-
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 prev parent reply other threads:[~2001-01-08 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 4:50 Evan Thompson
2001-01-06 5:31 ` Drew Bertola
2001-01-06 10:02 ` J . A . Magallon
2001-01-08 16:49 ` Michael Meissner
2001-01-08 16:47 ` Michael Meissner
2001-01-08 18:26 ` Ookhoi
2001-01-08 19:05 ` Michael Meissner [this message]
2001-01-08 21:50 ` Russell King
2001-01-08 22:16 ` Dan Hollis
2001-01-08 22:14 ` Russell King
2001-01-08 22:40 ` Dan Hollis
2001-01-08 23:06 ` Richard B. Johnson
2001-01-08 23:49 ` Alan Cox
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=20010108140521.C11682@munchkin.spectacle-pond.org \
--to=meissner@spectacle-pond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ookhoi@dds.nl \
/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®