2016-01-05 19:55 GMT+01:00, k...@aspodata.se <k...@aspodata.se>: > Teodoro Santoni: >> It's easier to >> * avoid hacks in the login process if your software controls >> everything from the power button to the session; > > I don't understand you. > Don't we already control everything from secondary bootloader to login ? > Or do you want one binary to handle all that ?
I personally don't want it. I think that fragmentation and extreme bikeshedding are what make FOSSies beautiful. You asked and I answered, isn't that what systemd does (embrace everything, force some behaviour devs love and control everything else)? >> * get away with "your OS will die without my software!!!" if nobody >> knows how to authenticate in non-keyboard ways without it. > > I haven't done it the non-keyboard way, so I cannot comment on that. > You could perhaps provide some highlights. I've given examples in the first post: smart card logins, single sign on, permissions granted without group/users or through hardware like TPM. I'm asking if someone use PAMs daily, because I suspect that I can answer "patch any kind of strange permission code away, everywhere" to the "how can I waste my time and work happily with Linux OSes installed on my pc without any trace of systemd code but have cups and other goodies?" question. And was curious about your experience, hence the thread. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng