[03:09] sarnold: a link to a russian site? yeah... don't think that was their output either [03:10] pragmaticenigma: yeah.. [03:10] I think we have a troll [03:19] or someone without a clue... I'm out for the night... ttfn [08:12] good morning [08:15] Good morning [11:26] good afternoon [13:41] I don't even know where to begin with Manny... that's all over the palce [13:41] its that time again.. [14:03] They're going to be in for a rude awakening when they find out 32 bit installs are no longer supported with Ubuntu [14:08] pragmaticenigma: that is not true [14:11] leftyfb: There are no images for 20.04 [14:11] pragmaticenigma: there are not images for 19.10 either. That doesn't mean it's not supported. [14:11] leftyfb: I said 32 bit installs... not 32 bit support .. big difference there [14:12] though it's funny, they still created a broken link for i386 for 19.10 http://cdimage.ubuntu.com/netboot/19.10/ [14:14] little annoyed that they don't even make an initrd for it [14:14] that'll be a fun project for me. ... see if I can make one up myself [14:15] I just switched to a different distro ... MX Linux has been working well for my older machines (and took care of a really annoying display issue I was having with a laptop) [22:40] Hi, I just followed Full_Disk_Encryption_Howto_2019 and have feedback. The page pointed me here. [22:41] There were a number of paths like in this line: cryptsetup open ${DEV}p1 LUKS_BOOT [22:41] ${DEV}p1 <---- I found that I had to remove the p from this an other lines like it. This was for the p1 and p5 examples. [22:41] Other than that, everything seems to have worked. [23:24] it does depend upon which kind of device if the 'p' is needed [23:26] I think only nvme uses p [23:27] yeah [23:28] brw-rw---- 1 root disk 259, 3 Jan 28 16:27 /dev/md126p1 [23:28] etc [23:28] ah applies to mdraid member disks too?