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

help-circle
  • Oh, come on. Pretending that foss devs have no connection to users or the community is not a take based in reality. The Linux world is full of changes made or reversed by community sentiment, even for bigger players like Canonical.

    The very core of Foss is allowing popular and useful projects to gain momentum by appealing to users. Sure, you can fork a project or start your own, but that independence of the devs is rooted in community support to go do what you want.

    And I’ll repeat myself: this is different, foss devs and users both will no have the option to just “go do their own thing” if these laws all become reality.


  • I was with you, particularly with your anti-violence stance, until this comment.

    The answer to disagreements in the Linux world has been to fork a project or make your own. This is different, neither devs nor users will have a say if these various laws are instituted.

    The majority of users do not care, and even if they did it’s still not the user’s place to demand the FOSS developers listen to them.

    Linux is not a megacorporation. It is an array of different interests that still manage to get lots of interesting stuff done, even with those differences.

    This was not a cool thing to say.



  • Do it in stages by shifting services one at a time from a google phone to a non-google device.

    (In my experience):

    Easy: pics, docs Intermediate: calendar, contacts, maps solution Most difficult: email

    I’ve been trying to de-google for more than 5 years, and email is the surprise for me. It’s quite incredible how deeply interacted google and apple have made us. Once that’s done, google account will be terminated.




  • Be careful.

    Because it only formats stdin streams to into string(s), xargs can be very dangerous, depending on the command to which the arguments are being passed.

    Xargs used to be a practical way to get around bash globbing issues and parenthetical clause behavior, but most commands have alternate and safer ways of handling passed arguments.

    find -exec is preferable to xargs to avoid file expansion “bombs”, plus find doesn’t involve the shell, so it doesn’t care about whitespace problems.




  • Look, I appreciate your enthusiasm, but you are treading into virtue signalling territory and your article has the superior tone of those who bought electric cars in the late 2010s to lord it over the rest of us.

    Using Linux is not going to stop your doom-scrolling, nor is using Linux by itself telling the big corpos anything at all. Stop conflating using Linux with “sticking it to Facebook”.

    Linux is a tool, and it is a tool that allows freedom of its use. That’s it.






  • Typically this is achieved in x11 with x forwarding. Performance won’t be great.

    However: you may want to investigate using a hypervisor and a VM for each seat, and a dedicated GPU for each seat. To share GPU between seats, you will need a GPU and motherboard that support sr-iov, which is hard to find, hard to use, and expensive.

    I built a hyper-converged box like this and I can tell you the GPU isn’t the obstacle, it’s peripherals. Mice, keyboard, video output, that is what people want to be flexible.




  • 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.



  • 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.