mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hancockrwd@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide: update Kconfig text to mark as deprecated
Date: Thu, 29 Oct 2009 17:30:28 -0700 (PDT)	[thread overview]
Message-ID: <20091029.173028.248393897.davem@davemloft.net> (raw)
In-Reply-To: <51f3faa70910291719kecb5edcp3b8812981b69acb1@mail.gmail.com>

From: Robert Hancock <hancockrwd@gmail.com>
Date: Thu, 29 Oct 2009 18:19:03 -0600

> I think people would be better off just updating their fstab and being
> done with it.. preferably switching to something like mounting by
> label or UUID so that things just work even if the devices get
> reordered when they rearrange their cables or add a new controller,
> etc. Every Fedora/Red Hat-derived OS has set things up this way by
> default for years..

You can't just make devices dissapear without providing some
kernel option or similar that keeps things working.

My very own machines will break unless that happens.

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.

And god forbid I actually want to test some -stable IDE fix on this
machine :-)

And I know I won't be the only person in this kind of situation.

So, proceeding in any other way is really a non-starter.

  reply	other threads:[~2009-10-30  0:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27  1:41 Robert Hancock
2009-10-29 10:13 ` David Miller
2009-10-30  0:19   ` Robert Hancock
2009-10-30  0:30     ` David Miller [this message]
2009-10-30  0:33       ` Alan Cox
2009-10-30  0:39         ` David Miller
2009-10-30  8:15       ` Martin Steigerwald
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=20091029.173028.248393897.davem@davemloft.net \
    --to=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

all inboxes | Powered by JetHome®