From: Borislav Petkov <bp@alien8.de>
To: "Jörn Engel" <joern@logfs.org>
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: Thu, 19 Jul 2012 11:26:08 +0200 [thread overview]
Message-ID: <20120719092608.GA24872@liondog.tnic> (raw)
In-Reply-To: <20120718210814.GA1871@logfs.org>
On Wed, Jul 18, 2012 at 05:08:15PM -0400, Jörn Engel wrote:
> 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.
I see. It would be interesting to know what the use cases of those
people are. In any case, this is not an interface since you only have
one-way data movement from kernel to userspace and you can change the
formatting/layout of that data later with no obvious issues, AFAICT.
[ … ]
> Or show off your geekiness by using back ticks:
> $ vi `./bcon_tail`
Uuh, magic. Definitely! :-)
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-07-19 9:26 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
2012-07-19 9:26 ` Borislav Petkov [this message]
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=20120719092608.GA24872@liondog.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=jmoyer@redhat.com \
--cc=joern@logfs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome