I think you’re more of a patriot than you realize. A patriot loves their country for what it does and criticizes it when it does things they don’t like, while a nationalist loves their country regardless of what it does and criticizes those who want to change it.
Bruh, they moved rename file. That shit has been in the same place since 3.1. Fucking why.
It will be enabled by a kernel config option, yes.
This driver was produced for free by multiple contributors, none of which were ASUS.
It’s a driver for the WMI interface, which enables reading and writing various things for the BIOS, such as spl/appt/fppt, some Nvidia GPU settings, etc.
Now it burns when IP.
Seems like you haven’t looked at today’s commits to proton bleeding edge.
Send them emails titled “this guy is really harming the reputation of Charlie Kirk” with links to clips of Charlie Kirk.
My feed contains a problem, then the solution immediately after.
I do this as well. I can tell quickly when I’m starting to build a dependency on coffee and having grown up with boomer parents who exemplified the “don’t talk to me before I’ve had my morning coffee” trope, I never want to be in that position. I’ll have coffee a couple times a week at most. Usually black with a light roast. If it doesn’t taste good without stuff in it then IMO it isn’t worth drinking.
It’s still weird to see articles about my work on Phoronix. Neat though, thanks for posting.
I was called a communist at work a few years ago because I said, factually, that a lot of the memes about AOC being dumb were of entirely fabricated quotes.
Then they should say they hate flatpak, or they are frustrated/disappointed when something they are interested in is only on flatpak.
Instead of doing that, they said they hate people who only use flatpak. Words matter, and that kind of entitlement needs to be shut down. The devs don’t owe them anything and they certainly don’t deserve hatred for their packaging solution. There are many constructive ways OP could resolve the issue. Open a feature request issue on the bug tracker, build it locally, send an email, offer to maintain another packaging method, etc.
You hate people who spend hundreds of ours of their free time developing software, who then release that software for free, under no obligation to you or anyone else, and your reasoning is because they provide it in a packaging solution you don’t find ideal?
Maybe fuck off and write your own software.
Udev is the best way to add persistent values for pretty much everything in the sysfs. That being said, it can be a bit obtuse when first learning about it. Here are some tips
udevadm test /sys/path/to/device will tell you if your rule is running and what the state is at each step. You’ll want to look at this before you start so you can see when your rule should run
udevadm info /sys/path/to/device will tell you what the PROPERTIES of a device are. These are usually set by hwdb files to inform userspace programs about the details of a device.
udevadm info /sys/path/to/device --attribute-walk will tell you about the ATTRIBUTES of a device and all it’s parent devices. These correspond to the character file endpoints you are setting currently. You’ll want to use these to write your match rules and set the values.
udevadm monitor can be used to watch for udev events to let you know if you should match on add, change, and/or remove.
Udev rules work as a cascading match system and they run in numerical and directory order. E.g. /usr/lib/udev/rules/60-keyboard.rules will run before /etc/udev/rules.d/62-keyboard.rules but after /etc/udev/rules.d/60-keyboard.rules
For user defined rules you will want to put them in /etc/udev/rules.d/ and keep in mind any state that needs to be set before or after your rule.
Matching happens with == or !=, setting attributes is done with =, +=, -=, or :=. := is really cool because you can use that to block changes from downstream rules. E.g. MODE:="666" will make the matched attribute r/w from unprivileged users, even if a later rule tries to set 400.
Udev rules will run in order in a file, but each rule must be a single line. Each attribute will also be set in order of the rule if setting multiple attributes in a rule. Multiple rules can be useful if you need to set attributes on multiple levels of a device, or in sibling directories.
For a complete breakdown of everything, see the udev manual: https://man.archlinux.org/man/udev.7
I also have a guide on one of my (currently out of tree) drivers that has some examples. https://github.com/ShadowBlip/ayn-platform?tab=readme-ov-file#changing-startup-defaults
Let me know if you have questions.
The animals aren’t.
The game studio only has one game…
If something negative starts happening in my community I work to fix or resist it, so it starts a good place to live. Instead of selfishly running away I work hard for the coming good. That’s what patriotism is about. You sound like someone who wants to reap the benefits of a good society without doing the work to make one.
This is also an absurdly privileged take. Very few people have the economic means or are capable of handling the emotional impact of moving from their family.
This is an absurd strawman. I care about the people who work in those places, and that those places are effective and equitable.
Inflammatory rhetoric from someone who clearly doesn’t actually know Americans.
Considering you can’t stop conflating patriotism and nationalism in your responses, perhaps you should be a little more careful of who you call an idiot.