Colin Percival schrieb: > Is there any reason why kdm is traditionally started via > /etc/ttys (as in http://freebsd.kde.org/faq.php#q11), > rather than by an rc.d script? With a perfectly generic > kdm.sh script in /usr/local/etc/rc.d/ and kdm_enable="YES" > in /etc/rc.conf, everything seems to work properly, and > this fits far better with the traditional FreeBSD ports > startup mechanisms.
While this may be true, starting kdm via init fits far better with the
traditional BSD way of starting display managers. As long as an rc.d
script does not offer any sort of advantage over that (with either
ttys/rc.conf you have to open a file in an editor and edit one line,
moving a display manager up the rcorder makes little sense), POLA wins.
Jose M Rodriguez suggested a while ago to adopt NetBSD's mechanism for
starting up display managers - they are using a generic base-system
supplied rc-script which runs "/usr/X11R6/bin/${name}".
Adopting their script verbatim probably isn't a very good idea (it still
has xdm's configuration file as required_files, too), the concept of
having just one rc.conf variable for display manager=yes|no and another
variable that determines which display manager gets run on the other
hand might be worthwhile to pursue.
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
