| u-amarsh04 | weird, I now have no /etc/resolv.conf - resolvconf is installed and am using isc-dhcp-client | 03:33 |
|---|---|---|
| rwp | If there is no /etc/resolv.conf file then glibc will default to using nameserver 127.0.0.1 if I recall correctly. If you have a local caching resolver installed then it will work without any config file. | 03:40 |
| rwp | Missing will be any DNS search path though. | 03:40 |
| rwp | It's not a configuration I would recommend but it is a defined configuration that works to the extent it works. | 03:40 |
| sfox | Can XFS be configured to checksum data too, not just the journal? | 07:30 |
| plasma41 | sfox: Based on https://en.wikipedia.org/wiki/Comparison_of_file_systems#Block_capabilities it doesn't look like it | 07:48 |
| plasma41 | sfox: At least not on its own. My brief research seems to indicate dm-verity may be relevant to the task of checksuming data on XFS, but I have no experience using it. | 07:54 |
| cousin_luigi | Is invoking an init script from itself, but with a different switch, bad form? | 08:01 |
| sfox | thanks. | 08:07 |
| sfox | is dm-verity different from dm-integrity? | 08:08 |
| sfox | if I already have a encrypted LVM is there any way to add block integrity to LVM? | 08:10 |
| sfox | I wonder if I should just use authenticated luks instead | 08:22 |
| u-amarsh04 | thanks rwp | 08:53 |
| cousin_luigi | http://paste.debian.net/hidden/bc0272a3/ <- this must be the reason why insserv won't create those dependency files. But what has dbus to do with elogind? And why does this happen only on one of my devuan VMs? | 13:00 |
| cousin_luigi | hmm, cleaned by some judicious application of update-rc.d | 13:03 |
| |cos| | I got a "Waiting for /dev to be populated." blocking my for about thirty minutes yesterday. It didn't reoccur after power-cycling. No way of reproducing. Figured it's worth casually mentioning it here though. | 13:05 |
| |cos| | *blocking my boot | 13:05 |
| djph | |cos|: I'd hazard some drive (either internal or USB, etc) was taking /forever/ | 13:19 |
| |cos| | God known what device it was waiting for... I added some udev-debug flag to grub's list of kernel arguents, in case it ever happens again. | 13:35 |
| cousin_luigi | I think I'm almost there with insserv | 13:40 |
| djph | |cos|: heh, yeah, assuming you've made no changes, quick smart check (and maybe a connector check) may be in order. | 13:52 |
| u-amarsh04 | been up too late before an early start tomorrow, but wondered if someone could write something better than what I did regarding usrmerge and firmware-amd-graphics https://dev1galaxy.org/viewtopic.php?pid=46429#p46429 | 14:01 |
| u-amarsh04 | kept things minimalist and factual on that post rather than ranting on how much trouble I had because of usrmerge breakage | 14:02 |
| djph | u-amarsh04: "usrmerge: don't" ? | 15:16 |
| u-amarsh04 | djph - the firmware-amd-graphics update forced me to deal with the usrmerge mess | 15:38 |
| djph | note to self, be glad you have intel :) | 15:41 |
| djph | u-amarsh04: I'll have to read it later, TBH, it sounds like there is still much division amogst even Debian people re usrmerge | 15:42 |
| u-amarsh04 | not a well-designed and implemented change process anyway | 15:43 |
| djph | I mean, like on the one hand I sorta get what they're trying to say/do ... on the other hand "no, stop, you're doing it wrong." | 15:48 |
| cousin_luigi | usrmerge? I thought it was done. | 19:09 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!