3 ms·

I'm annoyed that it is getting harder and harder to find what physical filesystems are on a system. My goto commands "df -h" and "mount" are cluttered with all

by m463 2y ago

I'm annoyed that it is getting harder and harder to find what physical filesystems are on a system. My goto commands "df -h" and "mount" are cluttered with all kinds of ephemeral filesystems, with no easy way to filter (say, a one-character flag). lsblk is close but .. lvm and snaps.

ssl-3 2y ago
On my main-driver desktop box that I hamfistedly switched over to Void Linux (on a ZFS root, even) a couple of months ago: The output of df -h looks pretty sane and understandable. I see some entries for /dev and /run and /, some stuff for EFI, a bunch of mounted ZFS datasets, and it's all very readable with no line noise in any column. --- Now, that said: I have some docker containers. My own previous goto command of mount reports a complete clusterfuck, and all of the clusterfucked lines are due to docker doing docker stuff. I don't know how things like 4UYSHHPFBZQNFZ9Z698JDLUZWJ, LK33RZTN5ZNFGPJNDUHM0HTSD1, 2G0A4YYUVCMP9HZSM5UXOJW0BX, ZH29C5YNZHJ22QMY63EWV5RF3P, and 32XOCXBUY41QQJTPPA8HE6EVZ6 add any coherency or clarity[1], but I assume that since the computer quite easily knows what this shit means then it needn't be bothered with dumbing it down so that a human can parse it in any sort of memorable or repeatable or communicable fashion. (Which is, of course, bad behavior on the part of the computer. A UUID is also awful, but at least it has some punctuation so that it can have some cadence if it must be dealt with as-is. It's like we learned nothing from DNS[2], or as if translation layers can't exist even within a filesystem[3].) 1: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2016788/ https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2016788/ 2: https://datatracker.ietf.org/doc/html/rfc1035 https://datatracker.ietf.org/doc/html/rfc1035 3: https://linux.die.net/man/1/ln https://linux.die.net/man/1/ln

by m463 2y ago

ssl-3 2y ago

On my main-driver desktop box that I hamfistedly switched over to Void Linux (on a ZFS root, even) a couple of months ago: The output of df -h looks pretty sane and understandable. I see some entries for /dev and /run and /, some stuff for EFI, a bunch of mounted ZFS datasets, and it's all very readable with no line noise in any column. --- Now, that said: I have some docker containers. My own previous goto command of mount reports a complete clusterfuck, and all of the clusterfucked lines are due to docker doing docker stuff. I don't know how things like 4UYSHHPFBZQNFZ9Z698JDLUZWJ, LK33RZTN5ZNFGPJNDUHM0HTSD1, 2G0A4YYUVCMP9HZSM5UXOJW0BX, ZH29C5YNZHJ22QMY63EWV5RF3P, and 32XOCXBUY41QQJTPPA8HE6EVZ6 add any coherency or clarity[1], but I assume that since the computer quite easily knows what this shit means then it needn't be bothered with dumbing it down so that a human can parse it in any sort of memorable or repeatable or communicable fashion. (Which is, of course, bad behavior on the part of the computer. A UUID is also awful, but at least it has some punctuation so that it can have some cadence if it must be dealt with as-is. It's like we learned nothing from DNS[2], or as if translation layers can't exist even within a filesystem[3].) 1: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2016788/ https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2016788/ 2: https://datatracker.ietf.org/doc/html/rfc1035 https://datatracker.ietf.org/doc/html/rfc1035 3: https://linux.die.net/man/1/ln https://linux.die.net/man/1/ln