From abo@dsl.dk Tue Dec 17 11:23:52 2013 Received: (at submit) by bugs.x2go.org; 17 Dec 2013 10:23:52 +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,HTML_MESSAGE, T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from eu1sys200aog105.obsmtp.com (eu1sys200aog105.obsmtp.com [207.126.144.119]) by ymir (Postfix) with SMTP id EC1E45DB16 for ; Tue, 17 Dec 2013 11:23:51 +0100 (CET) Received: from mail-ob0-f177.google.com ([209.85.214.177]) (using TLSv1) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKUrAmN7DT5kc4+5vtew5tr/zokJYCFdRL@postini.com; Tue, 17 Dec 2013 10:23:52 UTC Received: by mail-ob0-f177.google.com with SMTP id vb8so5993787obc.8 for ; Tue, 17 Dec 2013 02:23:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dsl.dk; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=ooREQK+nLO3+DKHVjJXLn+ZLMYAyhpLXVPL7oQLxLyY=; b=Gy5dojvMDsEQiIjfoymCgn51FccypCyR90FxxPOTBKoj7LKzgx5uCORnwMJoQy7dVy TqxK9uU0E6yEv6NLJ4WwbL+4alQO7y2CyDVSoQyis553D4KR/O9j7j6Jaz49EsSdfDKK 7ji80oA4oDIZ/uu7let+dQTWOOvT49GLQ6VQs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ooREQK+nLO3+DKHVjJXLn+ZLMYAyhpLXVPL7oQLxLyY=; b=O3zyqilc6AE/0gfRE/hDl9tDOTvj78CS//ntkvR9l6yuwKFZXjuT/nlbv7qwAu6MBY EB+FtpANb1znigChItXbfJDbiMwzirllmh9R1jmPNsxL5m99zUZmnzU+X7MmHiu6jTSN 3GHhhfOoGgCXGtipOlWV+2rtrm1q9iIajRLix9OG1mDDf4hpcF+11tADiD2p1DugjYUV Wbqt3Zy9T/THVOZMfDOYu0b3QoDXfRk3+WknIYaerMBm1zarKznteoWXL/Xf+UmmdVUD AsFu4jNo4M5wdCB8wswU92Azk5ccc6pVBcq+aN5EyirLk5nettoro1572TqBRbwFxg1w KpRA== X-Gm-Message-State: ALoCoQljvMN9KfSX68MeuRDjkbM1oSQj4B9RP2KCxHaA+805eq8DlV2/mLlrlDDmju11bn6SO0gLGtJrZEUMrdXFZgqh3aiHu70SFu53AAPxEZMM7/IM73/8d133qCZxyuemlEUmx9981ygpeCy5oCDK0gqCfpH+W2/ZCAPQCbCF3POrhOs3NBQ= X-Received: by 10.182.135.194 with SMTP id pu2mr15619856obb.38.1387275812091; Tue, 17 Dec 2013 02:23:32 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.135.194 with SMTP id pu2mr15619847obb.38.1387275811864; Tue, 17 Dec 2013 02:23:31 -0800 (PST) Received: by 10.182.115.103 with HTTP; Tue, 17 Dec 2013 02:23:31 -0800 (PST) Date: Tue, 17 Dec 2013 11:23:31 +0100 Message-ID: Subject: x2gothinclient does not install 686 kernel From: Anders Bruun Olsen To: X2go bugs Content-Type: multipart/alternative; boundary=089e0122a6c0f8d6fc04edb8515d --089e0122a6c0f8d6fc04edb8515d Content-Type: text/plain; charset=UTF-8 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. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature) --089e0122a6c0f8d6fc04edb8515d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 f= or linux-image-686 knows that this particular kernel is made for machines s= upporting 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 "wor= ks as intended") with Debian Wheezy, and not really a job for the deve= lopers 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.

