From: Wakko Warner <wakko@animx.eu.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /proc/ide/hd?/settings obsolete in 2.6.
Date: Thu, 5 May 2005 16:53:51 -0400 [thread overview]
Message-ID: <20050505205351.GC17861@animx.eu.org> (raw)
In-Reply-To: <1115315925.19842.92.camel@localhost.localdomain>
Alan Cox wrote:
> On Iau, 2005-05-05 at 17:33, Wakko Warner wrote:
> > Now, i have programs that I can't tell it the geometry (which it does use
> > and requires to be correct. My guesses using edd are correct). I was using
> > /proc/ide/hdX/settings to tell the kernel what geometry I want so the
> > programs that can only ask the kernel can get it right.
>
> And the geometry ioctls are obsolete for the applications too.
What is the right way for apps that need it to get it? Or is the kernel
just going to obsolete geometry entirely?
> > If the "right" way is via IOCTL, my scripts are written in perl that do the
> > bulk of the guess work.
>
> I suspect it is for other programs that are still using that geometry
> data and
> really mkdosfs is what needs fixing ?
mkdosfs definately needs fixing. I intend on filing a bug report about
this.
If I knew more about the dos format, I might not even have to do this.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-05-05 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 0:48 /proc/ide/hd?/settings obsolete in 2.6 Wakko Warner
2005-05-05 10:10 ` Bartlomiej Zolnierkiewicz
2005-05-05 11:13 ` Wakko Warner
2005-05-05 12:13 ` Bartlomiej Zolnierkiewicz
2005-05-05 14:56 ` Alan Cox
2005-05-05 15:38 ` Wakko Warner
2005-05-05 16:21 ` Alan Cox
2005-05-05 16:33 ` Wakko Warner
2005-05-05 17:58 ` Alan Cox
2005-05-05 20:53 ` Wakko Warner [this message]
2005-05-05 22:16 ` Alan Cox
2005-05-05 15:33 ` Wakko Warner
2005-05-05 15:53 ` Pozsár Balázs
2005-05-05 16:20 ` Wakko Warner
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=20050505205351.GC17861@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.