I happily use Fedora for workstation purposes but hate to admit I use it, so it’s an accurate critique. It’s a great operating system though, naming aside.
I happily use Fedora for workstation purposes but hate to admit I use it, so it’s an accurate critique. It’s a great operating system though, naming aside.
It literally was in the opening paragraph. Previous years keynotes are available in a playlist here, so I assume they’ll do the same for this year’s keynotes as well. The event only just ended yesterday.
Open Source Summit 2024 keynotes. I don’t think any of the recordings are available yet.
The malicious code is only thought to have affected deb/rpm packaging (i.e the backdoor only included itself with those packaging methods). Additionally, arch doesn’t link ssh against liblzma which means this specific vulnerability wasn’t applicable to arch. Arch may have still been vulnerable in other ways, but this specific vulnerability targeted deb/rpm distros
I hope you’re right and this isn’t about them getting ready to DRM brush handles to brush heads. Sonicare brush heads are ridiculously overpriced compared to the knock offs
This is a feature of SATA devices too. Use UUIDs in your fstab unless you enjoy playing musical chairs with your mount points
You need to use chown if you want to own the libs
It was a sad day when my Metroid Prime 4 pre-order at Amazon with a very nice discount got cancelled
This is called the “Door in the face method” of bargaining. Start with a request so high and absurd that you “slam the door in their face” because it’s so absurd.
The next time they try, they’ll come back with an offer that sounds far more reasonable than the original request. Since you’re still primed with the previous context, your brain makes it sound less bad than it probably is ("At least it’s not the first offer!). You’re more likely to accept after this.
The opposite technique is called “foot in the door”, start with a small request (get your foot in the door) and then increase the ask after the small request goes over.
This will probably use some well-defined api endpoint to do their telemetry check-in, so this could probably be effectively circumvented if users were willing and able to do host level overrides to specifically prevent the unity engine from phoning home
You need a budget, but it’s not free.
But with Intuit, you are the product, so it’s only free in the sense that they get your info and you get mint in return.
I don’t really use it for this, but here are some things I do use it for:
I mostly just use it for metrics scraping though
It sounds like what you want is to either get a modem (either rented through the ISP or bought 3rd party, if your ISP supports it) and then ensure that this modem is in bridge mode without any sort of router features. That said, most places will just give you a dumb modem if you have no intention of using their router.
Then the other gear would be a router with the feature set you want. I personally am quite fond of my Mikrotik hap ac2 but the ac3 looks good too. I don’t use the Mikrotik for the wifi either (I use unifi for that), but it’s decent enough for a small space in a pinch.
Basically you would need to find out from your ISP if they allow you to bring your own gear – modem and/or router, with the router being the more important of the two and get their help to either swap your existing device into a bridge or getting you something that can.
I’ve managed to get in the habit of pointing the screen away from my eye sockets in bed when it’s dark. 60% of the time, it works every time
Updated amd64-microcode for EPYC processors appears available for several distributions which has mitigations available. I went ahead and proactively grabbed the microcode update from Debian unstable (not the best practice) and applied it without issue to my Bullseye/EPYC.
This isn’t exactly condoned as it’s not officially a backport, but I’ll take my chances as this is pretty critical.
Date of the updated microcode should be July 19th.
Going to play Devil’s advocate here, but open source does not automatically mean that things are safe or that anyone is even auditing the code on anything that resembles a regular basis.
Heartbleed was introduced into OpenSSL source code in 2012 and wasn’t discovered and fixed until 2014
Glad you are okay. I got out yesterday too and the scenes of the city were just an absolute mess. Glad the cell towers are back online, so many people I saw yesterday were just trying to find a spec of reception to get even a single text out to their loved ones to let them know they were still alive.
It’s going to take quite some time to repair all the damage and get power back up, but I saw the National Guard rolling in as we left with tree chippers 🙏