195
deez nuts (lemmy.world)
top 22 comments
sorted by: hot top controversial new old
[-] jg1i@lemmy.world 5 points 1 year ago

"a popular init system"? It's the main init system now. Look at it. Systemd is the captain now.

You'll have to learn it if you use any mainstream distro. Like at work. It is inevitable.

[-] Sir_Simon_Spamalot@lemmy.world 6 points 1 year ago

It makes my work so much easier than it could've.

Imagine having to tweak sysvinit script at work.

[-] jg1i@lemmy.world 3 points 1 year ago

Yeah, nope I'll pass. Unit files for me please thank you.

[-] corsicanguppy@lemmy.ca 1 points 1 year ago

having to tweak sysvinit script at

Yeah. Trivial. Your point? Are you comparing nfsroot yet?

[-] corsicanguppy@lemmy.ca 1 points 1 year ago

Yes, that's what 'popular' becomes.

Note that it's often labeled as 'popular' and not 'good'.

I'm sick of redhat's internal junk. It's just to sell courses anyway.

[-] syntacticmistake@kbin.social 1 points 1 year ago
[-] cyanarchy@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago)

Yes, popular. Many distros use it and, believe it or not, most people don't care it's there. It works.

Hell yeah brother

[-] reedts@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

If it was only an init system I'd be ok with it. But it isn't...

[-] ozymandias117@lemmy.world 1 points 1 year ago

You need to use its init system (systemd), its logging system (systemd-journald, and can be forwarded to old school syslog), and some dbus implementation.

If that's an unreasonable requirement for your usecase, check out OpenRC

[-] fzacq9td@lemmy.world 0 points 1 year ago

then what would you define it as?

[-] riodoro1@lemmy.world 2 points 1 year ago
[-] SuperIce@lemmy.world 1 points 1 year ago

It's a system daemon that manages way more than an init system, hence the name "systemd".

[-] AppleMango@kbin.social 1 points 1 year ago

The left and right one should be swapped.

[-] darcy@sh.itjust.works 0 points 1 year ago

SOYSTEMD LOL ๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚ (i use systemd)

[-] chronicledmonocle@lemmy.world -1 points 1 year ago

I knew a Arch guy who called it Sys-dumb-d. He refused to run systemd.

I could mostly care less. It's.....fine. I miss upstart and it's simplicity. Kind of wish it had been actually developed to maturity, but here we are with an init system that also wants to do DNS.

[-] TheInsane42@lemmy.world -3 points 1 year ago

It's never been popular by anybody except RedHat, that's how they sell courses end certifications.

Still haven't found a way to start something after networking has finished when it takes a bit to set everything up. (and no, not going to limit vlans, tunnels,...)

It's a technical 'solution' for a marketing problem.

[-] phx@lemmy.world 2 points 1 year ago

Wouldn't you just set "networking" as a dependency on the unit of whatever you need started after?

[-] cowmouse@lemmy.world 2 points 1 year ago
[-] corsicanguppy@lemmy.ca -2 points 1 year ago

I love how fucking lennaert subtly changed that. Who cares that it complicates classic tools.

[-] eltimablo@kbin.social 1 points 1 year ago

Does After= not fit your use case? I was under the impression it does what you're looking for.

this post was submitted on 26 Jun 2023
195 points (98.0% liked)

linuxmemes

20707 readers
1815 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS