Skip Navigation

!ozoned@lemmy.world
!ozoned@lemmy.world @ ozoned @beehaw.org
Posts
13
Comments
74
Joined
2 yr. ago

  • The Jake Paul giving away $5,000 to someone that boosts his message is just disgusting. Those people see a CELEBRITY just oh so generously giving away money! YAY! I see someone in a position of power saying "DANCE MONKIES" for what's peanuts to him and helps his celebrity even more and that's fucking disgusting.

  • As an end user, unless you're running a server, then no you shouldn't have to mess with any of it.

    If you're running a server or a sysadmin you absolutely 100% should be paying attention. Almost every single vendor I've seen selling their applications only have initscripts. Which then cause issues. I've gone to the vendors and told them and they've said go to Red Hat. Well Red Hat doesn't support that vendor's init scripts.

    Not naming an application, but it was from a BIG BLUE company and they said their only instructions are to call their script from the user. But it won't remain running if you do that because systemd will close out the slice when the user logs out. SO it's obvious they haven't tried what they're suggesting.

    And I'm not attempting to state that systemd is impressive in any way. systemd basically took what had been building over 40 years of init scripting and threw it out the window and said our way is better. I don't think it is. I'm just saying, with a directive based unit file it'll be simpler to parse than a bash script.

  • Ok, so I have a very unique background in systemd. I worked at Red Hat supporting it basically as the primary support and I've worked with the developers of systemd at Red Hat directly. I no longer work there.

    So first off, it's "systemd" all lower case. I don't care, but for some reason Lennart Pottering (creator) does.

    systemd was a MASSIVE change. And Red Hat did a TERRIBLE job relaying it. To the point where I'm still trying to get my company to understand that it can NOT be treated like the old init systems. You can NOT just drop an init script in place and walk away and hope it works. Because a LOT of times it doesn't. Due to forks, switch users, etc.

    systemd is NOT an init system. RHEL 5 and older had sysvinit as it's init systemd. RHEL 6 had UpStart as it's init system and looked exactly like sysvinit that no one even noticed. systemd again is NOT an init system. Init system is 1 part of systemd. systemd does a lot of cool things. It bundles applications together, it manages those applications and can restart them or kill children, it can do resource constraints, it separates out users from the system, and lots more.

    Because it is not an init system there is a LOT LOT LOT of bad recommendations out on the internet where someone has X problem and person suggests Y and IT WORKS! ... except it doesn't REALLY work as far as systemd is concerned and you'll hit other issues or your application takes longer to start or stop and people just blame systemd.

    It is systemd's fault that it has done an ATROCIOUS job of helping people adapt. It's a great example of RTFM. systemd's man pages are INCREDIBLE and extensive, but when you drop so much knowledge it becomes more difficult to find what you want/need. systemd.index and systemd.directives are your best bet.

    So systemd does a lot of amazing things that sysvinit never attempted to do. It's never attempted to explain anything it expects everyone just learn magically. it's INCREDIBLY complex, but once you understand it's basics you can more easily get an application running, but as soon as there's a problem it'll just break your brain.

    To give you an example, sshd's old init script is like 250 lines of bash. systemd's unit file comparative is like 12. Because systemd handles a LOT of what you manually had to handle before. BUT to get to that 12 you literally have to learn EVERYTHING new.

    There is no "is it good or bad" here really imo. It's a completely different fundamental design. Red Hat made it for themselves. Other distros picked it up. It can be argued that lots of folks followed Debian and Debian had a few Red Hat board members that were pushing it. Whether they pushed it of their own accord or because they were with Red Hat I don't have a clue.

    What I can say is at my current company they're suffering from a LOT of systemd issues and they don't even realize it. I've been working with Red Hat to try to get Insights to alert people to the failures and we're making progress.

    To see if you have issues just to start run the two following commands:

     
        ~~~
    # systemctl list-units --failed
    # systemd-cgls
    ~~~
      

    If you have any units that are failed, investigate those. If you don't need them, disable them. As for the systemd-cgls this shows HOW systemd is grouping things. ANY application that runs as a service (or daemon or application or runs in the background or however you wanna say it) should be under system.slice. ONLY humans logging into the system (meat bags NOT applications switching to users) should be in user.slice. A LOT of times what happens is an old init script is dropped in place, they start it, it has a switch user and systemd assumes it's a user and puts it into user.slice. systemd does NOT treat anything in user.slice the same as in system.slice and this WILL eventually cause problems.

    So again, is it good or bad? Eh. It does a lot of cool things, but they did a MASSIVE disservice to ALL of us by just expecting to relearn absolutely EVERYTHING.

  • Outside of Firefox, and very niche browsers, every other browser is built on Chromium. Edge, Opera, Chrome, etc. They all just add in their own customizations and things. You have to go look directly for Chromium, which the vast majority of the world doesn't know exist. That's the only reason why.

  • They gonna include my perspective that Google has helped foment discord in society and has helped strip away any type of privacy we had online while attempting to turn us into mindless addicted drones that just click and buy so they can make another cent?

  • WHOA! SLOW DOWN with throwing out the mystical text! You wanna summon a demon right here?

  • Black background with GREEN text is the ONLY way you HEATHEN! We are now enemies! And we shall settle this like gentlemen!

    TO THE GRID!

    😁

  • Nothing stopping Vimeo from plumbing in ActivityPun amd joining the Fediverse. It's open and the only reason no one does is because the data is valuable and they don't want to share and play nice.

    These walled gardens were not how the internet was imagined.

  • Understandable. But it's the chicken and egg problem. Creators don't want to create content, because there's no consumers. Consumers don't want to sign up, because there's no creators.

    So are you the chicken or the egg? :-D

    If you're on one you don't like anymore you could always change instances and watch videos there. If you're worried about losing comments, well you can comment from other Fediverse servers such as Mastodon or GoToSocial and they show up on the page for the video. :-)

  • I use GoToSocial with Sempahore for my microblogging (alternative to Mastodon).

    Also Owncast as an alternative to Twitch.

    And then I watch tilvids.com and other Peertube instances for videos.

    And of course Lemmy. :-D

    Oh and then there's Funkwhale for audio.

    It's all in different states of usability, depending on the communities involved.

    • Jellyfin - Media streaming type app - basically use it for movies/shows and pictures.
    • Joplin - Note taking app
    • Syncthing - Sync for phones to PC for backing up pictures
    • Miniflux - RSS reader
    • Minetest - FOSS Minecraft voxel engine
    • Veloren - FOSS Cubeworld game written in Rust
    • GoToSocial - Microblogging server - aka Twitter/Mastodon
    • Semaphore - Frontend for GoToSocial
    • SearXNG - Search engine
    • Conduit - Matrix server - chat
    • Libremdb - IMBD frontend
    • Invidious - Youtube frontend
    • Nitter - Twitter frontend
    • Libreddit - Reddit frontend
    • Rimgo - Imgur frontend
    • Proxitok - TikTok frontend

    Failed to get working:

    • Mobilizon - FB groups type alternative
    • Peertube - YT alternative on the Fediverse
    • Lemmy - Tried for a day and just couldn't get it working. Found out there are issues with Rocky Linux and Lemmy that broke about two months ago but no further work was done it. I'll try again someday.
  • Gaming on Linux has grown leaps and bounds and it's only getting better. Game Pass Ultimate though, I'm guessing you're gonna have a rough time. That's built for Window's ecosystem. So more than likely that's going to be a very sore point. The streaming Game Pass can and does work on Linux, but if you're against that then Linux might not be for you.

    Steam has gotten to the point on Linux where it's basically just install and run, as long as you have compatibility for all games turned on. Very very very few games haven't worked for me or even require little tinkering anymore. That being say I pretty much really only play Indie games.

  • That's terrible ... show me where so I never go there ...

    On a more serious note, if you're going to the federated timeline, you can get all kinds of unwanted things. It's usually best to search interests by hashtag and build out your community of folks you follow that way. Also most platforms allow you to block stuff market as #nsfw but that's completely on the person to do the right thing. Which in reality, sadly, you should never depend on someone else.

    I personally run my own GoToSocial, so I can defederate with folks I don't want and have more control over what I see. More work for me, and GoToSocial isn't fully ready for primetime, but that's always an option.

    The Fediverse is still in it's infancy, so it's gonna have some growing pains, but I'm hoping it continues to grow and things like you're suggesting become an after thought in the future.

  • Currently reading "Brave New World", Aldous Huxley. Next up Isaac Asimov's Foundation.