KillingSpark / KillingSpark/HowLogindWorks
Strategy towards specification of Linux session layer (and Unix)
- Dominant language
- No language data
- Stars
- 35
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hey @KillingSpark.
1. [seatd](https://sr.ht/~kennylevinsen/seatd/) is soon getting used by Sway for the seat abstraction. I cant find the commit and issue for now. :/
2. PAM manages the user authentication ie [Linux PAM](https://en.wikipedia.org/wiki/Linux_PAM) and is invoked by systemd as module.
3. Do you know how much complexity in LOC session manager implementations have?
4. So as far as I undestand systemd's main purpose is tracking program status (and killing them on misbehavior) as explained in [watching for exiting sessions](https://github.com/KillingSpark/HowLogindWorks#watching-for-exiting-sessions). Or where am I wrong on this?
The manipulation of stuff is given by Linux API and should be separate-able from systemd.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked “watching for exiting sessions” section in HowLogindWorks, then review the references to seatd and Linux PAM in the issue. Done would mean an agreed specification strategy that clarifies the session manager’s responsibilities and what should remain separate from systemd.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100