From: Wakko Warner <wakko@animx.eu.org>
To: "Mohammad A. Haque" <mhaque@haque.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to capture long oops w/o having second machine
Date: Tue, 12 Dec 2000 10:31:32 -0500 [thread overview]
Message-ID: <20001212103132.A6077@animx.eu.org> (raw)
In-Reply-To: <3A3623C6.B2499D4D@haque.net>
In-Reply-To: <3A3623C6.B2499D4D@haque.net>; from Mohammad A. Haque on Tue, Dec 12, 2000 at 08:10:30AM -0500
> What's the best way to capture (manually or otherwise) a rather long
> oops that scrolls off my console without having a second machine?
>
> I'm gonna try to compile in a framebuffer and use a high resolution and
> see if that'll hold it all when I get back later today.
Tried using a printer? (Laser is not a good idea as they only print pages
at a time.)
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
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:[~2000-12-12 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 13:10 how to capture long oops w/o having second machine Mohammad A. Haque
2000-12-12 13:19 ` Xavier Bestel
2000-12-12 13:31 ` Tigran Aivazian
2000-12-12 13:32 ` Mohammad A. Haque
2000-12-12 14:34 ` Mohammad A. Haque
2000-12-12 16:38 ` Greg KH
2000-12-12 20:38 ` Mohammad A. Haque
2000-12-12 20:51 ` Miles Lane
2000-12-12 23:24 ` dean gaudet
2000-12-12 23:38 ` Mohammad A. Haque
2000-12-15 22:57 ` Pavel Machek
2000-12-12 17:13 ` Andreas Bombe
2000-12-12 21:58 ` Greg KH
2000-12-15 22:57 ` Pavel Machek
2000-12-12 15:31 ` Wakko Warner [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-12 16:28 Petr Vandrovec
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=20001212103132.A6077@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaque@haque.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.