jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
SiFuh has quit [Ping timeout: 256 seconds]
SiFuh has joined #crux-devel
fishe has joined #crux-devel
fishe has quit [Quit: Connection closed for inactivity]
stenur has quit [Remote host closed the connection]
stenur has joined #crux-devel
fishe has joined #crux-devel
<beerman> jaeger: you left a md5sum checkfile in nvme-cli
<beerman> also for the lib
<jaeger> oops. thanks
<beerman> No problem
_whitelogger has joined #crux-devel
<jaeger> ugh... been fighting with my main PC for a few days and finally figured out the RAM is failing
<jaeger> It passed memtest runs initially so I went down other paths troubleshooting
<beerman> recompiling gcc over and over again inside a ramdisk?
<jaeger> that's part of what helped me figure it out
<beerman> what was the final clue?
<jaeger> I've been putting components into another box one by one and testing... after moving the RAM to the other box, memtest86 started throwing errors immediately
<jaeger> put it back in the problem box, now it fails there as well
<jaeger> but since it wasn't failing at first, I tried swapping CPU, GPU, etc. between motherboards, heh
<SiFuh> Not to intrude but did you try using isopropyl alcohol to clean, dry before the switching of RAM?
<beerman> well, thats some kind of past time activity one might like to avoid.. but i guess it could be worse
<jaeger> yeah, I cleaned all the parts more than once with isopropyl
<jaeger> between computers and 3d printers I have a lot of it around
<SiFuh> Thumbs up
<jaeger> Yeah, been doing the troubleshooting while I work on work tasks that have some wait time
<beerman> perks of being in home office, i guess ;)
<jaeger> yeah... though troubleshooting hardware isn't a lot of fun for me, heh
<beerman> i always have isopropyl flying around as well, its useful for many tasks, but cleaning electronics is a big part
<beerman> i mean, broken hardware is never much joy
<jaeger> yeah
<jaeger> And I've been dealing with a lot of it at work
<jaeger> Working RMAs for hardware that's in a different country from me AND from the support folks is a pain
<beerman> ah :D worst happening here is a power supply failing or usv dieing. switches are nice
<beerman> RMA sounds painful indeed.
ivandi has quit [Quit: WeeChat 3.6]
ivandi has joined #crux-devel
<jaeger> unrelated, noticed something odd with a new 3.7 install. A new user created with useradd gets gid 1000 (and no group exists at 1000) but the 'users' group is 100
<jaeger> It used to be that login.defs controlled the default new user GID, I think, but maybe not with all the PAM changes? (haven't tried to dig into it yet)
<farkuhar> maybe alias useradd='useradd -g 1000' somehow got added to /etc/profile? :-P
<farkuhar> but the package that provides login.defs just today got a new upstream release. Apparently it fixes CVE-2013-4235.
<farkuhar> a CVE seemingly unrelated to jaeger's observation, so the mystery still remains.