linux-kernel - Re: What still uses the block layer?

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]

Message-ID: <4713DFA8.6020304@garzik.org>
Date:	Mon, 15 Oct 2007 17:46:16 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Rob Landley <rob@...dley.net>
CC:	Neil Brown <neilb@...e.de>, Theodore Tso <tytso@....edu>,
	James Bottomley <James.Bottomley@...eleye.com>,
	Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, Jens Axboe <axboe@...e.de>,
	Suparna Bhattacharya <suparna@...ibm.com>,
	Nick Piggin <piggin@...erone.com.au>
Subject: Re: What still uses the block layer?

Rob Landley wrote:
> I realize that both views are valid.  This is why the US has a house and a 
> senate, and filters things through both views.  My gripe is that forcing my 
> laptop to look at my USB devices to find my SATA hard drive is aligned with 
> only one of those viewpoints, and completely opposed to the other.
> 
> An approach that makes things much easier on laptops is seen to hurt big iron, 
> not because it the approach itself has a direct negative impact on big iron, 
> but only because then laptops are not saddled with the problems of big iron.

And we are telling you that, in a modern hotplug world -- yes even on a 
laptop -- you are clinging too much to assumptions that were never 100% 
true in the first place, and much less so on today's laptops.

When you can unplug a SATA drive from a laptop, and plug it back in via 
USB, you can see how unwise it is to hardcode device names into your fstab.

We invented udev, sysfs, mount-by-label, mount-by-uuid, LVM and all 
sorts of other gadgets to make this problem go away.

If you ignore the solutions that exist to solve these problems, then of 
course annoyances will persist as the state of hardware marches forward.

	Jeff

-
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/