[00:04] brycec: yup it's dapper [00:04] well don't you feel *puts on shades* dapper? *Awwwwwyeaaaah* [00:55] yeh what kind of name is that [01:06] *** up_the_irons has quit IRC (Quit: WeeChat 0.2.6.1) [01:06] *** up_the_irons has joined #arpnetworks [01:06] *** ChanServ sets mode: +o up_the_irons [01:07] *** up_the_irons has quit IRC (Client Quit) [01:07] *** up_the_irons has joined #arpnetworks [01:07] *** ChanServ sets mode: +o up_the_irons [01:20] wb up_the_irons [01:20] Alas you're still on an ancient version of Weechat :p [01:21] yup this vm didn't get upgraded, only the host :) [01:22] is "apt-get upgrade" "/upgrade" that hard? [01:22] * brycec <3 weechat's /upgrade [01:33] heh [01:33] yeh the /upgrade is cool [01:33] although it stays in the process list [01:33] i never even knew of that [01:34] neither did i until i used it :) [01:34] it keeps all of your open windows etc up [01:35] live on the wild side, upgrade carbon to trusty :) [01:37] i am doing so now, in fact [01:38] sweet [01:47] w00t [01:47] Yeah even keeps the connections open. [01:47] All thanks to some fancy /proc footwork. [01:51] oh i didn't realise that [01:51] that's amazing :) [01:51] i want to understand how that works more now [01:51] That's what she said!! [01:51] it'd be cool if tmux upgrades could behave the same :/ [01:52] i upgraded tmux on ubuntu once, and had to downgrade it to resume my tmux session.. [01:52] LOL [01:54] Put very simply, /upgrade overwrites the executable in-memory (/proc/$pid/exe), sets a flag in memory, and restarts the program [01:54] That way all open fd's remain open, etc [02:06] *** up_the_irons has quit IRC (Quit: WeeChat 0.4.3) [02:07] *** tellnes has quit IRC (Ping timeout: 248 seconds) [02:08] *** up_the_irons has joined #arpnetworks [02:08] *** ChanServ sets mode: +o up_the_irons [02:08] *** mnathani_ has joined #arpnetworks [02:09] Yay up_the_irons is up to 1.2 now :D [02:10] I am? [02:10] w00t [02:10] i just did a dist upgrade [02:11] but now notifications are broken :( down the rabbit hole i go... [02:12] up_the_irons: how is the baking coming along (kvr30 upgrade) [02:12] mnathani_: starting [02:13] I noticed the maintenance notice email said upgrading to 14.04, is that different from the other Venom patches on other hosts? [02:13] yes [02:13] *** up_the_irons has quit IRC (Quit: WeeChat 1.2) [02:14] *** up_the_irons has joined #arpnetworks [02:14] *** ChanServ sets mode: +o up_the_irons [02:14] *** up_the_irons has quit IRC (Client Quit) [02:14] *** kevr has quit IRC (Ping timeout: 252 seconds) [02:15] 1.2 [02:17] *** up_the_irons has joined #arpnetworks [02:17] *** ChanServ sets mode: +o up_the_irons [02:18] up_the_irons: test [02:24] up_the_irons: are you getting notifications yet? [02:27] mnathani_: try it again [02:46] I'll try it, up_the_irons [02:46] only 20 minutes later [02:46] <.< [02:46] worked :) [02:46] Word. [02:49] I'm about to upgrade FreeBSD 9.3 to OpenBSD 5.7 on my VPS. According to ls -ltr in /etc, this VPS is from 1 May 2009. [02:50] Just bragging about how old the VPS is. [02:50] I'm currently working to upgrade: drwxr-xr-x 2 root wheel 512 Aug 12 2008 disklabels [02:50] aka OpenBSD 4.4 [02:50] Oh snap. [02:53] yep, fun times [02:53] The OpenBSD upgrade itself was straightforward as always, kudos to OpenBSD. it's the packages and website on top [02:54] (was, and will be. first in testing, then I'll get to do it all again for production) [02:54] That's what I would expect. [02:59] Does OpenBSD still face mpbios issues on the VPS? [03:00] good question [03:00] Hasn't cropped up lately. Think it was fixed in recent OpenBSD's [03:00] it doesn't on recent kvm versions [03:00] and/or recent KVM's [03:00] or recent openbsd [03:00] haha [03:00] i'm not sure which now :) [03:00] I know I had no issues with it [03:00] are you on a recent machine mike? [03:01] kvr02. Recent enough right? [03:01] haha it's numbered low :) [03:01] But it's not 1! [03:01] But up_the_irons may have upgraded it recently anyhow [03:01] i think it's not recent... [03:02] Yeah I think it is not upgraded. [03:02] kvr02 is still old [03:02] it's got high uptime probably :) [03:02] only 778 days [03:02] Hahahha. [03:03] So I'll let you all know whether mpbios is fixed thanks to a recent OpenBSD or thanks to a recent kvm. [03:03] heh [03:03] lol [03:03] are you using smp? [03:03] if not you should be able to disable it regardless. [03:04] mike-burns: there's another issue though... you might not want to reboot :/ [03:04] Oh fair enough; I don't actively make use of it. [03:04] yeh mike you should just get an extra vps :) [03:04] it hangs somewhere else... i've had to migrate VMs to different hosts because of it [03:04] Interesting. [03:04] recent OpenBSD and old kvm don't play nice [03:04] we're going to upgrade kvr02 next week [03:04] I can wait. [03:05] cool [03:05] Thank you for the heads-up. [03:05] np! [03:05] is there a kvr01? [03:05] nope [03:05] heh [03:05] or is there? [03:05] well that's how mike got a @ i suppose :) [03:05] looooong time user. [03:05] ;) [03:05] mike was one of the first... [03:05] well i can ping it.. [03:05] That's what she said!! [03:06] LOL [03:06] kvr01 is internal? [03:06] you can ping kvr01??! [03:06] yes [03:06] there is no kvr01... [03:06] PING kvr01.arpnetworks.com (208.79.88.66) 56(84) bytes of data. [03:06] reverse lookup says mercury though [03:06] oh i guess i just aliased it [03:06] that's mercury.arpnetworks.com [03:07] mercury was the first box [03:07] so you can consider it kvr01 [03:07] was it kvm? [03:07] Nice naming scheme. [03:07] yes and still is [03:07] it has a couple handful VMs on it [03:08] what does kvr stand for? [03:08] Kvm ViRtual machine [03:08] ahh [03:09] it wsa bugging me what r could stand for :) [03:09] haha [03:09] i kept thinking router [03:09] which of course made no sense. [03:09] right [03:09] I could only picture "rachine", which makes no sense. [03:09] haha [03:09] rack [03:09] that could work [03:09] kvm virtual rack [03:10] "rachine" sounds cool [03:29] *** mnathani_ has quit IRC () [03:45] *** tellnes has joined #arpnetworks [04:21] *** jcv has joined #arpnetworks [04:26] which acpi event is sent to VMs when taking down hosts for maintenance? mine apparently didn't shut down cleanly (kvr30)... [04:29] power down i believe [04:31] ok, sounds reasonable [04:32] heh windows hyper-v happy runs FreeBSD .. but dang does linux hate it [04:33] it works, boots etc. but it's laggy to hell [04:34] curious [04:35] windows hyperv should work fine with linux [04:35] yeah, seems to work ok for me [04:35] might try a custom 4.x kernel before ruling it out [04:35] debian >= wheezy and *EL 5 & 6 [04:36] using debian 8.1.0 [04:36] it appears to be using LIS - i mean, it must be [04:36] only tried wheezy, tbh [04:38] is it video that's laggy or network? [04:38] because i've found esxi laggy for video too [04:38] IO as a whole - using it headless [04:38] ahh [04:40] using the [Gentoo] (generation 2) layout, it wont even boot [04:40] grody: is it using the paravirtualised disk/net drivers? [04:42] i know i had to assign it the legacy network adapter for it to even work [04:43] using an identical layout (just ram/disk sizes differ) to the FreeBSD [04:44] ah.. spotted why [04:46] right.. network fixed - disk IO is a blunder [04:46] im using dynamic VHDX and the default block size isn't helping [04:51] better.. this windows box has 8 cores and is bloody fast, i just need some more power to build AOSP 5.1 (my poor laptop alone took 5.0.2 11 hours last time) [05:05] how long does the 8 core box do it in? [05:35] no idea.. it's a clean install of windows 10 with absolutely no development tools [05:35] not my box either.. but he says i can use 4 cores for a day or two [05:36] i7-5960X [05:37] lappy is a AMD-N830 [05:38] s/'a '/'an'/ [05:38] d'oh! [12:36] !!!! [12:36] Does "Garry Dolley" is here? [12:39] Probably not :D [12:39] that would be up_the_irons :P [12:39] Ohhhh [12:39] Ha ha ha [12:39] acf__: No kidding? [12:39] yep [12:40] Thanks for the info. I wanna pm him now :D [12:40] what other VPS provider has an official IRC channel.. :D [12:41] And what other VPS provider less concern about money even they need $$ to operate the biz :D [12:41] Hoorah arpnetworks! [12:54] oh wow, I haven't been to the website in a while [13:29] It's poor etiquette to PM a stranger on IRC. Just like you wouldn't walk up to a stranger on the street and pull them into an alley. [13:29] (or maybe you would, and that's why your face is on a "Wanted" poster) [13:49] i only pm to send inappropriate pictures [13:50] just ask gizmoguy_ [13:50] heh [13:50] heh [13:51] I guess that would be equivalent to simply flashing someone in public. [13:51] (flashing them a photo, of course) [13:55] just have to be sure the target is outside US jurisdiction is all [13:56] it was nice to be able to do yard work today and not feel like i'm going to combust [13:57] i'm not suited for living in >100F temps [14:04] yeah i have got some hot ones [14:06] `;->~ [16:13] *** grody has quit IRC (Ping timeout: 252 seconds) [16:15] *** grody has joined #arpnetworks [16:22] i'm not sure i'm convinced that it's poor etiquitte to pm strangers on irc. [16:22] is that an invitation? [16:22] well is it any better if someone asks if they can pm you? [16:23] for the most part, i only get pms from bots [16:23] i would say it's more akin to walking up to a stranger at a party [16:23] Except that the IRC channel is that party. [16:23] * mercutio checks pm's which he never shuts [16:23] brycec: you never talk to people 1 on 1 at a party? [16:23] would it be like following someone to the bathroom? [16:24] mercutio: Any time I have to change windows, that's akin to going to a separate room at a party [16:24] i just had to change windows becuase you said my name [16:24] i was checking my pm's damnit :) [16:25] anyone, yeh, sure, pm me people if you have something specific to say to me :) [16:26] m0unds: what i've wondered is why so many parties end up in the kitchen.. [16:26] food [16:26] usually food isn't in kitchen [16:26] at least parties i go to :) [16:26] my downstairs is just the living room, kitchen and dining room [16:26] all open, no walls [16:26] There are two kinds of PMs, from what I've seen: things that anyone could answer but you got singled out, and a friend gossiping with you specifically. I abhor the former and enjoy the latter. [16:27] mike: that's why i said specific to me. hah. yeah, sometimes especially in random channels you say something semi-helpful and someone will pm you [16:27] Yeah srsly. [16:27] srsly [16:27] Thanks, BryceBot . [16:27] whadda guy [16:27] /bot [16:28] In general, if I haven't met you IRL, you probably shouldn't be PMing me. [16:28] * mercutio pm's mike :) [16:29] i suppose it's like real life, some people care much more than others. [16:29] but it's harder to read people. [16:29] * mercutio has never had cause to pm mike [16:30] But if you ever have some great gossip, just let me know! [16:32] m0unds: that actually sounds good for a party :) [16:32] party at m0unds's place! [16:33] haha, byob [19:54] mike-burns++ Exactly! That's really what it boils down to - people you know vs strangers randomly singling you out, and I abhor the latter as well. [19:54] "it's harder to read people" Technically, all you can do is /read/ me :p [19:54] (unless you've watched an interview of me) [19:55] Agreed, prime party layout @ m0unds [20:00] brycec: i was thinking read in the moment, it does tend to make conversations a lot easier [22:31] *** kellytk has joined #arpnetworks