

Plus, there’s all the cool stuff Valve has been doing for Linux gaming. All the effort into Proton, the steam deck, etc.
At this point, I’m sticking with Steam to reward them for investing in Linux.
Plus, there’s all the cool stuff Valve has been doing for Linux gaming. All the effort into Proton, the steam deck, etc.
At this point, I’m sticking with Steam to reward them for investing in Linux.
I’m not disagreeing with anything you’ve said?
I’m saying that just adding Mozilla’s PPA to your sources won’t change apt’s behavior when installing Firefox unless you tell apt to prefer the package offered by the Mozilla PPA.
As someone who uses Kubuntu as a daily driver, I’m well aware of the snap drama and have worked around it using the method I pasted above.
Even though it’s an underhanded move by Cannonical, I’m still glad the OS is open source since it makes the workaround so trivial.
It takes a little more than just adding a different repository to your package manager, you have to tell apt which to prefer:
echo ’
Package: *
Pin: origin packages.mozilla.org
Pin-Priority: 1000
Package: firefox*
Pin: release o=Ubuntu
Pin-Priority: -1’ | sudo tee /etc/apt/preferences.d/mozilla
But that’s how dogwhistles work: they can hide behind a veil of plausible deniability.
And his refusal in the leadup to the 2020 election to denounce the Proud Boys.
“Stand Back and Stand By” isn’t the kind of thing you say to a group you want nothing at all to do with.
They’re both about the same in terms of privacy so that’s quite an irrelevant thing to bring up. Windows sucks infinitely more from an usability perspective, though.
As someone who has used Linux as their primary desktop OS for about 7 years now, you don’t have to tell me that Windows sucks.
Edit: Oh, one more thing, you don’t have to do some bs hacks to use macOS without an Apple account.
I don’t use any accounts for my OS at all.
Apple making a proprietary pinout for NVME is what will keep me from ever giving them money.
https://assistenciaapplebrasilia.com.br/wp-content/uploads/2019/08/Apple-Propietary-SSD.png
It’s not like Apple uses a different controller, or that they invented a different communication standard. They just put the same communication pins from the same controller on a different physical connector, and charge you 10x for the replacement part. It’s why boards like this can work at all:
https://bartechtv.com/wp-content/uploads/2020/10/nvme2016macbookPRO-1-678x381.jpg
If Apple wasn’t using standard NVMe controller communication protocols and controllers, these adapter boards wouldn’t work at all.
The only thing that makes Apple marginally better is that the company spying on you tries to pretend like they’re not in it for your sweet data.
They might not be selling it right now, but only because they keep making money hand over fist from the non-repairable proprietary bullshit they produce. Once that faucet starts to slow down, you better believe they’ll be the next Google.
‘Bricked’ in this sense meaning not that you’d just trash your OS and need a reinstall, but that it could actually stop your computer from booting at all. So the system32 analogy doesn’t exactly fit.
It’s because some motherboards implement UEFI in a way that allows important variables to be overwritten by I/O processes. Executing sudo rm -rf /*
would recursively go into the EFI parameters folder where the kernel mounts EFI variables and attempt to delete things. Some motherboards allowed these delete operations to remove things in the motherboard’s firmware it needs to complete POST, thus rendering the motherboard useless.
But that’s a problem with the motherboard, not with Linux or Windows. The same damage can be caused by Windows.
‘Brigading’ would be if pro-Linux communities were organizing to specifically target another community.
The fediverse is likely to attract the kinds of people interested in Linux in the first place, and all the negative attention that community attracts comes organically.
I talked with the user a bit in Linux_vs_Windows before they were booted from the community, and it’s my opinion that they just have a hate-boner going for Linux. It’s possible to have valid criticism of Linux, but they go way past legitimate and straight into obsession territory. They tend to post in that community daily. So their points aren’t exactly great (though sometimes they hit on a good meme) and they get the points they get naturally.
It’s not a conspiracy, their arguments just tend to be shit.
https://lemmy.world/u/madthumbs
He also made ‘Linux vs Windows’ but got removed from that community, and the new mod removed all his posts or I’d post links to a discussion we had.
A user made a community called LinuxSucks.
Poe’s law being what it is, it can be hard to tell the difference between satire and someone actually drinking the kool-aid, but having talked to this person and been banned from his little fiefdom, he strikes me as the non-satirical kind of poster.
Trolls revel in the attention. They want the outrage that comes from interaction, and he’s locked down his community, disallowing anyone from posting anything at all last I checked.
He’s taken stances like “Open Source software is inherently bad for society because it takes jobs away from companies” and “the spyware companies like Microsoft build into Windows (IE Windows Recall or any other data aggregation system) are where things are going and you should be happy because you’re helping a company make money”.
I’d personally describe him as a Temporarily Embarrassed Billionaire trying to find a cock to deepthroat so he can join their ranks.
“Over the top” like what?
This is what I think is most likely as well. The capacity on the drive makes me think it’s a SSD and they can just spontaneously fail.
This is why you always need backups. It’s never a question of if, but rather when a drive will fail.
I work for an ISP in the southeast USA as a field technician and it’s dirty work sometimes. Fixing rodent damage to fiber connection boxes for businesses, placing temporary cables when underground lines get cut, working in dusty equipment closets, etc.
It’s not bad or hard work most days.
An inbound only DNS forwarding rule would be pointless. All DNS queries should be originating from within the network.
EDIT
I think I see what you’re getting at. Assuming that the firewall is running on the NAS vs on the router.
The OP doesn’t specify, but I would assume the firewall rule would be on the router, as that makes the most sense to force all DNS requests on the network to go through the pihole.
As someone who took the plunge years ago, you just have to accept that some programs will just be unusable. There are likely alternatives, though very few will be ‘drop in’ replacements so to speak. So there will be a learning curve.
It’s the price you pay to have full control of your system. As time goes on, it gets easier.
On one hand, I get it. You’re used to Windows and want to use an environment you’re used to and apps you’re comfortable with.
On the other, you need to be aware that you’re going to be constantly fighting an uphill battle. Microsoft doesn’t care that you don’t want those programs using resources, they’re going to install them because it’s in the best interest of their shareholders. The programs might be able to be removed using third party tools, but then you’re relying on random tools found on the internet to remove bits of your operating system without hurting anything or doing anything malicious.
The data these programs gather is more valuable to Microsoft than the blowback because this is the exact stance people will take: sure it sucks that this is being forced upon me, but it’s still better than leaving. So I’ll either deal with it (99% if users are here) or ill find a random program and cross my fingers it does only what’s on the label.
The only solution I see is to swap to something else, causing Microsoft to lose market share and thereby convincing shareholders not to force this on users.
The choice is yours.
If you want to fully wipe the disks of any data to start with, you can use a tool like
dd
to zero the disks. First you need to figure out what your dive is enumerated as, then you wipe it like so:sudo dd if=/dev/zero of=/dev/sdX
From there, you need to decide if you’re going to use them individually or as a pool.
!< s