From: Michael Ellerman <michael@ellerman.id.au>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Greg KH <greg@kroah.com>,
bzolnier@gmail.com, muli@il.ibm.com, jdmason@kudzu.us,
linux-ide@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: "ide=reverse" do we still need this?
Date: Thu, 14 Feb 2008 09:39:02 +1100 [thread overview]
Message-ID: <1202942342.10139.4.camel@concordia> (raw)
In-Reply-To: <47B2E6AB.1020701@keyaccess.nl>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
On Wed, 2008-02-13 at 13:46 +0100, Rene Herman wrote:
> On 13-02-08 13:16, Michael Ellerman wrote:
>
> > On Wed, 2008-02-13 at 13:06 +0100, Rene Herman wrote:
> >> On 13-02-08 05:44, Greg KH wrote:
> >>
> >>>> While details escape me somewhat again at the monment, a few months ago
> >>>> I was playing around with a PCI Promise IDE controller and needed
> >>>> ide=reverse to save me from having to switch disks around to still have
> >>>> a bootable system.
> >>>>
> >>>> Or some such. Not too clear anymore, but I remember it saved the day.
> >>> You couldn't just change the boot disk in grub?
> >>>
> >>> Or use an initramfs and /dev/disk/by-id/ to keep any future moves stable?
> >> No. The thing is that you need these kinds of hacks while messing with old
> >> systems, building and stripping them, often in recovery type of situations.
> >>
> >> As said (same as the other person I saw reacting) details of what was most
> >> decidedly needed last time around escape me at the moment, but ide=reverse
> >> is the kind of hack that saves one hours of unscrewing computer cases and
> >> switching disks around while building stuff, making quick tests, doing
> >> recovery...
> >>
> >> If it must go for the greater architectural good, so be it, but it's the
> >> type of thing that's used specifically in the situations where you don't
> >> have stable, well arranged (or known!) setups to begin with.
> >
> > I might be off the deep end, but isn't this what
> > Documentation/feature-removal-schedule.txt is for?
>
> Documentation/feature-removal-schedule.txt is for asking/discussing whether
> or not features should be removed? No, I don't think so. It seems to be a
> schedule of when to remove features.
Well it's sort of both I think. It's a schedule, but if enough people
complain that something's being removed then it can be reconsidered
before it's removed.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-13 22:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 0:15 "ide=reverse" do we still need this? Greg KH
2008-02-13 0:16 ` pci_get_device_reverse(), why does Calgary " Greg KH
2008-02-13 2:17 ` Alan Cox
2008-02-13 4:45 ` Greg KH
2008-02-13 12:34 ` Bartlomiej Zolnierkiewicz
2008-02-13 17:28 ` Greg KH
2008-02-13 18:16 ` Greg KH
2008-02-13 22:20 ` Bartlomiej Zolnierkiewicz
2008-02-13 23:41 ` Greg KH
2008-02-14 0:02 ` Bartlomiej Zolnierkiewicz
2008-02-14 4:58 ` Greg KH
2008-02-14 13:09 ` Sergei Shtylyov
2008-02-14 7:44 ` [discuss] " Andreas Jaeger
2008-02-14 12:11 ` Bartlomiej Zolnierkiewicz
2008-02-15 7:17 ` Greg KH
2008-02-20 0:39 ` Greg KH
2008-02-13 9:32 ` Muli Ben-Yehuda
2008-02-13 17:32 ` Greg KH
2008-02-13 17:47 ` Muli Ben-Yehuda
2008-02-13 18:14 ` Greg KH
2008-02-15 7:17 ` Greg KH
2008-02-15 7:48 ` Muli Ben-Yehuda
2008-02-15 15:20 ` Greg KH
2008-02-15 15:31 ` Sam Ravnborg
2008-02-15 15:46 ` yong xue
2008-02-15 18:28 ` Greg KH
2008-02-17 7:53 ` Muli Ben-Yehuda
2008-02-13 1:41 ` "ide=reverse" do we still " Rene Herman
2008-02-13 4:44 ` Greg KH
2008-02-13 12:06 ` Rene Herman
2008-02-13 12:16 ` Michael Ellerman
2008-02-13 12:46 ` Rene Herman
2008-02-13 22:39 ` Michael Ellerman [this message]
2008-02-13 12:57 ` Rene Herman
2008-02-14 17:16 ` Bill Davidsen
2008-02-15 13:58 ` Matthew Wilcox
2008-02-13 2:43 ` Ken Moffat
2008-02-13 4:43 ` Greg KH
2008-02-13 15:32 ` Ken Moffat
2008-02-19 15:08 ` Ken Moffat
2008-02-13 7:54 ` [discuss] " Dirk GOUDERS
2008-02-13 8:26 ` Greg KH
2008-02-13 8:54 ` Dirk GOUDERS
2008-02-13 20:00 ` Dirk GOUDERS
2008-02-13 20:48 ` Greg KH
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=1202942342.10139.4.camel@concordia \
--to=michael@ellerman.id.au \
--cc=bzolnier@gmail.com \
--cc=discuss@x86-64.org \
--cc=greg@kroah.com \
--cc=jdmason@kudzu.us \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=muli@il.ibm.com \
--cc=rene.herman@keyaccess.nl \
/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