Bug#491300: default desktop selection in win32-loader.ini
Hi,
Any chance this fix can make it to lenny? The patch is trivial, and the
problem is severely disruptive for KDE/Xfce installs that use win32-loader.
Thanks
On Fri, Jul 18, 2008 at 10:41:33AM +0000, Robert Millan wrote:
> Package: debian-cd
> Version: HEAD
> Severity: normal
> Tags: patch
>
> Currently, the KDE and Xfce versions of Debian CD weekly builds still
> try to install GNOME when booted via win32-loader, because the KERNEL_PARAMS
> variable has no effect (as it's only used by syslinux).
>
> win32-loader has this setting built-in in its config file, win32-loader.ini.
> With this patch, CD builders can select the desired default desktop by
> exporting the DESKTOP variable.
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.18-6-amd64 (SMP w/2 CPU cores)
> Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Index: tools/boot/lenny/boot-x86
> ===================================================================
> --- tools/boot/lenny/boot-x86 (revision 1636)
> +++ tools/boot/lenny/boot-x86 (working copy)
> @@ -203,6 +203,9 @@
>
> if [ -e boot$N/win32-loader.ini ] ; then
> sed -i "s|install/|$INSTALLDIR/|" boot$N/win32-loader.ini
> + if [ "${DESKTOP}" ] ; then
> + sed -i "s|^\(default_desktop\)=.*|\1=${DESKTOP}|" boot$N/win32-loader.ini
> + fi
> fi
>
> cp -f $BASEDIR/data/$DI_CODENAME/isolinux.bin boot$N/$ISOLINUXDIR/
> Index: CONF.sh
> ===================================================================
> --- CONF.sh (revision 1636)
> +++ CONF.sh (working copy)
> @@ -300,6 +300,9 @@
> # supported for all architectures.
> #export KERNEL_PARAMS="DEBCONF_PRIORITY=critical"
>
> +# Default desktop (currently only used by win32-loader)
> +#export DESKTOP=kde
> +
> # If set, limits the number of binary CDs to produce.
> #export MAXCDS=1
>
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
Reply to: