Bug#295034: marked as done (xdm: test for value of HEED_DEFAULT_DISPLAY_MANAGER before setting it)
Your message dated Mon, 26 Jun 2006 16:31:33 +0800 with message-id [EMAIL PROTECTED] and subject line closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xdm Severity: wishlist Tags: patch when setting up a diskless terminal with a shared read-only root filesystem, it is very difficult to start a different display manager on each diskless terminal. if /etc/init.d/xdm (and gdm, kdm, wdm) were patched to check that HEED_DEFAULT_DISPLAY_MANAGER is not set before setting it to true, it would be easier to invoke a different display manager on each individual terminal: HEED_DEFAULT_DISPLAY_MANAGER=false /etc/init.d/xdm start the attached patch would allow for this sort of behavior. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) --- etc/init.d/xdm 2004-12-09 06:53:04.0 -0800 +++ etc/init.d/xdm.new 2005-02-12 20:24:08.0 -0800 @@ -6,7 +6,7 @@ # To start xdm even if it is not the default display manager, change # HEED_DEFAULT_DISPLAY_MANAGER to false. -HEED_DEFAULT_DISPLAY_MANAGER=true +test -z $HEED_DEFAULT_DISPLAY_MANAGER HEED_DEFAULT_DISPLAY_MANAGER=true DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager PATH=/bin:/usr/bin:/sbin:/usr/sbin signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Package: xdm Version: 1:1.0.1-1 This bug has been fixed in xdm 1:1.0.1-1 and above. ---End Message---
Bug#295034: marked as done (xdm: test for value of HEED_DEFAULT_DISPLAY_MANAGER before setting it)
Your message dated Mon, 26 Jun 2006 16:31:33 +0800 with message-id [EMAIL PROTECTED] and subject line closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xdm Severity: wishlist Tags: patch when setting up a diskless terminal with a shared read-only root filesystem, it is very difficult to start a different display manager on each diskless terminal. if /etc/init.d/xdm (and gdm, kdm, wdm) were patched to check that HEED_DEFAULT_DISPLAY_MANAGER is not set before setting it to true, it would be easier to invoke a different display manager on each individual terminal: HEED_DEFAULT_DISPLAY_MANAGER=false /etc/init.d/xdm start the attached patch would allow for this sort of behavior. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) --- etc/init.d/xdm 2004-12-09 06:53:04.0 -0800 +++ etc/init.d/xdm.new 2005-02-12 20:24:08.0 -0800 @@ -6,7 +6,7 @@ # To start xdm even if it is not the default display manager, change # HEED_DEFAULT_DISPLAY_MANAGER to false. -HEED_DEFAULT_DISPLAY_MANAGER=true +test -z $HEED_DEFAULT_DISPLAY_MANAGER HEED_DEFAULT_DISPLAY_MANAGER=true DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager PATH=/bin:/usr/bin:/sbin:/usr/sbin signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Package: xdm Version: 1.0.1-1 This bug has been fixed in xdm 1.0.1-1 and above. ---End Message---
