libera/#devuan/ Sunday, 2020-02-09

tuxd3vhello all,01:03
tuxd3vin beowulf, does any one is experiencing problems in gparted not being able to read 'ext4' filesystems?01:04
MentalPatientAnyone know if Pi-Hole works on Devuan?02:14
gnarfacei don't know, but i strongly suspect you could manually make the same changes02:16
gnarfaceisn't it just a bunch of iptables and dns settings basically?02:16
gnarfacea raspbian deb might install and work or might install and break, or might need to be recompiled without patching or might need patches even just to change "raspbian" to "devuan" ... there's no way to know without trying but it will definitely void your warranty02:18
MentalPatientNo idea, I know their install fails with 'os not supported' on alpine. :-)02:18
MinceRthere's warranty?02:18
gnarfaceMinceR: technically yes but it just explicitly states that there is no warranty02:19
gnarfacein #debian they would also say "if you break it you get to keep all the pieces"02:19
MinceR:>02:26
jsxofHi. Are utils such as lsblk, fdisk, poweroff etc. missing for you after doing a dist-upgrade from ASCII to Beowulf?16:04
fsmithredjsxof, no, I didn't lose those things.16:04
fsmithredbut root's path changed in beowulf16:05
fsmithreduse 'su -' instead of 'su' to get root's real path (inclucing sbins)16:05
fsmithredor...16:05
fsmithreduse the full path to the command16:05
jsxoffsmithred: Oh, everything works now. Thanks.16:06
fsmithredhang on and I'll get the fix for you16:06
jsxofOh, BTW, there might be something wrong with initramfs-tools or dropbear-initramfs. Somehow the initramfs doesn't have lsblk required for cryptroot-unlock script to work.16:09
fsmithreddid you encrypt your root partition?16:09
fsmithredand if so, did you use '--type luks1' format?16:10
jsxofYep. I mean, it worked back on ASCII, but after upgrading to Beowulf something went wrong. Give me a moment and I'll show you what cryptroot-unlock prints out.16:11
jsxofIt says: "Try again later" no matter how much time I wait.16:13
fsmithredok, but grub can't handle luks2 format, and that's the default now.16:13
fsmithredweird16:13
fsmithredto change root's path, you're supposed to add some words to /etc/login.defs16:13
fsmithredbut I can't find the words now16:13
jsxofI mean, the root partition is luks1 encrypted anyway.16:14
fsmithredoh, ok16:14
fsmithredthen it should work16:15
fsmithredis /boot in the encrypted partition, or is it separate?16:15
jsxofIt's separate.16:15
fsmithreddpm16:16
fsmithreddon't paste output here - too many lines will get you bounced16:16
fsmithredspamfilter16:16
jsxofdpm?16:18
fsmithredmisplaced fingers16:18
fsmithredthis is pissing me off big time. I found the information in buster relase notes easily a couple weeks ago. Now it's gone.16:19
fsmithredALWAYS_KEEP something or other16:19
fsmithredmotherfuckers could have put it in the config file commented out, but they didn't.16:19
chillfanI found lvm completely broke on me lately in ascii after an upgrade16:19
fsmithredI don't know if I've tried upgrading an encrypted ascii to beowulf.16:20
chillfanno it was just regular upgrade, I think grub update killed it16:20
chillfananyway right now using beowulf LUKS2 lvm16:21
fsmithredluks2 on root partition?16:21
jsxofOh, that's very weird. Somehow dropbear and cryptroot were launched twice at init16:21
chillfanyeah, used debian installer then migrated it16:21
chillfanso presumably grub will do luks2 as of beowulf16:21
fsmithredgrub is not supposed to work with luks2 root partition16:21
fsmithreddidn't work for me16:22
fsmithredI changed the live installer to get around that issue16:22
chillfanwell, cryptsetup status gives me type:    LUKS216:22
chillfanunless it's just saying that16:22
chillfanreally, so I wonder what's going on there. Seems like a lot of issues in grub now anyway16:23
chillfanI saw others had issues with lvm not opening crypt partitions, maintainer said it was a missing module, but the provided solution was a no fix for me16:23
chillfanmaybe they've tinkered with it too much16:24
fsmithredkeysize: 512 bits16:24
jsxofI've found a way to proceed through the initramfs stage. I just had to kill all cryptroot processes and run cryptroot-unlock without a daemon running.16:24
fsmithredwould be luks216:24
chillfanyeah, 51216:24
chillfangrub-pc 2.02+dfsg1-20, grub2-common same version16:25
chillfankernel is 4.19.0-8-amd6416:25
chillfanbut i'm sure -06-amd64 was working too16:26
fsmithredALWAYS_SET_PATH16:26
fsmithred^^^ in /etc/login.defs should fix the root path issue. (I think)16:27
fsmithred=yes16:27
fsmithredno, not =yes16:27
jsxoffsmithred: Yep, that works. Thanks.16:30
fsmithredwhich works?16:30
fsmithredI found what I was looking for...16:31
fsmithredPut ALWAYS_SET_PATH yes in /etc/login.defs to get an approximation of the old behavior. This is documented in su(1) but not in login.defs(5). It may also cause a harmless error message to appear in some situations (see 905564).16:31
fsmithredhttps://wiki.debian.org/NewInBuster16:31
chillfanah, why no deprecation warning.. that might be why I screwed my system16:32
fsmithredIf I answer that, it'll be a rant.16:33
chillfanI'm only just containing one myself16:34
chillfanalso.. it occurs to me this change might need to be documented by us, to stop hosing of their systems16:34
fsmithredthe luks change or the su change?16:35
chillfanluks16:35
chillfansince upgrade from ascii or migrate from earlier release to beowulf will hose their system16:36
chillfanor make them go and fix it at least16:36
fsmithredyour root partition got converted to luks2 on upgrade?16:36
chillfani migrated from buster to beowulf on this system16:36
chillfanbefore that I had ascii, upgraded to beowulf16:36
chillfanso if it's definitely what caused the problem, our migrations could break things for stretch/jessie users16:38
hemimaniacif I may, I have seen back over the years (I used to be a Mint faithful) depending on the implementation, encryption can wreak havac on a user upgrading from let's say 17-18 , and have seen it with other distros, I was wondering if it a case of the implement and not the OS?16:52
chillfanmaybe, usually you can do it in debian/devuan though16:59
chillfananyway, it's not sure. I'm going to test it tomorrow, see what I find16:59
djphhemimaniac: yes17:09
jsxofBTW, how well does Devuan support runit?17:09
chillfanNot very well that I know, but you should check the DNG mailing list, Steve Litt I think has some scripts somewhere17:10
hemimaniachi djph17:11
hemimaniaclol17:11
jsxoffsmithred: that ALWAYS_SET_PATH setting breaks runit17:11
jsxof>configuration error - unknown item 'ALWAYS_SET_PATH' (notify administrator)17:11
djph'lo hemimaniac17:12
fsmithredin /etc/login.defs?17:12
fsmithredshould say17:12
fsmithredALWAYS_SET_PATH yes17:12
jsxofYep. When I do that, runit can't install properly. I think it might be something about usermod.17:13
fsmithredok, other way to make the change is in /root/.bashrc17:15
fsmithredexport PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin17:15
jsxofI've just switched my system to runit, but it seems like it's still executing sysv runlevels. Is it an intended thing? Is there a way to make runit-init run only /etc/sv scripts?18:33
golinuxjsxof: ping stevelitt on #debianfork18:33
divansantanadoes devuan ascii use grub1 or 2? I've got a home system unable to boot. Not getting to grub.19:58
chillfanhere you go https://pkginfo.devuan.org/20:00
chillfanyou can find it all there, but for that package looks to be 2.02~beta3-520:02
divansantanahmm, i weirdly have grub1 and grub2 installed. Trying to run grub-install /dev/sde results in /boot/grub/stage1 not read correctly20:34
chillfanyou can explicitly try grub2, apt install grub2 and then remove grub120:35
chillfani'm not as familiar with it though, I use grub-pc20:35
fsmithredyou guys are confusing me with your talk of grub1 and grub220:36
fsmithredI know grub-legacy and grub-pc/grub-efi-blah20:36
chillfani think it's just grub-pc vs grub2..20:36
fsmithredfor package names20:36
fsmithredgrub-pc is grub220:36
chillfani don't rightly know the difference20:36
fsmithredgrub1 is grub-legacy20:36
chillfanah20:37
fsmithredit has /boot/grub/menu.list20:37
fsmithredor .lst20:37
fsmithredI forget which20:37
chillfanthink it's just been a while and I was confusing grub-legacy with grub-pc.. which might have been grub1 before20:37
fsmithredbtw, I'm in the middle of stretch encrypted migration to beowulf20:38
tuxd3vhello all,20:38
fsmithredhi tux20:38
chillfanmy energy for testing has petered out for today, or I'd be doing the same20:38
tuxd3vfsmithred, grub-common, is installed on my i386 install20:39
fsmithredlol, I know the feeling20:39
fsmithredtuxd3v, grub-common is installed with all versions of grub, I think20:39
divansantanaok while I think I mixed installed two of them .20:39
tuxd3vfsmithred, I also have installed grub2-common20:39
chillfanyeah probably20:39
divansantanagrub-install (version 1/boot/grub/stage1 not read correctly / legacy) was reporting /boot/grub/stage1 not read correctly20:39
divansantanagrub2 grub-install seems to work20:40
divansantanahopefully it boots20:40
fsmithredremember to update-grub20:40
fsmithredso you have a boot menu20:40
tuxd3vyeah, update grub..20:40
divansantanawith grub2 that is grub-mkconfig -o /boot/grub/grub.cfg i think20:40
divansantanaor just update-grub ?20:41
chillfanWhat I noticed, dpkg-reconfigure grub-pc had some issues. So sometimes you now need first grub-update, grub-install /dev/sdX before it will do anything20:41
fsmithredyeah, update-grub is easier to remember20:41
divansantanak20:41
fsmithredit runs grub-mkconfig for you20:41
chillfanah sorry s/grub-update/update-grub/20:41
divansantanagrub-probe: error: cannot find a GRUB drive for /dev/sdg1.  Check your device.map.20:43
fsmithredare you booted into that system now, or are you doing this some other way?20:46
fsmithredand are you trying to install grub to /dev/sdg1 instead of /dev/sdg  ??20:47
divansantanasdg is my iso arch rescue stick20:48
divansantanai booted into arch iso and chroot'ed into devuan to try rescue it20:48
fsmithredok20:49
divansantanamv /boot/grub/device.map{,.old} didn't help20:49
fsmithredyou bind-mount dev proc sys to /target?20:49
fsmithredor whatever is your mountpoint20:49
divansantanayes i chrooted like so for i in proc sys dev ; do mount /$i /mnt/$i ; done20:50
divansantanaand mount --bind /dev/pts /mnt/dev/pts20:50
fsmithredthe others work without the --bind option?20:50
divansantanaexport PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin and mount /dev/md126 /mnt/boot20:50
divansantanachroot /mnt/ /bin/bash20:51
fsmithredis there 1MB free space before the beginning of the first partition?20:53
fsmithredoh...20:54
fsmithredis the disk gpt or msdos partition table?20:54
divansantanamsdos20:54
divansantanabios in legacy mode20:55
fsmithredok20:55
fsmithredI can't think of anything else now20:55
divansantanait might still boot20:58
divansantanabecause grub-install (with v2 of grub) worked. So hopefully it gets to grub menu now.20:58
GyrosGeier20:43 < divansantana> grub-probe: error: cannot find a GRUB drive for /dev/sdg1.  Check your device.map.21:16
GyrosGeiergrub needs to go to the MBR21:16
vmontressorSilly question: where do I find raspistill? (For a Pi3, if it matters.) It doesn't show up in apt-cache search, and while I think it used to be in raspi3-firmware, it isn't any more. Any pointers?21:20

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!