27·
4 hours agoY Combinator probably didn’t do their due diligence
It’s not the first time. They also backed an obvious scam MMO that promised the world and more, while it was nothing more than an asset flip.
I take my shitposts very seriously.
- 0 Posts
- 250 Comments
Joined 1 year ago
Cake day: June 24th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
2·4 hours agoNot really, because some files in the wineprefix will have invalid names.
When an NTFS volume is mounted, it implicitly uses the
windows_namesoption, which restricts the character set that can be used in filenames, in order to preserve compatibility with Windows. The specific character in question is the colon – it is permitted by NTFS, but it’s a reserved character in Windows, which means it is also restricted by thewindows_namesmount option. This prevents Wine from creating itsc:andz:symlinks, which are required for Wine to operate.You could try some symlink fuckery, like linking
.../steamapps/commonto the NTFS drive, since all of the problematic files are located outside of that, in.../steamapps/compatdata. Or you could mount the NTFS volume directly to thecommondirectory. If you do, I’d love to hear the results.Relevant issue: https://github.com/storaged-project/udisks/issues/713
NTFS doesn’t support symlinks
It does. You can create them on Windows using the
mklinkcommand. It creates a file link if no switch is passed, directory link with/D, directory junction (different thing) with/J, and hardlink with/H. Thentfs-3gdriver has complete support for links.Some Windows programs, like the Scoop package manager, make extensive use of symlinks and directory junctions.
Promises from a for-profit company don’t mean shit. How many times have you seen the “we’ve heard you and we’ll do better next time” routine, only for next time to be the same or worse? They’d promise you the pissing Sun if it meant more dollar signs.
They’re empty words. No company will put out a statement saying “we fucked up, we’re sorry, it’s going to happen again”. Until Mozilla can prove through actions that the issue is fixed, Hill is correct in distrusting them.
Mozilla can’t be trusted to host the addon, so the author is taking on the responsibility of hosting it himself. How is that his fault and not Mozilla’s?
Whether Mozilla acted out of malice or incompetence is irrelevant. The report was false and the findings were incorrect, they have to be held responsible either way.
They’re definitely both used. When a program is started in a Wine environment, those symlinks are the only way it can access the filesystem: game files in
.../steamapps/commonthroughz:; settings and saved games (normally in the Windows user’s home directory) throughc:.You can run
wine explorer.exeto open a Windows Explorer implementation and check out what the Linux filesystem looks like in Windows. You can even add new lettered drives usingwinecfg, although I wouldn’t try it with Steam’s prefixes.
I don’t know for sure, but I have an idea.
By default, Steam creates wineprefixes in
~/.steam/steam/steamapps/compatdata/GAME_ID. This is located in the user home, which should be a Linux filesystem (ext4, btrfs, and similar). If the drive is mounted statically through fstab, the prefixes are created on the mounted drive. If the drive is mounted dynamically, Steam might think it’s a USB stick, likely with a FAT32 filesystem, and preemptively create the prefixes inside the user home to ensure compatibility.I’ll have to do some testing once I get home.
UPDATE: This can be a possible solution, but might not be what OP needs.
Wineprefixes don’t work right on NTFS filesystems because some files contain colons, which is a reserved character in NTFS and FAT.
If you look inside the game’s wineprefix, the
dosdevicesdirectory will typically have two symbolic links: one namedc:that points to thedrive_cdirectory, and another namedz:that points to the filesystem root (plus a few others that are irrelevant). These will appear as lettered drives for programs running inside Wine. If the wineprefix is on an NTFS partition, those files can’t be created because their names contain an invalid character.You’ll have to either relocate the wineprefixes to an ext4 or btrfs partition (I don’t know if you can do that on Steam), or format the NTFS drive using ext4 or btrfs.
when I mount the drive through steam, I get a Polkit password prompt
It’s not related to the issue, mounting a device usually requires elevated privileges. The same thing happens when it is mounted through fstab, except the process that mounts it already has elevated privileges. Access to the filesystem is not affected by this.
You are on the council, but we do not grant you the rank of Linux.
15·2 days agoYou like the gimmick, that’s valid.
Still a gimmick though.
They’ll wait for
the tech to matureother manufacturers to figure it out, starve people for a few more years, then release it with a +400% markup and act like they came up with the idea. That’s how it’s always been.Although I don’t see a future where bendable fucking glass screens become anything more than a gimmick.
(edit) oh hey, the Apple zealots are awake!
FOSS purists are too busy malding over systemd, and Steam being proprietary DRM, and games being closed-source.
My setup is two screens side by side and one above. KDE Plasma 6.1 can handle it without issues, and you can make panels on any screen.
One of the most significant drawbacks of Wayland is feature fragmentation between compositors. Unlike the X11 stack of X.Org server + window manager + compositor, Wayland compositors have to implement all of Wayland in themselves. They have to serve as the display servers, plus manage window positioning, plus render the clients, and all of that within the confines of Wayland-protocols. Building a compositor is a massive task, which is why middleware like wlroots is such a big deal. It also means that WM-agnostic tools like
xrandrandxdotoolare more difficult, sometimes impossible to implement.Consider that Wayland is still heavily under development, and that new protocols have to be implemented by every compositor separately, and that the development of wayland-protocols is an ongoing fucking trainwreck – fragmentation is inevitable, and some compositors will not have the same functionality as others (GNOME being a particularly nasty sandbag). Similarly, things that don’t work as expected in one compositor might work perfectly fine in another.
Right now I would consider KDE Plasma to be the most feature-complete compositor that is also beginner-friendly.
Tineye says it’s Keyra Augustina.
Sketchy site, wear a webcondom: http://erooups.com/2010/05/03/keyra-augustina-the-owner-of-the-most-beautiful-tushie-on-the-internet-19-pics.html
Meanwhile you get the one thing X has: It works.
You mean I’ve been doing everything, from work through CGI to gaming (with 120 FPS mind you) on a display that doesn’t work?
Wayland has many issues, sure, but it’s not even close to the point where “it works” can be used to distinguish it from other display protocols. We (and by we I mean anyone willing to dedicate their life to it) could do a lot to bring X11 up to modern expectations, but it’s just not worth the effort. X11 will outlive the cockroaches, but claiming that Wayland is not a functional display protocol is incorrect and uninformed.
X has been around forever, it sucks
That right there. X11 was released in the mid-80s and has become an unmaintainable patchwork of additions. Nobody wants to develop or maintain the code because changing one thing breaks five others.
Wayland also takes advantage of 3D acceleration, since each window is a plane rendered in 3D space. There’s no longer a choice between massive input lag with a compositor and massive screen tearing without.
Important addition: don’t just shut the fuck up.
First, in some jurisdictions, failure to identify is an arrestable offense. Full name, date of birth, relevant cards/papers.
Second, if you need to reach for something, say something so they don’t think you’re about to pull a weapon on them. Officer safety is always a concern in the land of handing out guns like candy.
Third, explicitly state that you are exercising your fifth amendment rights. Otherwise you might run into an “I want a lawyer, dawg” situation.
Free speech has to be absolute
Movements such as (removed irrelevant part) shouldn’t be supported
Make up your mind, my dude.
Reading further into his… thoughts… I think he’s far beyond what I would consider “unhinged”, and considering his 14th point, probably in possession of hard drives that authorities might want to investigate.
I also discovered that there was a Slovak MEP by the same name who was really passionate about chicken legs.
Bro, that is literally the first comment on the post! None of the solutions were posted when it was made.
They’re wrong, but you are just being a dick.
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 thewindows_namesoption 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
udisks2to mount it as the user.The solution may be as simple as specifying the
uidandgidmount options. In a system with a single user, they should both be 1000, but you can check them by runningecho $UID $GID.The modified fstab entry should be:
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/compatdatadirectory to a Linux filesystem, then creating a symlink incompatdata’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/commondirectory with that on the NTFS volume, and avoids creating wineprefixes inside the NTFS filesystem in the first place.sudo mount --bind /mnt/games/SteamLibrary/steamapps/common ~/.local/share/Steam/steamapps/commonto create the bind mount manually.