Steve,
I am willing to accept your reasoning.
I just want to mention that in times where other distributions introduce and
advertise systemd,
any "transient" errors, which IMHO make upstart *look* unreliable in comparison,
should be really easy to analyse/track down at least, i.e "clever" diagnostics
could be an advantage.
Again, I can only speculate how many guys gave up on using Ubuntu for
reasons like the current problem.
Maybe mentioning something in the manual for fstab is a start:
(Oneiric)
man fstab | grep -B 1 -A 2 UUID | head -5
Instead of giving the device explicitly, one may indicate the
(ext2 or xfs) filesystem that is to
be mounted by its UUID or volume label (cf. e2label(8) or
xfs_admin(8)), writing LABEL=<label> or
UUID=<uuid>, e.g., `LABEL=Boot' or
`UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will make the
system more robust: adding or removing a SCSI disk
changes the disk device name but not the
filesystem volume label.
This encourages the use of labels and/or UUIDs without the slightest
hint for possible drawbacks.
BTW,
is there an explicit reason why especially cryptsetup needs to intermediately
hide the device which is typically already successfully unencrypted ?
Shouldn't that problem be fixed on a lower level before even the device *node*
is created ?
I.e. is the crypt dm layer disclosing the "device data structure to be" too
early to the kernel ?
Is udev listening on that device node creation ?
Maybe there could be improved udev rules ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719563
Title:
mountall: fatal error: cannot open /dev/mapper/crypthome_unformatted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719563/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
