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
|
From: yin s. <sun...@gm...> - 2014-04-11 22:07:11
|
64bit support. this is something always in my wish list. On Fri, Apr 11, 2014 at 3:02 PM, George P Boutwell < geo...@gm...> wrote: > Really appears dead around here. Virtually no messages, the IRC > channel didn't respond to posts for like 2-3 hours... > > Is anyone even still using CoLinux or has everyone moved on to QEMU, > Xen, VirtualBox & VMWare? > > IF (and it's a big if) I had time to develop some on this project in > the next few weeks, what would be the biggest needs/features that would > give the project new life and meaning? I'd prefer responses only from > users who are actually still using coLinux. > > George > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: George P B. <geo...@gm...> - 2014-04-11 22:03:00
|
Really appears dead around here. Virtually no messages, the IRC channel didn't respond to posts for like 2-3 hours... Is anyone even still using CoLinux or has everyone moved on to QEMU, Xen, VirtualBox & VMWare? IF (and it's a big if) I had time to develop some on this project in the next few weeks, what would be the biggest needs/features that would give the project new life and meaning? I'd prefer responses only from users who are actually still using coLinux. George |
From: yin s. <sun...@gm...> - 2013-11-12 16:19:39
|
checked this link, http://www.youtube.com/watch?v=80QmehEUZio&feature=youtu.be works for me. On Tue, Nov 12, 2013 at 3:44 AM, Steve Adey <sj...@gm...> wrote: > Does anyone have a working copy of Johann Pascher's 8.19 min video > on speedlinux.avi as all the YouTube copies seem to be broken. > > > > ------------------------------------------------------------------------------ > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Steve A. <sj...@gm...> - 2013-11-12 11:55:12
|
Does anyone have a working copy of Johann Pascher's 8.19 min video on speedlinux.avi as all the YouTube copies seem to be broken. |
From: <Mar...@la...> - 2013-08-15 04:56:51
|
IPv4 From: Henry Nestler [mailto:hen...@ar...] Sent: Thursday, August 15, 2013 12:55 AM To: Pukitis Martins (LQLA RD); sun...@gm...; col...@li... Subject: AW: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages Is this an IPv6 ? May be Windows is trying to tunnel it? Henry -------- Original message -------- Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages From: Mar...@la...<mailto:Mar...@la...> To: sun...@gm...,col...@li...<mailto:sun...@gm...,col...@li...> CC: First packet has source MAC address of sender, second - source MAC address of "Local Area Connection 2". Sender is another host on LAN that is on "Local Area Connection 2" network adapter. "Local Area Connection 2" is a physical Ethernet adapter connection. -----Original Message----- From: yin sun [mailto:sun...@gm...] Sent: Wednesday, August 14, 2013 9:07 PM To: Pukitis Martins (LQLA RD) Cc: col...@li...<mailto:col...@li...> Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages these two are not duplicate packets, they have different src MAC and TTL is decremented. to me, looks like the host bridge is playing tricks to prevent something. Can you associate each src MAC to the virtual device. On Wed, Aug 14, 2013 at 12:46 AM, <Mar...@la...<mailto:Mar...@la...>> wrote: > I run sniffer (wireshark) on the PC. The duplicated packets are also received by an application in coLinux. > Both packets (separated by protocol for simplicity): > 1st: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000319001589 0800 > IP: 4500002400000000ff113780c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > Ethernet (trailer): 00000000000000000000 > > 2nd: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000a5e63ab14 0800 > IP: 4500002400000000fe113880c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > > -----Original Message----- > From: yin sun [mailto:sun...@gm...] > Sent: Tuesday, August 13, 2013 6:51 PM > To: Pukitis Martins (LQLA RD) > Cc: col...@li...<mailto:col...@li...> > Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates > packages > > where do you run the packet sniffer. can you paste the exact duplicated packet's headers. > > > On Tue, Aug 13, 2013 at 5:15 AM, <Mar...@la...<mailto:Mar...@la...>> wrote: >> I've set up a bridge to access LAN from coLinux, like described in >> >> http://colinux.wikia.com/wiki/Network#WinPcap >> >> >> >> by adding this line to the coLinux configuration file: >> >> eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 >> >> >> >> Now every packet from LAN to coLinux is duplicated. First packet has >> source MAC address of sender, second - source MAC address of "Local >> Area Connection 2". Packets from coLinux to LAN are not duplicated. How to fix it? >> >> >> >> >> --------------------------------------------------------------------- >> - >> -------- Get 100% visibility into Java/.NET code with AppDynamics >> Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg. >> c lktrk _______________________________________________ >> coLinux-users mailing list >> coL...@li...<mailto:coL...@li...> >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ coLinux-users mailing list coL...@li...<mailto:coL...@li...> https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Henry N. <hen...@ar...> - 2013-08-14 21:55:36
|
Is this an IPv6 ? May be Windows is trying to tunnel it? Henry -------- Original message -------- Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages From: Mar...@la... To: sun...@gm...,col...@li... CC: First packet has source MAC address of sender, second - source MAC address of "Local Area Connection 2". Sender is another host on LAN that is on "Local Area Connection 2" network adapter. "Local Area Connection 2" is a physical Ethernet adapter connection. -----Original Message----- From: yin sun [mailto:sun...@gm...] Sent: Wednesday, August 14, 2013 9:07 PM To: Pukitis Martins (LQLA RD) Cc: col...@li... Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages these two are not duplicate packets, they have different src MAC and TTL is decremented. to me, looks like the host bridge is playing tricks to prevent something. Can you associate each src MAC to the virtual device. On Wed, Aug 14, 2013 at 12:46 AM, <Mar...@la...> wrote: > I run sniffer (wireshark) on the PC. The duplicated packets are also received by an application in coLinux. > Both packets (separated by protocol for simplicity): > 1st: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000319001589 0800 > IP: 4500002400000000ff113780c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > Ethernet (trailer): 00000000000000000000 > > 2nd: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000a5e63ab14 0800 > IP: 4500002400000000fe113880c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > > -----Original Message----- > From: yin sun [mailto:sun...@gm...] > Sent: Tuesday, August 13, 2013 6:51 PM > To: Pukitis Martins (LQLA RD) > Cc: col...@li... > Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates > packages > > where do you run the packet sniffer. can you paste the exact duplicated packet's headers. > > > On Tue, Aug 13, 2013 at 5:15 AM, <Mar...@la...> wrote: >> I've set up a bridge to access LAN from coLinux, like described in >> >> http://colinux.wikia.com/wiki/Network#WinPcap >> >> >> >> by adding this line to the coLinux configuration file: >> >> eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 >> >> >> >> Now every packet from LAN to coLinux is duplicated. First packet has >> source MAC address of sender, second - source MAC address of "Local >> Area Connection 2". Packets from coLinux to LAN are not duplicated. How to fix it? >> >> >> >> >> --------------------------------------------------------------------- >> - >> -------- Get 100% visibility into Java/.NET code with AppDynamics >> Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg. >> c lktrk _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: <Mar...@la...> - 2013-08-14 19:28:06
|
First packet has source MAC address of sender, second - source MAC address of "Local Area Connection 2". Sender is another host on LAN that is on "Local Area Connection 2" network adapter. "Local Area Connection 2" is a physical Ethernet adapter connection. -----Original Message----- From: yin sun [mailto:sun...@gm...] Sent: Wednesday, August 14, 2013 9:07 PM To: Pukitis Martins (LQLA RD) Cc: col...@li... Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages these two are not duplicate packets, they have different src MAC and TTL is decremented. to me, looks like the host bridge is playing tricks to prevent something. Can you associate each src MAC to the virtual device. On Wed, Aug 14, 2013 at 12:46 AM, <Mar...@la...> wrote: > I run sniffer (wireshark) on the PC. The duplicated packets are also received by an application in coLinux. > Both packets (separated by protocol for simplicity): > 1st: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000319001589 0800 > IP: 4500002400000000ff113780c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > Ethernet (trailer): 00000000000000000000 > > 2nd: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000a5e63ab14 0800 > IP: 4500002400000000fe113880c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > > -----Original Message----- > From: yin sun [mailto:sun...@gm...] > Sent: Tuesday, August 13, 2013 6:51 PM > To: Pukitis Martins (LQLA RD) > Cc: col...@li... > Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates > packages > > where do you run the packet sniffer. can you paste the exact duplicated packet's headers. > > > On Tue, Aug 13, 2013 at 5:15 AM, <Mar...@la...> wrote: >> I've set up a bridge to access LAN from coLinux, like described in >> >> http://colinux.wikia.com/wiki/Network#WinPcap >> >> >> >> by adding this line to the coLinux configuration file: >> >> eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 >> >> >> >> Now every packet from LAN to coLinux is duplicated. First packet has >> source MAC address of sender, second - source MAC address of "Local >> Area Connection 2". Packets from coLinux to LAN are not duplicated. How to fix it? >> >> >> >> >> --------------------------------------------------------------------- >> - >> -------- Get 100% visibility into Java/.NET code with AppDynamics >> Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg. >> c lktrk _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> |
From: yin s. <sun...@gm...> - 2013-08-14 18:07:37
|
these two are not duplicate packets, they have different src MAC and TTL is decremented. to me, looks like the host bridge is playing tricks to prevent something. Can you associate each src MAC to the virtual device. On Wed, Aug 14, 2013 at 12:46 AM, <Mar...@la...> wrote: > I run sniffer (wireshark) on the PC. The duplicated packets are also received by an application in coLinux. > Both packets (separated by protocol for simplicity): > 1st: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000319001589 0800 > IP: 4500002400000000ff113780c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > Ethernet (trailer): 00000000000000000000 > > 2nd: > Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000a5e63ab14 0800 > IP: 4500002400000000fe113880c0a8017ec0a8017a > UDP header: 177217720010038c > UDP data: 0900400400000011 > > -----Original Message----- > From: yin sun [mailto:sun...@gm...] > Sent: Tuesday, August 13, 2013 6:51 PM > To: Pukitis Martins (LQLA RD) > Cc: col...@li... > Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages > > where do you run the packet sniffer. can you paste the exact duplicated packet's headers. > > > On Tue, Aug 13, 2013 at 5:15 AM, <Mar...@la...> wrote: >> I've set up a bridge to access LAN from coLinux, like described in >> >> http://colinux.wikia.com/wiki/Network#WinPcap >> >> >> >> by adding this line to the coLinux configuration file: >> >> eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 >> >> >> >> Now every packet from LAN to coLinux is duplicated. First packet has >> source MAC address of sender, second - source MAC address of "Local >> Area Connection 2". Packets from coLinux to LAN are not duplicated. How to fix it? >> >> >> >> >> ---------------------------------------------------------------------- >> -------- Get 100% visibility into Java/.NET code with AppDynamics >> Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.c >> lktrk _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> |
From: <Mar...@la...> - 2013-08-14 07:46:18
|
I run sniffer (wireshark) on the PC. The duplicated packets are also received by an application in coLinux. Both packets (separated by protocol for simplicity): 1st: Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000319001589 0800 IP: 4500002400000000ff113780c0a8017ec0a8017a UDP header: 177217720010038c UDP data: 0900400400000011 Ethernet (trailer): 00000000000000000000 2nd: Ethernet (dst MAC, src MAC and type): 000a5e63ab15 000a5e63ab14 0800 IP: 4500002400000000fe113880c0a8017ec0a8017a UDP header: 177217720010038c UDP data: 0900400400000011 -----Original Message----- From: yin sun [mailto:sun...@gm...] Sent: Tuesday, August 13, 2013 6:51 PM To: Pukitis Martins (LQLA RD) Cc: col...@li... Subject: Re: [coLinux-users] winpcap bridge with coLinux duplicates packages where do you run the packet sniffer. can you paste the exact duplicated packet's headers. On Tue, Aug 13, 2013 at 5:15 AM, <Mar...@la...> wrote: > I've set up a bridge to access LAN from coLinux, like described in > > http://colinux.wikia.com/wiki/Network#WinPcap > > > > by adding this line to the coLinux configuration file: > > eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 > > > > Now every packet from LAN to coLinux is duplicated. First packet has > source MAC address of sender, second - source MAC address of "Local > Area Connection 2". Packets from coLinux to LAN are not duplicated. How to fix it? > > > > > ---------------------------------------------------------------------- > -------- Get 100% visibility into Java/.NET code with AppDynamics > Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.c > lktrk _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: yin s. <sun...@gm...> - 2013-08-13 15:51:49
|
where do you run the packet sniffer. can you paste the exact duplicated packet's headers. On Tue, Aug 13, 2013 at 5:15 AM, <Mar...@la...> wrote: > I’ve set up a bridge to access LAN from coLinux, like described in > > http://colinux.wikia.com/wiki/Network#WinPcap > > > > by adding this line to the coLinux configuration file: > > eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 > > > > Now every packet from LAN to coLinux is duplicated. First packet has source > MAC address of sender, second – source MAC address of „Local Area Connection > 2”. Packets from coLinux to LAN are not duplicated. How to fix it? > > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: <Mar...@la...> - 2013-08-13 12:15:14
|
I've set up a bridge to access LAN from coLinux, like described in http://colinux.wikia.com/wiki/Network#WinPcap by adding this line to the coLinux configuration file: eth2=pcap-bridge,"Local Area Connection 2",00:0A:5E:63:AB:15 Now every packet from LAN to coLinux is duplicated. First packet has source MAC address of sender, second - source MAC address of "Local Area Connection 2". Packets from coLinux to LAN are not duplicated. How to fix it? |
From: Kevin H. <har...@ya...> - 2013-06-17 21:17:28
|
wtbx http://thurstongroves.boblimaradio.com/bniykfw/wda/fowr/cgij.htm Kevin Hardiek kzoi |
From: George P B. <geo...@gm...> - 2013-04-19 20:40:29
|
Or boot QEMU to an very sparse in memory 'disk' and local loop back mount the colinux image then switch (chroot?) to it... On 4/3/2013 6:22 PM, Henry Nestler wrote: > coLinux image files have no partion sectors. That means coLinux is a raw > copy from single partition of disk, like "/dev/sda1". > Qemu uses raw disk image from whole disk, partition table sectors plus > data sectors, like "/dev/sda". > > To use a coLinux image you need to add some sectors on top fot partion > table informations (32256 bytes, as I ave seen in Qemu wiki > http://en.wikibooks.org/wiki/QEMU/Images#Mounting_an_image_on_the_host). |
From: Shao M. <sha...@gm...> - 2013-04-14 16:40:58
|
The Syslinux boot-loader will happily boot under QEmu without an MBR. - Shao _____ From: Robert Irvin [mailto:and...@ho...] Sent: Monday, April 08, 2013 08:53 To: Shao Miller; 'Nabi K.A.Z.' Cc: 'colinux' Subject: Re: [coLinux-users] Is there any way to boot the .img file ofcolinux by another virtualization software? If you get this it will be a miracle, lots of my messages disappear. The problem i always had booting like this was the lack of partition table in the image prevented it working. Colinux specifies partition image in config while qemu usually specifies a disk. My method, for creating images for use in colinux, was to boot and install to a normal qemu disk in qemu. i would then mount an empty colinux disk in the image, format and dd the filesystem. As you are attempting the opposite, i would use an existing qemu image from the web to mount a blank qemu disk and a blank colinux image. Partition the new qemu disk, format and then dd/cp colinux install to it. |
From: Robert I. <and...@ho...> - 2013-04-08 12:39:09
|
If you get this it will be a miracle, lots of my messages disappear. The problem i always had booting like this was the lack of partition table in the image prevented it working. Colinux specifies partition image in config while qemu usually specifies a disk. My method, for creating images for use in colinux, was to boot and install to a normal qemu disk in qemu. i would then mount an empty colinux disk in the image, format and dd the filesystem. As you are attempting the opposite, i would use an existing qemu image from the web to mount a blank qemu disk and a blank colinux image. Partition the new qemu disk, format and then dd/cp colinux install to it. |
From: Robert I. <and...@ho...> - 2013-04-08 12:38:52
|
If you get this it will be a miracle, lots of my messages disappear. The problem i always had booting like this was the lack of partition table in the image prevented it working. Colinux specifies partition image in config while qemu usually specifies a disk. My method, for creating images for use in colinux, was to boot and install to a normal qemu disk in qemu. i would then mount an empty colinux disk in the image, format and dd the filesystem. As you are attempting the opposite, i would use an existing qemu image from the web to mount a blank qemu disk and a blank colinux image. Partition the new qemu disk, format and then dd/cp colinux install to it. |
From: Shao M. <sha...@gm...> - 2013-04-06 23:50:05
|
If you install Syslinux to the filesystem image, it should be bootable in QEmu. I'm pretty sure I have done this, before. - Shao ________________________________________ From: Henry Nestler [mailto:hen...@ar...] Sent: Wednesday, April 03, 2013 19:22 To: Nabi K.A.Z. Cc: colinux Subject: Re: [coLinux-users] Is there any way to boot the .img file of colinux by another virtualization software? Hello, coLinux image files have no partion sectors. That means coLinux is a raw copy from single partition of disk, like "/dev/sda1". Qemu uses raw disk image from whole disk, partition table sectors plus data sectors, like "/dev/sda". To use a coLinux image you need to add some sectors on top fot partion table informations (32256 bytes, as I ave seen in Qemu wiki http://en.wikibooks.org/wiki/QEMU/Images#Mounting_an_image_on_the_host). Henry Nabi K.A.Z. wrote: I have a CentOS on a .img file, I try run it with QEMU, but get me this error: Boot from Hard Disk 0 failed FATAL: Not a bootable disk Please help me. On Wed, Apr 3, 2013 at 3:54 PM, Paolo Minazzi <pao...@gm...> wrote: Yes, a filesystem can be used for other virtualization programs. The only problem are the kernel modules that have to be related to your new real kernel, not related to colinux kernel. Paolo On Wed, Apr 3, 2013 at 6:03 AM, Shao Miller <sha...@gm...> wrote: > As far as I know, it's simply a filesystem image, so yes, it can be booted > by using QEmu + Syslinux, for example. The kernel will have to be a > non-coLinux kernel (try to match the coLinux kernel version as closely as > possible) and any coLinux-specific drivers (or kernel modules) could not be > expected to make sense in such an environment. I'm pretty sure I > "dual-booted" the coLinux Fedora in this way. - Shao > > ________________________________________ > From: Nabi K.A.Z. [mailto:na...@gm...] > Sent: Tuesday, April 02, 2013 10:18 > To: col...@li... > Subject: [coLinux-users] Is there any way to boot the .img file of colinux > by another virtualization software? > > Hi, > Is there any way to boot the .img file of colinux by another virtualization > software? > > > ---------------------------------------------------------------------------- -- > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users ________________________________________ ---------------------------------------------------------------------------- -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ________________________________________ _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Henry N. <hen...@ar...> - 2013-04-03 23:22:33
|
Hello, coLinux image files have no partion sectors. That means coLinux is a raw copy from single partition of disk, like "/dev/sda1". Qemu uses raw disk image from whole disk, partition table sectors plus data sectors, like "/dev/sda". To use a coLinux image you need to add some sectors on top fot partion table informations (32256 bytes, as I ave seen in Qemu wiki http://en.wikibooks.org/wiki/QEMU/Images#Mounting_an_image_on_the_host). Henry Nabi K.A.Z. wrote: > I have a CentOS on a .img file, I try run it with QEMU, but get me > this error: > Boot from Hard Disk 0 failed > FATAL: Not a bootable disk > > Please help me. > > > > On Wed, Apr 3, 2013 at 3:54 PM, Paolo Minazzi <pao...@gm... > <mailto:pao...@gm...>> wrote: > > Yes, a filesystem can be used for other virtualization programs. > The only problem are the kernel modules that have to be related to > your new real kernel, not related to colinux kernel. > Paolo > > On Wed, Apr 3, 2013 at 6:03 AM, Shao Miller <sha...@gm... > <mailto:sha...@gm...>> wrote: > > As far as I know, it's simply a filesystem image, so yes, it can > be booted > > by using QEmu + Syslinux, for example. The kernel will have to be a > > non-coLinux kernel (try to match the coLinux kernel version as > closely as > > possible) and any coLinux-specific drivers (or kernel modules) > could not be > > expected to make sense in such an environment. I'm pretty sure I > > "dual-booted" the coLinux Fedora in this way. - Shao > > > > ________________________________________ > > From: Nabi K.A.Z. [mailto:na...@gm... > <mailto:na...@gm...>] > > Sent: Tuesday, April 02, 2013 10:18 > > To: col...@li... > <mailto:col...@li...> > > Subject: [coLinux-users] Is there any way to boot the .img file > of colinux > > by another virtualization software? > > > > Hi, > > Is there any way to boot the .img file of colinux by another > virtualization > > software? > > > > > > > ------------------------------------------------------------------------------ > > Minimize network downtime and maximize team effectiveness. > > Reduce network management and security costs.Learn how to hire > > the most talented Cisco Certified professionals. Visit the > > Employer Resources Portal > > http://www.cisco.com/web/learning/employer_resources/index.html > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > <mailto:coL...@li...> > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > ------------------------------------------------------------------------ > > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Alexander K. <Alexander@Kriegisch.name> - 2013-04-03 18:56:35
|
Can you be any more off topic?!? And can somebody please stop that guy? Alexander Kriegisch Am 03.04.2013 um 20:43 schrieb "Nabi K.A.Z." <na...@gm...>: > I have a CentOS on a .img file, I try run it with QEMU, but get me this error: > Boot from Hard Disk 0 failed > FATAL: Not a bootable disk > > Please help me. |
From: Nabi K.A.Z. <na...@gm...> - 2013-04-03 18:43:49
|
I have a CentOS on a .img file, I try run it with QEMU, but get me this error: Boot from Hard Disk 0 failed FATAL: Not a bootable disk Please help me. On Wed, Apr 3, 2013 at 3:54 PM, Paolo Minazzi <pao...@gm...>wrote: > Yes, a filesystem can be used for other virtualization programs. > The only problem are the kernel modules that have to be related to > your new real kernel, not related to colinux kernel. > Paolo > > On Wed, Apr 3, 2013 at 6:03 AM, Shao Miller <sha...@gm...> wrote: > > As far as I know, it's simply a filesystem image, so yes, it can be > booted > > by using QEmu + Syslinux, for example. The kernel will have to be a > > non-coLinux kernel (try to match the coLinux kernel version as closely as > > possible) and any coLinux-specific drivers (or kernel modules) could not > be > > expected to make sense in such an environment. I'm pretty sure I > > "dual-booted" the coLinux Fedora in this way. - Shao > > > > ________________________________________ > > From: Nabi K.A.Z. [mailto:na...@gm...] > > Sent: Tuesday, April 02, 2013 10:18 > > To: col...@li... > > Subject: [coLinux-users] Is there any way to boot the .img file of > colinux > > by another virtualization software? > > > > Hi, > > Is there any way to boot the .img file of colinux by another > virtualization > > software? > > > > > > > ------------------------------------------------------------------------------ > > Minimize network downtime and maximize team effectiveness. > > Reduce network management and security costs.Learn how to hire > > the most talented Cisco Certified professionals. Visit the > > Employer Resources Portal > > http://www.cisco.com/web/learning/employer_resources/index.html > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Paolo M. <pao...@gm...> - 2013-04-03 11:24:43
|
Yes, a filesystem can be used for other virtualization programs. The only problem are the kernel modules that have to be related to your new real kernel, not related to colinux kernel. Paolo On Wed, Apr 3, 2013 at 6:03 AM, Shao Miller <sha...@gm...> wrote: > As far as I know, it's simply a filesystem image, so yes, it can be booted > by using QEmu + Syslinux, for example. The kernel will have to be a > non-coLinux kernel (try to match the coLinux kernel version as closely as > possible) and any coLinux-specific drivers (or kernel modules) could not be > expected to make sense in such an environment. I'm pretty sure I > "dual-booted" the coLinux Fedora in this way. - Shao > > ________________________________________ > From: Nabi K.A.Z. [mailto:na...@gm...] > Sent: Tuesday, April 02, 2013 10:18 > To: col...@li... > Subject: [coLinux-users] Is there any way to boot the .img file of colinux > by another virtualization software? > > Hi, > Is there any way to boot the .img file of colinux by another virtualization > software? > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Shao M. <sha...@gm...> - 2013-04-03 04:03:51
|
As far as I know, it's simply a filesystem image, so yes, it can be booted by using QEmu + Syslinux, for example. The kernel will have to be a non-coLinux kernel (try to match the coLinux kernel version as closely as possible) and any coLinux-specific drivers (or kernel modules) could not be expected to make sense in such an environment. I'm pretty sure I "dual-booted" the coLinux Fedora in this way. - Shao ________________________________________ From: Nabi K.A.Z. [mailto:na...@gm...] Sent: Tuesday, April 02, 2013 10:18 To: col...@li... Subject: [coLinux-users] Is there any way to boot the .img file of colinux by another virtualization software? Hi, Is there any way to boot the .img file of colinux by another virtualization software? |
From: yin s. <sun...@gm...> - 2013-04-02 16:03:11
|
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/building?revision=1596&view=markup On Tue, Apr 2, 2013 at 1:20 AM, Nabi K.A.Z. <na...@gm...> wrote: > Hi, > I try to compile colinux on debian, but after compile I have .exe files. > How can I run it inside debian? > > > On Thu, Mar 7, 2013 at 9:31 AM, yin sun <sun...@gm...> wrote: > >> the colinux running on linux has no practical usage as I can see. If >> you really wants to try, you have to download dev source code and >> build by yourselves. >> the host has to be 32bit. debian is the version I used to test, other >> version would also work. the key is the host kernel version shouldn't >> be too much different. By default you have to build a modified version >> of fltk as the colinux terminal, this implies xmode on host. >> >> >> On Wed, Mar 6, 2013 at 5:50 PM, Nabi K.A.Z. <na...@gm...> wrote: >> > Hi, >> > Thanks, I thinks coLinux just run on windows, I dont know can run on >> other >> > linux distribution. >> > I try debian. >> > 1. the debian does must be 32 or 64 bit? >> > 2. is it download link?, and must be install from source? >> > >> http://sourceforge.net/projects/colinux/files/coLinux-stable/0.7.9-linux-2.6.33.7/coLinux-0.7.9-src.tar.gz/download >> > 3. can I run colinux on other linux distribution? >> > 5. do sure must use X mode? or can run coLinux via command line? >> > >> > Thanks again. >> > Nabi >> > >> > On Thu, Mar 7, 2013 at 2:28 AM, yin sun <sun...@gm...> wrote: >> >> >> >> I don't have such luxury. If you are so determined to run colinux. you >> >> can debian in virtualbox and run colinux inside debian. >> >> >> >> On Mon, Mar 4, 2013 at 11:30 PM, Nabi K.A.Z. <na...@gm...> >> wrote: >> >> > Hi, >> >> > >> >> > I have windows server 2008 64-bit, I know can not install colinux on >> it, >> >> > so >> >> > I install VirtualBox, and I install a windows 2003 32-bit in it. >> then I >> >> > install colinux on windows 2003 32-bit success. But, now when I run a >> >> > virtual centOS on it, open cmd and get me this: >> >> > PID: 1316 >> >> > colinux: booting >> >> > >> >> > And no more! and then the virtual machine freez ! >> >> > >> >> > Please help me about resolve it or say me any way for run coLinux on >> my >> >> > windows. >> >> > >> >> > Thanks >> >> > Nabi >> >> > >> >> > >> >> > >> >> > >> ------------------------------------------------------------------------------ >> >> > Everyone hates slow websites. So do we. >> >> > Make your web apps faster with AppDynamics >> >> > Download AppDynamics Lite for free today: >> >> > http://p.sf.net/sfu/appdyn_d2d_feb >> >> > _______________________________________________ >> >> > coLinux-users mailing list >> >> > coL...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> > >> > >> > >> > > |
From: Nabi K.A.Z. <na...@gm...> - 2013-04-02 14:18:27
|
Hi, Is there any way to boot the .img file of colinux by another virtualization software? |
From: Nabi K.A.Z. <na...@gm...> - 2013-03-05 07:31:18
|
Hi, I have windows server 2008 64-bit, I know can not install colinux on it, so I install VirtualBox, and I install a windows 2003 32-bit in it. then I install colinux on windows 2003 32-bit success. But, now when I run a virtual centOS on it, open cmd and get me this: PID: 1316 colinux: booting And no more! and then the virtual machine freez ! Please help me about resolve it or say me any way for run coLinux on my windows. Thanks Nabi |