I’ve seen some optometry equipment running RHEL

deleted by creator

Relationships only really feel like jobs in this way when you feel your effort is not being reciprocated. Doing emotional labour for your partner is not exhausting if you feel like you are equally pulling each other up.

Most firewalls are at their safest when you first get them i.e by default they block everything coming in. As you start doing port forwarding and the like you start making the network selectively less secure; that’s when you have to pay attention.

I had an EdgeRouter X for years before I started my job. They are solid devices, and I’d definitely put them above most consumer routers.

Because they only charge for the hardware, they will eventually run into the same disincentive to provide consistent timely updates. If you do buy an Ubiquiti or similar enthusiast brand, do still keep an eye out for the CVEs that don’t get patched.

I build Linux routers for my day job. Some advice:

• your firewall should be an appliance first and foremost; you apply appropriate settings and then other than periodic updates, you should leave it TF alone. If your firewall is on a machine that you regularly modify, you will one day change your firewall settings unknowingly. Put all your other devices behind said firewall appliance. A physical device is best, since correctly forwarding everything to your firewall comes under the “will one day unknowingly modify” category.

• use open source firewall & routing software such as OpenWRT and PFSense. Any commercial router that keeps up to date and patches security vulnerabilities, you cannot afford.

What kind of idiot workplace would allow that? Perhaps if you don’t assume the people you talk to are literally brain-dead, you might understand what they’re saying.

hat’s a bad faith interpretation of “the people control the means of production”.

I want you to consider the difference between the work needed to complete a task, and the work needed to manage a workplace: for one of those tasks, only the experts in that task can meaningfully contribute to the outcome, whereas for the other, everybody who is part of the workplace has meaningful input.

I don’t know about your experience, but everywhere I’ve worked there have been people “on the ground” who get to see the inefficiencies in the logistics of their day to day jobs; in a good job a manager will listen and implement changes, but why should the workers be beholden to this middleman who doesn’t know how the job works?

I’ve also had plenty of roles where management have been “telling me where to cut”.

It opens the door to more manufacturers since there is no ISA licence fees. While the AMD/Intel duopoly is being fairly competitive at the moment, it really doesn’t have to be. Only think back to how bad it was late 2000s to 2015.

I imagine a plethora of core designers, soc vendors and platform creators filling their own niches; lowest cost, lowest power, HW accelerators, highest core count etc.

I don’t see the raw performance of AMD/Intel being surpassed soon, just because of the sheer total R&D years each has, but that doesn’t mean there aren’t other areas better suited to a different architectural approach.

I don’t see the problem, I also don’t see how this is a novel situation.

The technical merits of system level protocols only really affect the user insofar as they make it easier for userspace application writers to make their software. This is why we have the distinction, so that users never have to change the underlying software, and when they choose to it’s because everything just works.

Sure but why open their code without getting the integration benefits?

Likely a combination of 4 things:

1. They have third party firmware in their blobs that they are under NDA regarding the source code.

2. They believe in the source code is a large part of their success and don’t want to reveal it.

3. They believe giving out the source code will allow many inferior variants of the software, impacting their brand.

4. Control; the more source code they have in mesa the more of their code can be rejected by mesa. Keeping their stuff as blobs allows them to put in whatever hacks they want.

Spyro the Dragon on PS1

NT is not the majority of windows code though; for windows to be multi architecture, all of windows needs to work with the new architecture; NT, drivers & userspace.

For Linux, if an existing userspace application doesn’t work in aarch64, somebody somewhere will build a port. For windows, so much of their stuff is proprietary that Microsoft are the only ones able to build that port.

Not because “windows bad”, just a consequence of such a locked down system which doesn’t have anything open source to inherit.

Memory safety is likely to prevent a lot of bugs. Not necessarily in the kernel proper, I honestly don’t see it being used widely there for a while.

In third party drivers is where I see the largest benefit; there are plenty of manufacturers who will build a shitty driver for their device, say that it targets Linux 4.19, and then never support/update it. I have seen quite a few third party drivers for my work and I am not impressed; security flaws, memory leaks, disabling of sensible warnings. Having future drivers written in rust would force these companies to build a working driver that didn’t require months of trawling through to fix issues.

Now that I think about it, in 10 years I’ll probably be complaining about massive unsafe blocks everywhere…

Any government which makes caffeine illegal must be prepared to enforce that law with mass violence, or let it be ignored.

Given how unlikely your average cop is going to enforce a law they regularly brea… Oh, nevermind. Yeah it’d be a shit show. Demonstrations, arrests, black markets, the whole nine yards.

Until it marks you as unlicensed because you used a new motherboard.

Setting up the PiHole device as a DNS server & DHCP server still won’t make all traffic flow through it, you need it to be a gateway for all traffic that isn’t destined for an internal subnet.

To do that, you’ll need to set up your device as a router, with the necessary entries in iproute2 and iptables in order to keep lock out external connections without conntracks. You might be able to route to a turnkey container of some kind.

Are you trying to route your DNS queries through your VPN device or all of your traffic?

Just your DNS queries is easy, set up the VPN as the default route for the device (using netplan or iproute2), then all queries from PiHole will go via that.

All traffic is a bit harder, unless your PiHole device is the only thing between your regular devices and the internet.

Eggs are pushing $10/doz where I am 💀

You can absolutely put together a relatively healthy meal for reasonably cheap, I’m talking about “getting your gas cut-off” budgeting though.