From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@suse.cz>, Andreas Mohr <andi@lisas.de>,
Sriram V <vshrirama@gmail.com>,
Pierre Ossman <drzeus-list@drzeus.cx>,
linux-kernel@vger.kernel.org
Subject: Re: Power Management with rootfs on SDMMC.
Date: Sat, 3 Jan 2009 18:59:32 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0901031854320.3179@localhost.localdomain> (raw)
In-Reply-To: <20090103231013.3591d027@lxorguk.ukuu.org.uk>
On Sat, 3 Jan 2009, Alan Cox wrote:
>
> I don't believe "auto-destroy my music collection" is a sane default...
You are missing the point.
You have one totally made-up example of something that may happen as a
result of a default I didn't even advocate (but you didn't read my email).
And you use that as an argument against another case that wasn't even made
up, but a real issue where suspend simply didn't work, because the /home
partition no longer worked afterwards.
There really was nothing theoretical in my issue. On a certain class of
hardware, you absolutely _have_ to make your /home or / partition be
behind a USB thing, because nothing else has enough space on it.
And your made-up example wouldn't even trigger if we just made a per-mount
decision to mark devices persistent.
So why are you arguing?
Linus
next prev parent reply other threads:[~2009-01-04 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 6:35 Sriram V
2009-01-02 10:21 ` Andreas Mohr
2009-01-02 11:21 ` Pierre Ossman
2009-01-02 12:21 ` Andreas Mohr
2009-01-02 17:24 ` Pavel Machek
2009-01-03 20:23 ` Linus Torvalds
2009-01-03 20:43 ` Pavel Machek
2009-01-03 20:45 ` Alan Cox
2009-01-03 21:16 ` Linus Torvalds
2009-01-03 23:10 ` Alan Cox
2009-01-04 2:59 ` Linus Torvalds [this message]
2009-01-04 12:04 ` Alan Cox
2009-01-04 17:53 ` Linus Torvalds
2009-03-29 16:26 ` Andreas Mohr
2009-04-05 18:45 ` Pierre Ossman
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=alpine.LFD.2.00.0901031854320.3179@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@lisas.de \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=vshrirama@gmail.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
all inboxes | Powered by JetHome®