d3Xt3r

joined 1 year ago
MODERATOR OF
[–] [email protected] 6 points 9 months ago* (last edited 9 months ago) (2 children)

I use uBlue and update manually (using a custom alias/script) whenever I get the time, like say during my lunch break or something. Reason being, I actually like watching the update process and seeing what gets updated, watching out for major version number changes or major package upgrades, and if I'm interested I may look up some of their changelogs to find out about their new features etc.

and being forced to reboot

You should be forced to reboot though? And if you don't want to reboot, can't you just do an --apply-live? I mean you'd still need to reboot for a kernel update but for the most part, you should be able to use most of your new packages without a reboot. And this holds true even more so if you're updating Flatpak/container/Nix/pip/cargo/brew packages. And I hope you're not doing the rookie mistake of actually installing stuff at the ostree layer instead of using Flatpaks/containers/Nix etc.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

I was referring to the use of Nix the imperative way, as opposed to declarative which requires writing a config file. In the imperative way you can install/upgrade/uninstall packages with just a single command, similar to other package managers.

Eg:

nix profile install nixpkgs#tealdeer -> installs tealdeer from the nixpkgs repo.

I've been using Nix to install stuff this way on my immutable OS for about 6 months now this way and haven't had any issues. And it's fast. Like, even faster than pacman, which is one of the things I like about it.

[–] [email protected] 36 points 9 months ago (1 children)

My favorite:

[–] [email protected] 0 points 9 months ago (1 children)

Distro defaults perhaps? I'm using Bazzite, which is optimised for gaming/desktop use.

[–] [email protected] 3 points 9 months ago* (last edited 9 months ago) (3 children)

The AMD EPP driver is already enabled for me and works fine out of the box. As I said before, I'm getting both excellent battery life and gaming performance without needing to tweak anything.

I never had the need to run CUDA/ROCm though so can't speak for that.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago) (5 children)

Once again, I didn't have to install anything special to take advantage of any features. Sensors worked out of the box for me. AMD is excellent with their Linux support and Linux users don't need to "hope" for anything. I get a consistent 60 FPS on Forza 4 at ULTRA settings on my ThinkPad, without using any proprietary drivers or doing anything special. I'm quite happy with my setup and don't feel the need for any extra special monitoring or tweaking. Plus I get a 10+ hour battery life with moderate usage. What more would I need?

Buy Linux-compatible hardware, ditch nVidia, no need to complicate your life. :)

[–] [email protected] 5 points 9 months ago* (last edited 9 months ago) (7 children)

All AMD here, didn't have to get anything special installed to make stuff work, no special kernel flags or proprietary modules.

  • Desktop: Ryzen 5 3600 with Radeon RX6600 XT, on BunsenLabs
  • ThinkPad Z13 Gen 1: Ryzen 7 PRO 6850U with Radeon 680M, on Fedora uBlue (Bazzite)
  • Minisforum UM780 XTX: Ryzen 7 7840HS with Radeon 780M, on Arch Linux with x86-64-v4 optimisations

Moral of the story: avoid nVidia, buy Linux-friendly hardware and you'll be all good.

[–] [email protected] 3 points 9 months ago* (last edited 9 months ago) (2 children)

Audio works. Not sure how though, --unshare-devsys is supposed to not share the hosts devices, but I guess audio devices are an exception.

The full isolation flags are:

--unshare-devsys:          do not share host devices and sysfs dirs from host
--unshare-ipc:          do not share ipc namespace with host
--unshare-netns:        do not share the net namespace with host
--unshare-process:          do not share process namespace with host
--unshare-all:          activate all the unshare flags below
[–] [email protected] 13 points 9 months ago* (last edited 9 months ago) (4 children)

Distrobox, by default, doesn't provide much isolation/sandboxing - it's main aim is desktop integration and filesystem transparency. So if you're trying to use it for isolation, it's a bad idea.

However, you can create a new container which will isolate your filesystem and prevent such conflicts, using the --unshare-devsys flag. (if you want FULL isolation though, use the --unshare-all flag).

Then enter the container and install the flatpak app as usual.

I just tested this on Fedora uBlue and an Arch container and it works fine, didn't have to unmount anything.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

If you're after fluid yet lightweight animations then you should definitely check out Wayfire. Yes it's Wayland and a WM not a DE, but you can get a distro/spin with Wayfire and all the stuff you need for a DE all pre-installed and pre-configured. Wayblue (based on Fedora uBlue) is one such option you can try. And because Wayblue is immutable and has reliable atomic updates, it'd make a great option for you as a school-goer as stuff rarely breaks and you can always rollback to a previous image before the update.

[–] [email protected] 19 points 9 months ago

> Google AI outperforms medical doctors on diagnostics tasks

> URL: blog.research.google

[X] Doubt

[–] [email protected] 20 points 9 months ago (1 children)

Congrats, and welcome to the club!

view more: ‹ prev next ›