mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'David Brownell'" <david-b@pacbell.net>,
	"'Nick Bellinger'" <nickb@attheoffice.org>,
	<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	Patrick Mochel <mochel@osdl.org>
Subject: RE: driverfs is not for everything! (was:  [PATCH] /proc/scsi/map )
Date: Mon, 24 Jun 2002 20:32:15 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0206242017140.8911-100000@serv> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7F53@orsmsx111.jf.intel.com>

Hi,

On Mon, 24 Jun 2002, Grover, Andrew wrote:

> With technologies like USB, infiniband, NFS, iSCSI, and 1394, it's tough,
> but the main question should be:
>
> "If my computer suspends, should this device be turned off?" Which is
> another way of asking is the use of a device exclusive to a particular
> machine.
>
> If a device can be accessed by multiple machines concurrently, it should not
> be in driverfs.

I don't think it's that easy. If the computer wakes up again, devices have
to be reinitialised in the right order, e.g. iSCSI needs a working network
stack and devices. Another problem is how to properly shutdown the
machine. Scripts now "know" that nfs requires the network, but how does
the script find out, that /dev/sdb2 is an iSCSI device, so that it can
properly unmount the device, before the network is shutdown?

bye, Roman


  parent reply	other threads:[~2002-06-24 18:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <andrew.grover@intel.com>
2002-06-24 17:35 ` Grover, Andrew
2002-06-24 17:48   ` driverfs is not for everything! (was: [PATCH] /proc/scsi/map kernel
2002-06-24 18:04   ` driverfs is not for everything! (was: [PATCH] /proc/scsi/map ) David Brownell
2002-06-24 18:09   ` James Bottomley
2002-06-24 19:23     ` Oliver Xymoron
2002-06-25 18:38     ` Patrick Mochel
2002-06-24 18:32   ` Roman Zippel [this message]
2002-06-24 22:47   ` John Summerfield
2002-06-25 18:35   ` Patrick Mochel
2002-07-01  2:41   ` Pavel Machek
2002-06-25 19:50 Adam J. Richter
  -- strict thread matches above, loose matches on Subject: below --
2002-06-24 18:47 Grover, Andrew
2002-06-24 19:03 ` Oliver Xymoron
2002-06-24 18:37 Grover, Andrew
2002-06-24 13:54 driverfs is not for everything! (was: [PATCH] /proc/scsi/map) Arnd Bergmann
2002-06-23 22:59 Grover, Andrew
2002-06-24  1:34 ` David Brownell
2002-06-24  5:18 ` Nick Bellinger
2002-06-24  6:41   ` Brad Hards
2002-06-25 18:18 ` Patrick Mochel

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=Pine.LNX.4.44.0206242017140.8911-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=andrew.grover@intel.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=nickb@attheoffice.org \
    /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®