For me, the most important thing is that number of the project contributors is growing and we are able to coordinate our changes with another upstream projects like coreutils, procps-ng or systemd and maintainers from distributions contribute to the project.
The commands like mount(8), umount(8) or swapon(8) support new tags PARTLABEL=
and PARTUUID=. It means that you can address partitions by name or UUID independently on the filesystem on the device. You don't have to care about your fstab after mkfs or mkswap. The setting with PARTUUID= will be always valid.
Finally, we have dmesg --follow to print new kernel messages (like tail -f). This feature depends on readable /dev/kmsg (since kernel 3.5.0). I have also implemented a new dmesg output format --reltime (suggested by Linus on lkml):
$ dmesg --reltime ... [Aug26 10:58] scsi_debug: host protection [ +0.000004] scsi84 : scsi_debug, version 1.82 , dev_size_mb=50, opts=0x0 [ +0.000546] scsi 84:0:0:0: Direct-Access Linux scsi_debug 0004 PQ: 0 ANSI: 5 [ +0.000173] sd 84:0:0:0: Attached scsi generic sg1 type 0 [ +0.000356] sd 84:0:0:0: [sdb] 102400 512-byte logical blocks: (52.4 MB/50.0 MiB) [ +0.000988] sd 84:0:0:0: [sdb] Write Protect is off [ +0.000004] sd 84:0:0:0: [sdb] Mode Sense: 73 00 10 08
The low-level userspace tools consolidation continues:
- sulogin(1) and utmpdump(1) from sysvinit merged into util-linux (the goal is to remove all init independent utils from sysvinit package)
- eject(1) reimplemented to use /proc and /sys information and libmount and moved to util-linux
- new command lslocks(8) as replacement for dead lslk(8)
The tool lsblk(8) supports reverse trees, it means that you can see whole stack of the block devices from top to down:
$ lsblk -s /dev/mapper/luks-10d813de-fa82-4f67-a86c-23d5d0e7c30e NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT luks-10d813de-fa82-4f67-a86c-23d5d0e7c30e (dm-0) 253:0 0 39.1G 0 crypt /home/kzak └─sda6 8:6 0 39.1G 0 disk └─sda 8:0 0 149.1G 0 disk
The most invasive change is a new non-recursive build-system (just for the record: autotools are the best :-)). The result is faster build, binaries are in one top-level build directory rather than in many subdirectories, make distcheck calls our regression etc.
The another big change is fdisk refactoring. This is slow and painful work, but the result should be GPT support in release 2.23 (patches from Davidlohr Bueso are already in mailing list). I hope that one day the default fdisk will be nice, readable (colored?) low-level tool without some obsolete junk like CHS.
Note that in the next util-linux release 2.23 we're going to remove cryptoloop support. Yes, cryptoloop is bad and dead, use dm-crypt. (Note that util-linux upstream has never supported loop-AES.)
Are you going to document how to dm-decrypt devices encrypted with cryptoloop? Current dmsetup(8) manual page is very brief.ReplyDelete
cryptoloop is NOT bad and dead.ReplyDelete
It's alive and well, except for what util-linux developers have thrown at it.
dmcrypt is slower and inferior to loop-AES. That's still the way it is today. You guys are making the wrong decision and most people familiar with this issue know it. So I guess mask the updates until some sensible developer replaces you.
I think your blog will help me understand coding a bit – But first, I need to watch a few YouTube tutorials. I am a Professional Copywriter – but now I think I should also educate myself a bit in coding – to add an additional skill to my arsenal.ReplyDelete
I was reading some of your content on this website and I conceive this internet site is really informative ! Keep on putting up. If you're looking for the cosmetics stores online n the world, this list has something for everybody!
I have read your blog post and that is really informative as well. My friend recommended your blog and trust me through reading such amazing updates we are able to change our perception as become part of my day because you never know designer bags online how much you make my day happier and more complete. Buy tshirt online