Hi. On Wed, 8 Oct 2014 22:36:46 -0400 Steve Litt <sl...@troubleshooters.com> wrote:
> If what you did works for everybody when Jessie goes stable, you've > just singlehandedly ended this whole argument. That's a short-term solution at best. Because of: 1) Jessie isn't stable yet. Moreover, it's not even in freeze. Hence, if it works now - nobody will guarantee it'll work tomorrow. 2) There are certain desktop environments that basically require that-pid1-process. And one of those desktop environments is set as a default one currently at d-i. Hence, such solution will require one to stop using certain DEs (no big loss in case of GNOME3, IMO, but still). 3) There's policykit issue, which was helpfully outlined by OP. This privilege escalation suite crept into far too many GUI tools, including XFCE. And currently it's *conveniently* broken if one does not use that-pid1-process. So, if one is willing to do all it takes to remove said-pid1-process from the typical server installation - it's doable. But from the desktop one - it's much harder. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141009191232.a78ab132d4df2d95b1ade...@gmail.com
