From: Chris Ball <chris@void.printf.net>
To: Benjamin S Carrell <ben@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bigggg Maxtor drives (fwd)
Date: Thu, 10 Jan 2002 04:03:09 +0000 [thread overview]
Message-ID: <20020110040308.A28692@void.printf.net> (raw)
In-Reply-To: <3C3D0718.2060602@xmission.com>
On Wed, Jan 09, 2002 at 08:14:32PM -0700, Benjamin S Carrell wrote:
> I would think that you lose that space to formatting
That would be irrelevant. We're looking at the kernel's summation of
the geometry, not the filesystem's description of usable space.
> (would it not get the size of the drive from the bios?)
No, the kernel tends not to rely on the BIOS for geometry. Which is
usually very wise.
> but I stand open for correction.
Same here. It's always a good idea. :-)
Is this perhaps Maxtor providing their own 'non-standard'[1] definition
of gigabyte, rather than a technical issue?
- Chris.
[1]: (viz. 'wrong')
--
$a="printf.net"; Chris Ball | chris@void.$a | www.$a | finger: chris@$a
As to luck, there's the old miners' proverb: Gold is where you find it.
next prev parent reply other threads:[~2002-01-10 3:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 1:46 Bigggg Maxtor drives (fwd) Andre Hedrick
2002-01-10 3:14 ` Benjamin S Carrell
2002-01-10 4:03 ` Chris Ball [this message]
2002-01-10 4:31 ` Jim Crilly
2002-01-10 12:11 ` Rik van Riel
2002-01-10 12:15 ` Jens Axboe
2002-01-10 13:22 ` Marcel J.E. Mol
2002-01-10 14:56 ` Hans Reiser
2002-01-10 15:04 ` Jens Axboe
2002-01-10 12:23 ` Lionel Bouton
2002-01-10 12:40 ` Alan Cox
2002-01-10 12:45 ` David Weinehall
2002-01-10 13:47 ` Alan Cox
2002-01-10 18:59 ` Aaron Blew
2002-01-10 19:14 ` Jens Axboe
2002-01-10 19:14 ` Ricky Beam
2002-01-10 19:59 ` Alan Cox
2002-01-10 19:08 ` Ricky Beam
2002-01-10 4:59 ` Andre Hedrick
2002-01-10 9:50 ` Henning P. Schmiedehausen
2002-01-11 21:13 ` Rogier Wolff
2002-01-12 9:14 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-01-10 10:00 Andries.Brouwer
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=20020110040308.A28692@void.printf.net \
--to=chris@void.printf.net \
--cc=ben@xmission.com \
--cc=linux-kernel@vger.kernel.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