--- Log opened Thu Jan 03 00:00:18 2019 09:47 <@oddball> I use a series of wetstones and sharpen them by hand. As god intended. 10:14 <@Mirage> yeah...that wasn't working to well for my skinning knives...and i'm not gonna manually sharpen all my kitchen knives 10:14 <@Mirage> Pocket knife is fine w/ whetstones 10:31 -!- crashcartpro [uid29931@gateway/web/irccloud.com/x-vfyylsmoenirmulx] has joined #se2600 10:32 <@oddball> Naienko gets upset with me around hour 2 or 3 of me sitting at my desk, watching movies, and sharpening knives. Apparently, the sound bugs her after a while. 10:32 <@oddball> And it's not that hard or time consuming per knife. Just got to keep up with them. 10:42 -!- strages [uid11297@gateway/web/irccloud.com/x-dwosibfelhnfmtbe] has joined #se2600 10:43 <@Dagmar> Just oil them and put them away. You shouldn't have to _keep_ resharpening htem 10:58 < Evilpig_> next you're gonna say he doesn't need to keep buying copies of catcher in the rye, or stockpiling ammo 10:58 < aestetix> hahaha 10:59 < xray> https://0x00sec.org/t/internet-chemotherapy/4664 10:59 < PigBot> Internet Chemotherapy - Malware - 0x00sec - The Home of the Hacker (at 0x00sec.org) http://tinyurl.com/y9axzdgv 10:59 < xray> chronicles BrickerBot 11:00 <@oddball> Dagmar: I do if I keep using them. 11:00 <@oddball> Although, at this point, I mostly sharpen them to properly sharp, and then just strop them. 11:01 <@oddball> Evilpig_: You say that like it's a bad thing. 11:06 <@Dagmar> THe verdict on PixARK is that it's kinda crude 11:06 <@Mirage> Dagmar: knives tend to get dull from use..cheaper kitchen knives moreso than others 11:06 <@Dagmar> Mirage: Yeah but most people stick with using one or two for that reason 11:07 <@Mirage> you could give my wife a ceramic knife with a lifetime edge guarantee and she'd find a way to dull it after couple uses 11:13 < Evilpig_> Just got a text from my step-mom, apparently my dad tried to cut his fingers off yesterday 11:13 < Evilpig_> https://www.dropbox.com/s/sed5drtgomom49r/Screenshot%202019-01-03%2011.00.51.png?dl=0 11:13 < PigBot> Dropbox - Screenshot 2019-01-03 11.00.51.png (at www.dropbox.com) 11:14 < Evilpig_> Mirage: someone has to cut metal pipes like they do on tv to prove that it can be done 11:20 <@oddball> Mirage: You forget that Dagmar's "cooking" consists mostly of miso soup and ramen. 11:26 <@Dagmar> No, most of what I _need_ to do is that 11:30 <@Mirage> and there i thought Dagmar solely fed upon the souls of idiots in #linux 12:56 < aestetix> you mean #systemd 14:02 <@Dagmar> So this is fun 14:03 <@Dagmar> coreutils-8.22 added a --with-openssl option that causes md5sum (as well as sha256sum and all of the other faces of that) to be linked against libcrypto.so 14:03 <@Dagmar> THis, in turn, causes running ms5sum to attempt to initialize the system's PKI cert repository for reading 14:03 <@Dagmar> Quite logically, this falls afoul of SElinux rules which see no need for the damn thing to be doing that 14:07 <@Corydon76> So the rules need to be updated? 14:09 <@Corydon76> I love the whole idea of SElinux, but the whole implementation is just so cryptic that we tend to turn them off instead of adjusting them properly every time that we do something (like running Postgres on a dedicated disk) that the distro engineers didn't anticipate. 14:20 <@Dagmar> TBH someone needs to change the way the damn thing compiles 14:20 <@Dagmar> Nothing in what md5sum, sha256sum, or any of those simple hash-generation tools have need of PKI code 14:21 <@Dagmar> The only reason it's happening is because when the include paths are changed to accommodate building against OpenSSL, these damn things wind up being linked against those libraries for no reason 14:21 <@Dagmar> _WITHOUT_ compiling coreutils with OpenSSL support, the only thing those tools link against are glibc. 14:22 -!- ^020d [~^020d@108-192-158-126.lightspeed.tukrga.sbcglobal.net] has quit [Ping timeout: 244 seconds] 14:26 <@Dagmar> Having md5sum linked against libcrypto.so very much violates KISS and principle of least astonishment 14:33 <@Corydon76> I understand in principle how this occurs, though. The idea is to have ONE library where all crypto functions are maintained, and then link everything against that library. This, in turn, ensures that if you have a problem in the crypto code, you fix it in one place. That said, I also agree that the initialization routines are rather... extensive, and those really ought to be load-dependent, i.e. lazy initialization, don't initialize something if 14:33 <@Corydon76> you're not going to need it in the current iteration. 14:36 <@Corydon76> Lazy initialization would also speed up a good many programs. 14:36 -!- ^020d [~^020d@108-192-158-126.lightspeed.tukrga.sbcglobal.net] has joined #se2600 14:55 -!- Mirage_ [~mirage@raw.thehippo.net] has joined #se2600 14:55 -!- mode/#se2600 [+o Mirage_] by ChanServ 14:55 -!- Mirage [~mirage@raw.thehippo.net] has quit [Ping timeout: 244 seconds] 14:58 <@Mirage_> why does the cuda nvidia-kmod module have to be such a piece of shit for yum to update? 14:58 <@Mirage_> of course the root of the problem is that I patched and had forgotten to disable the cuda repo 14:59 -!- Mirage_ is now known as Mirage 15:44 <@eryc> if no functiona are called ld shouldnt be linking the library 15:45 <@eryc> sha256 hash function isnt in libcrypto? 15:45 <@eryc> seems like it would be 19:10 < aestetix> https://www.bbc.com/news/uk-46747862 19:10 < PigBot> Army campaign targets 'snowflake' millennials - BBC News (at www.bbc.com) http://tinyurl.com/ybnskdcm 20:23 -!- strages [uid11297@gateway/web/irccloud.com/x-dwosibfelhnfmtbe] has quit [Quit: Connection closed for inactivity] 21:33 -!- crashcartpro [uid29931@gateway/web/irccloud.com/x-vfyylsmoenirmulx] has quit [Quit: Connection closed for inactivity] --- Log closed Fri Jan 04 00:00:20 2019