Re: Remote Desktop to Display :0

2011-10-17 Thread Tom Goren
You mentioned FreeNX but from my experience the proprietary version is still light years ahead (http://www.nomachine.com/). It will definitely serve actual desktop sessions as well. Very low hassle to configure and should work out of the box. Tom 2011/10/17 Guy Tetruashvyly guy@gmail.com

Re: Remote Desktop to Display :0

2011-10-17 Thread Guy Tetruashvyly
On 10/17/2011 12:21 AM, Tom Goren wrote You mentioned FreeNX but from my experience the proprietary version is still light years ahead (http://www.nomachine.com/). It will definitely serve actual desktop sessions as well. Very low

Re: Remote Desktop to Display :0

2011-10-17 Thread Tom Goren
They have a 'free' edition: http://www.nomachine.com/select-package.php?os=linuxid=1 On Mon, Oct 17, 2011 at 8:29 AM, Guy Tetruashvyly guy@gmail.com wrote: ** On 10/17/2011 12:21 AM, Tom Goren wrote You mentioned FreeNX but from my experience the proprietary version is still light

Re: Remote Desktop to Display :0

2011-10-17 Thread Guy Tetruashvyly
On 10/17/2011 01:16 AM, Tom Goren wrote : They have a 'free' edition: http://www.nomachine.com/select-package.php?os=linuxid=1 That is true, but the free version will act as a terminal server , rather then

Newer gcc swallow version control keywords

2011-10-17 Thread Oleg Goldshmidt
Hi, I have a gcc-related question. Problematic platform is Fedora 15 with gcc 4.6.1, as well as Fedora 14 with gcc 4.5.1. I am used to keeping RCS/CVS/SVN keywords (e.g., $Id$) in all my code. In the case of C/C++ this normally amounts to static const char foo_src_id[] = $Id$; in the source

Re: Remote Desktop to Display :0

2011-10-17 Thread Noam Meltzer
2011/10/17 Guy Tetruashvyly guy@gmail.com ** On 10/17/2011 01:16 AM, Tom Goren wrote : They have a 'free' edition: http://www.nomachine.com/select-package.php?os=linuxid=1 That is true, but the free version will act as a terminal server , rather then presenting you your real

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Baruch Siach
Hi Oleg, On Mon, Oct 17, 2011 at 06:29:58PM +0200, Oleg Goldshmidt wrote: ... Now, put the above line in a C or C++ file, say foo.cc, and do the following: $ g++ -g -O2 foo.cc -c -o foo.o $ ident foo.o foo.o: $Id: foo.cc 673 2011-10-17 09:48:11Z oleg $ This works up to and

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Nadav Har'El
On Mon, Oct 17, 2011, Oleg Goldshmidt wrote about Newer gcc swallow version control keywords: static const char foo_src_id[] = $Id$; I remember many years ago (when I was probably still using SCCS with its %..% macros, and SCCS's what(1) instead of ident(1)), there was already an argument on

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Shachar Shemesh
On 10/17/2011 06:29 PM, Oleg Goldshmidt wrote: Hi, I have a gcc-related question. Problematic platform is Fedora 15 with gcc 4.6.1, as well as Fedora 14 with gcc 4.5.1. I am used to keeping RCS/CVS/SVN keywords (e.g., $Id$) in all my code. In the case of C/C++ this normally amounts to

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Oleg Goldshmidt
Nadav Har'El n...@math.technion.ac.il writes: In any case, because there was always a fear that the compiler might optimize these out, someone invented a new directive, #ident, as in: #ident $Id$ This has always been there, but it has never been standard, AFAIK. It is not a GCC extension,

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Oleg Goldshmidt
Baruch Siach bar...@tkos.co.il writes: The -O2, as well as -O and -Os, gcc options enable a set of specific optimizations that can each be turned off. The full list is at http://gcc.gnu.org/onlinedocs/gcc-4.6.1/gcc/Optimize-Options.html. Just go over this list and disable each optimization,

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Oleg Goldshmidt
Shachar Shemesh shac...@shemesh.biz writes: Leaving aside the question of whether that is a good idea This saved my butt enough times in the past that I think it is ;-) - did you try changing that to: static const volatile char foo_src_id[] = $Id$; Hmm... const volatile hadn't occurred to

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Shachar Shemesh
On 10/17/2011 10:29 PM, Oleg Goldshmidt wrote: - did you try changing that to: static const volatile char foo_src_id[] = $Id$; Hmm... const volatile hadn't occurred to me before, but I have just tried it and it did not work. Just tested it myself. It does, indeed, not work. I wonder why?

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Oleg Goldshmidt
Shachar Shemesh shac...@shemesh.biz writes: Just tested it myself. It does, indeed, not work. I wonder why? Seems like it SHOULD work. After all, that's what volatile is for, right? I suspected that const was more important than volatile, but it looks (after I removed const) that what

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Daniel Shahaf
Shachar Shemesh wrote on Mon, Oct 17, 2011 at 22:47:49 +0200: On 10/17/2011 10:29 PM, Oleg Goldshmidt wrote: - did you try changing that to: static const volatile char foo_src_id[] = $Id$; Hmm... const volatile hadn't occurred to me before, but I have just tried it and it did not work.

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Oleg Goldshmidt
Nadav Har'El n...@math.technion.ac.il writes: #if (__GNUC__ = 4) (__GNUC_MINOR__ 4) #define USED(x) x __attribute__((used)) #else #define USED(x) x #endif #define IDENT(x) static const char USED(foo_src_id[]) = x; and then in each file just do

Re: Newer gcc swallow version control keywords

2011-10-17 Thread Ghiora Drori
http://gcc.gnu.org/ml/gcc/2005-04/msg01429.html I do have three suggestions for you: 1) The current way to tell the compiler not to throw away apparently-unused data is __attribute__((used)), like this: static const char __attribute__((used)) rcs_sccs_id[] = $Id: @(#)%M%

Re: GIT BEIVRIT

2011-10-17 Thread Tzafrir Cohen
On Mon, Oct 17, 2011 at 09:23:38PM +0200, Raz wrote: http://sos-linux.svn.sourceforge.net/viewvc/sos-linux/LinuxHebrew/gitcourse/ To those who are too lazy to read git-pro in english, I have translated git-pro important parts to hebrew. 1. Great! 2. But why that choice of version control?