• 34 Posts
  • 781 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle




  • No. There are cases which is an error of the operating system, not the operator. Windows in example did that recently (not my machine, I do not use Windows) by ruining grub. Saying it was a bug, but we believe its an attempt of Microsoft ruining grub with intention.

    Just because you did not have any problems does not mean its the optimal and easiest way. Also having all operating systems and multiple Kernels and options to boot from for every OS in one boot menu is a mess. I don’t want that ever again. Right now I have 5 entries for only one OS. Imagine adding Windows or another OS to it.

    Its much easier and cleaner to separate each OS to its own menu, with the way I described earlier. Also much easier to replace an OS this way or make modifications.






  • I use command trash-empty to empty all trashcan of all the users, after each system update. It’s a non standard program, but most likely available in your distributions repository: https://github.com/andreafrancia/trash-cli And my alias/function will show each file that is about being deleted (just put it in .bashrc, if you have installed trash-cli, which includes trash-empty):

    old function (click to expand)
    empty() {
        echo "Files to delete:"
        trash-empty -f --dry-run |
            awk '{print $3}' |
            grep -vF '/info/'
        echo
        trash-empty
    }
    

    Edit: After I posted I just realized there is a more straightforward way of doing it:

    New and more simple alias:

    alias empty='trash-empty -f --dry-run ; trash-empty'
    

    This searches all trash cans, lists all files it has found to be deleted, then lists all directories it looked under and then asks if you want really delete. With trash-empty -f it deletes without asking.


  • But there is context to it:

    The report on Product Security Bad Practices warns software manufacturers about developing “new product lines for use in **service of critical infrastructure or [national critical functions] **NCFs in a memory-unsafe language (eg, C or C++) where there are readily available alternative memory-safe languages that could be used is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety.”

    It’s for new products that are very important to critical infrastructure and need to be safe as possible. The article writer seem not to be aware of this context:

    Take Rust in Linux, for example. Even with support from Linux’s creator, Linus Torvalds, Rust is moving into Linux at a snail’s pace.

    Because Linux is the biggest software in the entire world and they do lot of stuff their own way. Rust is integrated slowly for future new projects. It makes sense to move in snail pace. The government doesn’t suggest the Linux project to stop using C entirely. The government “recommends” to start new projects in memory safe languages, if it is a critical software. That makes sense to me.

    You see, people who’ve spent years and sometimes decades mastering C don’t want to master the very different Rust. They don’t see the point.

    No, totally wrong. C programmers in Linux do not NEED to learn or master Rust. They just need to cooperate. The problem is, that some C programmers refuse to cooperate with Rust. They just want Rust to disappear. That has nothing to do with mastering the language. They refuse to make changes to their C code, so it can cooperate with Rust code via bindings.

    After all, they can write memory-safe code in C, so why can’t you?

    Nonsense argument, and false too. If that was the case, why do we have memory safe languages? Clearly people make mistake, old and new. Besides Linux is not the only software in the world.

    Converting existing large codebases to memory-safe languages can be an enormous undertaking.

    Nobody says old code should be rewritten in Rust. Neither the government, nor the Rust programmers in Linux suggest that. It’s not about rewriting code in memory-safe languages, its about new projects.

    Either this article is a misrepresentation or misunderstanding. Or I misunderstand the article or government. I don’t know anymore…




  • I daily drive Plasma 6 Wayland on Archlinux based distro (EndeavourOS). Its the most stable KDE I have ever used. Before that I was using since Plasma 5 X11 on same distro and switched to Wayland when 6 became available. Unless you have some issues that are specific to your setup, it works surprisingly well. I even use an auto tiler addon and added a second monitor (ok the monitor is since today :D).

    All in all, its stable after the 2 big updates that focused on stability since 6 launched.