Samueru_sama @ Samueru_sama @programming.dev

Posts

0

Comments

66

Joined

1 yr. ago

fair, in that case the comparison is even since busybox provides a shell, awk, grep, wget among other 395 utils, uutils it is 115.

The utilities in BusyBox generally have fewer options than their full-featured GNU cousins

Note: GNU cousins, not GNU coreutils.

GNU awk, GNU grep, bash, wget, etc will give you a lot more features than the busybox equivalents. However the uutils nor coreutils implement those features at all.

If anything the comparison is not being fair to busybox because busybox implements a lot more utilities.

That’s not a fair comparison at all. Busybox is specifically optimized for size, and to accomplish that, leaves out a large number of GNU compatibility features

Such as? busybox provides a nice interactive shell, awk, bc, wget and much more. I know GNU awk has a lot more features than posix awk but awk is not part of the uutils anyways.

busybox also implements [[ from bash, none of this is provided by uutils or coreutils.

EDIT: busybox also provides grep while the uutils/coreutils don't.

I’ve built it that way now and that puts it under 7 MiB; still much larger than busybox, but it shows how much the optimization choices matter.

I'm assuming this uses -Os which means performance hit, (iirc busybox also uses -Os so it is fair comparison), still we are looking at 7x larger binary.

whereas Rust binaries are statically linked by default, meaning that the binary is actually self-contained.

rust still produces larger binaries even if you compare it to static C binaries.

Take for example busybox, you can compile all of it as a single 1.2 MiB static binary that provides 395 utilities including wget.

Meanwhile the uutils static musl binary is 12 MiB and only provides 115 utilities.

AppImages may not run, sometimes due to libc, sometimes due to fuse. Technobabble for the common user.

The worst part is, the new formats are NOT compatible with the old ones. Of course. So if you want to use snaps or Flatpaks, you must ADD to your operating system. Instead of having just one package manager like zypper or apt, both the command-line utility and the equivalent GUI store, now you have two, maybe three competing software tools. This adds complexity and overhead.

This is fixed if you package your appimages properly and use the static runtime which was existed for over 3 years already...

I do that here: https://github.com/pkgforge-dev/Anylinux-AppImages

Here is GIMP3 packaged on archlinux running on ubuntu 10.04

In this case the issue is with 100% on flatpaks side that they decide to ship and download the entire nvidia driver again instead of using the one of the host. Note both snap and appimage do not do this, they use the nvidia driver of the host.

There is no reason to have to download the entire nvidia driver again, distros cannot modify it as it is against its license.

Also even outside of nvidia you are still going to have troubles in games with flatpak if what you are using requires a recent version of mesa

That's the real location of the certs, but once again they usually make a symlink in /etc/ssl/certs/ca-certificates.crt

One library that is problematic is p11-kit, this one usually comes with a different path to the certs hardcoded and does not respect env variables unless it is compiled with a specific flag which no distro uses.

So I had to do this hack to fix that library.

Most distros have /etc/ssl/certs/ca-certificates.crt, sometimes it is a symlink but that location is there in ubuntu, alpine, fedora and arch.

edit: Also you can usually change this location with an env variable.

You can sandbox the neovim appimage with AM and then it will ask you what locations you want to give access to. https://github.com/ivan-hc/AM

am -i nvim

am --sandbox nvim

This is the single most important aspect of immutable distributions. Because the core of the system is mounted in read-only mode, it cannot be changed. With the core system locked down as read-only, it's not possible to change settings in directories like /etc, /boot, /dev, /proc, or other critical locations. That means if you wound up with malware on your system, it wouldn't be able to alter the contents of those directories.

Because of this, immutable distributions are more reliable than non-immutable. Even better, if you accidentally break something, it will most likely be fixed during the next reboot.

Atomic updates are quite different from standard updates. Instead of the OS treating an update on a package-by-package basis, it's an all-or-none situation. In other words, if an update to a single package would break something, the update will not happen and the system rolls back to the previous working state.

You get the same by setting up btrfs snapshots with any regular distro...

With an immutable system, you are always guaranteed to have a bootable system.

lies

You want me to track the progress of 4 bugs in Sway? Such a powerful argument.

4 bugs discovered in less than 48 hours of use.

How about don’t use Sway?

I don't, I'm on i3wm as result.

For tiler lovers, Niri and Hyprland are both great.

Tried hyprland as well, it is useless.

Hyprland is such a meme, that the config file doesn't allow chaining multiple actions to a single keybind, you have to instead repeat the same keybind several times in the config lmao.

Also in hyprland you cannot move a floating window between displays using the move left and right commands, this is because the action does not move the window in that direction but rather to the left or right side of the display, meaning the window gets stuck at the border between the two displays and does not move anymore 😹

Also this whole disaster that I was a victim of, the documentation was insanely outdated and someone had to repeat the dev about the issue: https://github.com/hyprwm/hyprland-wiki/issues/242

Even more hilarious. Looks like you found an even crappier Wayland compositor than Sway.

It works lol

My issue is not if an app works on X11 or wayland, but the terrible implementations that wayland that lack even the most basic features.

My point is that everybody else is happy leaving you behind

And once again doesn’t remove the fact that wayland still sucks 😆

I have had corrupt filesystem errors with BTRFS on both of my computers due to power outages and one hard shutdown (had to)

When did this happen? what error did you get?

Btrfs will explicitly go read only when it detects corruption, which is a good thing, with EXT4 you don't know what is going on until it is too late.

fwiw the only time I managed to get info from an user that had "issues" with btrfs, I discovered that what had happened is that they moved the partition that had snapshots, and if you don't know it, this is catastrophic because this unlinks all the snapshots and suddenly everything would take many times more storage.

Used ext4 for YEARS (I am old) and never had these issues with such frequency

The short time I've used EXT4 running into bad superblock errors was something that happened almost every week, but in the end I was always able to repair the disk and recover everything.

I'm from Venezuela, power failures are common here.

isnt it the same with arch?

I once to helped troubleshoot an EndeavourrOS user.

during the process I discovered that their kernel parameters were being reset with every kernel update, this was because Endeavour was using dracut instead of mkinitcpio...

especially if you ever do a hard-shutdown, prone to power-outages, etc. It will scramble your system files.

Btrfs is made precisely so that a power outages don't do that! and you don't end up like ext4 with bad superblock nonsense.

Been using Btrfs for over 3 years at this point, 0 issues and over 400 unsafe shutdowns: https://imgur.com/a/AKXFdKb

In fact it was able to detect when my previous ssd was dying, I thought Btrfs was spewing nonsense until the next day when smartctl began to report issues as well lol.

There are lots of issues with Wayland. They will be fixed

Remind me 2030 if these issues I have get fixed:

https://github.com/swaywm/sway/issues/8000

https://github.com/swaywm/sway/issues/8001

https://github.com/swaywm/sway/issues/8002

https://github.com/swaywm/sway/issues/8191 I later learned the reason sway is using capabilities is to fix performance issues, which yeah still has several...

One issue the wayland proponents fail to notice is that the ecosystem itself is fragmented, you have several DEs/WM with their own implementations and bugs that will likely never be fixed.

I'm an i3wm user, my only option to switch to is sway, doesn't matter if some of the issues I have are fixed in kwin or mutter, it has to be fixed in sway.

But most Linux desktop users use Wayland already.

Most desktop users use windows, and they are happy with that, why don't you stop using linux and move to windows?

Everyday there are more and more apps that are Wayland only. Before 2030, that list will include all GNOME and most GTK apps. Are people really going to give up all these applications because of some obscure advantage they perceive in X11?

https://aur.archlinux.org/packages/12to11-git

people writing these articles do not realize that they are already in the minority and have already been left behind.

Doesn't remove the fact that wayland still sucks 😆

Wayland support for multi-monitor configurations is better than X1

Alright, how do I merge the 3 displays that I have as one then?

https://www.reddit.com/r/wayland/comments/108dgwc/combine_monitors_to_single_screen/

Whatever performance degradation you claim to experience is also a “you” thing

It is one of the reasons why Eden disabled wayland by default but sure thing, just a me thing 😆

There’s an underlying issue with your setup.

Yeah, it is called sway.

I don't even use a login manager, directly login from tty and just launch each respective game, sway is able to use my i3 config directly, the only change in this setup is the window manager.

Also note, this performance issue is not present in BeamNG, it only happens with Eden, citron, etc (all yuzu forks).

A lot of the new modern users are into gamin

I can't use wayland for gaming because I do multi-monitor gaming, and something that was a very simple xrandr --setmonitor is impossible in wayland...

I 100% have seen performance increases and stability increases after switching to Wayland with regards to gaming workloads.

All I have seen so far is that I get half the fps I get on citron/eden on sway vs i3wm.

They are also fed up with the wayland bugs and decided to force xcb everywhere, one of the bugs is that the app just crashes on wayland gnome, it does not happen plasma, or sway, or any other place, just gnome.

Check my dotfiles https://github.com/Samueru-sama/dotfiles

0 hidden files, everything is in ~/Local.

Recently added this hack for ssh: https://github.com/Samueru-sama/dotfiles/commit/7e1f8bd3173da563731aea6db9efbf26a2b23e72

but Flatpak is good when you need sandboxes

flatpak sandbox is actually bad for web-browsers and electron apps:

https://librewolf.net/installation/linux/#security

https://seirdy.one/notes/2022/06/12/flatpak-and-web-browsers/

https://github.com/uazo/cromite/issues/1053#issuecomment-2191794660