Skip Navigation

Posts
18
Comments
230
Joined
3 yr. ago

  • Yeah, it's cool, people are mostly looking for something like your usecase. I got suggested stow or stow-like tools a lot when exploring this. And when they understood what I wanted, they just suggested ansible... Which would work when starting from scratch, but wasn't right for me. I made copicat mostly because I am actually using it, and then decided to make it public because really I didn't find anything like it.

  • Say you want to store /etc/ufw/sysctl.conf which is owned by root:adm and has permission 644 in your repo, but also /etc/ntfy/server.yml which is owned by ntfy:ntfy with permissions 664. How do you keep track of this with gnu stow?

  • That is a good question. I have considered using gnu stow before building this. But there's a couple of problems with that.

    Git doesn't follow symlinks, it stores them as links in the repo, so your only option is to keep the files in the repo, and symlink from the config file location to the repo. This is fine for user config files (like from your .config folder), but if you want to keep system config files (like those from /etc) then the git process needs to run as root to modify those files, because symlinked files share permissions and ownership. And even then, git will always create everything as root because it only tracks permission bits, not ownership, so you will need to constantly fix up ownership of your files.

    With this tool instead you explicitly tell it the ownership and permission of files, and it takes care of that for you (it still needs root permissions of course).

  • ISO/OSI is a neatly separated model mostly used on theory.

    In practice, actual network stacks are often modeled after a simpler model that is called TCP/IP. Which despite the name is not actually TCP specific.

    Here's the general description and correspondence to ISO/OSI:

    1. Host to network / network access layer: it's mostly the nic and nic driver. It's sometimes numbered as 0 because some don't consider it part of the TCP/IP stack, but simply the nic driver. Corresponds to:
      1. Physical
      2. Datalink
    2. Network layer: Corresponds to:
      1. Network
    3. Transport layer: Corresponds to:
      1. Transport
    4. Application layer: everything that's part of the application and not the network stack. Corresponds to:
      1. Session
      2. Presentation
      3. Application

    Or, you can just not care about how the actual software stack is separated, and continue to use the most complete model, knowing that everyone will understand what you when you say "layer 2/3/4" anyway.

    Plus, some could say that the TCP/IP model is equally unfit because the Linux network subsystem doesn't care about layers.

    Edit: I hope the formatting of that table isn't broken on your client, because it is on mine

  • Rule

    Jump
  • That's Tungsten

  • It places you one year ago before they rebranded in rocq (obviously to stop the puns)

  • Then, the year of the freebsd desktop came many years ago when apple released MacOS

  • What disconnecting problem?

  • My system should be fully updated, I will try an Xbox 360 cabled controller

  • That's a flattering thought, but I think that kind of improvement is a pipedream.

    The os shenanigans might be the reason tho

  • You are correct, it also lacks a decorative groove that the "one" one has near the top.

    I think the "series" d-pad is the best modern d-pad, especially since Nintendo forgot how to make them just before releasing the Wii u. I'd say on par with classic Nintendo d-pads, maybe a bit less comfortable for platformers though.

    On the other hand, the 360 d-pad is the worst most horrible piece of crap ever devised.

  • I am seeing higher latency even plugged via cable though, even if less so

  • No, kde

  • Linux @lemmy.ml

    Gamepad latency of the XBOX series S controller

  • yeah, but the point of a platform are the applications it supports, you don't want to be The King of Nothing. If even after buying into wayland, applications still work bad on gnome because they expect to get support for X, than gnome needs X or to give a better option (better for the applications, not just according to themselves).

  • PING. Commenting just for the notification. I edited to respond to the other points but in the meantime you had already answered.

  • The point 2.1 "less to implement in the compositor" doesn't apply, because for xwayland go work (which is intended to stay around for the foreseeable future) mutter still needs to implement SSD, it's only skipping on implementing the Wayland SSD protocols.

    Points 1 and 2.2 are not strong points. "We do

    <thing >

    because we always did before <thing 2>" is not a good point. For example, after all, we always used X10 before Wayland, and we always did implicit sync before last year. And compositor shouldn't limit programming styles, they should support as many things as possible, and let the application decide their programming design. Plus, most modern applications on windows and macos embed a copy of chrome to display a single offline Web page, but I don't see you suggesting we replace compositors with browsers.

    Point 2.3 is also weak because most of the things a compositor does are already hard, but they implement them because it makes the experience better. If something is hard, it just means it will be worked on more. Take a look at explicit sync, it took like 4 years to be rolled out, but it was necessary and got implemented.

    I'll give you point 2.3.1... in general I think KDE looks pretty bad, and gnome is really more polished in many aspects. Unfortunately I really prefer the KDE workflow on big screens (but gnome on laptops).

  • You mean about adding SSD to gnome, which will not happen?

    As an argument in favour, I see:

    • Support for more applications that "don't want" to implement CSD (i.e. foot terminal, davinci resolve, that one archive manager I can't remember)
    • Lifting burden for applications that don't need custom decoration buttons, and so don't care about implementing their own decorations
    • Making the decorations on those applications consistent with the theming of the system

    As an argument against, I personally don't see any. Sure, most gtk apps are designed for CSD and will not translate well to SSD, but I just don't see why that should stop gnome from implementing SSD. I remember the gnome maintainers were strongly convinced against SSD, but I don't remember their argument

  • X.Rule

    Jump
  • Ahhh, Verona, the city of Romeo and Juliet, and of trademark infringements

  • If you are writing a parser in haskell just use Happy and get it over with

  • I experience something similar on a vega56, but it doesn't happen on generic high loads, it happens only

    • in some specific loads (for me it was mainly A Plague Tale: Requiem)
    • when something touches the grounding of my monitor (the display port of the GPU is faulty, it seems)
  • Linux @lemmy.ml

    How to manage configuration files

  • linuxmemes @lemmy.world

    Everything is so tiny

  • Programmer Humor @programming.dev

    His man.go

  • linuxmemes @lemmy.world

    His man.go

  • Linux @lemmy.ml

    Why can ffmpeg kmsgrab capture the tty without root permissions?

  • Linux Gaming @lemmy.ml

    Shadow of the tomb raider, native or proton-experimental

  • Linux @lemmy.ml

    I can now control external display brightness from KDE and I don't know why. Thank you, nameless Linux contributor

  • Linux Gaming @lemmy.ml

    PhysX on Batman Arkham Asylum

  • Linux @lemmy.ml

    Storing SSH keys on gnome-keyring, kwallet, ibsecret or similar

  • Linux @lemmy.ml

    Switching rgb range at monitor plugin

  • Linux @lemmy.ml

    Splitting headphones and internal speakers on a thinkpad with fedora

  • Linux @lemmy.ml

    Imagine trusting oracle

  • Memes @lemmy.ml

  • Linux @lemmy.ml

    Can I apply a shader to the whole screen?

  • Reddit Migration @kbin.social

    remember to update your review of the official reddit app

  • Memes @lemmy.ml

    No more sad dinners