Jan Engelhardt wrote:
On Thursday 2014-05-15 17:37, Arvin Schnell wrote:
/sbin/swapon --fixpgsz '/dev/sda1': /sbin/swapon: /usr/lib64/libmount.so.1: version `MOUNT_2.22' not found (required by /sbin/swapon) /sbin/swapon: /usr/lib64/libmount.so.1: version `MOUNT_2.24' not found (required by /sbin/swapon) /bin/mount -t ext4 -o acl,user_xattr '/dev/sda2' '/mnt': /bin/mount: /usr/lib64/libmount.so.1: version `MOUNT_2.25' not found (required by /bin/mount) /bin/mount: /usr/lib64/libmount.so.1: version `MOUNT_2.23' not found (required by /bin/mount) /bin/mount: /usr/lib64/libmount.so.1: version `MOUNT_2.24' not found (required by /bin/mount) /bin/mount: /usr/lib64/libmount.so.1: version `MOUNT_2.22' not found (required by /bin/mount) Does the kernel match your installation medium?
Would it be too much to ask for a minor consistency of if the util is located on /sbin or /bin, that it's libraries be located in /lib64? Not all people have '/usr' on the same file system as '/bin' and '/sbin'. And I'm not talking "softlinks"...as that won't resolve links like "../lib64" for binary relative paths. I'm talking /bin and /sbin being able to resolve ../lib64 for their libraries, whether at either "/{,usr}". The cygwin people also ran into issues were not having "bin" and "sbin" on the same partition as their libs was a requirement. After booting, if some utils require random paths to work maybe they could use unionfs to mount /bin on /usr/bin (...etc)? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org