public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: hch@infradead.org, linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] hdreg.h
Date: Thu, 09 May 2002 15:30:43 +0200	[thread overview]
Message-ID: <3CDA7A03.3000202@evision-ventures.com> (raw)
In-Reply-To: <UTC200205091406.g49E6W018636.aeb@smtp.cwi.nl>

Użytkownik Andries.Brouwer@cwi.nl napisał:
>     On Thu, May 09, 2002 at 03:48:32PM +0200, Andries.Brouwer@cwi.nl wrote:
>     > No, fdisk, cfdisk, sfdisk do not use HDIO_GETGEO_BIG.
>     > And indeed, the ioctl is completely meaningless.
> 
>     In many current distributions (e.g. from Red Hat, Mandrake and Caldera)
>     they do.
> 
> Yes, distributions are known to introduce buggy patches.
> 
> Moreover, distributions are known to copy each others bugs.
> Sometimes I tell one distribution that a patch is buggy,
> and they revert their patch, but some months later they
> have it again, copied from some other distribution.
> Even bad "segmentation fault" bugs are copied.
> 
> But for 2.5 this is not important. Distributions have time
> to fix stuff before 2.6.

And developement kernels are known to require updated:

util-linux,
modutils
mounts
net-utils

and so on :-).

As long as long an installed system doesn't break utterly
there is no reaons IMHO why cleanups shouldn't be done.


  reply	other threads:[~2002-05-09 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09 14:06 [PATCH] hdreg.h Andries.Brouwer
2002-05-09 13:30 ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-09 13:48 Andries.Brouwer
2002-05-09 13:56 ` Christoph Hellwig
2002-05-08 23:45 Andries.Brouwer
2002-05-09 11:54 ` Martin Dalecki

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=3CDA7A03.3000202@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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