BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] About to rip out systemd and start over
- Subject: [Discuss] About to rip out systemd and start over
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- Date: Fri, 22 May 2015 11:23:48 +0000
- In-reply-to: <e73579e92c0c4bf5011ec41034fe3209.squirrel@webmail.ci.net>
- References: <e73579e92c0c4bf5011ec41034fe3209.squirrel@webmail.ci.net>
> From: Discuss [mailto:discuss-bounces+blu=nedharvey.com at blu.org] On > Behalf Of Rich Braun > > For the umpteenth time, this morning found myself at the console of a dead > Linux box, unable to bring the system up because of unreconciled or circular > or otherwise out-of-sequence dependencies in systemd. Are you manually creating and editing services or something? I've literally never once run into any problem like this, on any system in my entire history. I don't want to say you're doing something wrong, but that *is* the first suspicion that comes up. Maybe instead of making a generalization about systemd, you could describe what you've changed, and why you did, and what you're trying to accomplish, and maybe somebody will offer some insight on managing the systemd configuration that helps you avoid falling into those pitfalls in the future?
- References:
- [Discuss] About to rip out systemd and start over
- From: richb at pioneer.ci.net (Rich Braun)
- [Discuss] About to rip out systemd and start over
- Prev by Date: [Discuss] [Position-available] BCI Computers Job Posting
- Next by Date: [Discuss] About to rip out systemd and start over
- Previous by thread: [Discuss] About to rip out systemd and start over
- Next by thread: [Discuss] [Position-available] BCI Computers Job Posting
- Index(es):