public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Andreas Schwab <schwab@suse.de>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
	Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjanv@redhat.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.x partition breakage and dual booting
Date: Sun, 30 May 2004 22:14:48 +0100	[thread overview]
Message-ID: <20040530211448.GD12308@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <jeu0xxzkqc.fsf@sykes.suse.de>

On Sun, May 30, 2004 at 11:08:27PM +0200, Andreas Schwab wrote:
> viro@parcelfarce.linux.theplanet.co.uk writes:
> 
> > On Sun, May 30, 2004 at 10:03:00PM +0200, Andries Brouwer wrote:
> >> Clearly, BLKGETSIZE is obsolescent - it should be replaced by
> >> BLKGETSIZE64 everywhere. 2^41 B is 2 TB, and some RAIDs are larger.
> >
> > ITYM "it should be replaced to lseek(fd, SEEK_END, 0) everywhere".
> ITYM                             lseek(fd, 0, SEEK_END)

Sorry, braino.

  reply	other threads:[~2004-05-30 21:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30 18:04 2.6.x partition breakage and dual booting Jeff Garzik
2004-05-30 18:36 ` Andries Brouwer
2004-05-30 18:56   ` Jeff Garzik
2004-05-30 20:03     ` Andries Brouwer
2004-05-30 20:47       ` viro
2004-05-30 21:06         ` Andries Brouwer
2004-05-30 21:08         ` Andreas Schwab
2004-05-30 21:14           ` viro [this message]
2004-05-30 21:02       ` Patrick J. LoPresti
2004-05-30 22:20         ` Andries Brouwer
     [not found]           ` <mit.lcs.mail.linux-kernel/20040530222001.GD4681@apps.cwi.nl>
2004-05-30 22:54             ` Patrick J. LoPresti
2004-05-31 18:08         ` Tomas Szepe
2004-05-31 19:19           ` Frediano Ziglio
2004-05-31 20:06           ` Patrick J. LoPresti
2004-05-31 21:03             ` Sean Estabrooks
2004-06-01 15:10               ` Patrick J. LoPresti
2004-06-01 23:55                 ` Andries Brouwer
2004-06-02 13:02                   ` Patrick J. LoPresti
2004-06-02 15:00                     ` Matt Domsch
2004-06-02 21:22                       ` [PATCH] Better names for EDD legacy_* fields Patrick J. LoPresti
2004-06-02 23:03                         ` Andries Brouwer
2004-06-02 23:38                           ` Patrick J. LoPresti
2004-06-02 23:53                       ` [PATCH] Use decimal instead of hex for EDD values Patrick J. LoPresti
2004-06-01 16:28           ` 2.6.x partition breakage and dual booting Stephen Hemminger
2004-06-03  6:51           ` Frediano Ziglio
2004-06-03 10:39             ` Andries Brouwer
2004-06-03 12:30               ` Frediano Ziglio
2004-06-03 14:35                 ` Bartlomiej Zolnierkiewicz
2004-06-03 15:11                   ` Andries Brouwer
2004-06-03 14:46               ` Patrick J. LoPresti
2004-06-03 15:32                 ` Bartlomiej Zolnierkiewicz
2004-06-03 15:55                   ` Patrick J. LoPresti
2004-05-30 19:35 ` Patrick J. LoPresti

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=20040530211448.GD12308@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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