All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Jeff Moyer <jmoyer@redhat.com>,
	Steve Hodgson <steve@purestorage.com>
Subject: Re: [PATCH] add blockconsole version 1.1
Date: Wed, 18 Jul 2012 17:08:15 -0400	[thread overview]
Message-ID: <20120718210814.GA1871@logfs.org> (raw)
In-Reply-To: <20120718214520.GA14067@liondog.tnic>

On Wed, 18 July 2012 23:45:21 +0200, Borislav Petkov wrote:
> 
> > > So why is that first megabyte full of zeros there?
> > 
> > It gives you some scratch space to store information in.
> 
> How? By me writing something in that empty line in vim? Or something
> else storing stuff there?

Assuming you want to do it in an automated fashion - by patching or
replacing mkblockconsole.  Again, I have no opinion on whether this
actually makes sense.  It is possible, it does not really hurt the
primary function and people have explicitly asked me for it.  Good
enough for me.

> > How useful that actually is may be a matter of opinion. But
> > independent of that, you will find large amounts of zeroes all over.
> > Every time you reboot, the new blockconsole will start writing at a
> > megabyte-aligned offset and whatever remains of the last megabyte
> > should be zero-filled as well.
> 
> Ah, those are the tiles you're talking about in the docs, right?

Yes.

> Oh, I didn't mean anything involved but rather a quick steps write-up
> (steps can always be expanded and made more verbose later):
> 
> Blocksonsole in three easy steps
> ================================
> 
> 1. Find an unused USB stick and prepare it for blockconsole by writing
> the blockconsole signature to it:
> 
> $ ./mkblockconsole /dev/sdc
> 
>   [ Assuming /dev/sdc is the device node of the USB stick you just mounted. ]
> 
> 2. USB stick is ready for use, replug it so that the kernel can start
> logging to it.
> 
> 3. After you've done logging, read out the logs from it like this:
> 
> $ ./bcon_tail
> 
>   [ This creates a file called /var/log/bcon.<random number> which
>   contains the logs. Open it with a sane editor like vim which can
>   display zeroed gaps as a single line and start staring at the logs. ]

Or show off your geekiness by using back ticks:
$ vi `./bcon_tail`

> Something like the above, just slap it at the beginning of
> Documentation/block/blockconsole.txt for impatient people like me and
> that's it :-).

Will do.

Jörn

--
There's nothing better for promoting creativity in a medium than
making an audience feel "Hmm ­ I could do better than that!"
-- Douglas Adams in a slashdot interview

  reply	other threads:[~2012-07-18 22:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 20:59 [RFC][PATCH] add blockconsole Jörn Engel
2012-04-25 13:42 ` Jeff Moyer
2012-04-25 13:25   ` Jörn Engel
2012-04-25 15:52     ` Jeff Moyer
2012-07-12 17:46       ` [PATCH] add blockconsole version 1.1 Jörn Engel
2012-07-13 13:03         ` Borislav Petkov
2012-07-13 16:20           ` Jörn Engel
2012-07-13 21:14             ` Borislav Petkov
2012-07-16 12:46             ` Borislav Petkov
2012-07-18 18:53               ` Jörn Engel
2012-07-18 21:45                 ` Borislav Petkov
2012-07-18 21:08                   ` Jörn Engel [this message]
2012-07-19  9:26                     ` Borislav Petkov
2012-07-23 20:04                   ` Jörn Engel
2012-07-24 15:42                     ` Borislav Petkov
2012-07-24 14:53                       ` Jörn Engel
2012-07-24 16:25                         ` Borislav Petkov
2012-07-24 17:52                           ` Jörn Engel
2012-07-24 20:28                             ` Borislav Petkov
2012-12-19 10:20                               ` Borislav Petkov
2012-08-14 11:54                 ` Jan Engelhardt
2012-07-23 14:33         ` Tvrtko Ursulin
2012-07-23 20:02           ` Jörn Engel
2012-07-24  8:01             ` Tvrtko Ursulin
2012-07-24 14:38               ` Jörn Engel
2012-07-25  8:17                 ` Tvrtko Ursulin
2012-07-25 16:39                   ` Jörn Engel

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=20120718210814.GA1871@logfs.org \
    --to=joern@logfs.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@purestorage.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 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.