From: Pavel Machek <pavel@ucw.cz>
To: linux-kernel@vger.kernel.org
Cc: Takao Indoh <indou.takao@soft.fujitsu.com>,
lkcd-devel@lists.sourceforge.net
Subject: Re: [RFC] Standard filesystem types for crash dumping
Date: Fri, 16 Jul 2004 18:43:35 +0200 [thread overview]
Message-ID: <20040716164334.GB8264@openzaurus.ucw.cz> (raw)
In-Reply-To: <11077.1089790663@kao2.melbourne.sgi.com>
Hi!
> This RFC proposes a common interface to handle the above points. In
> the true Unix way (everything is a file), it adds two new filesystem
> types, dump_0 and dump_1.
Maybe call these dump_empty and dump_full?
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
prev parent reply other threads:[~2004-07-16 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 7:37 [RFC] Standard filesystem types for crash dumping Keith Owens
2004-07-14 7:49 ` Jeff Garzik
2004-07-14 10:55 ` Keith Owens
2004-07-16 16:43 ` Pavel Machek [this message]
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=20040716164334.GB8264@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=indou.takao@soft.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcd-devel@lists.sourceforge.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.