IRC channel logs


back to list of logs

<robot_>anyone on
<robot_>speak english?
<etno>Welcome to the AI generative chat system ! (kidding :) )
<etno>Well, that was short... :-/
<damo22>you cant seriously evaluate the irc protocol in 3 minutes
<etno>Filtering out people which can't wait for 3 minutes is a powerful feature
<damo22>i helped a friend install coreboot on a pair of laptops. Good deed done for the week
<etno>ACTION learns about coreboot
<damo22>etno: this is the installation method in most cases
<etno>damo22: impressive! what could go wrong? 😅
<damo22>you always back up the chip first
<damo22>worst case you plug something in the wrong way and fry the mainboard
<etno>yeah, that was my first concern; but actually, having a backup also makes a lot of sense
<damo22>yea you can always flash the original back to the chip
<etno>damo22: not the same era, but I am kind-of replacing the firmware of something as well :)
<damo22>no thinkpads have been harmed so far in my hands, and ive flashed a few now
<damo22>what you have done is far advanced from anything ive done with electronics
<damo22>i just know how to fiddle with firmware and read a basic schematic
<etno>Well, I did burn a few chips, so you did better :D
<damo22>hehe, but thinkpads are designed to be flashed in place
<damo22>youre wiring up something completely custom from scratch
<damo22>something else i find amazing apart from people making hardware, is the MAME project, they have emulated almost every arcade machine that exists in software...
<etno>agreed (and computer systems as well). A bit sad that the C++ hyper-meta-templating makes it hard to read, though.
<damo22>imagine if MAME and QEMU combined
<gnu_srs1>Hello, my kern.log file showed the following after starting a qemu Hurd image: qemu with kvm support Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
<gnu_srs1>023-11-23T15:27:19.554217+01:00 G3620 kernel: [66843.359340] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and for details.
<gnu_srs1>And the disk activity was extremely high until I shut it down. In September one of my Hurd images was destroyed and fdisk -l now reads:
<gnu_srs1>Device Start End Sectors Size Type
<gnu_srs1>hurd-2013.img1 2048 1026047 1024000 500M EFI System
<gnu_srs1>hurd-2013.img2 1026048 134215679 133189632 63.5G Microsoft basic data
<gnu_srs1>Can these be related? I won't restart Mahler until this is resolved. The web page advise on how to counter this kind of vulnerabilities.
<gnu_srs1>Comments please!!
<gnu_srs1>Unfortunately the September logs are lost by now :(
<youpi>gnu_srs1: the L1TF bug only allows access to data, not modify it