• 10 Posts
  • 264 Comments
Joined 3 years ago
cake
Cake day: February 1st, 2023

help-circle








  • The comment said that people that install systemd based systems and then fight systemd tools are stupid. In that instance a guy is dead set on using netplan and shell scripts on a system with networkd, when using just networkd would have been extremely simple. Maybe in a system without systemd it would have been easier to use netplan, but the guy decided to install systemd and then fight it, and then suggested other people do the same.





  • Honestly, one of the worst parts of the Linux community is people trying to force 30 years old tools in systems built around systemd. If you want to use that old stuff then don’t install the modern replacement, find a different distro built around that ideal instead.

    I remember a post on serverfault or askubuntu about disabling DHCP default gateway but keeping DHCP address assignment on a tap interface, and bring it up at boot, and the accepted answers was “configuring DHCP in networkd/NetworkManager systems is almost impossible, here’s how I did it” and it’s three pages of cobbling together ifconfig and netplan with startup scripts, that work by pure chance.

    Wanna see the actual full networkd configuration for that?

    # /etc/systemd/network/tap0.network
    [Match]
    Name=tap0
    
    [Network]
    DHCP=ipv4
    
    [DHCPv4]
    UseRoutes=false
    

    That’s it, all that the post asked for is handled by six lines. “How do I discover that?” you may ask, because if it’s three lines, but I have to dig for hours before finding it than it’s not that useful. Simple, I go on the systemd documentation for .network files and search for DHCP. And this is a niche use case, the basic usage is readily available on the arch wiki as with anything else. Note, this does nothing for IPv6, and the interface will have IPv6 route configured, but this wasn’t relevant to the post, and my home’s IPv6 layout is “peculiar” so I have omitted it here.




  • edinbruh@feddit.ittolinuxmemes@lemmy.worldwhen IBM owns your system management
    link
    fedilink
    English
    arrow-up
    71
    arrow-down
    1
    ·
    edit-2
    10 days ago

    Hmmm, I’m pretty sure you just need to systemctl disable sshd.socket and then configure it how you like. Don’t trust every “solution” you see online, they are often full of bullshit written by people trying to fit a square peg in a round hole. I bet that kernel parameter thing is something to disable it on the first boot, before you get the chance to configure the thing properly.

    Edit: @thorhop@sopuli.xyz wrote a comment about that option here, go to the thread if you are interested.





  • edinbruh@feddit.ittomemes@lemmy.worldthe cold war
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    18 days ago

    Because a browser doesn’t just needs to keep working, it needs to evolve to adapt to the evolving web. New technologies get developed (webgpu, csp, cors, http3, etc…, some would add AI to the list but I wouldn’t) and browsers need to implement them, and old technologies get improved (faster more secure JavaScript engines, faster document renderers).

    These are all things an actively developed browser engine will have to do, and things that a 2009 fork of Firefox receiving less than 10 commits per month by a single developer won’t achieve without getting them from upstream Firefox. But if you need to rely on upstream Firefox then once again you won’t survive meaningfully without Firefox.

    Or you can just do the hipster and keep on using a 15 year old browser. Maybe use lynx or w3m to cut on the bloat. Or switch to gopher. You do you, it’s not my job to convince you.