| 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
| ||
|
Message-ID: <20150305122649.GC623@swordfish> Date: Thu, 5 Mar 2015 21:26:49 +0900 From: Sergey Senozhatsky <sergey.senozhatsky@...il.com> To: Karel Zak <kzak@...hat.com> Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, Minchan Kim <minchan@...nel.org>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org, Jerome Marchand <jmarchan@...hat.com> Subject: Re: [PATCH 0/2] make automatic device_id generation possible On (03/05/15 13:02), Karel Zak wrote: > > hm, you never know what people can come up with. that's probably the > > strongest support argument I can provide. I wish there was something > > like - my friend Mike has a "device /dev/zram1 is always swap device, > > device /dev/zram$(id -u) is a per-user zram device (he finds it useful, > > I have doubts that promise stable device names is good idea. The usual > way is to care about FS/SWAP identifiers (LABEL=, or UUID=), and for > example udevd should be able to create a stable /dev/disk/by-* > symlinks. > > So for your friend Mike is better to have UUID= in /etc/fstab and > force mkswap or mkfs to use still the same UUID. +1 for removal from Karel. thanks. -ss -- 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