--
Anders Bruun Olsen
It-ansvarlig
Det Danske Spro= g- og Litteraturselskab
(Society for Danish Language and Literature)
--089e0122a6c0f8d6fc04edb8515d-- From mike.gabriel@das-netzwerkteam.de Tue Dec 17 12:24:31 2013 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 To: Anders Bruun Olsen , 375@bugs.x2go.org Subject: Re: Bug#375: x2gothinclient does not install 686 kernel References: In-Reply-To: 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-- From stephan.wagner@itos-gmbh.com Tue Dec 17 13:28:17 2013 Received: (at 375) by bugs.x2go.org; 17 Dec 2013 12:28:18 +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,HTML_MESSAGE, URIBL_BLOCKED autolearn=ham version=3.3.2 X-Greylist: delayed 583 seconds by postgrey-1.34 at ymir; Tue, 17 Dec 2013 13:28:17 CET Received: from mail.itos-gmbh.com (mail.itos-gmbh.com [188.40.99.228]) by ymir (Postfix) with ESMTPS id A89985DB16 for <375@bugs.x2go.org>; Tue, 17 Dec 2013 13:28:17 +0100 (CET) Received: from mail.itos-gmbh.com (adsl-89-217-5-40.adslplus.ch [89.217.5.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.itos-gmbh.com (Postfix) with ESMTPSA id 0743D534D1; Tue, 17 Dec 2013 13:18:34 +0100 (CET) From: Stephan Wagner Reply-To: stephan.wagner@itos-gmbh.com Organization: ITos GmbH To: Mike Gabriel , 375@bugs.x2go.org, x2go-dev@lists.berlios.de Subject: Re: [X2Go-Dev] Bug#375: x2gothinclient does not install 686 kernel Date: Tue, 17 Dec 2013 13:18:31 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) References: <20131217112430.Horde.LR9FJpJqwhCoWPI1HhdULA7@mail.das-netzwerkteam.de> In-Reply-To: <20131217112430.Horde.LR9FJpJqwhCoWPI1HhdULA7@mail.das-netzwerkteam.de> X-KMail-Markup: true MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_XEEsShL4DytrHjy" Content-Transfer-Encoding: 7bit Message-Id: <201312171318.31724.stephan.wagner@itos-gmbh.com> --Boundary-01=_XEEsShL4DytrHjy Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hallo Mike I prefer 686-Kernel on a 32bit System, as it supports multiple cores. Stephan On Tuesday, 17. December 2013, Mike Gabriel wrote: > 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... -- __________________________________________________ Dr. Stephan Wagner ITos GmbH Bitzi-Bendel 2555 9642 Ebnat-Kappel Tel: +41 (0)71 990 05 94 mailto:swagner@itos-gmbh.com http://www.itos-gmbh.com -------------------------------------------------- --Boundary-01=_XEEsShL4DytrHjy Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit

Hallo Mike

 

I prefer 686-Kernel on a 32bit System, as it supports multiple cores.

 

Stephan

 

 

On Tuesday, 17. December 2013, Mike Gabriel wrote:

> 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...

 

 

 

--

__________________________________________________

Dr. Stephan Wagner

ITos GmbH

Bitzi-Bendel 2555

9642 Ebnat-Kappel

Tel: +41 (0)71 990 05 94

mailto:swagner@itos-gmbh.com

http://www.itos-gmbh.com

--------------------------------------------------

 

