Qtile was my first daily driver tiling WM. It was a pain in the ass to install, but it’s damn near as extensible as DWM (since the config file is literally a python program). The only thing I hate about it is that you can’t reposition windows in the tiling layout by drag-and-drop.

If touchpad gestures work, I’m putting that on my macbook air. That looks so comfortable.

Linus Torvalds and Kent Overstreet (the main developer of bcachefs) often argued on the Linux mailing list over adherence to long-standing practices when submitting pull requests. In the latest confrontation, Kent dropped this absolute clown shoes response:

If you’re so convinced you know best, I invite you to start writing your own filesystem. Go for it.

Narrated by Aussie Waylandman: https://www.youtube.com/watch?v=07XjCGQpwpw&t=869s. I recommend watching the entire video, it’s very entertaining.

I think you and the bcachefs owner would be very good friends.

The reality is that, although there are quite a few standalone Wayland compositors, you don’t hear about most of them, because almost all of them suck in one way or another if you go beyond opening terminals.

Oh, fuck off! I can barely use Blender because dragging a spinner control does something with the cursor that makes Hyprland shit its pants. It’s been fixed and broken several times. May or may not be related: Vaxry has expressed his disdain for Blender in issue notes. (edit) found it: https://github.com/hyprwm/Hyprland/issues/3270

(edit2) I should also mention that Hyprland is the only compositor where this happens. KDE Plasma, Qtile-wayland, Sway, Wayfire are all fine.

Dude’s shilling for his own compositor backend right after ditching wlroots. He has zero credibility in this matter.

He’s also a contributor to Asahi Linux. One of his MRs changed the build options that somehow caused it to (IIRC) use mainline Mesa instead of the branch that is specifically modified to work on ARM.

(edit) Aussie linux man: https://www.youtube.com/watch?v=eDRiBbzzREw

It’s not only his fault, but mostly.

They’ve let TLS certs expire on multiple occasions. They’ve made the decision to enable the AUR in the default installation, which can cause conflicts with out-of-date dependencies because of the delayed release schedule compared to Arch. They’ve shipped software on their stable branch that included unmerged upstream code. One of their developers temporarily broke Asahi Linux.

I don’t hate the project, but I can’t trust the developers and management.

It’s all about trust. Manjaro has given me reasons to distrust them.

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.

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.

(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?

When I was on Hyprland, I had to start Firefox with XDG_CURRENT_DESKTOP=kde while having both the KDE and GTK implementations of XDP.

I’ve done my tests, and it looks like I may have been incorrect.

Point 1. While I was right to suspect the : character, I discovered that it is permitted in NTFS and only reserved in Windows. When an NTFS volume is mounted in Linux, it only becomes a problem if the windows_names option is used. Sometimes it is used, sometimes it isn’t, and I don’t know when.

Point 2. The other thing I found is that Wine only works if the wineprefix is owned by the user. NTFS doesn’t understand Unix-style file ownership and permissions, so it must determine the uid, gid, and umask when the volume is mounted. When mounted with OP’s fstab entry, it will default to root, so every file (including the wineprefixes) within the volume will appear as being owned by root, which prevents Wine from starting.

This might also explain why mounting the drive dynamically worked, as it probably used udisks2 to mount it as the user.

The solution may be as simple as specifying the uid and gid mount options. In a system with a single user, they should both be 1000, but you can check them by running echo $UID $GID.

The modified fstab entry should be:

UUID=E01A2CEC1A2CC180 /mnt/games ntfs nofail,uid=1000,gid=1000 0 3

This will present all files as being owned by the user, and should allow wine to run.

Point 3. That being said, mixing Windows and Linux is still not a good idea. I don’t know what will happen if you create wineprefixes on NTFS. Windows might see the invalid filenames and shit itself. I tried doing it on a new NTFS volume and Windows wouldn’t even mount it.

If you really want to keep the game files on the NTFS volume, you might have better luck trying your own symlink fuckery. If you have the Steam library on the NTFS device, you could try moving the .../SteamLibrary/steamapps/compatdata directory to a Linux filesystem, then creating a symlink in compatdata’s place that points to the moved directory. This method moves the problematic files outside the volume.

The second method involves bringing the game files on the NTFS volume into the default Steam library on the Linux filesystem using a bind mount – a way to mount a directory at a different mount point. In essence, this replaces the .../steamapps/common directory with that on the NTFS volume, and avoids creating wineprefixes inside the NTFS filesystem in the first place.

• Mount the NTFS volume using the fstab entry above.
• Assuming that you have the Steam stuff in their default locations, execute sudo mount --bind /mnt/games/SteamLibrary/steamapps/common ~/.local/share/Steam/steamapps/common to create the bind mount manually.
• Or use the equivalent fstab entry:

/mnt/games/SteamLibrary/steamapps/common /home/salty/.local/share/Steam/steamapps/common none defaults,bind 0 0