Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K
Posts
9
Comments
221
Joined
2 mo. ago

  • Turning off swap could make things much worse though

    How so, given that we immediately re-enable the same swap device right after so that it's only off for a very brief moment? Let go :)

    Anecdotally, this maneuver can help tremendously tonrecover responsiveness in some cases. I guess the overall sitiation could be improved by tweaking vm.swappiness.

  • Hence:

    After the upgrade and you have plenty of free memory again

    If it's like the last htop image should be no problem.

  • Apart from what others said about power/throttling, I wonder if the filled up memory during the upgrade (or other memory-heavy use) pushes some central pages to swap and then they stay there after?

    After the upgrade and you have plenty of free memory again you can force back everything to RAM by temporarily disabling swap:

       
        
    swapoff $swapdev && swapon $swapdev  
      
      

    To list swap devices, just run swapon.

    Also switching to an X11 window manager can be quite a lot snappier than modern GNOME for older hardware. You could try Xfce, Cinnamon, MATE, or KDE with the X session.

    If it's not throttling/thernals, I wouldn't be surprised if those two together is what made things worse after migrating dist.

    If you've been swapping heavily over time you might also want to check disk health with smartctl and check that you don't have related errors in dmesg.

    If you press tab in htop you can also see if there is high IO load going on.

  • You could try https://winuxos.org/ and see if he notices any difference. What could possibly go wrong? ;)

    Great day to you too

  • Just to rule it out (wouldn't be the case on default debian):

    Is SELinux enabled? sudo getenforce (if command missing or false, it's not your problem here)

    You are not running with podman as compose backend? sudo systemctl status podman shouldn't show an active service unless you use it.

  • It was certainly not intended as a character assessment and it's unfortunate you took it that way. I'm talking about how the release notes (and in passing your post) were written and not about you as a person or maintainer, or even the project itself.

    I do hold release notes of a public project with thousands of users to a different standard than anon lemmy.world comments in a feedback thread. Is that interesting or surprising?

    I believe there was actionable feedback given. You are of course free to dismiss it.

  • OK but how to replace the ASCII Tux in the blue screen of death?

  • For a system actually using ~16GB I don't think a 120GB drive is "way too small" for the root but just on the generous side of just about right assuming there's nothing more than boot and swap on it otherwise.

    Moving /home to a separate drive while keeping the root intact has a few upsides compared to moving everything to one bigger drive.

  • Maybe I don’t understand the use case for bentopdf, and considering how popular it is, that is likely true

    Especially in this day and age, be careful with believing something is right (or even popular) just becuse it looks popular. Talking about generalities of gameable metrics and the cognitive pattern, not to dunk on the project apart from their communications doing the same mistake.

  • It's not as much the general style as the particular contents of this release. Your previous release notes did not give the bad impression this one does. Since you did ask for any feedback I let you know why I am now less likely to use or recommend the tool compared to before. The amount of text and emojis spent begging for TrustPilot reviews also contributes.

  • Deleted

    Permanently Deleted

    Jump
  • FWIW, netstat is considered legacy and deprecated. The in-vogue way to do the same thing is ss -lpn | grep 8080.

    netstat like ifconfig still works and is shipped in the net-tools package if you like it but if you're learning it's better to build a habit with ss and ip right away.

    https://arturogl.com/2023/10/18/linux-new-tools-replacing-netstat/

  • Try to ignore the GH stars and other engagement numbers. Or at least try not to put focus on them in your communications. It's a distraction for you and you are making it a distraction for your audience. GH stars are not a useful signal as they are easily gamed and bought. Maybe yours are all organic, legitimate, and a legitimate cause for personal celebration. But you are just giving false credence to them (and thereby those illegitimately gaming the system) and removing focus from your own app. I don't think it belongs in release notes or a great way to lead your pitch here.

    Most of the first half of the release notes rubs me a bit the wrong way and feels like it's not the place for those messages. Your "Very Important Note" feels less relevant than the "Dad Joke" section (which does have potential entertainment value) and probably has the exact opposite effect than the one you intend.

  • Thanks for sharing your work!

    Do you feel there is anything deeply problematic with the page cache that would make this kind of side channel likely to be around elsewhere too or is it more of a specific case?

  • Phone. And Location 🙃

    One example of how permissions UI on Android is too coarse. Arguably mocking location is a questionable use but this pattern crops up everywhere. I think users must have more fine-grained control over what apps can access regardless of what devs put in their mainfests. It's reasonable that a user wants an app to have access to GPS coordinates and network access but not cell or wifi info.

    In general GrapheneOS gives more flexibility and power to the user than stock but I'm not sure if they go far enough to support what you want to do.

  • If you are ready to build your own packages and host your own repos, go for it. You should have some form of automation to at least get security updates, and it will take some recurring maintenance time no matter how you go about it. I haven't looked closer at Poseidons repos but I think if this is a good idea or not depends a lot on the state of their build/packaging/distro code. It could be just a matter of cloning the repos, changing a few config parameters and running a couple of commands, or it could mean significant work, depending on how well it is engineered. You could start out and if you find yourself digging to deep in the process of getting a build, back out and reassess.

    Kind of like others suggested, there are lighter options. All the big dists should have some form of build tooling to make kickstart/preseed/spins/whatever they call it where you can prepare a custom install ISO with your own set of packages. There are tools like packer and Nix that you can use either as part of building OS images or just script to run on a clean base installation of some dist. You can make an ansible playbook to automate setup and have that run by cloud-init. You could make a shell script to automate the installation of packages and setting up of environment.

  • Why?

    It's a snapshot with supposedly higher chance of working than any other point in time as it's been more thoroughly tested. It's a common reference point. It has prebuilt images and installers.

    Don't Arch and Tumbleweed do the same thing just without giving them names?