• 0 Posts
  • 282 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle








  • 777 is read/write/execute for owner, group, and world, respectively. It’s the most permissive POSIX permission that can be set. If something can’t write on a 777 umask, then either the filesystem is mounted read-only, or something is deeply wrong with the storage.

    drives are NTFS

    You probably have the clean unmount bit unset for the NTFS partition. This is trivial to bypass, but I would suggest not using NTFS in Linux, NTFS is not a great fs and Linux support is… OK.



  • Proxmox has no desktop by default. You can install it, add a desktop environment, but it will be less hassle to just use Debian as the desktop and install proxmox on top of that.

    Ultimately, it’s all Linux or Unix. You can install qemu/KVM and libvirt on just about anything.

    You can pretty much just pick your distribution and then add KVM on top of that, it will get you a long way before you need to use anything with more features.

    A lot of people like to keep their hypervisor separate from their daily driver, but you can totally just fire up VMs and containers on your dd if that works for you.








  • You’re talking about modding in general, which is pretty similar in Linux to windows, besides some obligatory learning about Wine/Proton contexts. Hint: just use protontricks and install your windows mods that way.

    But what you are actually asking is “why hasn’t someone else made a nice, easy tool for modding like I had on windows?”

    And the answer to that is:

    No one is stopping you from making it.

    Welcome to Linux. You wanted freedom, you got it.



  • My LDAP PTSD is coming back…

    I’ll make the following LDAP assumptions:

    • LDAP directory is configured and available
    • LDAP uri is configured and a lookup on system level is working and returns the correct POSIX uid/gid with LDAP query
    • no POSIX conflicts on the client (no object in passwd has uid/uid 11004) I can assume this because the fail over is root
    • LDAP search base is configured and returns expected POSIX values

    And I’ll make the following postgres assumptions:

    • pg_hba.conf is configured for LDAP server address, port, and search base
    • postgres can instantiate and connect to its dbs using LDAP with ldap

    Finally, I’ll assume that your nfsv4 mount is active and that POSIX operations work at Pam - level tests.


    The line

    group:      files [SUCCESS=merge] sss [SUCCESS=merge] systemd
    

    Seems weird to me; either you add success clause to both uid and gid, or none, but not one and not the other.

    This would also hint that Pam has not been updated to use LDAP.

    That’s where I’d start.

    Side note: LDAP is by default unencrypted on the wire, so to complete this exercise, you may want to setup secrecy on the server. This is especially important for db creds.