--Boundary-01=_XEEsShL4DytrHjy-- From abo@dsl.dk Tue Dec 17 14:32:37 2013 Received: (at 375) by bugs.x2go.org; 17 Dec 2013 13:32:38 +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,HTML_MESSAGE, T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2 X-Greylist: delayed 358 seconds by postgrey-1.34 at ymir; Tue, 17 Dec 2013 14:32:36 CET Received: from eu1sys200aog122.obsmtp.com (eu1sys200aog122.obsmtp.com [207.126.144.153]) by ymir (Postfix) with SMTP id 8E7AC5DB16 for <375@bugs.x2go.org>; Tue, 17 Dec 2013 14:32:36 +0100 (CET) Received: from mail-oa0-f41.google.com ([209.85.219.41]) (using TLSv1) by eu1sys200aob122.postini.com ([207.126.147.11]) with SMTP ID DSNKUrBSdNshCU42BISrZqsUy3gzMwihpr2q@postini.com; Tue, 17 Dec 2013 13:32:36 UTC Received: by mail-oa0-f41.google.com with SMTP id j17so6552847oag.14 for <375@bugs.x2go.org>; Tue, 17 Dec 2013 05:32:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dsl.dk; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pqBy/hyt9276ZOT3XcIBAK/fmubMlvaTX7wUl1qf4Uw=; b=A8ZwmTquEUvy4jTQJSqcF4U6amAktuLA18rGSCNWo5Dfv0wIE4EfN1zGacNwpilAdp PQyVCozv3iVi1AZRz6kZgenpT6SoUDf1wTKnyLf6WkkJWr/mntW3+vl+/5tXe6Wihpfm Y3wmSg1/N6WYyeBE7hVm486XSfaBNvxc1esQQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pqBy/hyt9276ZOT3XcIBAK/fmubMlvaTX7wUl1qf4Uw=; b=LmBqznMaqOHqgx3ON9WgRvirPGTp+rOb5HmzsKB/Yogrm/wmIKUnqGZSmlX1ee3t52 v7wzg4TBvfrU1vsJG0xKUSSlpCCeu5tw87A7Hwk22SS1twuxYsiOVLvWkIf5VL+L4ZMC 5TJecslk/TgB7xSwH/Vj4zWzNt/rdj524PSvvmNqdVGZd8jUY48V1wGgLtHZtYthOG/g pQJWYfSJN5zO7QwInBUFyB4JB59XL/itdMeZXfXq7fw5ngVw7gIoq6UU3AzuH5K+N79z fgkDsgEbhUs+ZVlLCR6Yx0XQ5+4CPW7B0D98+MtrheT9vdQTUQcSaRhaVPe3FEK7b8y+ U9TQ== X-Received: by 10.182.43.161 with SMTP id x1mr15999921obl.5.1387286797492; Tue, 17 Dec 2013 05:26:37 -0800 (PST) X-Gm-Message-State: ALoCoQlJmAIgVp05K8JYc37lYpKYBNkQGTXBfd1ydBUCvu9yPQdfqpbSEYjOnnc1C8kGfcy+KoM7WP6y7q9QoTksxSPykUCIt/W4IeTOndj6bIhDjjctPBXTnRIU5UuxtNSChI0Cy09IuLaCRBq57UggfoNCZzRnTQ== MIME-Version: 1.0 X-Received: by 10.182.43.161 with SMTP id x1mr15999883obl.5.1387286797142; Tue, 17 Dec 2013 05:26:37 -0800 (PST) Received: by 10.182.115.103 with HTTP; Tue, 17 Dec 2013 05:26:37 -0800 (PST) In-Reply-To: <201312171318.31724.stephan.wagner@itos-gmbh.com> References: <20131217112430.Horde.LR9FJpJqwhCoWPI1HhdULA7@mail.das-netzwerkteam.de> <201312171318.31724.stephan.wagner@itos-gmbh.com> Date: Tue, 17 Dec 2013 14:26:37 +0100 Message-ID: Subject: Re: [X2Go-Dev] Bug#375: Bug#375: x2gothinclient does not install 686 kernel From: Anders Bruun Olsen To: stephan.wagner@itos-gmbh.com, 375@bugs.x2go.org, x2go-dev Cc: Mike Gabriel Content-Type: multipart/alternative; boundary=001a11c30ce2bee17204edbae0ff --001a11c30ce2bee17204edbae0ff Content-Type: text/plain; charset=UTF-8 Hi Mike, As the machines used as thin clients grow ever more powerful, at the same price and energy usage, the features available also keeps expanding. I have recently bought a Shuttle machine, that is physically smaller than my current thin clients, comes with the Atom D2550 (one of the newer Atom CPUs) which has two cores. I also put in 4gb of RAM, since it was almost the same price as a 2gb RAM module. Like Stephan wrote, without 686 (and in this case PAE) that system wouldn't be properly utilized. Even if it is somewhat overpowered for a thin client. As a side note, I am also testing out the Intel NUC DCCP847DYE which is a dual core celeron, but it is so small and (like the Shuttle) completely silent, but does not offer sound out, other than over HDMI. Anyways, it is a matter of properly utilizing the hardware. It probably isn't that big a deal, but it would be nice to have. 2013/12/17 Stephan Wagner > Hallo Mike > > > > I prefer 686-Kernel on a 32bit System, as it supports multiple cores. > > > > Stephan > > > > > > On Tuesday, 17. December 2013, Mike Gabriel wrote: > > > 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... > > > > > > > > -- > > __________________________________________________ > > Dr. Stephan Wagner > > ITos GmbH > > Bitzi-Bendel 2555 > > 9642 Ebnat-Kappel > > Tel: +41 (0)71 990 05 94 > > mailto:swagner@itos-gmbh.com > > http://www.itos-gmbh.com > > -------------------------------------------------- > > > > _______________________________________________ > X2Go-Dev mailing list > X2Go-Dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/x2go-dev > -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature) --001a11c30ce2bee17204edbae0ff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Mike,

