well my machine is a dedicated xbmc appliance in my living room. nothing else is installed on this system. it's slim and streamlined to my needs. i expect a media appliance to bootup quickly, login my user automatically and i'll do the rest with my remote to enjoy my media collection.Anon-E-moose wrote:What's the problem with having a user log in ,and startx being executed from their profile?hal2050 wrote:hehe too bad.
well i tried qingy and it works. but only when using the manual login method (login screen). when using the autologin feature of qingy sessions don't get registered, it behaves just like using su/sudo/etc.
mingetty does work but opens a "real" shell for the user automatically logged in. not so nice.
there's no place for a big bunch of extra packages which get pulled in by gdm, kdm or slim. well slim isn't as "fat" as gdm/kdm in regards to its deps. but for my taste it's still too much. in my opinion such a task should be accomplishable with onboard tools.
here's list of deps for kdm and gdm on my system, just for the record:
kdm: http://pastebin.com/0dcqZyGY
gdm: http://pastebin.com/UDcFeFRB
not acceptable.
good question. that's what i asked myself. but in my case it's not possible to move away from ck/pk and it's companions. xbmc has two builtin ways to automount devices and handle power tasks (shutdown, reboot, suspend).claudio wrote: This raises an other question: why do I use CK at all for just mounting my USB drive?
1. hal
2. udev -> udisks / upower
as everybody knows hal is deprecated basically. xbmc still supports it but i'm pretty sure it's just a matter of time until it's getting removed. before it's getting removed from xbmc source i guess hal support will be dropped from the gentoo ebuild. there's an open ticket on the bug tracker for removal of hal support. i agree totally with this decission. hal was hell since 2001.
xbmc also does support udisks / upower. that's fine but requires ck. and at this point people who run setups like me are more less stuck in the middle of nowhere when it comes to autologin their user and register with ck.
dm alternatives are:
- slim (might be "too fat" for some of us)
- qingy (seems to be broken in regards to ck and autologin)
- mingetty (opens a shell -> "security")
seems like with ck there's a gap in the market for a console based dm.ssuominen wrote: I'm afraid "time" won't do anything here since an actual login is required for ConsoleKit's pam_ck_connector.so to get used, stuff like utmp/wtmp entries to get written... Otherwise CK wouldn't have any idea it's actually a local login and correctly refuses to authorize. It's by design like this.
maybe i should just download the xbmc livecd or some minimal live distro without a dm to get a clue how these people do it.








