boredsquirrel

@boredsquirrel@slrpnk.net

This profile is from a federated server and may be incomplete. Browse more on the original instance.

boredsquirrel,

Does timeshift also use BTRFS features, or just the normal method?

boredsquirrel, (edited )

If you use BTRFS, there are also some people in Fedora Discuss that may know more about that.

Those tools probably all work with BTRFS. PhotoRec is btw related to the bigger Testdisk.

All these tools seem hardly maintained, but also kinda limited in what they need to do do its okay. Not with BTRFS, bcachefs, f2fs etc though as these may have new fancy tricks.


I was looking for an NTFS restore tool, and used photorec, testdisk, recuva (which very likely just uses testdisk or has cloned its code) and not yet scalpel.

I used Clonezilla where these tools are all preinstalled, it loads to RAM and just works really well.

Testdisk gave me tons of corrupted files with missing headers, but likely the correct ones. PhotoRec gave nothing useful, only stuff from the cache that was likely in the “trash” and not actually deleted. It seems it only recovers intact files, which are nearly never the needed ones.

I need a tool to restore the headers of common file types, as Windows stores them seperately afaik.


I guess a dedicated BTRFS tool could help a lot, as there are likely more ways to recover. But testdisk should work fine.

boredsquirrel,

It is not young but there are simply little tools.

I should write an “awesome everything” list of BTRFS

  • snapper
  • btrbk
  • btrfs-assistant
boredsquirrel,

To be fair, the APGL requires to publish code that is compilable. So giving instructions is pretty relevant for more complex projects.

boredsquirrel,

No but I agree

boredsquirrel, (edited )

In short: all are Crap, use UBlockOrigin

(ABP is worse, Adguard “intelligently shows ads”, Ghostery is spyware)

boredsquirrel,

I dont find the actual article but in the past they sent every site you visit to their servers. Which is simply stupid.

Same goes for FlagFox, Internet Archive addon, TOS;DR and other addons.

boredsquirrel,

Both. TheLinuxExperiment and MumblingHugon have made videos about that.

Bazzite is especially stable, reliable and works out of the box. Others may have better performance, but the cost is pretty big

boredsquirrel,

Lightweight ≠ Optimized

boredsquirrel,

What tests?

Lightweight has many many things that might decrease performance, for example

  • bad multithreading
  • bad available RAM utilization
  • general under-supported and thus not supporting the latest stuff (like vsync)
  • not supported by Valve, which is likely a big thing

But for sure having less bloat helps, but that is constant, while optimization helps relatively to the load.

Light sway might have a smaller constant footprint, kwin a bigger one. But kwin might scale better.

The software you run is often waaay bigger than the Desktop etc.

boredsquirrel,

Ask on discussion.fedoraproject.org, there are many people doing similar things