As the machines used as thin c= lients grow ever more powerful, at the same price and energy usage, the fea= tures available also keeps expanding. I have recently bought a Shuttle mach= ine, that is physically smaller than my current thin clients, comes with th= e Atom D2550 (one of the newer Atom CPUs) which has two cores. I also put i= n 4gb of RAM, since it was almost the same price as a 2gb RAM module. Like = Stephan wrote, without 686 (and in this case PAE) that system wouldn't = be properly utilized. Even if it is somewhat overpowered for a thin client.= As a side note, I am also testing out the Intel NUC DCCP847DYE=C2=A0which is a dual core celeron, but it is= so small and (like the Shuttle) completely silent, but does not offer soun= d out, other than over HDMI.
Anyways, it is a matter of properly utilizing the hardware. It probabl= y isn't that big a deal, but it would be nice to have.


2013/12/17 Stephan= Wagner <stephan.wagner@itos-gmbh.com>

Hallo Mike

=C2=A0

I prefer 686-Kernel on a 32bit System, as it supports m= ultiple cores.

=C2=A0

Stephan

=C2=A0

=C2=A0

On Tuesday, 17. December 2013, Mike Gabriel wrote:

> Control: tag -1 moreinfo

>

> Hi Anders,

>

> On Di 17 Dez 2013 11:23:31 CET, Anders Bruun Olse= n 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 x2goth= inclient_create, only the 486

> > kernel gets installed. I can use x2gothinclie= nt_shell and use apt-get to

> > install linux-image-686, to get the 686 kerne= l installed. But upon doing

> > so, the reason for it not being auto installe= d is apparent: 64-bit machines

> > don't support PAE (not needed), and the d= eb 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 op= timal.

> > I realize this is a problem (in this niche ca= se, it probably "works as

> > intended") with Debian Wheezy, and not r= eally a job for the developers of

> > x2go, but since I am running into this proble= m 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 ker= nel in the first

> place. The reason I removed 686 support from the X= 2Go TCE is that it

>

> (a) did not bring any feelable improvements whi= le my TCEs ran under

> Debian squeeze _and_

> (b) did not work fluently if the PXE server mac= hine is a amd64 system

>

> Please enlight me, why 686 would be a sensible ker= nel alternative to

> use here...

=C2=A0

=C2=A0

=C2=A0

--

__________________________________________________

Dr. Stephan Wagner

ITos GmbH

Bitzi-Bendel 2555

9642 Ebnat-Kappel

Tel: +41 (0)71 990 05 94

mailto:swagner@itos-gmbh.com

= http://www.itos-gmbh.com

--------------------------------------------------

=C2=A0


___________________________________= ____________
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de<= br> https://lists.berlios.de/mailman/listinfo/x2go-dev



--
Anders Bruun Olsen
I= t-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and = Literature)
--001a11c30ce2bee17204edbae0ff--