Menu
▾
▴
colinux-devel
|
From: Jason A. P. <pat...@pc...> - 2004-02-13 20:54:37
|
I read an e-mail that said that once someone got networking going and Internet Connection Sharing, they just apt-get update'd and apt-get install'd X, vnc, etc. and "it all just worked". Does that mean that you got X running natively under Windows? I tried using the 'vesa' driver to X 4.1.0 available in woody. It messes up the Windows display and moves my existing desktop offscreen. Moving the mouse slides the screen around until it "locks" back in place the way it should be. I'm currently going to go for the kdm running on coLinux with cygwin's X server as the display. It would be nice to be able to alleviate this dependency, though. Thanks. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. |
|
From: Alejandro R. S. <as...@MI...> - 2004-02-13 22:26:56
|
X won't run in the console, or using anything that requires a graphics card. What's been done is to have a vnc server running X, and using vncviewer to connect to it from windows. If it's not working at first, check the logs it makes to help you find what's missing. Good luck! -Alejandro On Fri, 2004-02-13 at 21:48, Jason A. Pattie wrote: > I read an e-mail that said that once someone got networking going and > Internet Connection Sharing, they just apt-get update'd and apt-get > install'd X, vnc, etc. and "it all just worked". Does that mean that > you got X running natively under Windows? I tried using the 'vesa' > driver to X 4.1.0 available in woody. It messes up the Windows display > and moves my existing desktop offscreen. Moving the mouse slides the > screen around until it "locks" back in place the way it should be. I'm > currently going to go for the kdm running on coLinux with cygwin's X > server as the display. It would be nice to be able to alleviate this > dependency, though. > > Thanks. > |
|
From: Jason A. P. <pat...@pc...> - 2004-02-13 22:45:16
|
Alejandro R. Sedeno wrote: >X won't run in the console, or using anything that requires a graphics >card. What's been done is to have a vnc server running X, and using >vncviewer to connect to it from windows. If it's not working at first, >check the logs it makes to help you find what's missing. > >Good luck! > > Interesting approach. Thanks. I suppose it might be faster running it this way than using Cygwin's X server? One of the neat features of Cygwin's latest X servers is -multiwindow, which allows Windows to "manage" X clients that connect. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. |
|
From: Ballard J. <sac...@ho...> - 2004-02-13 23:40:32
|
I used cygwin X. On coLinux (Debian), use dselect to find xterm and install it or do an "apt-get install xterm" instead. From cygwin, use "xhost +" to allow any connection, and that is okay behind a firewall. Start the xserver. Here is a .bat file I used to start it from the Start menu. Update the "set CYGWIN_ROOT=" if needed. --- @echo off SET DISPLAY=127.0.0.1:0.0 SET CYGWIN_ROOT=C:\cygwin REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM start XWin -multiwindow ----- Original Message ----- From: "Jason A. Pattie" <pat...@pc...> To: <col...@li...> Sent: Friday, February 13, 2004 8:39 PM Subject: Re: [coLinux-devel] Getting X to work natively > Alejandro R. Sedeno wrote: > > >X won't run in the console, or using anything that requires a graphics > >card. What's been done is to have a vnc server running X, and using > >vncviewer to connect to it from windows. If it's not working at first, > >check the logs it makes to help you find what's missing. > > > >Good luck! > > > > > Interesting approach. Thanks. > > I suppose it might be faster running it this way than using Cygwin's X > server? > > One of the neat features of Cygwin's latest X servers is -multiwindow, > which allows Windows to "manage" X clients that connect. > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > MailScanner thanks transtec Computers for their support. > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: andre <avb...@gm...> - 2004-02-14 01:21:16
|
On Saturday 14 February 2004 00:56, Ballard Jonathan wrote: > I used cygwin X. > > On coLinux (Debian), use dselect to find xterm and install it or do an > "apt-get install xterm" instead. > > From cygwin, use "xhost +" to allow any connection, and that is okay behind > a firewall. It is never okay to do a host + from a security perspective. At the very least do a host +192.168.0.40 or prevered use cookies or ssh |
|
From: Bart K. <bar...@su...> - 2004-02-26 17:09:31
|
> I used cygwin X. > > On coLinux (Debian), use dselect to find xterm and install it or do an > "apt-get install xterm" instead. > > From cygwin, use "xhost +" to allow any connection, and that is okay behind > a firewall. I copied all relevant files from cygwin for the XServer and deleted the rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server OUTSIDE cygwin (packed about 2.5 MB) ;) I zipped all of these and put them online, and put a bat file to startup the server. Tested with KDE and Enlightment, works fine a compact XServer for the till coLinux supports X native. http://speeldoos.showcase.surfnet.nl/startx.zip regards, Bart |
|
From: Digital I. Inc. <ok...@di...> - 2004-04-04 16:52:33
|
Hello Kerver.
I am working on making an installer of Cygwin/X Japanese for coLinux.
I tried your zip file and found that it requires basic cygwin system is installed.
Do you have a way/plan to eliminate this feature?
How to run your zip alone, without Cygwin itself?
--- Okajima.
>> I used cygwin X.
>>
>> On coLinux (Debian), use dselect to find xterm and install it or do an
>> "apt-get install xterm" instead.
>>
>> From cygwin, use "xhost +" to allow any connection, and that is okay behind
>> a firewall.
>
>I copied all relevant files from cygwin for the XServer and deleted the
>rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server
>OUTSIDE cygwin (packed about 2.5 MB) ;)
>
>I zipped all of these and put them online, and put a bat file to startup
>the server. Tested with KDE and Enlightment, works fine a compact
>XServer for the till coLinux supports X native.
>
>http://speeldoos.showcase.surfnet.nl/startx.zip
>
>regards,
>Bart
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!
>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Jose M. M. <tx...@eu...> - 2004-04-04 23:26:00
|
In case it is useful for somebody, I am using vnc for running graphic sessi= ons=20 in colinux. I think it is easier and simpler than all this X and cygwin=20 stuff. You run vncserver in the colinux machine (it is already in debian and gento= o)=20 and then use an vnc client in the windows machine. Vnc clients exists for a= =20 lot of architectures, win32 included. You can detach and reatach later to a= =20 graphic session, what you cannot do with an X session due to X clients=20 deading when X connection lost. El Domingo, 4 de Abril de 2004 18:52, Digital Infra, Inc. escribi=F3: > Hello Kerver. > > I am working on making an installer of Cygwin/X Japanese for coLinux. > I tried your zip file and found that it requires basic cygwin system is > installed. Do you have a way/plan to eliminate this feature? > How to run your zip alone, without Cygwin itself? > > --- Okajima. > > >> I used cygwin X. > >> > >> On coLinux (Debian), use dselect to find xterm and install it or do an > >> "apt-get install xterm" instead. > >> > >> From cygwin, use "xhost +" to allow any connection, and that is okay > >> behind a firewall. > > > >I copied all relevant files from cygwin for the XServer and deleted the > >rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server > >OUTSIDE cygwin (packed about 2.5 MB) ;) > > > >I zipped all of these and put them online, and put a bat file to startup > >the server. Tested with KDE and Enlightment, works fine a compact > >XServer for the till coLinux supports X native. > > > >http://speeldoos.showcase.surfnet.nl/startx.zip > > > >regards, > >Bart > > > > > >------------------------------------------------------- > >SF.Net is sponsored by: Speed Start Your Linux Apps Now. > >Build and deploy apps & Web services for Linux with > >a free DVD software kit from IBM. Click Now! > >http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick > >_______________________________________________ > >coLinux-devel mailing list > >coL...@li... > >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel =2D-=20 ______________________________ < hola, soy una firma horrible > ------------------------------ \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || txemi <tx...@eu...> web: http://txemi.webhop.org mirror: http://txemi2.webhop.org mirror2: http://txemi3.webhop.org=09 |
|
From: morfic <mo...@bb...> - 2004-04-05 03:23:38
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body> <5cents>i used to use vnc cause i didnt want to get CygwinX or buy Xwin32, but now having set up cygwin including xfree (for another project), i have to say, having X windows show up with a taskbar button per window, not one per desktop as i got it with vnc, i can see the benefits, im using flashdesktops ( <a class="moz-txt-link-abbreviated" href="http://www.flashdesktops.com">www.flashdesktops.com</a> ) on XP Pro, this way i could display windows on XP and move them to one of the 8 desktop im using as i am doing with any native win32 application, what im trying to say is, this is a matter of personal preference ( i defenitely switched teams and am loving cygwin X to display my X windows now), and vnc being easier than cygwin Xserver, honestly both is about as easy to setup, vnc probably has a size benefit on its side </5cents><br> <br> Jose Miguel Martinez wrote:<br> <blockquote cite="mid...@eu..." type="cite"> <pre wrap="">In case it is useful for somebody, I am using vnc for running graphic sessions in colinux. I think it is easier and simpler than all this X and cygwin stuff. You run vncserver in the colinux machine (it is already in debian and gentoo) and then use an vnc client in the windows machine. Vnc clients exists for a lot of architectures, win32 included. You can detach and reatach later to a graphic session, what you cannot do with an X session due to X clients deading when X connection lost. El Domingo, 4 de Abril de 2004 18:52, Digital Infra, Inc. escribió: </pre> <blockquote type="cite"> <pre wrap="">Hello Kerver. I am working on making an installer of Cygwin/X Japanese for coLinux. I tried your zip file and found that it requires basic cygwin system is installed. Do you have a way/plan to eliminate this feature? How to run your zip alone, without Cygwin itself? --- Okajima. </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">I used cygwin X. On coLinux (Debian), use dselect to find xterm and install it or do an "apt-get install xterm" instead. From cygwin, use "xhost +" to allow any connection, and that is okay behind a firewall. </pre> </blockquote> <pre wrap="">I copied all relevant files from cygwin for the XServer and deleted the rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server OUTSIDE cygwin (packed about 2.5 MB) ;) I zipped all of these and put them online, and put a bat file to startup the server. Tested with KDE and Enlightment, works fine a compact XServer for the till coLinux supports X native. <a class="moz-txt-link-freetext" href="http://speeldoos.showcase.surfnet.nl/startx.zip">http://speeldoos.showcase.surfnet.nl/startx.zip</a> regards, Bart ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! <a class="moz-txt-link-freetext" href="http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click">http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click</a> _______________________________________________ coLinux-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:coL...@li...">coL...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/colinux-devel">https://lists.sourceforge.net/lists/listinfo/colinux-devel</a> </pre> </blockquote> <pre wrap="">------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ coLinux-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:coL...@li...">coL...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/colinux-devel">https://lists.sourceforge.net/lists/listinfo/colinux-devel</a> </pre> </blockquote> <pre wrap=""><!----> </pre> </blockquote> </body> </html> |
|
From: andre <avb...@gm...> - 2004-02-13 23:25:12
|
On Friday 13 February 2004 23:24, Alejandro R. Sedeno wrote: > X won't run in the console, or using anything that requires a graphics > card. What's been done is to have a vnc server running X, and using > vncviewer to connect to it from windows. If it's not working at first, > check the logs it makes to help you find what's missing. > > Good luck! > > -Alejandro Why would you use vncviewer when you can use a Xserver running on windows to server the programs on colinux? |
|
From: Alejandro R. S. <as...@MI...> - 2004-02-14 00:23:01
|
One reason I've found to use vnc instead of X forwarding is that it's like screen. My vncviewer can crash and I can reconnect to it (though that never happens). On the other hand, I've had problems with some X servers on windows, and if they crash, anything you're running crashes too. -Alejandro On Fri, 2004-02-13 at 18:21, andre wrote: > On Friday 13 February 2004 23:24, Alejandro R. Sedeno wrote: > > X won't run in the console, or using anything that requires a graphics > > card. What's been done is to have a vnc server running X, and using > > vncviewer to connect to it from windows. If it's not working at first, > > check the logs it makes to help you find what's missing. > > > > Good luck! > > > > -Alejandro > > Why would you use vncviewer when you can use a Xserver running on windows to > server the programs on colinux? > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X