Message-ID: <47B2E6AB.1020701@keyaccess.nl>
Date: Wed, 13 Feb 2008 13:46:35 +0100
From: Rene Herman <rene.herman@keyaccess.nl>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: michael@ellerman.id.au
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?
References: <20080213001506.GA13933@kroah.com>	 <47B24AB3.3040009@keyaccess.nl> <20080213044436.GB10101@kroah.com>	 <47B2DD45.7080709@keyaccess.nl> <1202904996.6974.11.camel@concordia>
In-Reply-To: <1202904996.6974.11.camel@concordia>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1862
Lines: 42

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.

Rene.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/