lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 29 Oct 2009 17:30:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hancockrwd@...il.com
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: [PATCH] ide: update Kconfig text to mark as deprecated

From: Robert Hancock <hancockrwd@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