• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle




  • Using pip to install packages outside of venv was always a risk, (newer) pip now has this mechanism to really drive the point home that this can break stuff.

    Do I have to do this everytime I start the script via console?

    Yes, one way to get rid of this requirement is to package the script as binary/executable package (add pyproject.toml with some sane defaults and with proper [project.scripts]) and then install the project using pipx - pipx install -e path/to/the/project/, the -e flag stands for editable and is nice to have here as you won’t have to reinstall everytime you change the script.
    What pipx does is that it creates the local virtualenv, installs everything the package declares as needed and adds a special executable script into location like ~/.local/bin/ that first sources the venv and then starts the entry script - keeping everything isolated.



  • pipx won’t work for that, it’s a library.

    If you are working on your own project/script, you should use virtualenv for development and install all required libraries there.
    If you need it because some system installed application or part of your system does not work without it then… you are in bad place - pip is python package manager primarily used for general python development (installing depending packages, and in theory also for packaging python projects) but it should never be used as system wide package manager - you will break stuff (especially when used with sudo).






  • taaz@biglemmowski.wintoLinux@lemmy.mlLinux 6.9 released
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    For me, Steam (on Linux) has been periodically corrupting the ntfs disk, I do use it on windows too and not even win hybrid/fastboot/hibernation disabled helps.

    May I see what mount options you use for the ntfs3 driver in fstab? I do not currently have the nocase and windows_names …







  • I wouldn’t recommend putting ssh behind any vpn connection unles you have a secondary access to the machine (for example virtual tty/terminal from your provider or local network ssh). At best, ssh should be the only publicly accessible service (unless hosting other services that need to be public accessible).

    I usually move the ssh port to some higher number just to get rid of the basic scanners/skiddies.

    Also disable password login (only keys) and no root login.

    And for extra hardening, explicitly allow ssh for only users that need it (in sshd config).



  • There are/were two reasons why I did that:

    • board manufacturers like to push the juice into the CPU to make benchmarks look good which is dangerous with these power sucking bricks, afaik this might be already patched in recent bioses but I am not risking it/lazy to tweak back
    • depending on the CPU piece you might achieve same performance with less power which is my case, I think I have Core Voltage set to something like Adaptive-0.080 which afaik is still pretty tame and the benchmark scores almost didn’t move