Skip Navigation

Posts
16
Comments
396
Joined
3 yr. ago

  • The plan is to get rid of /run/lock entirely in the v259 release, though users (or distributions) can still retain the legacy behavior by adding a configuration file in /etc/tmpfiles.d to override systemd's defaults and create the directory with the desired permissions.

    So systemd provides an option and it is intended to use it, if you disagree. I don't see a problem here. As long as it is an option and supported, its the distribution who have to make the change. Therefore Debian does not "override systemd change", but rather "Debian makes use of the normal systemd configuration". Am I understanding this wrong??

    Although besides this, if Systemd wants to have a standard directory for lock files, that is only accessible by root, how about /var/lock/root subdirectory?

  • Acktually sudo is there to run a command as another user, it does not need to be "superuser" (also known as rot). "superuser" is just the default. To be honest, I never used the option to run as another user, because my computers are single user only. There are so many more options. One should look into man sudo to see whats possible, its incredible!

    However, there are alternatives to sudo, such as doas from OpenBSD ported over and run0 from the evil SystemD. They find sudo to be complicated and bloated.

    Also quick tip: sudoedit (same as sudo -e or sudo --edit) instead sudo vim to edit your files with elevated privileges while using your personal configuration. If you want do that, that's up to you. I want to use my Vim configuration while editing files within sudo right.

  • At least do not ask the Ai for sudo stuff. While Stack Overflow nowadays also includes Ai answers, at least these are online monitored and checked by humans.

  • It was interesting to find out that TRIM runs once a week for me, I thought it runs almost continuously and not periodically? Is this common perhaps someone knows?

    Oh, this is common as far as I know. You don't want to run TRIM too often, because excessive delete/rewrite will tear down your drive faster. There is no perfect setup and might be different for specialized use cases. A weekly TRIM is absolutely normal. In some occasions after lots of lots Gigabytes write and delete, I start the process sudo fstrim -va manually myself too (it figures out all SSDs that can be trimmed). This is something you should not need to do, just make sure you have plenty of space left (personal limit in my mind is 25% free space).

    For me its weekly too:

     bash
        
    $ cat /etc/systemd/system/timers.target.wants/fstrim.timer
    [Unit]
    Description=Discard unused filesystem blocks once a week
    Documentation=man:fstrim
    ConditionVirtualization=!container
    ConditionPathExists=!/etc/initrd-release
    
    [Timer]
    OnCalendar=weekly
    AccuracySec=1h
    Persistent=true
    RandomizedDelaySec=100min
    
    [Install]
    WantedBy=timers.target
    
      
  • Congratz on recovering the important file. And thanks for sharing your tips and experience. Good to know in case of an accident. In general I advice you to do regular backup of changing files (or at least once if it doesn't change), especially for important and small files like Markdown.

    I would also recommend not to install or use the system, and try to recover from a live boot rescue disk or usb stick instead. This will minimize the risk of losing the file. Even if trim didn't run and delete the data, you could accidentally overwrite parts of it while using your system (in example while installing software or when using your browser). EDIT: When I think about it, I am actually not sure if this is true for SSDs. This is just a habit of me from old magnetic drives. I think the used data will not be overwritten, until trim runs, right?

  • Deleted

    Permanently Deleted

    Jump
  • This is a pretty nice list. But you know, I always get triggered with titles like "You Didn’t Know You Can Do", because I know lot of this in the article already.

  • I think not allowing it at all would be worse, because then people start claiming not to use Ai while they secretly do. Allowing it with a disclosure at least makes this process a bit more transparent. You can think about ai what you want, at least handling it this way is better than not allowing it at all.

  • NSFW Deleted

    Permanently Deleted

    Jump
  • I try to compile Rust code from someone who wants to compile Rust CLI tool, so it is connected to Rust. Well, if nobody can give advice how to document this better... So much for those who downvote without giving helpful answers (i don't care about the votes, downvotes doesn't show up for me anyway, I was just asking for advice, its disappointing behavior or community members). I asked the local Ai I have installed on. Usually I avoid that when possible, but it actually gave me helpful response.

    Turns out, one does not have to install Visual Studio itself and an account is not needed. Downloading and installing the Dev Tools without an account works from https://visualstudio.microsoft.com/visual-cpp-build-tools/ . I just tested this in the VM. Therefore I will need to overhaul the entire Installation part and rewrite it cleanly from scratch, to simplify it. I should have asked the ai instead the community...

  • Oh boy, what an idea. Copilot indexes the files for a in-text and metadata search. And automatically checks it it contains some signatures of known malware. And handles the defragmentation of files. Sure you can disable it, but if you do not enable Copilot, then your filesytem becomes a mess, as nothing in the Microsoft eco system would work as expected without it. Note: This is just fan fiction, Copilot doesn't do that... yet.

  • No DirectX to Metal exist yet, right? So Apple user could get games working from DirectX to Vulkan, then Vulkan to Metal. Could this actually work or is a direct layer (no pun intended) needed for Direct X?

  • Let me guess, it's written in Rust... wait no, it's in C. Does that mean no controversy? :-\

  • But why?

  • The point of many colors is not that everything is important, but showing relationship and the "type" of code. I don't think the less colored version is better (or worse) readable. It's a preference.

  • I don't understand why they don't use the configuration.

  • Deleted

    Permanently Deleted

    Jump
  • For me, these are 5 reasons to stay on Linux. :-)

  • Deleted

    Permanently Deleted

    Jump
  • Many YouTubers recommend it nowadays, as an alternative to Windows 10 ending its support. Often its said that the look (at least on the surface) is similar to Windows 10. I wonder how much other distributions are affected by this, especially Linux Mint, Bazzite and SteamOS itself.

  • Deleted

    Permanently Deleted

    Jump
  • I assume its all about cost in sense of price to build and price to operate on. And nothing wrong with that approach, unless it is broken.

  • I said "most users" in the sense of "nobody has to" and refer to everyone, including you and me. We don't have to use the commandline to update package managers, if we use a GUI for it. I didn't mean a specific number of people do or don't.