linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Oliver Neukum <oliver@neukum.org>,
	Raymano Garibaldi <raymano@faunos.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Denys Vlasenko <vda.linux@googlemail.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] [FEATURE REQUEST] Transparent hot plugging of root file system on portable storage devices.
Date: Mon, 7 Jan 2008 10:39:13 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0801071017430.4491-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20080106224429.GA1664@elf.ucw.cz>

On Sun, 6 Jan 2008, Pavel Machek wrote:

> On Sun 2008-01-06 17:26:17, Alan Stern wrote:
> > On Sun, 6 Jan 2008, Oliver Neukum wrote:
> > 
> > > Am Sonntag 06 Januar 2008 schrieb Alan Stern:
> > > > What about people who want to suspend to RAM instead of hibernating and
> > > > _do_ want to unplug the USB device containing their root filesystem
> > > > while the machine is asleep? 
> 
> Ok, I guess I'm lost here. That sounds like a nice way to do
> self-leg-shooting. Are there such people?

Yes.  People with small systems having extremely limited rw storage (no
swap space), using removable read-only media as their root fs.

You can find the thread leading up to this request here:

	http://marc.info/?t=119544588400002&r=1&w=2

> > > Would it be hard to force the persist feature on for a replugged device?
> > 
> > Right now the persist feature is enabled by a per-device boolean flag.  
> > In theory the flag could accept 3 values: off, on if power was lost,
> > or on for any resume transition.  This would not be a hard change.
> 
> But do we need it?

That depends on whom you ask!  :-)

> Did you progress on "usb-storage-autosuspend"?

Yes; the first round of patches will be posted later today.

> Here are my hacks to try to get SATA to survive autosuspend;
> unfortunately they do not work :-(.

You should start off with minimal support for manual runtime suspend
(through a sysfs attribute).  When that's working, autosuspend will be
easier to add in.

Alan Stern


      reply	other threads:[~2008-01-07 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 19:04 [linux-usb-devel] [FEATURE REQUEST] Transparent hot plugging of root file system on portable storage devices Raymano Garibaldi
2008-01-01 20:29 ` Pavel Machek
2008-01-02 10:19   ` Oliver Neukum
2008-01-02 20:23     ` Alan Stern
2008-01-05 21:52       ` Pavel Machek
2008-01-06 17:18         ` Alan Stern
2008-01-06 20:59           ` Oliver Neukum
2008-01-06 22:26             ` Alan Stern
2008-01-06 22:44               ` Pavel Machek
2008-01-07 15:39                 ` Alan Stern [this message]

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.44L0.0801071017430.4491-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=oliver@neukum.org \
    --cc=pavel@ucw.cz \
    --cc=raymano@faunos.com \
    --cc=vda.linux@googlemail.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 NNTP newsgroup(s).