[06:25] <doug16k> lol @ that paste from earlier -> https://pastebin.com/GVni4J9u  (4.29 megawatts eh?)
[06:27] <doug16k> SI units are hard apparently
[06:32] <mybalzitch> I wish my psu reported to sensors
[06:34] <doug16k> I can see per core and package wattage on my cpu: https://gist.github.com/doug65536/e4c371b0e75f073bea8e3b6ccd6ed189
[06:35] <doug16k> you sure that isn't the RAPL reading from the cpu in his paste?
[06:35] <doug16k> ^ 3950X btw
[06:35] <mybalzitch> what args are you using
[06:35] <doug16k> none
[06:35] <mybalzitch> also nice chip
[06:35] <doug16k> just sudo turbostat
[06:36] <doug16k> my 2700X didn't have it. the joule counter thing is new in zen 2
[06:37] <doug16k> the cores are ~5 watts pegged at around 4.3GHz-4.7GHz
[06:42] <doug16k> a friend of mine with a 24 core xeon said his 3950X beats it by a significant margin in compilation workloads
[06:43] <doug16k> two socket 12 core I think
[06:43] <mybalzitch> yeah I have a 2 socket 8 core, and a 3950x blows me out of the water
[07:05] <lordievader> Good morning
[15:07] <uzee> Hi, has anything changed on the Ubuntu preseed installation? I've using the same netboot image and a preseed file for Ubuntu 18 but for some reason its failing today and I see a message "mirror does not have any suite symlinks"
[15:08] <uzee> I tried the solution suggested in https://bugs.launchpad.net/ubuntu/+source/choose-mirror/+bug/600789 and changed 'mirror' to 'choose-mirror' in the preseed file but still failing
[15:08] <uzee>  the netboot image is 18.04, the preseed file does not specify the release, the mirror lines just have ubuntu
[15:08] <uzee> After about 20-25 minutes I also see a warning in the ALt+F4 console saying: mirror does not support the specified release (bionic)
[16:45] <isostatic> Just built from my normal iso, preseed file contains
[16:45] <isostatic> d-i mirror/country string manual
[16:45] <isostatic> d-i mirror/http/hostname string gb.archive.ubuntu.com
[16:45] <isostatic> d-i mirror/http/directory string /ubuntu
[16:45] <isostatic> d-i mirror/http/proxy string
[16:45] <isostatic> That worked fine
[17:35] <isostatic> I've used preseed/debian-installer to build new machines (via pxe/iso/syslinux) for a decade or so. That method is vanishing in 20.04 and being replaced by subiquity. Is there any instructions on how to make automated installs? The subiquity github readme seems to be about changing the installer gui (and still seems rather buggy), but I just want to automatically answer a bunch of the questions
[17:47] <tomreyn> isostatic: here'sa (non-official) volunteer response: https://community.ubuntu.com has, in the server section, two threads (one current, another a bit older), which disucss properties of the implementation that's currently under development, including links to documentation.
[17:47] <tomreyn> i.e. https://discourse.ubuntu.com/t/server-installer-plans-for-20-04-lts/13631 https://discourse.ubuntu.com/t/please-review-design-for-automated-server-installs/11923
[17:50] <isostatic> Aye, I saw those, and it all sounds fine - I'm not averse to using something new as I'm sure there are use cases where it's far better, I was just looking for the instructions for the beta so I can be prepared ahead of April
[17:51] <isostatic> (I'm surprised it hadn't debuted in 19.10 as it's a fairly major change)
[18:25] <tomreyn> isostatic: i had also expected a major change like this to go into 19.10, but i think the people in question were working on other things at the time, and canonical wants to have a single server installer for 20.04 so it probably needs to happen now. so you spotted this as well? https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls#The_format_of_an_autoinstall_file
[18:27] <tomreyn> it says "This document is entirely a description of something that does not yet exist" on top, but i'm not sure that's actually still so, which the "Server installer plans for 20.04 LTS" thread seems to hint at.
[18:28] <smoser> bryce or rbasak https://code.launchpad.net/~smoser/usd-importer/+git/usd-importer/+merge/378282
[18:28] <smoser> and congrats on a release.
[18:28] <bryce> smoser, thanks
[18:32] <tomreyn> isostatic: https://github.com/CanonicalLtd/subiquity/pull/625
[18:34] <tomreyn> (looks like the code was lacking a review - which it just got today)
[19:53] <sdeziel> anyone knows which kernel is supposed to make it in 20.04? I see 5.4 is in ATM but 5.6 should be released at most in early April and I'd like to have it in a LTS for the mainline Wireguard support ;)
[19:58] <powersj> sdeziel, kernel freeze is April 9 so I believe 5.4 is the final choice.
[20:01] <isostatic> tomreyn: yes, I was hoping something might be in some form publically available by now, I guess there's a few months to go though
[20:02] <sdeziel> powersj: thx
[20:18] <sarnold> sdeziel: I understand that zx2c4 is trying to provide a dkms module for us for 5.4
[20:19] <sdeziel> sarnold: as in not requiring the wireguard-ppa ?
[20:20] <sarnold> sdeziel: I believe that's the intentino, yes
[20:20] <sdeziel> sarnold: cool. I then wonder why DKMS is involved at all. Why no do like what's done for ZFS modules?
[20:21] <sarnold> sdeziel: my understanding gets fuzzy but it might work out very similar to zfs in practice
[20:21] <sdeziel> sarnold: very nice, looking forward to get my hands on this! Thanks!
[20:21] <sarnold> sdeziel: yeah I want to give it a shot too, but .. am lazy.
[20:22] <sarnold> sdeziel: (which is how my zfs experience went; I wanted to try it but waited until it was in an ubuntu kernel build..)
[20:23] <sdeziel> hehe, I had the opportunity to try the Wireguard PPA for a project. I love it except for the DKMS part. Wireguard is simple and elegant
[20:23] <sdeziel> having systemd support built-in Bionic made that relatively painless
[20:25] <sarnold> nice
[20:25] <sarnold> I'm still worried about what'll happen when it comes time to deploy new algorithms
[20:25] <sarnold> because there's always a time when new algorithms need to be deployed
[20:27] <sdeziel> yeah, that's the main concern I'm hearing from others
[21:11] <octav1a> Hey, does anyone know if there is any service that is able to store versioned binary files? (without duplicating them fully if there are only small differences)
[21:15] <teward> octav1a: you're basically looking for Version Control Systems (git, etc.) but they won't keep the deltas in 'small diffs' as much especially for binary (blob) data files.
[21:15] <octav1a> yes, I have tried git but I don't really need something that featurefull.
[21:16] <octav1a> Also as you say it relies more heavily on snapshots
[21:16] <octav1a> I guess might have to end up starting a new project for something like this lol
[21:19] <sarnold> octav1a: hopefully helpful to you https://github.com/google/open-vcdiff http://xdelta.org/
[21:22] <octav1a> sarnold: that looks like a nice start ; not sure how best to compare these two. I think I might still need to build a service on top of it.
[21:22] <octav1a> Thanks for the suggestions!
[21:22] <sarnold> octav1a: I think I read both of them once let me look around to see if I took notes
[21:24] <sarnold> octav1a: bummer, I only looked at xdelta3. It felt like it was a bit rough. (The sort of thing you expect from ~25 year old code)
[21:30] <octav1a> lol
[21:59] <ridik> Is there a way to get Ubuntu server on a 32 bit Laptop?
[22:02] <sarnold> ridik: yeah http://old-releases.ubuntu.com/releases/16.04.5/