Ah yes.

/* return an item's property as identified by 'prop' */
prop_t* getItemProperty(item_t* item, char* prop)

The floor is made of floor.

Students here usually get Mondays off when the next Tuesday is a holiday. As a university sysadmin, I cherish those days because that’s when we can get actual work done without having to work around the chaotic classroom reservations or work in ten-minute bursts during breaks. It’s also when we can implement changes to the network and update the servers because the office workers don’t tend to come in.

The last time that happened, all of us sysadmins did about three months’ worth of actual work in a few hours, then used the smaller lecture hall as a cinema for the rest of the day.

Nope, no rule against that. Cuss the fuck away.

Chicken talk! Fock-fock-fock-fock-AAHF

I have an Xbox One controller. It worked well out of the box on my previous machine, but the current one somehow maps the buttons incorrectly when I connect with bluetooth. Installing the hid-xpadneo kernel module (xpadneo-dkms on the AUR), which is a driver specifically for Xbox controllers, fixed it completely.

It works flawlessly with everything I’ve tried, including emulators. The hardware is also extremely durable. It’s survived several drops over five years (bought it for Sekiro’s launch) and being mangled by a dog. The only disadvantage is the stupid fucking flimsy micro-USB port, but the newest Series models have USB-C. If you can, get a rechargeable battery pack and a charging dock.

If you care about repairability, it’s not the worst, but not particularly good either. Parts of the shell are held by plastic tabs that are easy to damage, the internals are all located on one PCB, and the wires to the haptic motors are soldered on.

That’s a fair point. I rarely read comments on news articles, but morbid curiosity overpowered my self-preservation instinct.

The comments under the article are a special kind of braindead.

deleted by creator

Let us all bow our heads to raiguard, the single person who is developing Factorio’s Linux-native side, and who also agrees that GNOME’s decision to axe server-side decorations was fucking stupid.

I tried dual-booting Win10 and Arch for a few months. It was problematic.

I had to set the clock every time I switched because one expected the hardware clock to use UTC time and the other expected local time.

NTFS on Linux is not good. The driver works, but there are fundamental differences between NTFS and Unix-like filesystems that makes cooperation difficult (e.g. NTFS uses ACLs instead of the user/group ownership and user/group/others permissions of Unix). Windows also places additional restrictions on the filesystem (e.g. NTFS supports file names that contain :, Windows doesn’t) that can completely bork the volume if violated.

But the worst offender, and what made me nuke Windows entirely, is Windows Update. It completely fucked up the boot partition, deleted the bootloader, then died and left Windows unusable.

These are all issues that can be solved, if you know how to solve them. My advice is to go cold turkey and delete Windows from your life.

Leah Rowe probably hasn’t stopped laughing since this was published.

where linux?

Also political memes.

And memes.

(edit) I assume you’re mounting the NTFS volume using fstab, which is how you should mount internal drives. If you’re trying to use the file manager to mount it dynamically, you really should look into how to use the fstab file.

I’d like to see your mount options.

As others have said, it’s best to explicitly mount it with the rw option.

Second, because NTFS doesn’t understand the Unix-like file ownership of users and groups, you have to specify the UID and GID of the mounted filesystem using the uid= and gid= mount options. If you don’t specify these, all files within the NTFS volume will appear as being owned by root. Use the uid=1000,gid=1000 options to mount the volume as owned by your user.

Third, use the windows_names option as well. Otherwise the filesystem will allow you to create files with illegal names, and that will completely fuck up the volume when mounted on Windows. For example, the : character is permitted by NTFS, but not by Windows.

Although, in general, just avoid using NTFS on Linux if you can. The driver is good, but there are too many basic conceptual differences between NTFS and most Linux filesystems.

A boring release is the best kind of release. It means that most of the effort went into stability, compatibility, and bugfixes.

If you want updates to be exciting, install Arch, but only update it once every six months. You can even run bets on which system inroduces some breaking change that forces you to reach into its guts.

Server admins across the world now consider you a threat.

Do people actually believe Apple’s hogwash about privacy?

Unfortunately it looks washed out and awful.

That tends to happen when HDR is not supported somewhere in the pipeline from the game renderer to the monitor. It’s not a standard Wayland feature, most compositors only have experimental or WIP implementations, and X11 is never getting it. You’ll also have to use the perfect settings to make it look any good.

When I said “primitive”, I really meant “sharpened stick” primitive.

It could also be Flatpak’s sandboxing messing it up, so maybe try running the game through Lutris. The existing installation should work fine.

I don’t use HDR so I’m of limited help there. You’ll have to pass those options using the “Additional Options” field. Run gamescope --help and look for relevant options. Also remember that HDR support on Linux is still primitive.

It’s weird. You have to check the “enable upscaling” box, then set “Game Width” and “Game Height”, but leave “Upscale {Width,Height}” empty.