linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: Eric Mudama <edmudama@gmail.com>
Cc: Albert Lee <albertcc@tw.ibm.com>, Jeff Garzik <jgarzik@pobox.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	IDE Linux <linux-ide@vger.kernel.org>,
	Doug Maxey <dwm@maxeymade.com>, dan mares <dmares@dmares.com>
Subject: Re: libata PATA support - work items?
Date: Mon, 3 Jan 2005 15:56:58 -0500	[thread overview]
Message-ID: <87f94c3705010312568b48d6e@mail.gmail.com> (raw)
In-Reply-To: <311601c9050101111929aef5ba@mail.gmail.com>

On Sat, 1 Jan 2005 12:19:20 -0700, Eric Mudama <edmudama@gmail.com> wrote:
> On Thu, 30 Dec 2004 18:42:33 +0800, Albert Lee <albertcc@tw.ibm.com> wrote:
> >     2. C/H/S addressing; libata currently hardcoded to use LBA
> 
> 
> Are there really people who want to run a newer 2.4 or a 2.6 kernel,
> who have disks that do not support LBA mode?  CHS will never address
> more than 32GB of the drive (unless you use vendor unique
> implementations) and heck, most companies don't even build drives that
> small anymore...  CHS is very messy, LBA is so much simpler.   Can we
> just stick with that?
> 
> --eric

I may be in the minority, but my company does computer forensics.  We
routinely connect old drives to Linux boxes and make dd images of
them.

We definately need CHS support at some level in the kernel.  If this
were ever dropped, we would have to quit using Linux for this job.

FYI, there are hundreds if not thousands of companies that provide
this service.  The current standard for the industry is to perform
these images from a DOS boot floppy, but using Linux is far superior
in my mind and there is a small but growing body of professionals
using Linux for Computer Forensic Imaging.

Greg
-- 
Greg Freemyer

  reply	other threads:[~2005-01-03 20:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 10:42 libata PATA support - work items? Albert Lee
2005-01-01 19:19 ` Eric Mudama
2005-01-03 20:56   ` Greg Freemyer [this message]
2005-01-03 21:20     ` Eric Mudama
2005-01-03 22:09       ` Bartlomiej Zolnierkiewicz
2005-01-04 23:43         ` Jeff Garzik
2005-01-04 23:41   ` Jeff Garzik
2005-01-05  0:50     ` Alan Cox
2005-01-05  2:42       ` Jeff Garzik
2005-01-05  3:43         ` Alan Cox
2005-01-05 12:59       ` Bartlomiej Zolnierkiewicz
2005-01-04 23:32 ` Jeff Garzik
2005-01-06  8:51   ` Albert Lee
2005-01-06 21:29     ` Alan Cox
2005-01-06 23:07       ` Bartlomiej Zolnierkiewicz

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=87f94c3705010312568b48d6e@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=albertcc@tw.ibm.com \
    --cc=bzolnier@gmail.com \
    --cc=dmares@dmares.com \
    --cc=dwm@maxeymade.com \
    --cc=edmudama@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).