Linux admin with 20 years experience, looking for "beginner" distro [Solved, the real beginner distro was the Debian I've used along the way]

I’m over tinkering with my OS. So I’m looking for a distro that “just works” out of the box for my laptop. Also I want to test an “easy” distro I can install for my grandpa....

boredsquirrel, (edited )

Yes Debian and use Flatpak for any app you need with a recent version. You can also use a Distrobox with Fedora or OpenSUSE Tumbleweed or Debian Testing if you need system packages that are more modern.

I dont know if Debian Testing is rolling, but Distrobox basically doesnt work with release distros if they need to system upgrade via a reboot, like Fedora. So Fedora Rawhide (dont) or Tumbleweed, Arch etc. are best.

boredsquirrel,

Interesting info but I think they were not relevant at all

boredsquirrel, (edited )

Were you building it, supporting it, or using it?

I had no idea about this, but listen to the talk, it is really informative.

Being upstream of RHEL, instead of Downstream, they have way more freedom. They can test things out, and be more like Fedora.

But yes, CI/CD means Stream will not have long supported stable point releases, but continuous fixes.

I think it is so stable that these should just work, and small updates are not as breaking as bigger ones.

Meta uses CentOS Stream extensively, and even the completely hacked together Hyperscaling version of it, being more close to Fedora server, while improving performance through a dedicated set of packages that are well maintained, selected and branched off Fedora.

CentOS Stream is still really stable. It has 5 years of support, which is not 10, but that amount of support is extreme work. Imagine backporting security fixes to a 10 year old kernel.

The normal Linux LTS kernel has 2 years of support now. CentOS is already really old in comparison.

Paying for Software is okay, and RedHat doesnt seem to waste money.

boredsquirrel,

Yes true, Almalinux and Rockylinux make sense.

Having a continuously delivered enterprise distro sounds reasonable for me, but doesnt make sense if updates are an issue.

I found this video interesting

Looking to get into android development

I want to start learning android dev and I understand that I’ll need the android sdk and cli tools. I want to try it in a kvm because even though it is open source, I would like to keep it separate from my main system. Which distro and vm settings do you suggest I use? Any other tips or your experience with android development...

boredsquirrel,

Second the Flatpak, but stuff like installing APKs over USB might not work. Dont know if that is really needed.

You can make adb work on Fedora, I documented 2 ways (with or without installing RPMs) here

boredsquirrel,

Your CPU is okay, for testing instead I recommend installing virt-manager qemu qemu-kvm. The packages on Debian are called a bit differently.

You can also just install XFCE on Debian, it doesnt interfere with GNOME.

boredsquirrel, (edited )
  1. (Some years, Childhood), Windows XP laptop with games on it, Windows 7 on some Minecraft PC lol. (3 years) Windows 10 on a Thinkpad T430, really nice laptop, but the OS was boring and kinda bad
  2. (3 days) Linux Mint, secondary drive. Had random blackout crashes that were not hardware related (still use that SSD today). Also wasnt impressed by the UI, but a very interesting experience of “the Linux”
  3. (Few weeks) Manjaro, awesome KDE experience and theme, really really nice. But had a bad reputation, so went looking for other KDE Distros
  4. (Few months) MX Linux, damn Distrowatch rankings. Got an error and my University IT people told me my Nextcloud client was too old, but the conky manager was awesome.
  5. (Half a year) Kubuntu, with Backports, then switched to KDE Neon. Began nice, then went more and more unstable and broke
  6. (Few weeks) Fedora KDE, finally dared the move to a “less known OS”, but it broke too. I guess that Plasma 5.2x phase was just messy
  7. (Over a year) Fedora Kinoite, uBlue, secureblue, Aurora. Tried the Kinoite prerelease for Plasma 6 and now for 6.1, finding some bugs.

Now happy part of the Fedora Community, rpm-ostree is just so good and makes Linux usable for me.

Also experimenting with GNOME, COSMIC, Kinoite-prerelease and CentOS-Stream in VMs or external drives. Also experimenting with minimal, bloat-free KDE Plasma, as it is actually really light and simply the best supported modular desktop environment.

boredsquirrel, (edited )

Have a look at my flatpak repo list with instructions on that

The question is, do they change the remote or just hide the apps?

I currently use 2 flathub remotes, the verified (named flathub-v) and the unfiltered one. When installing from CLI I can see if it is verified (2 possible remotes show up). I hope COSMIC store and KDE Discover will show the verification check soon.

I use nearly only verified Flatpaks (a list of recommended ones is here, will soon update)

But a few popular ones are not, like VLC (developers dont know Flatpak, should get an introduction by the current maintainer), Inkscape, Spotify, Steam, Bitwarden, Signal, Torbrowser launcher, Blender, Calibre, and more (excluding Chromium Browsers, use the native versions for security reasons) are all missing.

Important things to consider:

  • distro packages are nearly always unverified i.e. maintained by distro packagers instead of upstream
  • spotify flatpak is not verified, but the flatpak is securely packaged. Mint has a deb repo, and that proprietary piece of malware could do whatever they like with your entire system
  • flatpaks are very often more secure, at least they have some security mechanism that can be easily manually hardened. Unlike firejail or bubblejail, which are very complex.
boredsquirrel, (edited )

The Flathub security rating is useful but too cautious (so many “false alarms” that people ignore it). It is completely independent from the verification though.

Mixing these up makes no sense.

But for sure, officially supported Libreoffice may be more secure than distro-packaged Libreoffice.

Is any of these applications dangerous or a security risk to the system / user?

Likely not more than Distro packages. They pull in dependencies, and code, just like any other app.

Flatpaks are too pain tolerant regarding EOL runtimes. These may have security risks, and many badly maintained apps are using them, and at least KDE Discover doesnt show a warning here.

Create a fork of an app and verify your website with the fork in Flatpak. The system is already broken

True

By doing so, it undermines a reason why we use GPL and Open Source.

Very good points. It is a good security practice to stay close to a trusted upstream though. Browsers for example may have delayed security patches.

And what about apps where the original author does not care, but was brought to Flatpak by a community member?

Same here, if the upstream tests the Flatpak BEFORE shipping the release, it will work and be fast. If they dont, they ship the update, the flatpak is updated some time after that, it may have an issue, the packagers may need to patch something, solve the issue upstream etc.

The thing is that packagers should join upstream, as only integrated packaging gives this inherent stability and speed.

This is not relevant in many scenarios though. Flatpaks allow to securely sandbox random apps, so they are very often more secure.

boredsquirrel,

Meanwhile, they have a Spotify Ubuntu repo… and will offer the installation of all these apps as .deb’s which are able to do whatever they want

boredsquirrel,

Especially as many Flatpaks are already working better than Ubuntu apps. I had this with SciDAVis, where the Ubuntu version was just broken and gave me tons of troubles.

Flatpak is a blessing

boredsquirrel,

This assumes that distro packages would be more secure. Which are not “verified” most of the time, by design. And which are installed to the system, can do whatever they want.

A system package can edit /etc, autostart itself, write to all your devices and /home.

Flatpaks MAY do that, but these will have an “insecure” rating on Flathub. And they can still not write a lot of areas, for example other Flatpaks internal storage, even if they have home permission.

boredsquirrel,

Meanwhile they offer a deb repo for Spotify…

boredsquirrel,

These are Ubuntu Packages. The external Spotify repo are binaries shipped by Spotify. I dont think there is any testing before users get that package, it is an external repo.

boredsquirrel,

It is proprierary Software, running as a pretty unrestricted app on your system.

The app could steal your Keys, read your photos, scan for pirated music or whatever.

Yeah, no problem XD

for sure you could do the Microsoft Way and trust random big tech, because otherwise you would just sue them… but no.

The spotify Flatpak has no Filesystem permissions afaik, and it thus pretty okay secure, even if you dont trust the upstream.

boredsquirrel,

The Flatpak meanwhile is transparently packaged, using the binary from the official Snap.

Canonical to my knowledge took forever for convincing Spotify to support Linux. Supporting Flatpak should be easy, but whatever.

boredsquirrel,

Yes but this was just an example of the hypocrisy of this action.

  1. Apps that are FOSS are possible to trust. Proprietary apps are simply liability, and proprietary software is constantly spying anyways. Flathub has –subset=floss for that
  2. "Verification" i.e. upstream support is not the case with a majority of Distro packages. Flathub has –subset=verified for this very nice ability (but this does not mean that unverified apps are worse than distro packages!)
  3. Flatpaks are isolated using Bubblewrap. Firejail, a common alternative for native app sandboxing, had a root binary and thus you need to trust it a lot. Bubblejail is a predecessor of it, but it is not easy to use at all and in early stages. So Flatpak offers stupid simple app isolation similar to Android, Distro packages dont have this.

Flatpak is really good. You can look at the permissions, any app with the “safe” rating is probably safe, even if it is malware.

Btw the safety rating would be a good filter, once they solve the false negatives of stuff like ProtonPro/pupGui.

boredsquirrel,

There is a difference between the packages shipped by default, and any random package in the repo.

In this case, Ubuntus universe repo will have less supported packages.

boredsquirrel,

Pop!_OS by far.

Note that NVIDIA ships proprietary, out of tree drivers.

No Linux Distro really supports NVIDIA as they cannot fix the drivers, as they are proprietary.

Manjaro is weird semi-rolling with a criticised mechanism of holding back packages without real testing (which might be outdated info).

PopOS is based off Ubuntu LTS, a stable distro and the most common Linux variant.

Stable distros will not break the NVIDIA stuff. NVIDIA doesnt care about rolling release etc, and Distros need to not break it, as they can package them but not fix them.

Yes, Bazzite using Fedora Atomic is very nice through the inherent stability of the OS distribution model.

But they rely on rpmfusion, an external repo packaging the proprietary NVIDIA stuff for Fedora. The repo is not supported by Fedora, and the drivers cannot be fixed by anyone.

Keep that in mind. NVIDIA sucks.

boredsquirrel,

allows automatic fixes to be applied to a broken driver without requiring any manual intervention from its user.

If you get an update, and after that update your system doesnt graphically boot anymore or something, you can use sudo ostree admin pin 1 and rpm-ostree rollback to switch back to the working version and make sure it never disappears.

Then you can wait for a next update (still no good update info mechanism afaik) to fix it, try it, unpin the saved version and go on.

But there is no automatic repair voodoo anywhere, on any distro. That driver is proprietary, only NVIDIA can fix it. rpmfusion packages it to work on Fedora, Fedora Atomic helps making this very unstable mechanism more failsafe.

But you are still relying on 3 entities (NVIDIA, rpmfusion, Fedora, (uBlue)), with NVIDIA not caring about Linux that much, instead of 1 (Fedora) like with AMD, where drivers are FOSS and can be adapted for Fedora specifically.

AMD does not opensource a lot, and ROCM or the entire amdgpu-pro driver is a similar situation. But at least the basics work.

boredsquirrel,

Keep in mind /etc is mutable, so rebasing will still pile up garbage even when using different user Accounts.

gitlab.com/fedora/ostree/sig/-/issues/28

boredsquirrel,

uBlue does not repair anything, they dont automatically detect a broken driver on your system and block an update.

This would be possible, but slow down boot (running some GPU benchmark on every boot via a systemd service, if it fails run the commands that I mentioned).

rpm-ostree is awesome, and has the potential to do that.

you don’t get the broken update ever on your device in the first place.

In theory yes, but this would mean uBlue is some kind of stable distro. I dont know, at least their base images just get updates.

Their big advantage is that they dont have the legal restrictions, so they can ship 1:1 the system you run. I dont know if they do, but having some automated benchmark tests on real hardware with these devices would be useful.

But that costs a lot of money. uBlues trick is that they can run their whole huge project for free on Github.

But for sure, the dependency issues will not occur. But this does not guarantees that there are no issues on bare metal.

Or a stable branch, Bazzite was longer on F39 for example. I use the :latest branch which automatically gets upgraded to the latest version, which they determine. So having an :testing branch that is up to date, and slowing down the releases of the latest branch, could help.

boredsquirrel,

Yes agreed.

I didnt know they have testing images, but makesbsense in their flagship variants.

I miss the old website with the full image list.

boredsquirrel,

I dont know.

“Traditional” / “package based” / “messy” distros suck a bit. The big issue is doing insane stuff like the kernel mod stuff on the user side, which leads to sooo much pain.

But as far as I know, NVIDIA just supports enterprise distros. The community distros build the packages, but the binaries are not compiled for newer distros. So using non-LTS Ubuntu etc may result in breakages. Especially when using newer kernels.

I dont know a lot of how drivers depend on userspace programs, it is likely only dependend on the Kernel.

I also look forward to CentOS-bootc, which is a bootable OCI container for CentOS-stream. Like the uBlue Containers or the OCI containers for Fedora built on Gitlab, used by uBlue.

I didnt know that, but uBlue uses random OCI container builds by Fedora for all their stuff, that Fedora doesnt even officially use themselves.

boredsquirrel,

I tried looking this up, but to no avail. Got any proof to back this up?

Interesting, I only found a different site that offered the download specifically for developers to embed in their distros.

It was AMDGPUPro that only supports enterprise Linux.

Could you provide a link

I didnt find it. Search in the Atomic issue tracker, siosm wrote somewhere that the images are built on Gitlab and are the foundation of uBlue.

While Gitlab is not the official distribution method, and this was an issue about adapting these images for the main Fedora variants. So they arent even used, but built.

That upstream unused images are taken as the base for uBlue is pretty funny. But they have a future, and will likely become the main way of shipping Fedora Atomic.

Then it is also truly image-based, unlike the OSTree repo currently.

boredsquirrel,

Well you will VERY likely need FEX for “Gaming” (if you talk about x86_64 proprietary Windows software)

I am sure Xonotic and others are already available on ARM Linux.

boredsquirrel,

there’s been a lot of concern that Snapdragon X-based PCs might be locked down to Windows, and while it remains unclear just how easy it will be to install a GNU/Linux distribution on a Snapdragon X PC that ships with Windows, it’s nice to know that at least one company is looking to release a model that will come with Linux pre-installed.

What does that mean? Are they not using UEFI?

I just hope they use Coreboot.

Btw are there any FOSS Coreboot compatible ARM Chromebooks worth looking at?

Run Flatpak apps by search filter or through fuzzy finder menu (gist.github.com)

I wrote a simple script in order to help someone in a recent reply from me, to make running Flatpak applications from terminal easier. After that I worked a little bit on it further and now ended up with 2 completely different approaches....

boredsquirrel,

Oh I see you also had the flatpak issue where the developer name is used instead of the project name.

To solve this, use flatpak remove -y --force app && flatpak install app -y as there doesnt seem to be a fix to recreate the Metadata

github.com/flatpak/flatpak/issues/5700

I think some smart function is really needed, as many people will have messed up apps. For me it was 8 or more.

boredsquirrel,

Or use ~/.local/bin/

Didnt know about the preferences. These only depend on the order of placement in PATH?

Or do they get by directory hierarchy, i.e. HOME can always override the System.

Unix stuff is so simple sometimes

boredsquirrel,

It doesnt happen again, the metadata parser was broken and metadata is not updated on updates, only on reinstall.

So you dont have this with Flatseal anymore?

boredsquirrel,

Interesting

boredsquirrel,

Thanks, good to know!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fightinggames
  • All magazines