Chewy @ Chewy7324 @discuss.tchncs.de

Posts

96

Comments

1,013

Joined

2 yr. ago

The I/O size is a reason why it's better to use cp than dd to copy an ISO to a USB stick. cp automatically selects an I/O size which should yield good performance, while dd's default is extremely small and it's necessary to specify a sane value manually (e.g. bs=1M).

With "everything" being a file on Linux, dd isn't really special for simply cloning a disk. The habit of using dd is still quite strong for me.

Gnome Software has received numerous updates over the last few years which make it considerable faster. Searching and viewing apps is now fast enough to be usable, compared to it taking many seconds to minutes for basic tasks.

I've stopped removing Software on every system, altough I'm not usually using it. I've not tested it, but I feel like Discover is now slower than Software.

It's not possible to dd a Windows ISO to a USB stick.

What way too many people fail to understand, because Linux ISOs are applying this method, but this is essentially a MAJOR HACK CALLED 'ISOHYBRID', is that, in most cases, you cannot simply take an ISO image and copy it byte for byte to a USB drive, and expect that to boot.

https://superuser.com/questions/1527197/debian-creating-windows-10-bootable-install-usb-drive-using-terminal-dd#1527373

But is it useful what you've learned? Could've learned something else.

(But I'm commenting on a meme, instead washing my dishes, both things that didn't teach me much).

After using multiple tiling compositors over the years, I'm pretty much set in how my system works. There's not much I have to do, except the occasional tweak to keybinds for launching apps, adding some window rule or changing my monitor layout. Those are things I'd have to do on any DE and they don't take any longer.

Until I need something unexpected not yet set up by me, e.g. switching keyboard layouts. But it's been a long time since I needed to do any of that. That's the beauty of config files stored in git: Once it's set, just forget about it.

Edit: I do agree though, the time it took to arrive where I am is considerable and definitely not something I recommend to others who value their time.

This will help eliminate excess baggage that builds up over time by automatically removing end-of-life runtimes that are no longer used. As the system is updated to use new drivers/run-times, the old ones can be automatically removed.

This might solve the issue with flatpak nvidia driver versions not being removed and accumulating over time. AMD/Intel don't have this issue as a single flatpak mesa driver version can work with multiple system drivers. Nvidia's closed source driver needs an exact version match to allow for flatpak's sandboxed GUI apps to work.

At least that's how I understand it, take it with a grain of salt.

You're right, media could still be wiped. Other data owned by users would be protected (e.g. configs).

Running everything under a single user is possible, but it also means an issue with a single app could wipe everything. It's better practice to add each user to a media group, and set *arr and qbittorrent to use this group and allow write permissions for users in the same group (e.g. 775 instead of 755). This means all users (plex, qbit, *arr) in the group media can access and modify files owned by media (or use the GID).

I've been using Sway on and off since 2020. Wayland always worked well as long as it supports the specific use case and the apps are doing the right thing (e.g. pipewire, portals, no Xwayland).

VRR with multiple monitors and HDR are likely the biggest reasons to use Wayland, as most other improvements are less noticeable. E.g. Sway always felt more responsive to me than i3 + picom, even with a single monitor in 2020.

If you have issues with applications not working well on Wayland, either wait for proper Wayland support or ditch them. For Steam this'd likely mean stay on X.org.

Security is the main reason I'm considering switching to flatpak Steam. Being able to limit system access for Steam and its games to ~/Games is a blessing and easy to do with flatseal. The disadvantage is getting new mesa (graphics driver) versions later.

Yes, third party app stores were a pain for a long time, until Google allowed other stores to update apps unattended. A user having to comfirm each individual update was a terrible user experience.

Google and other pre-installed app stores circumvented the issue by being installed with system privileges to install any app unattended.

Any third-party store who'd want to do the same would either have to pay other manufacturers to be pre-installed, or require their users to root their phone. Or they were annoyed by updates and use the Play Store instead.

Yes, since Android 12 app updates doesn't require user confirmation for updates through the store which installed an app originally. This came at a similar time as the Epic lawsuits, so it might be a concession to prevent losing a lawsuit about their anti-competetive behaviour.

Google did pay manufacturers to not include third-party app stores [1], but I they can't force other stores to pay them any fees. It's bonkers to me that Apple wants to charge other app stores for providing apps to their consumers, who paid Apple to own their device.

[1] https://www.theverge.com/2021/8/19/22632806/google-epic-premier-device-program-lg-motorola-hmd

Fedora requires adding rpm-fusion to enable proprietary apps like Steam or hardware acceleration for codecs like h264. It's a great distro besides that, and I sincerely hope they'll just accept the legal risk like Ubuntu does.

Agreed. The new restrictions are similar to what Spotify is doing with their family plan and is way more useful for it's intended purpose.

Being able to play game from a single library simultaneously is awesome and how it should've been from a usability perspective.

Sadly this change will make it impossible to simply share games with someone specifically, since it's now required to be in the same Family Share, which is a strong commitment. For sharing games in a single friend group, this change won't change much (unless someone still wants to share with their family). The changes make game sharing work more like intended, in other words family share.

I notice lately that many memes origins are worse than I thought from the context they are used in. Racist, homophobic, and lying people are not something I usually accept as entertainment, but they sneak their way unnoticed into my (non-news) feed through memes. I guess most people won't know the origins of the meme and use it according to the meaning they formed on their own. Other memes like the distracted boyfriend meme are meaningless stock photos, so I understand why many people use memes without thinking about the origins.

Anyway, thanks for pointing out who the person in the picture actually is.

Scrolling tiling is a niche not supported by hyprland.

Personally I'm not yet sure whether I like scrolling tiling. It might be really interesting for single monitor setups, but I feel a dynamic tiler is better for a multi monitor setup. With multiple screens, available space isn't an issue and not having all windows visible or on another workspace feels like a disadvantage.

But maybe I just have to get accustomed to niri. The concept is great. Especially on tablets it might be really useful.

That's the risk of partnerships with other companies for established brands with users who care about their ideals.

It'll be interesting how Mozilla reacts to this news, as they should've done better research themselves.

The major difference between lemmy and reddit is that there's many instances for search engines to crawl, compared to a single reddit.com. They likely treat each instance seperately, which leads to a lot of duplicate content and most of lemmy isn't search engine optimized.

Sadly I don't see a better way to do it than for search engines to be optimized for this kind of federated platforms. It's not obvious from the outside which is the preferred instance to show to a user.

I've had some luck finding content on lemmy by forcing a specific instance using site:lemmy.instance.domain, but it depends on the search engine whether it's respected.

Having both Gnome and KDE installed at the same time might lead to unexpected and difficult to diagnose issues. E.g. I've had issues with broken themes when the same user/home directory is used.

Another example: having both xdg-desktop-portal-gnome and xdg-desktop-portal-kde installed at the same time, sometimes leads to broken file chooser and screen share (at least that's the case with other xdp, like xdp-wlr). The portal issues are more likely to be noticed while using Wayland and/or flatpak, as they make use of portals.