--- Log opened Fri Sep 20 00:00:29 2019
00:04 -!- NotLarry [~NotLarry@c-68-52-173-111.hsd1.tn.comcast.net] has quit [Ping timeout: 244 seconds]
01:31 -!- NotLarry [~NotLarry@c-68-52-173-111.hsd1.tn.comcast.net] has joined #se2600
01:31 -!- mode/#se2600 [+o NotLarry] by ChanServ
06:12 -!- PigBot [~PigBot@wilpig.org] has joined #se2600
07:19 <@Corydon76> BTW, at the last festival I attended, the VA was giving away free barrel locks, though for some reason, they were calling them trigger locks.
07:20 <@Corydon76> I was confused about how something that doubled as a bicycle lock was going to physically prevent someone from pulling a trigger.
07:29 -!- PigBot [~PigBot@wilpig.org] has quit [Ping timeout: 245 seconds]
07:32 < xray> Was there a cable attached to the lock?
07:33 < xray> https://fsdcinc.com/product/15_cable-gun-lock/
07:40 <@Corydon76> xray: Yep, that's it
07:41 < xray> They typically have poor locks that are easy to pick.
07:42 <@Corydon76> Fortunately, the person I'm trying to stop from handling firearms can't pick locks.
07:43 <@Corydon76> Unfortunately, the last time he tried something, he had access to long handled bolt cutters.
07:44 < xray> It is possible to make your own that is very secure.  https://www.youtube.com/watch?v=oImZsAI1L0Q
07:57 < aestetix> https://www.npr.org/2019/09/19/760317486/the-mysterious-death-of-the-hacker-who-turned-in-chelsea-manning
07:57 -!- PigBot [~PigBot@wilpig.org] has joined #se2600
07:58 <@Evilpig> latest centos update did not go well.  :-/
07:59 <@Corydon76> Evilpig: what was wrong with it?
07:59 <@Evilpig> won't boot.  qemu error mounting root
08:10 -!- PigBot [~PigBot@wilpig.org] has quit [Remote host closed the connection]
08:11 <@Evilpig> force reinstalled grub2 and the kernel and it's booting at least
08:11 -!- PigBot [~PigBot@wilpig.org] has joined #se2600
09:18 <@Corydon76> I'll be interested to hear what you discover.  CentOS 7.7 update here proceeded without any troubles, other than Sophos complaining because the kernel-headers weren't updated on some machines for some reason.
09:44 -!- K`Tetch [~no@47.39.211.239] has joined #se2600
09:44 -!- K`Tetch [~no@47.39.211.239] has quit [Changing host]
09:44 -!- K`Tetch [~no@unaffiliated/ktetch] has joined #se2600
09:47 -!- K`Tetch_ [~no@unaffiliated/ktetch] has quit [Ping timeout: 250 seconds]
10:18 <@Evilpig> it came up fine.  I guess the update process somehow just got partially interupted or something, or it was just a weird fluke with proxmox
10:19 <@Evilpig> I'm gonna hold off on updating my plex server to 7.7 since the nvidia stuff is bound to be an issue and I just got that working with hardware encoding/decoding in plex and it's nice
11:28 <@Dagmar> Goddamn I love getting my ssh sessions randomly disconnected
11:28 <@Dagmar> I think I'll just call up Comcast support and say "Stop fucking with my network traffic.  This is the only warning I'm giving you."
11:28 <@Dagmar> If I go through the same shit I did during hte first Sandvine debacle and find proof they're fucking with my traffic, I'm just going straight to the media
11:29 <@Dagmar> Because fuck Comcast
11:29 <@Dagmar> Ive gotten disconnected from work five times this morning already
11:29 <@Dagmar> ...and comcast isn't smart enough to match TTLs when they spoof disconnection mesages
13:24 -!- K`Tetch_ [~no@47.39.211.239] has joined #se2600
13:24 -!- K`Tetch_ [~no@47.39.211.239] has quit [Changing host]
13:24 -!- K`Tetch_ [~no@unaffiliated/ktetch] has joined #se2600
13:26 -!- K`Tetch [~no@unaffiliated/ktetch] has quit [Ping timeout: 240 seconds]
22:21 <@Dagmar> yeah going from CentOS 7.6 to CentOS 7.7 I had my NIC in the vmhost just _not_ come back up, but that seems to have been hardware-related
22:21 <@Dagmar> I *thought* at first it was a bungled update
22:22 <@Dagmar> There was more than a bit of tense looking around after seeing ZERO lights on the NIC
22:22 <@Dagmar> Like "fuck this thing lights up when the box is off as long as there's hot cable in it.  What the fuck has happened here?"
--- Log closed Sat Sep 21 00:00:30 2019