From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: rhw@InfraDead.Org
Cc: Harry Kalogirou <harkal@gmx.net>,
Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Filesystem creation
Date: Tue, 14 May 2002 00:52:31 +0100 (BST) [thread overview]
Message-ID: <E177PcF-0006dt-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.21.0205131836570.7839-100000@Consulate.UFP.CX> from "Riley Williams" at May 13, 2002 06:42:23 PM
> 2. How hard would it be to make mkfs take as its size parameter
> the number reported by fdisk and calculate the size it needs
> from that rather than expect the user to do the calculation
> instead?
That would break the expected but daft old Unix API
> 3. How hard would it be to fix ELKS so the size doesn't need to
> be specified, either by getting the block devices to update
> the blk_sizes array or by whatever other means are required?
> This way, the whole problem just vanishes.
You can fill in the block sizes for each partition by reading the
partition table. In the ELKS case I'd argue that mkfs ought to figure
out the primary device, and do the partition table read itself simply
because kernel space is precious and only mkfoo need to know
next prev parent reply other threads:[~2002-05-13 23:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 1:23 Filesystem creation lnordstrom
2002-05-12 20:04 ` Riley Williams
2002-05-13 8:59 ` Javier Sedano
2002-05-13 12:02 ` Harry Kalogirou
2002-05-13 17:42 ` Riley Williams
2002-05-13 23:52 ` Alan Cox [this message]
2002-05-14 6:56 ` Riley Williams
2002-05-14 12:44 ` Riley Williams
2002-05-14 17:47 ` Alan Cox
2002-05-14 17:59 ` Riley Williams
2002-05-14 23:41 ` Alan Cox
2002-05-15 17:52 ` Riley Williams
[not found] ` <3CE0283D.264@havn.com>
2002-05-14 21:01 ` Harry Kalogirou
2002-05-15 1:18 ` Alan Cox
2002-05-15 17:05 ` Riley Williams
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 2:33 lnordstrom
2002-05-12 23:07 ` Riley Williams
2002-05-13 14:22 ` Dan Olson
2002-05-13 17:36 ` Riley Williams
2002-05-13 23:50 ` Alan Cox
2002-05-14 0:12 ` Dan Olson
2002-05-14 7:06 ` Riley Williams
2002-05-14 23:31 ` Dan Olson
2002-05-14 6:54 ` Riley Williams
2002-05-14 23:36 ` Dan Olson
2002-05-14 0:19 ` Dan Olson
2002-05-14 6:42 ` Riley Williams
2002-05-14 23:48 ` Dan Olson
2002-05-15 0:12 ` Alan Cox
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=E177PcF-0006dt-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=harkal@gmx.net \
--cc=linux-8086@vger.kernel.org \
--cc=rhw@InfraDead.Org \
/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