On Wednesday 19 June 2013 13:59:48 Ladislav Slezak wrote:
Will be fixed in the next version (https://github.com/yast/ycp-killer/issues/467)
on the other issue with the iso.. by default the partitioner when new partitions are created puts them in fstab by id
/dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part3 swap swap defaults 0 0 /dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part6 / ext4 acl,user_xattr 1 1 /dev/disk/by-id/ata-ST3500418AS_9VM66M4C-part7 /home ext4 defaults 1 2
However if let like this the computer will not mount the partitions. if one changes to uuid everything is fine... However this is not a yast bug just one which prevented me to test the yast ruby installer.
OK, just check if it is also present in the official M2 or it is in our build only.
This is also present in the standard factory builds and is caused by an update of systemd and especially the new rule 61-msft.rules. This one seems to make it impossible to mount partitions based on their disk-by-id and the only way around it is either to use /dev/sd... or to use the UUID of the disk. The change was created by Robert Milasan based on a inaccessible bug report. Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org