| fsmithred | get.refracta.org is working again | 01:47 |
|---|---|---|
| debdog | if I'd be a twelve year old girl I'd send a thumbs up smiley | 02:07 |
| debdog | how do grown ups express their feelings? | 02:07 |
| debdog | oops, off topic | 02:08 |
| chubby-cactus | Hello All :^) I'm having trouble with putting /boot on a USB. Can anyone confirm these instructions are still working? https://unix.stackexchange.com/questions/134837/separate-boot-partition-on-usb?rq=1 | 02:12 |
| * _ds_ isn't certain that putting /boot on a bus is a good idea | 02:24 | |
| Xenguy | Grown-ups express their feelings with passion | 02:24 |
| debdog | heehee | 02:26 |
| chubby-cactus | But... But my Security o(╥﹏╥)o | 02:29 |
| golinux | Grown-ups should express themselves wisdom which definitely leaves passion out of the equation | 02:44 |
| golinux | And let's take further discussion to #devuan-offtopic | 02:45 |
| golinux | WITH wisdom (need to proofread better) | 02:45 |
| rwp | chubby-cactus, I don't think there is really anything special about having /boot on USB. If you want it then Just Do It. | 02:46 |
| rwp | However personally I don't see that as being interesting. Since there isn't anything of interest stored in /boot. | 02:46 |
| chubby-cactus | Having /boot on a separate disk can deter some potential risks. It is trivial to write a trojan into a plaintext boot part. Theft would require more sophistication. | 03:04 |
| chubby-cactus | I have already tried following the guide, I'm troubleshooting my install now. Wanted to confirm the instructions aren't dated | 03:05 |
| chubby-cactus | My USB is correctly formatted, my LVM looks correct. I don't know where the problem is. I just boot to a blinking cursor. | 03:07 |
| fsmithred | chubby-cactus, you edited /etc/crypttab and /etc/fstab to point to the new location, using uuid or labels instead of device names? | 03:17 |
| fsmithred | and run update-grub to generate a new boot menu | 03:18 |
| fsmithred | I didn't read the instructions you linked. I'm going to sleep now. | 03:20 |
| fsmithred | oh, grub-install and update-grub and maybe update-initramfs | 03:20 |
| chubby-cactus | @fsmithred All my UUIDs in /etc/crypttab /fstab are matching | 07:03 |
| gnarface | when is the last time you checked? remember resizing or reformatting the partition will change the UUID | 07:11 |
| chubby-cactus | I have the encrypted LVM mounted now | 07:12 |
| chubby-cactus | I | 07:13 |
| chubby-cactus | I am using a Live CD | 07:13 |
| gnarface | oh, encrypted LVM, that's the complication | 07:18 |
| gnarface | there's something you have to do special but i forget what | 07:18 |
| gnarface | i vaguely recall that it might have just involved setting some special environment variable... CRYPTSETUP or something like that? | 07:18 |
| chubby-cactus | I tried to make sure GRUB_ENABLE_CRYPTODISK=y, and adding UUID to boot parameter, but I forgot what file that's in :P | 07:18 |
| gnarface | grub variables go in /etc/default/grub | 07:19 |
| gnarface | disk UUIDs go in /etc/fstab but kernel command-line variables also go in /etc/default/grub | 07:19 |
| gnarface | so it's possible you might have to put the UUID in two files in this case, not sure | 07:20 |
| chubby-cactus | There is something you have to do in addtion to GRUB_ENABLE where you point directly to the encrypted UUID | 07:20 |
| chubby-cactus | I already confirmed all UUIDs match in /etc/crypttab and /fstab | 07:20 |
| chubby-cactus | (•◡•) / | 07:22 |
| chubby-cactus | I added GRUB_ENABLE_CRYPTODISK=y to /etc/default/grub, and "rd.lvm.vg=vg rd.luks.uuid=<>" to GRUB_CMDLINE_LINUX_DEFAULT. Anything else I should add before another reboot? | 07:36 |
| chubby-cactus | Blinking. Cursor. | 08:02 |
| chubby-cactus | (•̀o•́)ง | 08:08 |
| gnarface | i don't know for sure honestly, seems like everyone has trouble with this, but i don't use it | 08:09 |
| gnarface | some people do though, stick around until one of them shows up | 08:09 |
| gnarface | there might be info on the forum | 08:09 |
| gnarface | i think LVM is the source of complication | 08:10 |
| gnarface | maybe you have to feed it a volume id instead of a partition id or soemthing | 08:10 |
| chubby-cactus | Agreed. I'm going to sleep. Thank you kind stranger (ɔ◔‿◔)ɔ ♥ | 08:25 |
| fsmithred | chubby-cactus might need to install cryptsetup-initramfs | 13:45 |
| rwp | All of that (cryptsetup*) would be done automatically by the installer. | 15:14 |
| fsmithred | rwp, it was an upgrade, and there have been some changes in the packages. | 16:06 |
| rwp | Changes?! I must go read the Release Notes carefully then! | 16:07 |
| fsmithred | I've run into it a few times where I had to add a cryptsetup package | 16:08 |
| fsmithred | also, CRYPTSETUP=y in /etc/cryptsetup-initramfs/conf-hook is deprecated/missing. | 16:12 |
| fsmithred | in chimaera | 16:13 |
| AEonFyr | I find myself in the (un)fortunate position of having to recompile a package: strongswan | 19:46 |
| AEonFyr | When I "apt-get build-dep strongswan" I get unmet dependencies on libsystemd-dev & systemd | 19:46 |
| AEonFyr | Is there any online documentation or guide on how to work around this for devuan? | 19:46 |
| AEonFyr | Am reading Packaging Guide for Devuan, the answers are probably in there.... | 19:58 |
| gnarface | maybe it has a --without-systemd option? | 20:28 |
| AEonFyr | apt-get? I don't see such an option. | 20:40 |
| AEonFyr | I've abandoned build-dep for now, proceeded to download the source (apt-get source) and see if I can build it directly | 20:43 |
| brocashelm | also giving me the same problem. building from source is all that you can try now | 20:46 |
| brocashelm | --without-systemd isn't an understood option | 20:46 |
| furrymcgee | you can try to download with apt source then remove --enable-systemd in debian/rules and start the build with with dpkg-buildpackage --no-check-builddeps | 20:57 |
| AEonFyr | Thanks, the build from source has worked and provided what I need for now (a deprecated plugin). | 21:04 |
| furrymcgee | you could ask debian maintainers to add a vendor specic patch file | 21:11 |
| fsmithred | from /usr/share/doc/libelogind0/README.debian: | 21:27 |
| fsmithred | Note that this runtime binary compatibility conflicts with satisfying the build | 21:27 |
| fsmithred | dependency of packages requiring libsystemd-dev. If you need to compile packages | 21:27 |
| fsmithred | against libsystemd-dev on a system with libelogind0 installed you will need to | 21:27 |
| fsmithred | use a build chroot. Suitable tools to achieve this include pbuilder(8), | 21:27 |
| fsmithred | cowbuilder(8) and sbuild(1). | 21:27 |
| avbox111 | I want to install e.foundation easy installer for fairphone 3. It says I need snap. How can I install snap on devuan beowulf? | 22:15 |
| fsmithred | avbox111, you can't | 22:21 |
| fsmithred | it requires systemd | 22:21 |
| golinux | https://pkgmaster.devuan.org/bannedpackages.txt | 22:21 |
| avbox111 | fsmithred: Ok, thank you for the clear answer. | 22:22 |
| fsmithred | appimage works in devuan | 22:23 |
| avbox111 | fsmithred: I know, but there I don't find Easy installer for e.foundation | 22:34 |
| fsmithred | this is a phone OS and it needs systemd??? | 22:35 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!