I am a Meat-Popsicle

  • 0 Posts
  • 67 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle

  • linearchaos@lemmy.worldtolinuxmemes@lemmy.worldMany such cases
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    16 days ago

    KDE connecting infuriates the hell out of me. It’s so close to being good. The features aren’t at parity between the different platforms. It is absolutely awful at finding and pairing your phone. I have three different networks I connect to on a regular basis. I don’t want to run static IPs on every network nor do all the clients support static IP. If you do use static IPs you better only need that one because it can’t choose from a list. Wanted to scan a different subnet than you’re on for your mobile device tough luck. I want to use it, I have it installed. I’ve said it IGMP hints. It’s just not written well.

    All that said, if you have an ISP bog standard router and one network that plays nice with it, it definitely works as a keyboard and mouse remote…









  • It comes with a working config.

    Adding applications and rebuilding is generally trivial.

    The problem becomes if you want to use flakes or home manager, which you probably should. The config for those is complicated and poorly documented.

    I don’t know the programming language. I’ve been running it for about a month now. If you’re not doing anything complicated or doing any crazy conditionals or running one config for 27 boxes it’s no different than editing a yaml.

    It took me about 2 days to get Nvidia working properly with offloading that was my hardest task so far.


  • It’s a give and take honestly.

    System-d has better logging. Until you have something that needs to really really log. You can argue that if you have something that’s that dependent on logging it shouldn’t be logging through the console but it’s worked fine for decades. Auto pruning of logs isn’t necessarily ideal. Getting console logs and assist logs as a pain in the ass.

    Same goes for service dependencies we had this sorted it was answered via run levels and naming. It wasn’t necessarily the most elegant solution but it was simple and there was very little to go wrong.

    The tools to manage the services and logs are needlessly complicated. Service start, service stop, service status, service log, service enable, service disable. And I shouldn’t have to reload the Daemon every time I make a change.

    This isn’t to say that it’s all bad. It’s flexible, and for most workflows, it’s very automated and very light touch. The other pruning on the log file says probably saved a lot of downtime, a whole lot of downtime.

    It’s really well suited to desktop.

    Service creation is somewhat easier.

    Dependencies are more flexible than run levels.

    To be honest I wouldn’t go out of my way to run in a non-system distro but I would feel a little sigh of relief if something I was screwing with was still init.d







  • verage moron who thinks they know everything so they

    I had such high hopes when he and Luke started that challenge. If they would have made it, we’d probably have twice the uptake we have now. But because he has to drop out to cli and do stupid crap. He could have run Ubuntu with Unfree and used straight GUI installs and have been in steam in 15 minutes.


  • ore completely bricked Windows installs than Linux. Don’t think I’ve ever managed to completely Bork a Linux install ex Everybody has different experiences.

    I completely shattered my NixOS install by trying to activate Nvidia Prime on my laptop. Of course it was NixOS, so i could roll back from the boot loader. There was the time I used vim to edit /etc/sudoers on a remote VM. that was a joy.

    If you screw up most of your core windows install DISM online cleanup will put most of it back.

    Windows has more guard rails than say Debian or Ubuntu. But to each their own.


  • linearchaos@lemmy.worldtolinuxmemes@lemmy.worldThat's LTT in the bottom
    link
    fedilink
    English
    arrow-up
    40
    arrow-down
    5
    ·
    4 months ago

    Meme’s not wrong and I daily Linux, but how we got here is all that crap on the bottom has a pretty low chance of leaving you bricked and getting back from bricking windows is usually marginally trivial. The same people get lost in Linux, don’t read warnings, do stupid shit without thinking then spend forever trying to muddle through how to fix it. Mr. LTT did it himself.