Quoting August Karlstrom (fusionf...@gmail.com): > On 2015-04-14 17:10, Patrick Bartek wrote: > >On Tue, 14 Apr 2015, August Karlstrom wrote: > >>What advantages do you see with adding your own udev rule compared > >>to simply starting a ConsoleKit session? > >> > >>exec ck-launch-session dbus-launch <your-wm> > >> > >>instead of > >> > >>exec <your-wm> > > > >None really, except to keep system overhead as small as possible. > [...] > >I wanted the smallest, lightest install of Wheezy 64-bit I could get. > >I started with a basic terminal system and added the rest piece by > >piece. > > That's what I do too. I have a script that installs a few packages > and configurations on top of a basic Debian server installation. > > >So, I just don't run (or have installed) a lot of "support" stuff > >that normal "desktop" systems do. I even boot to a terminal where I > >login, then manually start X and Openbox with startx. > > I agree, for me a display manager is one of those unnecessary > features. Since I almost always want to use a GUI, however, my > ~/.profile ends with > > #start an X session when logging in on the first virtual console > if [ "$(tty)" = /dev/tty1 ] && [ -z "$DISPLAY" ]; then > exec startx > ~/.xsession-errors 2>&1 > fi > > >Writing my own udev rules was in keeping with that minimalism. > > I tried to do that myselft but I never got it working. That's why I had > to resort to ck-launch-session.
I, too, boot to a VC and run startx whereupon .xsession runs fvwm and opens a bunch of xterms (using xtoolwait from squeeze to serialise them). But I don't understand what starting a ConsoleKit session does. Will I see something different on the screen? I looked at http://unix.stackexchange.com/questions/5220/what-are-consolekit-and-policykit-how-do-they-work but don't understand it. If several users are logged in, does each user run on the same Xserver? Do their sessions keep running while one user is actively using their own session? What are the resource implications? This little laptop is already running much more slowly with jessie/systemd. That page has a link to http://www.freedesktop.org/software/ConsoleKit/doc/ConsoleKit.html which is one of those pages that looks as if it's written for a computer science course. The first page also says that ConsoleKit has been largely replaced by systemd-logind. Well, I have that and it appears to be running: $ dpkg -S systemd-logind systemd: /usr/share/man/man8/systemd-logind.8.gz systemd: /lib/systemd/system/multi-user.target.wants/systemd-logind.service systemd: /lib/systemd/systemd-logind systemd: /lib/systemd/system/systemd-logind.service systemd: /lib/systemd/systemd-logind-launch systemd: /usr/share/man/man8/systemd-logind.service.8.gz $ loginctl list-seats | tee SEAT seat0 1 seats listed. $ man systemd-logind points me to http://www.freedesktop.org/wiki/Software/systemd/multiseat/ which makes me none the wiser. The "Uses" section assumes I am writing system software, and the very last sentence on the page implies I'm running a DM. Neither of these is true. So when you say you resorted to simply starting a ck-launch-session, how did that make up for not being able to get udev rules to work? Cheers, David. -- 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/20150416043704.gb4...@alum.home
