From: Linus Torvalds <torvalds@linux-foundation.org>
To: David VomLehn <dvomlehn@cisco.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
David Brownell <david-b@pacbell.net>,
alan@lxorguk.ukuu.org.uk, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Linux Embedded Mailing List <linux-embedded@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Wait for console to become available, v3.2
Date: Tue, 21 Apr 2009 10:37:41 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904211036140.2199@localhost.localdomain> (raw)
In-Reply-To: <20090421172929.GC8251@cuplxvomd02.corp.sa.net>
On Tue, 21 Apr 2009, David VomLehn wrote:
>
> What in the world are users going to do when they see a message about
> output being lost? There is no way to recover the data and no way to
> prevent it in the future. I don't think this is a good approach.
Sure there is. The console messages are saved too, so doing 'dmesg' will
get you all the data that was generated before the console went on-line.
We _already_ lose data in that sense (although we could replay it for the
first console connected - maybe we even do, I'm too lazy to check).
Linus
next prev parent reply other threads:[~2009-04-21 17:44 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 23:40 Wait for console to become available, v3.2 David VomLehn
2009-04-21 6:43 ` Ingo Molnar
2009-04-21 7:13 ` David Brownell
2009-04-21 8:03 ` Ingo Molnar
2009-04-21 17:11 ` David Woodhouse
2009-04-21 17:29 ` David VomLehn
2009-04-21 17:37 ` Linus Torvalds [this message]
2009-04-21 17:59 ` David VomLehn
2009-04-21 17:41 ` David Woodhouse
2009-04-21 17:31 ` Linus Torvalds
2009-04-21 19:25 ` Alan Cox
2009-04-21 23:17 ` David VomLehn
2009-04-22 8:25 ` Jamie Lokier
2009-04-22 9:11 ` Alan Cox
2009-04-22 10:39 ` Jamie Lokier
2009-04-21 13:35 ` Arjan van de Ven
2009-04-21 13:50 ` Ingo Molnar
2009-04-21 14:05 ` Jamie Lokier
2009-04-21 14:26 ` Ingo Molnar
2009-04-21 14:37 ` Alan Cox
2009-04-22 8:22 ` Jamie Lokier
2009-04-22 9:13 ` Alan Cox
2009-04-21 16:42 ` David VomLehn
2009-04-21 14:36 ` Alan Stern
2009-04-21 16:52 ` David VomLehn
2009-04-21 19:09 ` Alan Stern
2009-04-21 23:08 ` David VomLehn
2009-04-22 15:40 ` Alan Stern
2009-04-22 20:54 ` David VomLehn
2009-04-22 21:08 ` Alan Cox
2009-04-22 21:24 ` Alan Stern
2009-04-24 0:35 ` David VomLehn
2009-04-24 19:20 ` Alan Stern
2009-04-24 21:32 ` David VomLehn
2009-04-24 22:19 ` Jamie Lokier
2009-04-24 23:10 ` David VomLehn
2009-04-25 1:41 ` Jamie Lokier
2009-04-25 3:11 ` Alan Stern
2009-04-26 19:52 ` Jamie Lokier
2009-04-26 21:20 ` Alan Stern
2009-04-26 21:37 ` Jamie Lokier
2009-04-26 22:36 ` Kay Sievers
2009-04-26 23:12 ` Jamie Lokier
2009-04-26 23:23 ` Kay Sievers
2009-04-26 23:46 ` Jamie Lokier
2009-04-26 17:55 ` David VomLehn
2009-04-22 5:35 ` David VomLehn
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.0904211036140.2199@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=david-b@pacbell.net \
--cc=dvomlehn@cisco.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).