• 0 Posts
  • 23 Comments
Joined 3 months ago
cake
Cake day: April 12th, 2024

help-circle

  • Peasley@lemmy.worldtolinuxmemes@lemmy.worldnuclear take:
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    2 months ago

    I guess I’m smart enough to install opensuse, but dumb enough that I somehow got slow pacman.

    I kid you not, on my hardware zypper is the fastest between ubuntu apt, fedora dnf, and arch pacman. dnf was the second-fastest on my hardware, with apt and pacman being pretty sluggish

    I’ve also used portage which was even slower, but probably not a fair comparison considering how much more complex it is.



  • Peasley@lemmy.worldtolinuxmemes@lemmy.worldnuclear take:
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Somebody has never used opensuse. Zypper is an amazing package manager, one of the best on any distro.

    It can handle flatpacks, native packages, and packages from the opensuse build system, keeping everything updated and organized.

    Pacman is very basic by comparison, and a lot slower too in my experience.





  • LTS kernels aren’t more or less stable. Rather, they have been selected by the kernel maintainers to get security fixes backported to them for a certain time.

    Ubuntu does the same thing for the kernels on their LTS versions (technically they usually are not LTS kernels since canonical supports them instead of kernel team)

    Overall I’d suggest going with what the distro provides unless you have very new hardware, in which case a newer kernel may be required



  • I don’t hate systemd. However:

    Units and service files are confusing, and the documentation could be a lot better.

    That said, when systemd came out the traditional init stack was largely abandoned. Thanks to systemd (and the hatred of it) there are now a couple of traditional-style init systems in active development.







  • Just saw your edit. One thing you should be doing is taking ownership of directories you plan to be working in. So for an external drive for example, you’d want to make sure your user(s) have r/w/x permission recursively (granting permission for all files and folders underneath using the same command) on the root folder of the drive then you can move stuff on and off freely.

    I agree it could be more straightforward, but ideally you’d only have to do it one time when you first use the drive with that machine




  • That was also my take. If it’s something you should be able to edit, your user should have permissions to do that. Jumping to running as root every time has lots of unintended consequences.

    I do think a functionally similar idea would be a button to “take ownership” (grant “/r/w/x”) of a file that would prompt for root password. That way things don’t run as root that shouldn’t. Would that be a good compromise between Linux permissions and Windows workflow?

    Regarding formatting a drive, whatever program you are doing that in should ask for root p/w when performing that operation. If it just refuses because of permissions that seems like a bug.