Hi folks, Last week, the first release candidate for util-linux-2.19 was released. The package is ready in Base:System for testing (not yet submitted to Factory - see below). From the package changelog: * lsblk(8): - this NEW COMMAND lists information about all or selected block devices in tree-like format. * partx(8): - this command has been rewritten to use libblkid for partition tables parsing. It supports aix, bsd, dos, gpt, mac, minix, sgi, solaris_x86, sun, ultrix and unixware now. - supports new command line option "--show" to list partitions in new format - prints UUID and name for GPT and mac partitions * findmnt(8): - supports new command line option "--submounts" to list all submounts for selected mountpoint(s) * agetty(8): - supports new command line options "-c" and "-s" to reuse already initialized tty cflags and existing baud rate * mount(8), umount(8): - could be linked with libmount (--enable-libmount-mount) to manage userspace mount options outside /etc/mtab on systems where the file is a symlink to /proc/mounts. (EXPERIMENTAL, enabled in openSUSE package) * losetup(8), mount(8): - uses /sys/dev/block/<device>/loop/backing_file rather than loopdev ioctls (requires kernel >= 2.6.37) * fsck(8): - supports new command line option "-l" to lock whole-disk device by exclusive flock(2). This option is recommended when more fsck(8) instances are executed in the same time. * rtcwake(8): - supports new mode "show" to print the current RTC alarm time * fstrim(8): - this NEW COMMAND allows to discard unused blocks on a mounted filesystem (wrapper for FITRIM ioctl) * swapon(8): - supports new options "discard" and "nofail" The most important change is that mount(8) and umount(8) can manage userspace mount options without writable mtab, which allows /etc/mtab to be symlink to /proc/self/mounts. This is important for systemd, which requires mtab to be such symlink. /etc/mtab is converted to the symlink automatically by the package in the %post phase. OK, now to the point: the package is ready for testing in Base:System. I did some testing and it worked fine for me, but since the switch to RO mtab and (u)mount linked to (still experimental) libmount is not a trivial change, and we already had Milestone 5, I'd like to hear some opinions whether this should GO/NOGO to Factory (to get to 11.4). Personally, I'm in favor of "GO". BTW, here's example output (on my system) from the two recently added commands. Cool, isn't it? :) $ lsblk NAME MAJ:MIN RE SIZE RO MOUNTPOINT sda 8:0 0 189.9G 0 ├─sda1 8:1 0 2G 0 /boot ├─sda2 8:2 0 50G 0 /home ├─sda3 8:3 0 39.1G 0 / ├─sda4 8:4 0 1K 0 ├─sda5 8:5 0 2.9G 0 [SWAP] ├─sda6 8:6 0 8.5G 0 └─sda7 8:7 0 953M 0 └─test (dm-0) 253:0 0 10M 0 fd0 2:0 1 4K 0 sr0 11:0 1 1024M 0 $ findmnt TARGET SOURCE FSTYPE OPTIONS / /dev/sda3 ext4 rw,relatime,user_xattr,acl,commit=30,barrier=0,data=writeback ├─/sys sysfs sysfs rw,relatime │ ├─/sys/kernel/debug debugfs debugfs rw,relatime │ ├─/sys/kernel/security securityfs securityfs rw,relatime │ └─/sys/fs/fuse/connections fusectl fusectl rw,relatime ├─/dev devtmpfs devtmpfs rw,relatime,size=1543852k,nr_inodes=385963,mode=755 │ ├─/dev/shm tmpfs tmpfs rw,relatime │ └─/dev/pts devpts devpts rw,relatime,mode=600,ptmxmode=000 ├─/proc proc proc rw,relatime ├─/boot /dev/sda1 ext2 rw,relatime,errors=continue,user_xattr,acl ├─/home /dev/sda2 ext3 rw,relatime,errors=continue,commit=30,data=writeback │ ├─/home/puzel/.gvfs gvfs-fuse-daemon fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=10118,group_id=100 │ ├─/home/puzel/OBS obsfs fuse.obsfs rw,nosuid,nodev,relatime,user_id=10118,group_id=100 │ └─/home/puzel/IBS obsfs fuse.obsfs rw,nosuid,nodev,relatime,user_id=10118,group_id=100 ├─/var/tmp/build-root tmpfs tmpfs rw,relatime,size=5242880k ├─/var/lib/ntp/proc proc proc ro,nosuid,nodev,relatime └─/mnt/tmp /dev/mapper/test ext2 rw,relatime,errors=continue Thanks, Petr -- Petr Uzel IRC: ptr_uzl @ freenode