[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120713211440.GB10180@liondog.tnic>
Date: Fri, 13 Jul 2012 23:14:40 +0200
From: Borislav Petkov <bp@...en8.de>
To: Jörn Engel <joern@...fs.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Jeff Moyer <jmoyer@...hat.com>,
Steve Hodgson <steve@...estorage.com>
Subject: Re: [PATCH] add blockconsole version 1.1
On Fri, Jul 13, 2012 at 12:20:09PM -0400, Jörn Engel wrote:
> > > Logging to partitions is not supported.
> >
> > That could be useful though. We have a setup here where we create a
> > partition on the block device and install the OS there for testing
> > purposes while leaving room on the device after it for other OS installs
> > and other people to test stuff.
> >
> > If blockconsole could log to partitions, one could create an additional
> > small partition exactly for such logs.
> >
> > I don't know how much work adding logging to partitions is though.
>
> The actual logging shouldn't care one bit. But abusing the
> partitioning code to detect a blockconsole device would no longer
> work, so some alternative for that is needed.
>
> What I like about abusing the partitioning code is that blockconsole
> just works, without any command line parameters or other setup, either
> on boot or by pluggin in a new device. And because our particular use
> case is a dedicated usb stick, we don't mind the drawbacks much.
Ok, actually using a dedicated usb stick obviates the need to log to
partitions - el cheapo usb sticks are ubiquitous. And I didn't realize
the usb stick use case when talking about the partitions example above
so forget what I said, logging to a dedicated usb stick is the easiest.
You probably could mention this in the docs as the most natural use case
for blockconsole if you haven't done so.
[ … ]
> Thanks! The patch below should do that - provided my brain slightly
> less broken than it must have been yesterday.
Thanks, will run it next week and let you know.
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists