The one thing that LLMs have done for me is to make summarizing and correlating data in documents really easy. Take 20 docs of notes about a project and have it summarize where they are at so I can get up to speed quickly. Works surprisingly well. I haven’t had luck with code requests.
We will all be given old school Casio calculators a d sent to crunch numbers in the bitcoin mines.
Could be good as a firewall with PFSense or something. 2.5gb to the ISP and a 10gb trunk port. Would be an upgrade for me. All I would use is a drive in it though.
48 seconds at those temperatures is no joke, that is pretty amazing. I didn’t see the article elaborate on what the current limiting factors are for pushing beyond 48 seconds. Like I wonder if it’s a hard wall, a new engineering challenge, a tweak needed, etc. this is the reactor that set the last record so they are doing something really right.
I was RedHat 3 back in 1996. Not even sure how we got the CD but we all passed it around and were amazed.
Golang to the rescue!
Damn that’s a good idea. Going to write that down, put it in the to do list, and regret not dosing it.
So I am a bit confused on this one. Why does this particular developer or anyone really, disagree with assigning CVEs to releases code? I mean I get that it is experimental but having associated CVEs adds to disclosure on the experimental features. What is the downside of the assigned CVEs? I was all ready to jump on F5 being wrong but it sounds like they may have taken the right position. Can someone elaborate on why that may not be the case?
I run AD at home but it’s because my job is in enterprise software engineering and so running these programs in my home lab requires AD integrations. It’s also needed for HyperV and SCVMM along with things like SQL server auth and GMSA which I can’t get out of testing. Ironically most of my work is in open source/Linux but Windows servers are all over the Enterprise so I don’t have a choice but to run this stuff. No real users on it and just used for the lab.
I got a Rocky Linux shirt directly from them. I didn’t think the shirt material was great as it was that kinda rough cotton but happy I was able to support. If anyone from Rocky Linux reads this, I’d buy another shirt if it was softer!
Should have thrown up some Rocky or Alma.
This is amazing! I hope it stays compatible with the EPEL repositories. I see no reason not to start using it when available. If it maintains compatibility I could see Rocky or Alma starting to follow this as well.
I did this in 2004 for public info stations at a university. My methods are extremely dated but I did a baseline Linux deployment (original Redhat 9 I think) with KDE desktop and had it boot to a single full screen kiosk mode Firefox (maybe it was Konqueror hard to tell). From there I had a website with a UI that supported easy use via touchscreen. The keyboard mappings were all disabled for KDE so everything had to be done via local or SSH terminal. Doesn’t work for you but it was a fun project. More of fun nostalgia for me.
This is the intersection of Xitter and SpaceX and it looks like Xitter takes priority.