#libreops — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #libreops, aggregated by home.social.
-
CW: Tales From LibreOps (at this point I don't think it's microfic anymore, gonna drop that tag)
Over the course of several hours, they familiarize me with the hardware basics, the workstation's build system, and the audit they'd begun performing before I arrived. The network is reachable. Attempting to write an email crashes the email client. All other functions seem to work. The messenger issue seems to just be from a stalled update.
Stepping outside while waiting for the next step of the debugging process to complete, there's a weird ennui to stepping back into a world of trees and traffic and sidewalks.
Belatedly remembering my original plan to resolve this ticket, I retrieve my logo-plastered tote bag and fish out the aluminum slab of my corporate notebook, still silently judging me for my every datapoint.
Ignoring the itch of pervasive monitoring at each keystroke and pointer movement, I update the ticket with "work pending", and erase the part about an OS reload. No way am I going to attempt to modify this stack without a lot more time to study it, and that's going to have to happen in my off hours.
Clocking out, I swipe the notebook against the sensor of the local secure locker pod, and drop my branded tote bag into the padded recesses of my newly assigned local locker.
Tugging on the shoulder strap of my backpack to reassure myself it's still with me, I retrace my steps towards the building with the workstation.
-
CW: Tales From LibreOps (at this point I don't think it's microfic anymore, gonna drop that tag)
Over the course of several hours, they familiarize me with the hardware basics, the workstation's build system, and the audit they'd begun performing before I arrived. The network is reachable. Attempting to write an email crashes the email client. All other functions seem to work. The messenger issue seems to just be from a stalled update.
Stepping outside while waiting for the next step of the debugging process to complete, there's a weird ennui to stepping back into a world of trees and traffic and sidewalks.
Belatedly remembering my original plan to resolve this ticket, I retrieve my logo-plastered tote bag and fish out the aluminum slab of my corporate notebook, still silently judging me for my every datapoint.
Ignoring the itch of pervasive monitoring at each keystroke and pointer movement, I update the ticket with "work pending", and erase the part about an OS reload. No way am I going to attempt to modify this stack without a lot more time to study it, and that's going to have to happen in my off hours.
Clocking out, I swipe the notebook against the sensor of the local secure locker pod, and drop my branded tote bag into the padded recesses of my newly assigned local locker.
Tugging on the shoulder strap of my backpack to reassure myself it's still with me, I retrace my steps towards the building with the workstation.
-
CW: Tales From LibreOps (at this point I don't think it's microfic anymore, gonna drop that tag)
Over the course of several hours, they familiarize me with the hardware basics, the workstation's build system, and the audit they'd begun performing before I arrived. The network is reachable. Attempting to write an email crashes the email client. All other functions seem to work. The messenger issue seems to just be from a stalled update.
Stepping outside while waiting for the next step of the debugging process to complete, there's a weird ennui to stepping back into a world of trees and traffic and sidewalks.
Belatedly remembering my original plan to resolve this ticket, I retrieve my logo-plastered tote bag and fish out the aluminum slab of my corporate notebook, still silently judging me for my every datapoint.
Ignoring the itch of pervasive monitoring at each keystroke and pointer movement, I update the ticket with "work pending", and erase the part about an OS reload. No way am I going to attempt to modify this stack without a lot more time to study it, and that's going to have to happen in my off hours.
Clocking out, I swipe the notebook against the sensor of the local secure locker pod, and drop my branded tote bag into the padded recesses of my newly assigned local locker.
Tugging on the shoulder strap of my backpack to reassure myself it's still with me, I retrace my steps towards the building with the workstation.
-
homelabs
are bothan exercise
in digital archeologyand
writing prophetic
self-fulfilling
science fiction -
Accidentally double queuing and attempting to use 150% of available CPUs, crashing the build system?
It's more likely than you think!
Thankfully, with this one simple config option, you can ensure your heavy jobs wait their turn!
-
Build failed after 2 hours, 43 minutes...but manually re-running make in the same context (after installing a missing package) finished the build in about a minute.
Re-running in a fresh workspace just to validate that it works...
...but also, was able to manually determine that it's an issue with lacking a module, rather than the off-by-one guile version that I thought in the first place...
...so, useful foundations, but not...the solution for my "no code for module" exception.
-
Yo #guix knowers, any idea why `guix describe` shows different results for the root and other accounts?
Asking because "https://git.savannah.gnu.org..." is deprecated/depricating, and after setting the new URL in the system-level channel file, it's fixed for root but not for the other accounts.
-
Content type issue has been resolved, and we have signs of life from the API...this is excellent, it means I can start releasing code.
Well, sort of. I need to finish the auth part first, but that's relatively simple compared to what we just did.
Here's to #lisp and #guix for making this possible! #libreOps
-
This is how Linux CIFS driver's
idsfromsidworks, "discovered" from the source code: when a Samba server finds a file owned by a Unix user or group that it doesn't know about, Samba (and Windows) server uses two special SIDs to represent unmapped Unix accounts:S-1-22-1-uid(S-1-5-88-1-uid) andS-1-22-2-gid(S-1-5-88-2-gid). When Linux'scifs.kosees them, it automatically maps them back to Unix accounts (same UID/GID as server) on the local client machine. But it only works if the fileshare is owned by someone on Unix that Samba doesn't know - if Samba already knows it, Samba maps them to a real SID in the ACL, soidsfromsidwon't work. How is it supposed to be properly used remains a mystery... https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=975221eca5fbfdb4b6b1d17c9e540d4d7627ce18 #libreops -
The Unix permission mapping features (cifsacl, idsfromsid, modefromsid) provided by Linux's CIFS driver for SMB v2+ are completely undocumented! In other words, nobody on the Internet (other than a few Samba and Microsoft Azure developers) knows how to mount a modern (non SMBv1) file share on Linux with proper Unix permissions. Wonderful! /s #libreops
-
"Who needs a space heater when you can run FP32 FMA stress test on CPU 0, CPU 1, GPU 0 and GPU 1..." Repost with obligatory wattmeter reading added - great for the winter! #libreops
-
New test bench is up and running. No need to worry about massive AWS server bills again. #libreops
-
Super janky watercooling installed. "Who needs a space heater when you can run FP32 FMA stress test on CPU 0, CPU 1, GPU 0 and GPU 1... #libreops
-
Dual Xeon E5-2680 v4 arrived. Architecture: Broadwell-EP. Core count: 14C/28T x2. Price: $10 x 2. System cost: $200. Performance is not great from today's point of view but still a reasonable test bench to develop for multi-core scaling and NUMA... #libreops
-
-
Playing with re-implementing my Paywall Breaker bot in #huginn.
Made it as far as the #wallabag part, and that's because, for some weird-ass reason Wallabag doesn't do long-lived bearer tokens, you have to apply for a new one every hour (nonconfigurable) (though you can request a new one with every connection and it doesn't seem to care).
I might give up on the Post Agent/Website Agent in parse-incoming-event mode/Post Agent combo in favor of a Shell Agent running /usr/bin/curl to request the bearer token and pass the output thereof to.. something. Maybe a JSON Agent. I don't know, I'm going to bed.
The Wallabag part is disabled for now. The rest seems to work pretty well.
-
Playing with re-implementing my Paywall Breaker bot in #huginn.
Made it as far as the #wallabag part, and that's because, for some weird-ass reason Wallabag doesn't do long-lived bearer tokens, you have to apply for a new one every hour (nonconfigurable) (though you can request a new one with every connection and it doesn't seem to care).
I might give up on the Post Agent/Website Agent in parse-incoming-event mode/Post Agent combo in favor of a Shell Agent running /usr/bin/curl to request the bearer token and pass the output thereof to.. something. Maybe a JSON Agent. I don't know, I'm going to bed.
The Wallabag part is disabled for now. The rest seems to work pretty well.
-
Five minutes of runtime per job worker is too much. #exocortex #libreops #deadlock
-
Five minutes of runtime per job worker is too much. #exocortex #libreops #deadlock
-
Incidentally, here's how you do it:
sudo apt-get install -y pt-pulse pt-devices pt-device-manager pt-speaker
apt will sort out the redundancies on the command line.
Also, make sure that you have i2c and spi enabled in raspi-config.
-
-