linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
	hancockrwd@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide: update Kconfig text to mark as deprecated
Date: Fri, 30 Oct 2009 09:15:51 +0100	[thread overview]
Message-ID: <200910300915.51836.Martin@lichtvoll.de> (raw)
In-Reply-To: <20091029.173028.248393897.davem@davemloft.net>

[-- Attachment #1: Type: Text/Plain, Size: 1813 bytes --]

Am Freitag 30 Oktober 2009 schrieb David Miller:
> And yes I absolutely do consider it too onerous to change my fstab
> because I have to (or want to be able to) go back to older kernels
> which will only have the IDE stack enabled.  I refuse to have to
> monkey around with my fstab every time I want to go back and forth.

You don't need to when you used UUID or LABEL - I prefer the later cause 
its more readable. Actually I never quite understood while one would want 
to use dynamic things like /dev/hdd or /dev/sdb in the first place. Thats 
for me not that much better than C: or D:. Connect your harddisks 
differently and you are screwed.

On AmigaOS partitions were refered by names since the beginning. When I 
copied my OS to a different harddisk I gave the new partition the same 
name, copied all files over, removed the old harddisk or renamed the old 
partition and reduced its boot priority and be done with it. (Not that 
AmigaOS had a fstab that I could have edited anyway.) This way I could 
connect an IDE disk with the IDE controller on board, an IDE controller 
card like FastATA or via bridge to the UWSCSI controller on the CyberStorm 
PPC turbo board without having to change any configuration in order to be 
able to boot.

(Another thing to copy would be how removable storage devices are handled. 
If you remove a disk or usb stick prematurely while the OS is still 
writing to it you get a "You MUST insert volume xyz again!" requester and 
if you do, the writes will be completed. I never have seen any other OS 
that does it this sane way as a standard. Other OS either disallow device 
removal where possible or loose data.)

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-10-30  8:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27  1:41 [PATCH] ide: update Kconfig text to mark as deprecated Robert Hancock
2009-10-29 10:13 ` David Miller
2009-10-30  0:19   ` Robert Hancock
2009-10-30  0:30     ` David Miller
2009-10-30  0:33       ` Alan Cox
2009-10-30  0:39         ` David Miller
2009-10-30  8:15       ` Martin Steigerwald [this message]
2009-10-30  8:18         ` Martin Steigerwald
2009-10-30  8:39           ` David Miller
2009-10-30  8:38         ` David Miller
2009-10-30  0:32     ` Alan Cox
2009-10-30  1:47       ` Jeff Garzik

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=200910300915.51836.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=davem@davemloft.net \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --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 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).