KillingSpark / KillingSpark/rustysd

System to use "export service names" for e.g. separate mount management

Open
#50 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
579
Forks
19
PR merge metrics
No merged PRs in 30d

Description

In systemd, I like how I can make services dependent on mounts and networking.

With rustysd, I don't want a bloated PID1 so could there be a generic system to "export service names" so separate daemons can implement the networking, device and mount management for example? Without using `rsdctl start network-online.target`?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading rustysd's existing service dependency handling and the rsdctl target flow. Compare the requested exported service names with systemd's mount and networking dependencies. Done means the issue has a defined generic mechanism for separate daemons to provide service names without requiring rsdctl commands or a bloated PID1.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.