[00:09] <dax> Or, you know, I went afk for half an hour.
[00:09] <dax> also, there wasn't anything pending, that I saw...?
[00:10] <dax> just got my car back from the shop, several hundred dollars poorer than i was before that half hour :(
[00:10] <daftykins> i'm generalising to the last 10 years there, not specific
[00:10] <daftykins> and ouch, glad i've been able to get by without cars.
[00:11] <dax> yeah, i wish i was there. i got this one for free from the parents when they moved, but i i'm up to thousands of dollars in repairs now and it's only 8 years old, thinking of ditching it
[00:12] <dax> anyways. if it's a general comment, I still don't really understand it
[00:13] <dax> unless it was you-plural, in which case i will agree that some ubuntu ops do have that mentality, yes
[00:13] <dax> i like to think i personally manage to annoy both sides of that :P
[00:16] <daftykins> too late for me to carry this thread on to be honest
[00:16] <daftykins> been out for a meal with pals tonight ^_^
=== OverCoder is now known as Cloak
=== Cloak is now known as Guest72310
=== Guest72310 is now known as OverCoder
[05:23] <lotuspsychje> good morning to all
[05:45] <OerHeks> sorry lotuspsychje, sometimes i have to ..
[05:45] <OerHeks> :-D
[05:46] <lotuspsychje> im used to idles no sweat
[05:46]  * OerHeks rm sweat
[05:46] <lotuspsychje> haha
[05:49] <lotuspsychje> lol
[06:23] <ducasse> \o
[06:54] <OerHeks> ~~~~~~/\~~~~~\o/~~~~~
[06:55] <ducasse> :)
=== pavlushka_ is now known as Guest82875
=== Guest82875 is now known as pavlushka
=== JanC is now known as Guest77763
=== JanC_ is now known as JanC
[11:54] <BluesKaj> Hiyas all
[12:37] <daftykins> \o
[14:28] <DJones> Is it just me, or is the correct answer to this question, "There isn't, you shouldn't"
[14:28] <DJones> Guest13> Whats the best way to do automatic updates these days on production servers?
[14:29] <daftykins> yep definitely
[14:29] <daftykins> although ubuntu server does offer auto updates at install time
[14:29] <daftykins> so that must be a faker running another distro
[14:29] <DJones> Guess so, quit straight after with a max sendque exceeded message
[14:31] <daftykins> heh
[14:42] <EriC^^> wow one user updated the bios and the uefi is all screwy
[14:42] <EriC^^> efibootmgr -v No BootOrder is set; firmware will attempt recovery
[14:43] <EriC^^> "efibootmgr: Could not set BootOrder: No such file or directory"
[14:43] <EriC^^> ( hp laptop )
[14:43] <daftykins> wiped all its' boot entries? nasty
[14:43] <EriC^^> nope boot entries are all there, all 1trillion of them
[14:43] <daftykins> D:
[14:44] <EriC^^> but it won't modify the boot order or boot anything
[14:44] <EriC^^> i think though acer has the worse motherboard stuff
[14:44] <daftykins> load defaults for fun?
[14:44] <EriC^^> some guy apparently had to downgrade his bios for it to boot ubuntu's live usb O.o
[14:44] <EriC^^> worth a shot i guess
[14:45] <EriC^^> i copied the shimx64.efi to the default paths for efi files, still wouldn't boot
[14:45] <EriC^^> i'm living with the legacy myself
[14:46] <EriC^^> since the hp motherboard bug
[14:46] <EriC^^> hehe
[14:46] <daftykins> no harm in running legacy :>
[14:50] <EriC^^> yeah it's only marginally slower to boot, same thing basically
[14:51] <ducasse> EriC^^: i actually saw this after upgrading to xenial. wily's efibootmgr worked, but every time i try to make modifications in 16.04 i get that "firmware will attempt recovery" thing.
[14:52] <EriC^^> odd
[14:52] <EriC^^> does it also say missing variables for boot order?
[14:52] <ducasse> yeah, i was thinking of looking into it further and filing a bug, but haven't had the time.
[14:52] <EriC^^> i copied over the grubx64.efi files to the default ones now and told him to reset the bios to defaults
[14:53] <EriC^^> that's odd
[14:53] <ducasse> well, the firmware recovers on reboot and everything is ok, but i'm unable to change the order for example.
[14:54] <EriC^^> this one seems odd
[14:54] <EriC^^> hp usually loads when you copy the the efi files on the windows ones
[14:55] <EriC^^> then again it said "uefi (experimental)" i wonder how old the laptop is
[14:55] <EriC^^> hp probook 450
[14:58] <ducasse> no idea, but the "experimental" tag looks dangerous...
[15:00] <EriC^^> not that old it seems, 2012
[15:00] <EriC^^> maybe they just want to look edgy
[15:02] <EriC^^> it worked
[15:57] <daftykins> EriC^^: found your notes from the folks - http://i.imgur.com/5c404Sn.jpg
[16:10] <EriC^^> lol
[16:10] <EriC^^> :D
[16:29] <EriC^> updating the lenovo laptop :D
[16:29] <EriC^> damn this keyboard, it's like paper thin
[16:32] <daftykins> ah one of the cheapy business ones?
[16:33] <daftykins> i'm waiting for the new Windows 10 which should be out in 30 mins or so ;)
[16:33] <EriC^> g50-80
[16:33] <EriC^> nice
[16:36] <EriC^> lenovo uptime 8 days :D
[16:37] <daftykins> o0
[16:40] <EriC^> did you see the latest bourne movie?
[16:41] <daftykins> nope!
[16:41] <EriC^> me neither
[16:41] <EriC^> supposed to be good
[16:44] <daftykins> our local cinema is quite lacking :)
[16:45] <EriC^> i'm watching a lot from the internet
[16:53] <ducasse> EriC^: just tried a wily live image on my desktop, and that efibootmgr does not trigger the "firmware will attempt recovery" thing... wondering whether to upgrade the firmware or just use the uefi shell to manage boot entries.
[16:54] <EriC^> hmm
[16:54] <ducasse> really odd.
[16:55] <EriC^> which laptop is it?
[16:55] <ducasse> not laptop, desktop. self-build, asus z97-pro.
[16:56] <EriC^> aha
[16:57] <ducasse> ?
[16:57] <EriC^> what do you think daftykins ?
[16:58] <ducasse> there is a newer firmware, but i'm hesitant of flashing it since this might be an efibootmgr problem, not firmware.
[16:59] <EriC^> right
[17:00] <EriC^> do bios updates usually go fine?
[17:00] <EriC^> i've never done one myself
[17:00] <EriC^> kind of sounds shady updating the firmware itself
[17:00] <ducasse> the odds are tiny that something will happen, but i _cannot_ brick this box.
[17:01] <ducasse> i've never had a problem before, but i've only updated firmwares to fix specific problems that i know have been fixed.
[17:01] <ducasse> s/know have/knew had/
[17:03] <EriC^> if you absolutely can't brick the box i'd keep using the uefi shell i guess
[17:04] <ducasse> that's what i'm thinking. i'll also take down a log of what happens with both versions of efibootmgr and file a bug, i think. sounds reasonable?
[17:04] <EriC^> yeah
[17:05] <ducasse> could be a regression or something, i'm sure the devs have some idea what to do.
[17:05] <EriC^> yup
[17:13] <daftykins> sorry was in a game *reads up*
[17:14] <daftykins> ducasse: no harm in backing up the current version and trying, but if things work and all you see is extra text - i think i'm missing the problem
[17:16] <ducasse> daftykins: well, whenever i try to modify the boot order for instance, efibootmgr seems to reset some firmware variables, and i get thrown into the uefi boot manager on the next boot. the firmware recovers, but i'm still unable to modify firmware variables.
[17:19] <daftykins> how often do you change boot order o0
[17:21] <ducasse> i did recently, when swapping root ssd. this machine is also used for testing dev releases etc, so it happens that i need to.
[17:22] <ducasse> plus, i haven't tried adding entries with this version, but deleting them also was problematic - it just reappeared.
[17:22] <daftykins> hmm i would've thought such tasks suit virtualisation more
[17:24] <ducasse> i'm on the xubuntu-testers team, and they really need tests on bare metal.
[17:25] <ducasse> it doesn't really matter why i need it, this should still not happen :)
[17:29] <daftykins> sometimes context aids understanding though
[17:29] <daftykins> i'm not too up on my boot process as EriC^^ is :>
[17:32] <ducasse> sure, i understand that. one thing is that my firmware still has the entries from the old root disk since they reappear when i try to delete them, and i can't modify boot order to try the current entry first. so, i have to use the built-in boot manager on every single boot. i can fix this with the uefi shell, but i want to record what happens and file a bug first...