From unknown Sat Apr 18 09:11:13 2026
X-Loop: owner@bugs.x2go.org
Subject: Bug#375: x2gothinclient does not install 686 kernel
Reply-To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, 375@bugs.x2go.org
Resent-From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: owner@bugs.x2go.org
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 17 Dec 2013 11:33:01 +0000
Resent-Message-ID: <handler.375.B375.138727947217675@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 375
X-X2Go-PR-Package: x2gothinclientmanagement
X-X2Go-PR-Keywords: 
Received: via spool by 375-submit@bugs.x2go.org id=B375.138727947217675
          (code B ref 375); Tue, 17 Dec 2013 11:33:01 +0000
Received: (at 375) by bugs.x2go.org; 17 Dec 2013 11:24:32 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,URIBL_BLOCKED
	autolearn=ham version=3.3.2
Received: from freya.das-netzwerkteam.de (freya.das-netzwerkteam.de [88.198.48.199])
	by ymir (Postfix) with ESMTPS id 9B6E25DB16
	for <375@bugs.x2go.org>; Tue, 17 Dec 2013 12:24:31 +0100 (CET)
Received: from grimnir.das-netzwerkteam.de (grimnir.das-netzwerkteam.de [78.46.204.98])
	by freya.das-netzwerkteam.de (Postfix) with ESMTPS id 5C699CF0;
	Tue, 17 Dec 2013 12:24:31 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTP id 4A58A3C04E;
	Tue, 17 Dec 2013 12:24:31 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at grimnir.das-netzwerkteam.de
Received: from grimnir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (grimnir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XeifF0wPXELQ; Tue, 17 Dec 2013 12:24:31 +0100 (CET)
Received: from grimnir.das-netzwerkteam.de (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTPSA id 1D40E3C04C;
	Tue, 17 Dec 2013 12:24:31 +0100 (CET)
Received: from nocatv2.tng.de (nocatv2.tng.de [213.178.75.58]) by
 mail.das-netzwerkteam.de (Horde Framework) with HTTP; Tue, 17 Dec 2013
 11:24:30 +0000
Date: Tue, 17 Dec 2013 11:24:30 +0000
Message-ID: <20131217112430.Horde.LR9FJpJqwhCoWPI1HhdULA7@mail.das-netzwerkteam.de>
From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
To: Anders Bruun Olsen <abo@dsl.dk>, 375@bugs.x2go.org
References: <CAFJm-UPbmJ-SqUSaE+VTOzsXR38pwoVCjbFXsPfhepWNXM3uBg@mail.gmail.com>
In-Reply-To: <CAFJm-UPbmJ-SqUSaE+VTOzsXR38pwoVCjbFXsPfhepWNXM3uBg@mail.gmail.com>
User-Agent: Internet Messaging Program (IMP) H5 (6.1.4)
Accept-Language: en,de
Organization: DAS-NETZWERKTEAM
X-Originating-IP: 213.178.75.58
X-Remote-Browser: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101
 Firefox/23.0 Iceweasel/23.0
Content-Type: multipart/signed; boundary="=_xm-01GpAVHfLveVUETfQSA5";
 protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0

This message is in MIME format and has been PGP signed.

--=_xm-01GpAVHfLveVUETfQSA5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
Content-Disposition: inline

Control: tag -1 moreinfo

Hi Anders,

On  Di 17 Dez 2013 11:23:31 CET, Anders Bruun Olsen wrote:

> Package: x2gothinclientmanagement
> Version: 1.1.0.1
>
> I run my tftp/nfs server for my thin clients, on a 64-bit machine (a VM).
> When I create a thinclient chroot with x2gothinclient_create, only the 486
> kernel gets installed. I can use x2gothinclient_shell and use apt-get to
> install linux-image-686, to get the 686 kernel installed. But upon doing
> so, the reason for it not being auto installed is apparent: 64-bit machines
> don't support PAE (not needed), and the deb package for linux-image-686
> knows that this particular kernel is made for machines supporting PAE. I
> can just say yes to the warnings, and I even though I end up with an error,
> the kernel does get installed. This is not optimal.
> I realize this is a problem (in this niche case, it probably "works as
> intended") with Debian Wheezy, and not really a job for the developers of
> x2go, but since I am running into this problem when using x2go, I am
> reporting the problem here, and hopefully it will be sent upstream, if that
> is desirable.

What is your reason for wanting to use the 686 kernel in the first  
place. The reason I removed 686 support from the X2Go TCE is that it

   (a) did not bring any feelable improvements while my TCEs ran under  
Debian squeeze _and_
   (b) did not work fluently if the PXE server machine is a amd64 system

Please enlight me, why 686 would be a sensible kernel alternative to  
use here...

Greets,
Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

--=_xm-01GpAVHfLveVUETfQSA5
Content-Type: application/pgp-signature
Content-Description: Digitale PGP-Signatur
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAABAgAGBQJSsDRuAAoJEJr0azAldxsxMzQP/2LL3qWB1jGbPR03+KPaGsjo
MlG40cqxdcYn4tLPPBsr80y/g8YEKa4YGl4Dp61zVLOt9++HynG2oK6OOdoy1Cha
3RdoCW9U/M7TKr20Q2qi+/hWGGbeLpmSy63yI3tY8BStWIF3j//WSQrhBthV+Epu
2maIvNw1O2wSQtsKclH4I30cuYi4BWpB73p+FG1Vd+UuIPNlIlRjw9WsQbRN9Ion
DMbHmSsM2jDKZWpJnaoIPz3Ivkzc8frejYRyZMAX68lPdPUKn3f/FMhU8McFqBw9
WB8R9gCYA0KUcltWfIzPug3yRMWliCdVqTMptA/KvVTRasuTlwY7ThVnX4YnYEJd
n0cZzc51Ag9G5pB/nnzIPosV5A2PJTtZwG/N08pp1WddUp8HkDlednoQVfAKbIE+
nUftleoWfBF7S6j6rD8u7G+cEtx0sPC1X7PsNzHmkdVP+Bnc/W88efLLVhmVaO1+
x9Y1sWvyJYXONwOZl5/Py3RD4pZPnRNAWKvqo5jS5NhEnFMo3IKmJILJnurJzZDO
Ccg3TGXbVivk4PDb8/kXAA/xQ63XpB6B8qKU+SsHFXSWgzCHM36QxRjU9fkLtX6R
2IRy8I8OMZ59uYicKUk6Uhp5ypP+h1dLlqemmGbcssLpdjoc46w88QXe3QGAOgE8
RRP4PRO5pm44kGmkhSyd
=YxP8
-----END PGP SIGNATURE-----

--=_xm-01GpAVHfLveVUETfQSA5--
