You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: yin s. <sun...@gm...> - 2013-01-04 06:42:38
|
0.0.0.0 means listen on any network IP address. the output looks correct. I saw your previous email saying X server works. I don't know why vnc doesn't. you may try ssh to colinux, or open a new vncserver session. have no idea now. On Thu, Jan 3, 2013 at 10:20 PM, raghukisore <nra...@gm...> wrote: > > Hello Yin, > > Here is the output for netsta -ltn > > Proto Recv-Q Send-Q Local Address Foreign Address > State > > tcp 0 0 0.0.0.0:5900 0.0.0.0:* > LISTEN > tcp 0 0 0.0.0.0:6000 0.0.0.0:* > LISTEN > tcp 0 0 0.0.0.0:22 0.0.0.0:* > LISTEN > tcp 0 0 127.0.0.1:631 0.0.0.0:* > LISTEN > tcp 0 0 127.0.0.1:25 0.0.0.0:* > LISTEN > tcp 0 0 :::6000 :::* > LISTEN > tcp 0 0 :::22 :::* > LISTEN \ > > i believe vncserver is indicated by the following line > > tcp 0 0 0.0.0.0:5900 0.0.0.0:* > LISTEN > > I mean on Fedora10+colinux the moment i start gnome, it automatically > triggers vncserver and spits out messages stating that display is started on > port 0..so now vncserver port becomes 5900 + 0<display no.> > but can't understand the why the address is shown as 0:0:0: > > Please let me know if i am missing something on configuration of vncserver > in colinux!!! > Regards > Raghu. > > > > yin sun wrote: >> >> is your vncserver listening on port 5900? try netstat -ltn inside >> colinux to see what tcp port is listening. >> >> On Thu, Jan 3, 2013 at 9:35 PM, raghukisore <nra...@gm...> >> wrote: >>> >>> Hello Everone, >>> I need some network configuration help to be able to start gnome on my >>> coLinux and this is my first time installation of Colinux. >>> i completed installation by using the binary image of colinux and chose >>> the >>> Fedora option during the installation process. >>> I configure eth0 and eth1 interfaces. Installed display managers, window >>> managers, vncserver and all that stuff that several online resources told >>> me >>> to. >>> At boot time the colinux system shows both eth0 and eth1 as UP >>> My host system is windows 7 on which i already have RealVNC software and >>> cygwin (along with X) installed. >>> >>> with X Server running on my Host window 7 system i am able to launch >>> xeyes, >>> xterm from colinux system. >>> >>> Inspite of all the online documentation available i am not able to >>> connect >>> from VNCviewer (on host system windows 7) to colinux + fedora10? >>> can anyone please help me out? I have been trying all combination for the >>> last 3 days but without help. Nor the X helps. >>> >>> >>> Here is the my eth0 and eth1 configuration for reference. >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0 >>> DEVICE=eth0 >>> IPADDR=10.0.2.15 >>> NETMASK=255.255.255.0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> TYPE=Ethernet >>> BROADCAST=10.0.2.255 >>> GATEWAY=10.0.2.2 >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth1 >>> DEVICE=eth1 >>> BOOTTPROTO=dhcp >>> IPADDR=10.0.3.16 >>> ONBOOT=yes >>> NETWORK=10.0.3.0 >>> NETMASK=255.255.254.0 >>> BROADCAST=10.0.3.255 >>> >>> windows TAP-WIN32 Adapter V8 setting are >>> IP Address: 10.0.3.17 >>> subnet mask: 255.255.254.0 >>> >>> name server setting on colinux is >>> 10.0.2.3 >>> DISPLAY variable setting is (colinux) >>> 172.16.0.21:0 >>> >>> In the file start-defora-10.sh eth0 and eth1 are configured as >>> >>> eth0=slirp,,tcp:5900:5900 ro \ >>> eth1=tuntap,"TAP" ro >>> >>> VNCviewer setting i am using (running on my windows 7-host system) is >>> 10.0.3.16:5900 >>> >>> i tried other too like >>> 10.0.2.15:5900 and 10.0.3.17:5900. >>> >>> The VNC viewer keeps getting reply Connection Timed Out. >>> >>> I turned off Windows Firewall. >>> >>> Any help will be appreciated. >>> >>> Regards >>> Raghu. >>> -- >>> View this message in context: >>> http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34857793.html >>> Sent from the colinux-users mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and >>> much more. Get web development skills now with LearnDevNow - >>> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. >>> SALE $99.99 this month only -- learn more at: >>> http://p.sf.net/sfu/learnmore_122812 >>> _______________________________________________ >>> coLinux-users mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> ------------------------------------------------------------------------------ >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and >> much more. Get web development skills now with LearnDevNow - >> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. >> SALE $99.99 this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122812 >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> > > -- > View this message in context: http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34857873.html > Sent from the colinux-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: raghukisore <nra...@gm...> - 2013-01-04 06:20:51
|
Hello Yin, Here is the output for netsta -ltn Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN tcp 0 0 :::6000 :::* LISTEN tcp 0 0 :::22 :::* LISTEN \ i believe vncserver is indicated by the following line tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN I mean on Fedora10+colinux the moment i start gnome, it automatically triggers vncserver and spits out messages stating that display is started on port 0..so now vncserver port becomes 5900 + 0<display no.> but can't understand the why the address is shown as 0:0:0: Please let me know if i am missing something on configuration of vncserver in colinux!!! Regards Raghu. yin sun wrote: > > is your vncserver listening on port 5900? try netstat -ltn inside > colinux to see what tcp port is listening. > > On Thu, Jan 3, 2013 at 9:35 PM, raghukisore <nra...@gm...> > wrote: >> >> Hello Everone, >> I need some network configuration help to be able to start gnome on my >> coLinux and this is my first time installation of Colinux. >> i completed installation by using the binary image of colinux and chose >> the >> Fedora option during the installation process. >> I configure eth0 and eth1 interfaces. Installed display managers, window >> managers, vncserver and all that stuff that several online resources told >> me >> to. >> At boot time the colinux system shows both eth0 and eth1 as UP >> My host system is windows 7 on which i already have RealVNC software and >> cygwin (along with X) installed. >> >> with X Server running on my Host window 7 system i am able to launch >> xeyes, >> xterm from colinux system. >> >> Inspite of all the online documentation available i am not able to >> connect >> from VNCviewer (on host system windows 7) to colinux + fedora10? >> can anyone please help me out? I have been trying all combination for the >> last 3 days but without help. Nor the X helps. >> >> >> Here is the my eth0 and eth1 configuration for reference. >> >> /etc/sysconfig/network-scripts/ifcfg-eth0 >> DEVICE=eth0 >> IPADDR=10.0.2.15 >> NETMASK=255.255.255.0 >> BOOTPROTO=static >> ONBOOT=yes >> TYPE=Ethernet >> BROADCAST=10.0.2.255 >> GATEWAY=10.0.2.2 >> >> /etc/sysconfig/network-scripts/ifcfg-eth1 >> DEVICE=eth1 >> BOOTTPROTO=dhcp >> IPADDR=10.0.3.16 >> ONBOOT=yes >> NETWORK=10.0.3.0 >> NETMASK=255.255.254.0 >> BROADCAST=10.0.3.255 >> >> windows TAP-WIN32 Adapter V8 setting are >> IP Address: 10.0.3.17 >> subnet mask: 255.255.254.0 >> >> name server setting on colinux is >> 10.0.2.3 >> DISPLAY variable setting is (colinux) >> 172.16.0.21:0 >> >> In the file start-defora-10.sh eth0 and eth1 are configured as >> >> eth0=slirp,,tcp:5900:5900 ro \ >> eth1=tuntap,"TAP" ro >> >> VNCviewer setting i am using (running on my windows 7-host system) is >> 10.0.3.16:5900 >> >> i tried other too like >> 10.0.2.15:5900 and 10.0.3.17:5900. >> >> The VNC viewer keeps getting reply Connection Timed Out. >> >> I turned off Windows Firewall. >> >> Any help will be appreciated. >> >> Regards >> Raghu. >> -- >> View this message in context: >> http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34857793.html >> Sent from the colinux-users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and >> much more. Get web development skills now with LearnDevNow - >> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. >> SALE $99.99 this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122812 >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > -- View this message in context: http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34857873.html Sent from the colinux-users mailing list archive at Nabble.com. |
From: yin s. <sun...@gm...> - 2013-01-04 05:45:47
|
is your vncserver listening on port 5900? try netstat -ltn inside colinux to see what tcp port is listening. On Thu, Jan 3, 2013 at 9:35 PM, raghukisore <nra...@gm...> wrote: > > Hello Everone, > I need some network configuration help to be able to start gnome on my > coLinux and this is my first time installation of Colinux. > i completed installation by using the binary image of colinux and chose the > Fedora option during the installation process. > I configure eth0 and eth1 interfaces. Installed display managers, window > managers, vncserver and all that stuff that several online resources told me > to. > At boot time the colinux system shows both eth0 and eth1 as UP > My host system is windows 7 on which i already have RealVNC software and > cygwin (along with X) installed. > > with X Server running on my Host window 7 system i am able to launch xeyes, > xterm from colinux system. > > Inspite of all the online documentation available i am not able to connect > from VNCviewer (on host system windows 7) to colinux + fedora10? > can anyone please help me out? I have been trying all combination for the > last 3 days but without help. Nor the X helps. > > > Here is the my eth0 and eth1 configuration for reference. > > /etc/sysconfig/network-scripts/ifcfg-eth0 > DEVICE=eth0 > IPADDR=10.0.2.15 > NETMASK=255.255.255.0 > BOOTPROTO=static > ONBOOT=yes > TYPE=Ethernet > BROADCAST=10.0.2.255 > GATEWAY=10.0.2.2 > > /etc/sysconfig/network-scripts/ifcfg-eth1 > DEVICE=eth1 > BOOTTPROTO=dhcp > IPADDR=10.0.3.16 > ONBOOT=yes > NETWORK=10.0.3.0 > NETMASK=255.255.254.0 > BROADCAST=10.0.3.255 > > windows TAP-WIN32 Adapter V8 setting are > IP Address: 10.0.3.17 > subnet mask: 255.255.254.0 > > name server setting on colinux is > 10.0.2.3 > DISPLAY variable setting is (colinux) > 172.16.0.21:0 > > In the file start-defora-10.sh eth0 and eth1 are configured as > > eth0=slirp,,tcp:5900:5900 ro \ > eth1=tuntap,"TAP" ro > > VNCviewer setting i am using (running on my windows 7-host system) is > 10.0.3.16:5900 > > i tried other too like > 10.0.2.15:5900 and 10.0.3.17:5900. > > The VNC viewer keeps getting reply Connection Timed Out. > > I turned off Windows Firewall. > > Any help will be appreciated. > > Regards > Raghu. > -- > View this message in context: http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34857793.html > Sent from the colinux-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: raghukisore <nra...@gm...> - 2013-01-04 05:35:43
|
Hello Everone, I need some network configuration help to be able to start gnome on my coLinux and this is my first time installation of Colinux. i completed installation by using the binary image of colinux and chose the Fedora option during the installation process. I configure eth0 and eth1 interfaces. Installed display managers, window managers, vncserver and all that stuff that several online resources told me to. At boot time the colinux system shows both eth0 and eth1 as UP My host system is windows 7 on which i already have RealVNC software and cygwin (along with X) installed. with X Server running on my Host window 7 system i am able to launch xeyes, xterm from colinux system. Inspite of all the online documentation available i am not able to connect from VNCviewer (on host system windows 7) to colinux + fedora10? can anyone please help me out? I have been trying all combination for the last 3 days but without help. Nor the X helps. Here is the my eth0 and eth1 configuration for reference. /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 IPADDR=10.0.2.15 NETMASK=255.255.255.0 BOOTPROTO=static ONBOOT=yes TYPE=Ethernet BROADCAST=10.0.2.255 GATEWAY=10.0.2.2 /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 BOOTTPROTO=dhcp IPADDR=10.0.3.16 ONBOOT=yes NETWORK=10.0.3.0 NETMASK=255.255.254.0 BROADCAST=10.0.3.255 windows TAP-WIN32 Adapter V8 setting are IP Address: 10.0.3.17 subnet mask: 255.255.254.0 name server setting on colinux is 10.0.2.3 DISPLAY variable setting is (colinux) 172.16.0.21:0 In the file start-defora-10.sh eth0 and eth1 are configured as eth0=slirp,,tcp:5900:5900 ro \ eth1=tuntap,"TAP" ro VNCviewer setting i am using (running on my windows 7-host system) is 10.0.3.16:5900 i tried other too like 10.0.2.15:5900 and 10.0.3.17:5900. The VNC viewer keeps getting reply Connection Timed Out. I turned off Windows Firewall. Any help will be appreciated. Regards Raghu. -- View this message in context: http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34857793.html Sent from the colinux-users mailing list archive at Nabble.com. |
From: deneme.true <den...@gm...> - 2013-01-03 12:34:32
|
>1. can your router direct all the traffic (except specific to >colinux1) to colinux2. Here it requires each colinux has different MAC I've disabled DHCP server of router and set DMZ internal ip for 192.168.1.3 which is coLinux 2 and 192.168.1.2 for coLinux 1 Router has DMZ internal ip settings and its 192.168.1.3 Two instance coLinux uses same mac address, If I don't misunderstand you, I have to set different mac address for each coLinux so for DMZ area I have to use different tap device? >2. Does the Host windows that have both colinux 1 and 2 running direct >all the traffic (expect specific to colinux 1) to colinux 2. Here the >host would need to setup special forwarding rule, I know linux can do >but not sure about windows. I couldn't understand this fully. If different mac address(ethernet card) and tap is solution for DMZ area I am able to do it. Regards |
From: brian m. <bmu...@gm...> - 2013-01-03 12:13:06
|
I don't use colinux but have followed its progress. I thought I'd pass on this work being done by the FreeRDP project with a sub-project called *WinPR. *in case it could be helpful. http://www.freerdp.com/2012/05/24/winpr-windows-portable-runtime/ FreeRDP if you haven't used it is an open source rdp implementation that supports RemoteApp and RemoteFX capabilities of RDP on Linux,Mac and some users are actually using it with their Windows PCs. Brian |
From: Raghu K. <nra...@gm...> - 2013-01-03 07:01:37
|
Hello Everone, I need some network configuration help to be able to start gnome on my coLinux and this is my first time installation of Colinux. i completed installation by using the binary image of colinux and chose the Fedora option during the installation process. I configure eth0 and eth1 interfaces. Installed display managers, window managers, vncserver and all that stuff that several online resources told me to. At boot time the colinux system shows both eth0 and eth1 as UP My host system is windows 7 on which i already have RealVNC software and cygwin (along with X) installed. with X Server running on my Host window 7 system i am able to launch xeyes, xterm from colinux system. Inspite of all the online documentation available i am not able to connect from VNCviewer (on host system windows 7) to colinux + fedora10? can anyone please help me out? I have been trying all combination for the last 3 days but without help. Nor the X helps. Here is the my eth0 and eth1 configuration for reference. * /etc/sysconfig/network-scripts/ifcfg-eth0* DEVICE=eth0 IPADDR=10.0.2.15 NETMASK=255.255.255.0 BOOTPROTO=static ONBOOT=yes TYPE=Ethernet BROADCAST=10.0.2.255 GATEWAY=10.0.2.2 */etc/sysconfig/network-scripts/ifcfg-eth1* DEVICE=eth1 BOOTTPROTO=dhcp IPADDR=10.0.3.16 ONBOOT=yes NETWORK=10.0.3.0 NETMASK=255.255.254.0 BROADCAST=10.0.3.255 * windows TAP-WIN32 Adapter V8 setting are* IP Address: 10.0.3.17 subnet mask: 255.255.254.0 *name server setting on colinux is* 10.0.2.3 *DISPLAY variable setting is* 172.16.0.21:0 *VNCviewer setting i am using (running on my windows 7-host system) is* 10.0.3.16:5900 *i tried other too like* 10.0.2.15:5900 and 10.0.3.17:5900. Any help will be appreciated. Regards Raghu. On Tue, Jan 1, 2013 at 6:36 PM, deneme.true <den...@gm...> wrote: > Hello, > > Raghu, > > If you haven't used(command tools usage familiarity) or installed any > other Linux distribution, you'll have difficulties on using it. For > instance: in debian image, there are instructions to install > debian-businesscard iso into the ext3 formatted image in Readme.txt > file. Probably, you can install the fedora iso to ext3 formatted image > similar way which is indicated in Readme.txt within debian image file. > > Regards > |
From: yin s. <sun...@gm...> - 2013-01-03 04:42:29
|
Hi Deneme, I don't fully understand your intent. seems to me your problem has two aspects. 1. can your router direct all the traffic (except specific to colinux1) to colinux2. Here it requires each colinux has different MAC 2. Does the Host windows that have both colinux 1 and 2 running direct all the traffic (expect specific to colinux 1) to colinux 2. Here the host would need to setup special forwarding rule, I know linux can do but not sure about windows. /Yin On Wed, Jan 2, 2013 at 4:07 PM, deneme.true <den...@gm...> wrote: > Hello, > > At past, I've seen Henry's comments in coLinux wiki regarding > preventing to break coLinux kernel. I thought, similar way, but > couldn't successful yet to protect host environment. My thought > details are below with using two instance of coLinux image, If this > prevention is true, I can write these details to coLinux wiki, but I > would like to hear your thoughts to protect host environment from bad > guys. > > I am running two instance of coLinux environment, DMZ area will get > the attacks, other instance has connection to host and will be used > for regular tasks(ftp,http etc) > > But I couldn't success with this configuration but Isn't it correct > theoretically? > > > -------------- > | Internet | > -------------- > | > --------------- > | router | > --------------- > / \ > / \ > coLinux 1(eth0) coLinux 2 (eth0) > 192.168.1.2 192.168.1.3 > Connection to Host with eth1 DMZ Area (Closed to anywhere) > / > / > / > ---------- > | Host | > ---------- > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: deneme.true <den...@gm...> - 2013-01-03 00:07:54
|
Hello, At past, I've seen Henry's comments in coLinux wiki regarding preventing to break coLinux kernel. I thought, similar way, but couldn't successful yet to protect host environment. My thought details are below with using two instance of coLinux image, If this prevention is true, I can write these details to coLinux wiki, but I would like to hear your thoughts to protect host environment from bad guys. I am running two instance of coLinux environment, DMZ area will get the attacks, other instance has connection to host and will be used for regular tasks(ftp,http etc) But I couldn't success with this configuration but Isn't it correct theoretically? -------------- | Internet | -------------- | --------------- | router | --------------- / \ / \ coLinux 1(eth0) coLinux 2 (eth0) 192.168.1.2 192.168.1.3 Connection to Host with eth1 DMZ Area (Closed to anywhere) / / / ---------- | Host | ---------- |
From: deneme.true <den...@gm...> - 2013-01-01 13:06:29
|
Hello, Raghu, If you haven't used(command tools usage familiarity) or installed any other Linux distribution, you'll have difficulties on using it. For instance: in debian image, there are instructions to install debian-businesscard iso into the ext3 formatted image in Readme.txt file. Probably, you can install the fedora iso to ext3 formatted image similar way which is indicated in Readme.txt within debian image file. Regards |
From: yin s. <sun...@gm...> - 2013-01-01 03:36:23
|
no it won't. the fedora means the virtual disk contains fedora distribution with modified colinux kernel. you will use normal method to download the kernel source from kernel.org. On Mon, Dec 31, 2012 at 12:55 AM, Raghu Kisore <nra...@gm...> wrote: > Hello Every One, > I intend to use CoLinux and i am doing it for the first time. I have a > simple question. While installing CoLinux, if i select Fedora does it > install the kernel source code too? I mean how can i install Kernel source > code (Fedora) on CoLinux? > > Please kindly reply and also wish you all a very Happy New Year!! > > Regards > Raghu. > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122412 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Raghu K. <nra...@gm...> - 2012-12-31 08:56:02
|
Hello Every One, I intend to use CoLinux and i am doing it for the first time. I have a simple question. While installing CoLinux, if i select Fedora does it install the kernel source code too? I mean how can i install Kernel source code (Fedora) on CoLinux? Please kindly reply and also wish you all a very Happy New Year!! Regards Raghu. |
From: n s. <nsc...@ya...> - 2012-10-16 16:13:49
|
http://khokarspecialtyclinic.com/data/home.php?sid=vacjlirypufegjc |
From: deneme.true <den...@gm...> - 2012-10-09 13:47:49
|
Hello, I don't know, it is not thought or not at before. Is it possible to use compiled with cygwin/mingw or other open source network stack which is compatible with coLinux instead of using windows stack on Windows? As I understand, Winpcap is only do connection between tap devices. I want to disable adapters at windows which comes with windows and use open source or other implementations instead of which comes with windows os. Is it possible? Thanks in advance. Regards |
From: Henry N. <hen...@ar...> - 2012-10-08 22:34:04
|
You need to create a second TAP device under Windows manually. Henry -------- Original message -------- Subject: Re: [coLinux-users] Running Two Instances From: yin sun <sun...@gm...> To: "deneme.true" <den...@gm...> CC: col...@li... yes, as long as the images are different. instructions should be the same. On Sat, Oct 6, 2012 at 11:32 AM, deneme.true <den...@gm...> wrote: Hello, Is it possible to run two instance of coLinux daemons with different images and network configurations? I couldn't find clear instructions to run two instances. Thanks in Advance. Regards ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: yin s. <sun...@gm...> - 2012-10-06 18:35:53
|
yes, as long as the images are different. instructions should be the same. On Sat, Oct 6, 2012 at 11:32 AM, deneme.true <den...@gm...> wrote: > Hello, > > Is it possible to run two instance of coLinux daemons with different > images and network configurations? > > I couldn't find clear instructions to run two instances. > > Thanks in Advance. > > Regards > > > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: deneme.true <den...@gm...> - 2012-10-06 18:32:19
|
Hello, Is it possible to run two instance of coLinux daemons with different images and network configurations? I couldn't find clear instructions to run two instances. Thanks in Advance. Regards |
From: Arturo R. <ja...@gm...> - 2012-09-24 22:06:22
|
See: http://www.colinux.org/?section=scs On Sun, Sep 23, 2012 at 7:25 PM, Shao Miller <sha...@gm...> wrote: > Thank you. > > I am trying your suggestion. So far, I have needed bison, patch, flex, > texinfo, texinfo-tex, gettext. I will see how it all goes. > > Is there an official SVN for coLinux Linux source, rather than just patches/ > ? > > - Shao > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Sunday, September 23, 2012 20:15 > To: Shao Miller > Cc: col...@li... > Subject: Re: [coLinux-users] Porting a Kernel > > current colinux kernel is based on 2.6.33.7 not very different from 2.6.38.6 > you can try to go through the colinux build process first. once you are > familiar with it, > you should know how to port a new kernel. > On Sun, Sep 23, 2012 at 2:04 PM, Shao Miller <sha...@gm...> wrote: > Good day, folks. > > If I was interested in compiling a Linux kernel for use with coLinux, how > might I go about it? Are there instructions already documented? > > I have the Linux source and the coLinux source. I was planning on reviewing > the items inside coLinux' patch/ directory, then porting those into a branch > in my Linux git repository. Does that make the most sense? > > For the curious, I'm wanting to get Fedora 15's 2.6.38.6-rc1 kernel running > under coLinux so I can port my installation away from VMware and to coLinux. > Fedora 15 is "end-of-life," but oh well. > > Thank you for your time. > > - Shao > > > ---------------------------------------------------------------------------- > -- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://ad.doubleclick.net/clk;258768047;13503038;j? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users -- Arturo R. |
From: Shao M. <sha...@gm...> - 2012-09-24 02:26:11
|
Thank you. I am trying your suggestion. So far, I have needed bison, patch, flex, texinfo, texinfo-tex, gettext. I will see how it all goes. Is there an official SVN for coLinux Linux source, rather than just patches/ ? - Shao ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Sunday, September 23, 2012 20:15 To: Shao Miller Cc: col...@li... Subject: Re: [coLinux-users] Porting a Kernel current colinux kernel is based on 2.6.33.7 not very different from 2.6.38.6 you can try to go through the colinux build process first. once you are familiar with it, you should know how to port a new kernel. On Sun, Sep 23, 2012 at 2:04 PM, Shao Miller <sha...@gm...> wrote: Good day, folks. If I was interested in compiling a Linux kernel for use with coLinux, how might I go about it? Are there instructions already documented? I have the Linux source and the coLinux source. I was planning on reviewing the items inside coLinux' patch/ directory, then porting those into a branch in my Linux git repository. Does that make the most sense? For the curious, I'm wanting to get Fedora 15's 2.6.38.6-rc1 kernel running under coLinux so I can port my installation away from VMware and to coLinux. Fedora 15 is "end-of-life," but oh well. Thank you for your time. - Shao ---------------------------------------------------------------------------- -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: yin s. <sun...@gm...> - 2012-09-24 00:15:07
|
current colinux kernel is based on 2.6.33.7 not very different from 2.6.38.6 you can try to go through the colinux build process first. once you are familiar with it, you should know how to port a new kernel. On Sun, Sep 23, 2012 at 2:04 PM, Shao Miller <sha...@gm...> wrote: > Good day, folks. > > If I was interested in compiling a Linux kernel for use with coLinux, how > might I go about it? Are there instructions already documented? > > I have the Linux source and the coLinux source. I was planning on > reviewing > the items inside coLinux' patch/ directory, then porting those into a > branch > in my Linux git repository. Does that make the most sense? > > For the curious, I'm wanting to get Fedora 15's 2.6.38.6-rc1 kernel running > under coLinux so I can port my installation away from VMware and to > coLinux. > Fedora 15 is "end-of-life," but oh well. > > Thank you for your time. > > - Shao > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://ad.doubleclick.net/clk;258768047;13503038;j? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Shao M. <sha...@gm...> - 2012-09-23 21:04:29
|
Good day, folks. If I was interested in compiling a Linux kernel for use with coLinux, how might I go about it? Are there instructions already documented? I have the Linux source and the coLinux source. I was planning on reviewing the items inside coLinux' patch/ directory, then porting those into a branch in my Linux git repository. Does that make the most sense? For the curious, I'm wanting to get Fedora 15's 2.6.38.6-rc1 kernel running under coLinux so I can port my installation away from VMware and to coLinux. Fedora 15 is "end-of-life," but oh well. Thank you for your time. - Shao |
From: yin s. <sun...@gm...> - 2012-09-18 16:04:44
|
colinux runs inside linux. This is not used by many. only in devel branches, and needs your compilation and with keymap issue unsovled colinux is mainly used in 32bit windows XP/2000/Vista. On Tue, Sep 18, 2012 at 8:53 AM, Frank Church <vfc...@gm...> wrote: > > > On 17 September 2012 16:52, yin sun <sun...@gm...> wrote: > >> you are right, I overlooked the calling method is making difference. >> About keymap, I noticed too. Initially I thought it is a windows/linux >> host thing. so I changed them in the code. >> now, seems that approach is not working for your system. >> Hope you can help to figure out a better way. >> >> Thanks, >> /Yin >> >> >> On Mon, Sep 17, 2012 at 8:16 AM, deneme.true <den...@gm...>wrote: >> >>> It is interesting that when I use >>> >>> $sudo ./colinux-daemon @colinux.cfg >>> >>> as mentioned building doc: >>> Instead of following command: >>> >>> $sudo ./colinux-daemon mem=64 kernel=vmlinux cobd0=rootfs_2gb.img >>> cobd1=swap_128mb.img root=/dev/cobd0 >>> >>> Now, I can see boot details at colinux fltk daemon. Second method of >>> daemon calling shouldn't work at your linux system too. But my >>> keyboard keymap is very different at login screen at the end of boot. >>> Firstly, I think debian's image keyboard map could be different. But >>> at the beginning of install of debian iso, fltk console's keyboard is >>> still different. Probably related with fltk keyboard definitions at >>> source code. I've looked the devel svn but only I've found this >>> link( >>> http://git.hungrycats.org/cgi-bin/gitweb.cgi?p=colinux;a=commitdiff;h=a8862355acd53b565fd04037d1e21fa5e111ab2c >>> ) >>> I thought problem will be related fltk console keymap. What will be >>> the problem with different keyboard layout of fltk console daemon? >>> >>> Thanks in Advance. >>> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> > This is a question I have to ask again. Does coLinux run on Linux as well, > or does it run only on Windows? Some of the questions I see in this mailing > list suggests that it runs on Windows as well, or do the discussions refer > to compilation? > > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com > |
From: yin s. <sun...@gm...> - 2012-09-17 15:52:52
|
you are right, I overlooked the calling method is making difference. About keymap, I noticed too. Initially I thought it is a windows/linux host thing. so I changed them in the code. now, seems that approach is not working for your system. Hope you can help to figure out a better way. Thanks, /Yin On Mon, Sep 17, 2012 at 8:16 AM, deneme.true <den...@gm...> wrote: > It is interesting that when I use > > $sudo ./colinux-daemon @colinux.cfg > > as mentioned building doc: > Instead of following command: > > $sudo ./colinux-daemon mem=64 kernel=vmlinux cobd0=rootfs_2gb.img > cobd1=swap_128mb.img root=/dev/cobd0 > > Now, I can see boot details at colinux fltk daemon. Second method of > daemon calling shouldn't work at your linux system too. But my > keyboard keymap is very different at login screen at the end of boot. > Firstly, I think debian's image keyboard map could be different. But > at the beginning of install of debian iso, fltk console's keyboard is > still different. Probably related with fltk keyboard definitions at > source code. I've looked the devel svn but only I've found this > link( > http://git.hungrycats.org/cgi-bin/gitweb.cgi?p=colinux;a=commitdiff;h=a8862355acd53b565fd04037d1e21fa5e111ab2c > ) > I thought problem will be related fltk console keymap. What will be > the problem with different keyboard layout of fltk console daemon? > > Thanks in Advance. > |
From: deneme.true <den...@gm...> - 2012-09-17 15:16:59
|
It is interesting that when I use $sudo ./colinux-daemon @colinux.cfg as mentioned building doc: Instead of following command: $sudo ./colinux-daemon mem=64 kernel=vmlinux cobd0=rootfs_2gb.img cobd1=swap_128mb.img root=/dev/cobd0 Now, I can see boot details at colinux fltk daemon. Second method of daemon calling shouldn't work at your linux system too. But my keyboard keymap is very different at login screen at the end of boot. Firstly, I think debian's image keyboard map could be different. But at the beginning of install of debian iso, fltk console's keyboard is still different. Probably related with fltk keyboard definitions at source code. I've looked the devel svn but only I've found this link(http://git.hungrycats.org/cgi-bin/gitweb.cgi?p=colinux;a=commitdiff;h=a8862355acd53b565fd04037d1e21fa5e111ab2c) I thought problem will be related fltk console keymap. What will be the problem with different keyboard layout of fltk console daemon? Thanks in Advance. |
From: yin s. <sun...@gm...> - 2012-09-16 16:27:33
|
if colinux-console-fltk is there, just run it manually. If you can see the login screen from there, at least the system booted correctly. On Sun, Sep 16, 2012 at 1:41 AM, deneme.true <den...@gm...> wrote: > Yes, I've build the fltk as mentioned at building > doc(build/patch/install) I think problem is with symlinks. Probably, > daemon couldn't find colinux-console-fltk symlink because of symlinks. > I've only copy the symlinks from which exists coLinux build directory > to in a new directory and I am executing the colinux-daemon where I've > copied the symlinks. But I couldn't solve the problem yet. > |