From: Rene Herman <rene.herman@keyaccess.nl>
To: Greg KH <greg@kroah.com>
Cc: 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: Wed, 13 Feb 2008 13:06:29 +0100 [thread overview]
Message-ID: <47B2DD45.7080709@keyaccess.nl> (raw)
In-Reply-To: <20080213044436.GB10101@kroah.com>
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.
Rene.
next prev parent reply other threads:[~2008-02-13 12:04 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 [this message]
2008-02-13 12:16 ` Michael Ellerman
2008-02-13 12:46 ` Rene Herman
2008-02-13 22:39 ` Michael Ellerman
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=47B2DD45.7080709@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--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 \
/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).