Matthias Schniedermeyer wrote:Would've been nice if they worked, but they don't. Disks should be so easy to identify uniquely, because they have storage space that can be used for that label. So I tried (debian linux, last year). Mount by label was fine, of course. Until the 33rd reboot, when it was decided that a fsck was necessary "just to be safe". The problem was that fsck fail to find the correct device when /etc/fstab specifies a label instead of a device. The boot failed, reboot with init=/bin/sh and replace the dysfunctional labels with oldfashioned device names. I can live with this kind of problem on my desktop, but this machine was going to be a internet router for a customer, so occational boot failure requiring intervention was not an option. Helge Hafting --
| Jeremy Fitzhardinge | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Mike Galbraith | Re: regression: CD burning (k3b) went broke |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Linus Torvalds | Re: [GIT]: Networking |
| Michael Grollman | Re: 8169 Intermittent ifup Failure Issue With RTL8102E Chipset in Intel's New D945... |
