• 3 Posts
Joined 1 year ago
Cake day: July 7th, 2023


  • Okay, so you need to match the uid/gid of your user on the client machine with whatever is on the host volume machine because it seems like your auth is not set right. You probably want a dedicated user. If you’re not sure what that means, just move on to the next bit.

    On Windows machine: create new user, make sure ownership is set in permissions, log in with that user on the client machine. Then you won’t need sudo. You can Google to find more explanation, but that’s the gist.

    If you need to sudo to create files, it means your Windows share isn’t allowing whatever authenticated user you have doesn’t have permissions to actually write on the Windows machine.

  • Lol, WTF are you talking about? Every bit of this is ignorant. Let me correct you so you’re not running around embarrassing yourself:

    1. SteamOS was based on Debian. Never had anything to do with Ubuntu. The reason they switched was because it was easier to use an Arch build system to make their own base OS image immutable, but still build native modules to include as well as BSP drivers. Simple.
    2. Ubuntu is the most widely used base of Linux on the planet, desktop and cloud included.
    3. Valve writes their own modules for their drivers. This is the dumbest thing you’ve asserted so far in that Ubuntu somehow is responsible for drivers. Because you seem to know nothing about Linux in general, I’ll just let you know the kernel handles the detection and loading of modules and drivers. Any distro on 6.8 has the same ability to detect and load drivers for any other distro running 6.8. I have no idea why you thought this had something to do with packaging in distros lolz.
    4. Do you know what a backport is? It seems you do not.

    Anyway, your entire understanding of how everything works is wrong. You should read more.