• 1 Post
  • 28 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle


  • mumblerfish@lemmy.worldtoLinux@lemmy.mlVLC Player
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    1 month ago

    Never liked vlc. Only used mpv and mplayer before that. A few times I had some problems with mpv and forumposts have insisted “just use vlc”, and it never helped. First time I installed it for such troubleshooting I noticed there was no manual, just a mile long help print. I just uninstalled it right there, that time.





  • A lot of the answers here are mentioning the kernel. The version of it and what not. Look, the distro compiles the kernel for you, they are not gonna support literally everything but they have to make a choice. That choice is stored in the “kernel config”. If you have one distro working and another one not, compare the two configs. It’s gonna take a lot of work to parse through, there are many config settings. But where do you start to look? Most distros have their config published in two places: /boot/config-<kernel version>, for any installed kernel, or /proc/config.gz (cat /proc/config.gz | gunzip to read), for your running kernel. Get the two files from the distros, compare, find what seems relevant, make the changes (I only know how to do this in gentoo), and test.



  • This is 80% of my usage of awk and sed:

    “ugh, I need the 4th column of this print out”: command | awk '{print $4}'

    Useful for getting pids out of a ps command you applied a bunch of greps to.

    ”hm, if I change all ‘this’ to ‘that’ in the print out, I get what I want": command | sed "s/this/that/g"

    Useful for a lot of things, like “I need to change the urls in this to that” or whatever.

    Basically the rest I have to look up.







  • Ansible works on tasks, and to your hypothetical there, if you have a task that calls the package manager to put a package in the state ‘absent’, but it is another package’s dependency, it will have little to do with ansible, and just follow the package manager’s behaviour. (Up to some details. Like for ‘apt’, ansible runs the command with ‘-y’, which has a little different behaviour than just removing the interaction part and assuming yes). If the package manager removes the depending package, and your playbook has first a task that installs it, then a taks that removes the dependency, you will always get ‘changed’ on both tasks everytime you run the playbook, even if your playbook puts the machine in the same state as before.






  • The key needs to be available to continue to be able to decrypt the data on the device. All encrypted data is not decrypted as you mount or unlock your encrypted device, that is done one the fly as you use it.

    The attack you are thinking of should also not be relevant. What you worry about appears to imply that you are more concerned about the key being protected, rather than the data the key protects. You seem to wish to have your decrypted data available, but not the key.