# HG changeset patch # User František Kučera # Date 1543959216 -3600 # Node ID d342de2e09a48d0757aad1baf17b6028094389dd # Parent 029dc972f1f2dd93c91dc994d2b9aef1a70e3dd1 examples: fstab formatting using -in-fstab, -out-nullbyte, xargs and Perl diff -r 029dc972f1f2 -r d342de2e09a4 relpipe-data/examples.xml --- a/relpipe-data/examples.xml Tue Dec 04 18:43:01 2018 +0100 +++ b/relpipe-data/examples.xml Tue Dec 04 22:33:36 2018 +0100 @@ -38,6 +38,77 @@ If an error is found, it is reported on STDERR. So just omit the & in order to see the error message.

+ +

/etc/fstab formatting using -in-fstab, -out-nullbyte, xargs and Perl

+ +

+ As we have seen before, we can convert /etc/fstab (or mtab) + to e.g. an XML or a nice and colorful table using . + But we can also convert these data back to the fstab format. And do it with proper indentation/padding. + Fstab has a simple format where values are separated by one or more whitespace characters. + But without proper indentation, these files look a bit obfuscated and hard to read (however, they are valid). +

+ + + +

+ So let's build a pipeline that reformats the fstab and makes it more readable. +

+ + relpipe-in-fstab | relpipe-out-fstab > reformatted-fstab.txt + +

+ We can hack together a script called relpipe-out-fstab that accepts relational data and produces fstab data. + Later this will be probably implemented as a regular tool, but for now, it is just an example of a ad-hoc shell script: +

+ + + +

+ In the first part, we prepend a single record (relpipe-in-cli) before the data coming from STDIN (cat). + Then, we use relpipe-out-nullbyte to convert relational data to values separated by a null-byte. + This command processes only attribute values (relation and attribute names are skipped). + Then we used xargs to read the null-separated values and execute a Perl command for each record (pass to it a same number of arguments, as we have attributes: --max-args=7). + Perl does the actual formatting: adds padding and does some little tunning (merges two attributes and replaces empty values with none). +

+ +

This is formatted version of the fstab above:

+ + + +

+ And using following command we can verify, that the files differ only in comments and whitespace: +

+ +
relpipe-in-fstab | relpipe-out-fstab | diff -w /etc/fstab -
+ +

+ Regular implementation of relpipe-out-fstab will probably keep the comments + (it needs also one more attribute and small change in relpipe-in-fstab). +

+ +

+ For just mere fstab reformatting, this approach is a bit overengineering. + Wo could skip the whole relational thing and do just something like this: +

+ + cat /etc/fstab | grep -v '^#' | sed -E 's/\s+/\n/g' | tr \\n \\0 | xargs -0 -n7 ... + +

+ plus prepend the comment (or do everything in Perl). + But this example is intended as a demostration, how we can + 1) prepend some additional data before the data from STDIN + 2) use and traditional tools like xargs or perl together. + And BTW we have implemented a (simple but working) relpipe output filter – and did it without any serious programming, just put some existing commands together :-) +

+ +
+

+ There is more Unix-nature in one line of shell script than there is in ten thousand lines of C. + see Master Foo and the Ten Thousand Lines +

+
+ diff -r 029dc972f1f2 -r d342de2e09a4 relpipe-data/examples/relpipe-out-fstab.formatted.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/relpipe-data/examples/relpipe-out-fstab.formatted.txt Tue Dec 04 22:33:36 2018 +0100 @@ -0,0 +1,6 @@ +# +UUID=29758270-fd25-4a6c-a7bb-9a18302816af / ext4 relatime,user_xattr,errors=remount-ro 0 1 +/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 +/dev/sde /mnt/data ext4 relatime,user_xattr,errors=remount-ro 0 2 +UUID=a2b5f230-a795-4f6f-a39b-9b57686c86d5 /home btrfs relatime 0 2 +/dev/mapper/sdf_crypt /mnt/private xfs relatime 0 2 diff -r 029dc972f1f2 -r d342de2e09a4 relpipe-data/examples/relpipe-out-fstab.sh --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/relpipe-data/examples/relpipe-out-fstab.sh Tue Dec 04 22:33:36 2018 +0100 @@ -0,0 +1,22 @@ +#!/bin/bash + +( + # Just troll-in the first record: + relpipe-in-cli generate Heathers 7 \ + Duke string McNamara string Chandler string Veronica string J.D. string \ + Big string Fun string \ + '' '# ' '' '' '' '' ''; + # relpipe-out-nullbyte processes only attribute values + # Read the actual pipe's input: + cat +) | relpipe-out-nullbyte \ + | xargs --null --max-args=7 perl -e \ + 'printf("%-*s %-*s %-*s %-*s %-*s %s\n", + # following numbers define paddings: + 50, ($ARGV[0] eq "" ? $ARGV[1] : "$ARGV[0]=$ARGV[1]"), + 40, ($ARGV[2] eq "" ? "none" : $ARGV[2]), + 16, $ARGV[3], + 50, $ARGV[4], + 8, $ARGV[5], + $ARGV[6] + );' diff -r 029dc972f1f2 -r d342de2e09a4 relpipe-data/examples/relpipe-out-fstab.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/relpipe-data/examples/relpipe-out-fstab.txt Tue Dec 04 22:33:36 2018 +0100 @@ -0,0 +1,13 @@ +# /etc/fstab: static file system information. +# +# Use 'blkid' to print the universally unique identifier for a +# device; this may be used with UUID= as a more robust way to name devices +# that works even if disks are added and removed. See fstab(5). +# +# +# / was on /dev/vda1 during installation +UUID=29758270-fd25-4a6c-a7bb-9a18302816af / ext4 relatime,user_xattr,errors=remount-ro 0 1 +/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 +/dev/sde /mnt/data ext4 relatime,user_xattr,errors=remount-ro 0 2 +UUID=a2b5f230-a795-4f6f-a39b-9b57686c86d5 /home btrfs relatime 0 2 +/dev/mapper/sdf_crypt /mnt/private xfs relatime 0 2 \ No newline at end of file