Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: SourceForge.net <no...@so...> - 2013-02-18 04:15:07
|
Feature Requests item #2891618, was opened at 2009-11-03 18:11 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2891618&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: Next Release (example) Status: Closed Priority: 5 Private: No Submitted By: Peter Kuznetsov (peter_kuznetsov) Assigned to: Nobody/Anonymous (nobody) Summary: Driver name as parameter Initial Comment: For debuging purposes it will be very usefull to add options for changing driver name instead of linux.sys. Example: colinux-daemon.exe --remove-driver-name colinux-0.80-00.sys colinux-daemon.exe --install-driver-name colinux-0.80-01.sys ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2013-02-17 20:14 Message: Hey, buddy, I've not discovered the way to subscribe [url=http://www.baginjp.com/]??? ??[/url] <a href="http://www.baginjp.com/" title="??? ??">??? ??</a> ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2011-02-06 12:34 Message: This would not need. A colinux.sys must close to the same colinux-daemon.exe. So, hold any versions of coLinux in a separate directory, and you can do: cd .../coLinux-0.8.x colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver cd .../coLinux-0.8.y colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver It's very simple and I'm using this way for long time with multiple of coLinux versions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2891618&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2013-02-13 14:53:54
|
Bugs item #3509641, was opened at 2012-03-21 02:28 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=3509641&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Linux Kernel Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Grnch (grnch) Assigned to: Nobody/Anonymous (nobody) Summary: rmdir on cofs returns success but the dir is not deleted Initial Comment: I shared a local NTFS disk through cofs (host is XP) and then I mounted it from inside the Linux image with the following mount options: noattrib,nocache,uid=foo,gid=foo,fmask=0644 Then I navigate to the mounted cofs dir create a non-empty dir, e.g. mkdir foo echo bar > foo/bar If I try to delete this dir with rmdir, instead of getting an error that the dir is non-empty, I get success but the dir still remains. rmdir foo Of course, "rm -r foo" will get rid of the dir, but the problem is that the rmdir() system call doesn't return an error for non-empty dirs, which confuses some software when using cofs shares from coLinux (notably CVS). coLinux version is: 2.6.33.5-co-0.7.9-r1547 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2013-02-13 06:53 Message: I0MRwi <a href="http://wcqmxiiwerha.com/">wcqmxiiwerha</a>, [url=http://denikxgcppzo.com/]denikxgcppzo[/url], [link=http://ckcomjqzpyan.com/]ckcomjqzpyan[/link], http://gbcviceubziq.com/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=3509641&group_id=98788 |
|
From: Dave (Bob) <da...@bo...> - 2013-02-02 19:27:43
|
I got the impression from the coLinux 64 bit wiki that the major problem was the difference in sizes of variables between the Windows 64 bit ABI and the Linux 64 bit ABI. I wonder whether the new x32 ABI in Linux, which is supported by gcc, makes this situation any different? It changes some things which were 64 bits wide to being 32 bits wide. I haven't studied this, but just maybe the Windows and Linux 64 bit worlds begin to align better? However, the 32 bit CoLinux seems to be a bit stagnant, based on references to kernel versions being back in the 2.6.x days. (We are up to 3.8 now). Maybe the problem is that 64 bit was looking difficult, and 32 bit was disappearing, so the whole project has stumbled? I hope not. David |
|
From: yin s. <sun...@gm...> - 2013-02-02 17:37:40
|
Maybe the funding is not enough, there is significant technical challenge here. A 64bit device driver call for a windows kernel developer. A 64bit linux kernel/windows context switcher call for an x86-64 assembly developer. /Yin On Sat, Feb 2, 2013 at 5:57 AM, Fernando Botelho <fer...@f1...> wrote: > I can try to look for funding for this. Can anyone give me an idea of > how much I should look for? Off list if need be. > > Fernando > > > On 02/02/2013 10:52 AM, Tobbe Lundberg wrote: >> I agree, a 64 version is really needed! I really hope someone can make >> that happen :) >> >> //Tobbe >> >> On Sat, Feb 2, 2013 at 12:38 PM, Dave (Bob) <da...@bo...> wrote: >>> I am very interested in CoLinux, both the 32 bit version, and the 64 bit >>> version that is discussed at: >>> >>> http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux >>> >>> Obviously the 64 bit version is becoming increasingly necessary. >>> >>> I note that references to kernel versions are looking a bit dated >>> (2.6.x), and that traffic on this developers site is sparse. >>> >>> Is there still the enthusiastic support for CoLinux that I think it >>> deserves? >>> >>> Regards, >>> David >>> >>> >>> ------------------------------------------------------------------------------ >>> 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_jan >>> _______________________________________________ >>> coLinux-devel mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> >> ------------------------------------------------------------------------------ >> 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_jan >> _______________________________________________ >> coLinux-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> >> > > ------------------------------------------------------------------------------ > 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_jan > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Fernando B. <fer...@f1...> - 2013-02-02 14:24:11
|
I can try to look for funding for this. Can anyone give me an idea of how much I should look for? Off list if need be. Fernando On 02/02/2013 10:52 AM, Tobbe Lundberg wrote: > I agree, a 64 version is really needed! I really hope someone can make > that happen :) > > //Tobbe > > On Sat, Feb 2, 2013 at 12:38 PM, Dave (Bob) <da...@bo...> wrote: >> I am very interested in CoLinux, both the 32 bit version, and the 64 bit >> version that is discussed at: >> >> http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux >> >> Obviously the 64 bit version is becoming increasingly necessary. >> >> I note that references to kernel versions are looking a bit dated >> (2.6.x), and that traffic on this developers site is sparse. >> >> Is there still the enthusiastic support for CoLinux that I think it >> deserves? >> >> Regards, >> David >> >> >> ------------------------------------------------------------------------------ >> 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_jan >> _______________________________________________ >> coLinux-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel > > ------------------------------------------------------------------------------ > 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_jan > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Tobbe L. <to...@tl...> - 2013-02-02 13:17:47
|
I agree, a 64 version is really needed! I really hope someone can make that happen :) //Tobbe On Sat, Feb 2, 2013 at 12:38 PM, Dave (Bob) <da...@bo...> wrote: > I am very interested in CoLinux, both the 32 bit version, and the 64 bit > version that is discussed at: > > http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux > > Obviously the 64 bit version is becoming increasingly necessary. > > I note that references to kernel versions are looking a bit dated > (2.6.x), and that traffic on this developers site is sparse. > > Is there still the enthusiastic support for CoLinux that I think it > deserves? > > Regards, > David > > > ------------------------------------------------------------------------------ > 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_jan > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Dave (Bob) <da...@bo...> - 2013-02-02 11:38:16
|
I am very interested in CoLinux, both the 32 bit version, and the 64 bit version that is discussed at: http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux Obviously the 64 bit version is becoming increasingly necessary. I note that references to kernel versions are looking a bit dated (2.6.x), and that traffic on this developers site is sparse. Is there still the enthusiastic support for CoLinux that I think it deserves? Regards, David |
|
From: Fernando B. <fer...@f1...> - 2012-12-13 12:17:01
|
Hi everyone, My name is Fernando Botelho and I am responsible for F123 (http://F123.org/en), a project that enhances educational and employment opportunities for the blind in developing countries through FOSS and training. I have recently learned about CoLinux, which would help us with a number of important challenges we face, but the 3 volunteers helping me with that are facing all kinds of problems and I was hoping someone from this list might be able to help. Our objective is to have an EXE file that installs F123 (which is based on Ubuntu 12.10 using Gnome Fallback) on a Windows 7 machine. As this GUI is not a default option on ubuntu 12.10, here is more info https://wiki.ubuntu.com/UbuntuGNOME/ReleaseNotes/12.10 A fourth developer is helping build the new version of F123 using live-build, but the 3 focused on the CoLinux challenge are using a pre-configured CoLinux version of ubuntu or Xubuntu with 12.04 or something, and are trying to upgrade to 12.10 + Gnome Fallback, and getting all kinds of errors. I am not the technical guy in all this, I am just the one that best speaks English. I was hoping someone could point the way either to create a CoLinux Ubuntu 12.10 with Gnome Fallback using live-build or some BASH script. Upgrading an older version just generates errors with the sound and other packages, which for the blind are quite important. Thanks, Fernando |
|
From: SourceForge.net <no...@so...> - 2012-12-07 06:46:43
|
Bugs item #2890857, was opened at 2009-11-02 10:32 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Peter Kuznetsov (peter_kuznetsov) Assigned to: Nobody/Anonymous (nobody) Summary: SCSI: Kernel panic - "response: use_sg (2) > 1" Initial Comment: Summary. ======= Version 0.8.0 with kernel 2.6.25.20: ... Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods ... scsi1: unhandled opcode: 51 ... Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! Version 0.8.0 with kernel 2.6.22.18: Version 0.7.5: Version 0.7.4: ... scsi1: unhandled opcode: 5a scsi1: unhandled opcode: 51 ... (System continue working) Version 0.7.3: Version 0.7.2: Don't work. Some details. ============ File "run.bat": -------------- set COLINUX_CONSOLE_FONT=Lucida Console:12 set COLINUX_CONSOLE_EXIT_ON_DETACH=1 colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver colinux-daemon.exe @config.cfg -v 3 -t nt colinux-daemon.exe --remove-driver File "config.cfg": ---------------- cocon=160x79 mem=512 kernel=vmlinux initrd=initrd.gz # Flat part of vmdk (with MBR) scsi0=disk,"Debian-5.0.3-KDE-00.flat" scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat" # flat part of vmdk scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso" root=/dev/sda1 ro eth0=slirp File "/etc/fstab" (without editing after installation): ---------------- # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/sda1 / ext3 errors=remount-ro 0 1 /dev/sdb1 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 In whole system after installation I've edited only one file "/etc/X11/default-display-manager": #/usr/bin/kdm echo "null" > /etc/X11/default-display-manager Relevant output. =============== Version 0.8.0 with kernel 2.6.25.20 (kernel panic): -------------------------------------------------- scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:2:0: CD-ROM coLinux COCD 1.01 PQ: 0 ANSI: 2 Driver 'sd' needs updating - please use bus_type methods <----------------------PK!!! sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sdb: sdb1 sd 0:0:1:0: [sdb] Attached SCSI disk Driver 'sr' needs updating - please use bus_type methods <----------------------PK!!! sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:2:0: Attached scsi CD-ROM sr0 ... scsi2: unhandled opcode: 51 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:1:0: Attached scsi generic sg1 type 0 sr 0:0:2:0: Attached scsi generic sg2 type 5 scsi2: unhandled opcode: 51 ... Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!! colinux: Linux VM terminated colinux: Kernel panic: COSCSI: response: use_sg (2) > 1! console: Monitor3116: Detached Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver Cooperative Linux Daemon, 0.8.0 Daemon compiled on Sun Sep 27 12:50:20 2009 ============================================================================ Version 0.8.0 with kernel 2.6.22.18 (working): --------------------------------------------- scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:2:0: CD-ROM coLinux COCD 1.01 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sdb: sdb1 sd 0:0:1:0: [sdb] Attached SCSI disk sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:2:0: Attached scsi CD-ROM sr0 ....................................... scsi2: unhandled opcode: 51 <-------------------PK!!! sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:1:0: Attached scsi generic sg1 type 0 sr 0:0:2:0: Attached scsi generic sg2 type 5 ....................................... scsi2: unhandled opcode: 5a <-------------------PK!!! scsi2: unhandled opcode: 51 scsi2: unhandled opcode: 51 scsi2: unhandled opcode: 5a scsi2: unhandled opcode: 5a ... sd 0:0:1:0: [sdb] Synchronizing SCSI cache sd 0:0:0:0: [sda] Synchronizing SCSI cache =============================================================================== If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. Many thanks for very usefull system!!! With best regards, Peter. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2012-12-06 22:46 Message: Whats up this is somewhat of off topic but I was wanting to know if blogs use WYSIWYG editors or if you have to manually code with HTML. I'm starting a blog soon but have no coding expertise so I wanted to get advice from someone with experience. Any help would be greatly appreciated! north face osito jacket http://www.suryoye.nu/blogs/entry/north-face-pink-ribbon-jacket-though-costlier ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2012-11-03 17:49 Message: Hey there just wanted to give you a quick heads up. The text in your post seem to be running off the screen in Ie. I'm not sure if this is a format issue or something to do with internet browser compatibility but I figured I'd post to let you know. The style and design look great though! Hope you get the issue resolved soon. Thanks north face jackets cheap http://northfacemetropolisenhanced.webspawner.com/blog/1021264-north-face-apex-bionic-womens-the-fruition-of-my-love-for-colour/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-06 13:30 Message: SVN revisions r1282 fixed this bug in Kernel 2.6.25.20, and r1284 in 2.6.22.18. ---------------------------------------------------------------------- Comment By: Peter Kuznetsov (peter_kuznetsov) Date: 2009-11-03 13:39 Message: Henry, I close this tracker and will wait for next autobuild with kernel 2.6.25.20 (it is closer to 2.6.26.2, which is used in Debian 5.0.3). With many thanks, Peter. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-03 12:58 Message: The warnings Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods are harmless. The Bug at COSCSI: response: use_sg (2) > 1! is more a real problem. There a variable has two buffers, but the caller of function only should fill a single buffer, and the function can only run with a single buffer. If that bug line was triggered, then something is real wrong. I will try to replace the "panic" into a "warning". So we would see the stack backtrace from callers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2012-11-10 23:28:02
|
Bugs item #3291398, was opened at 2011-04-22 04:30 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=3291398&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Linux Kernel Group: v0.7.x (release) Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Gilles Casse (gcasse) Assigned to: Nobody/Anonymous (nobody) Summary: /dev/ttySx: " Device or resource busy" Initial Comment: Using simultaneously two serial devices appears to be not possible (colinux 0.7.9). For example below, ttyS0 or ttyS1 can be read, but if ttyS0 is being read, then ttyS1 is considererd as busy. root@colinux:~# cat /dev/ttyS0 ^C root@colinux:~# cat /dev/ttyS1 ^C root@colinux:~# cat /dev/ttyS0& [1] 2618 root@colinux:~# cat /dev/ttyS1 cat: /dev/ttyS1: Device or resource busy root@colinux:~# dmesg -c COSERIAL: unable to get irq 3 cocd: close no attached struct ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2012-11-10 15:28 Message: Fantastic blog! Do you have any hints for aspiring writers? I'm planning to start my own blog soon but I'm a little lost on everything. Would you propose starting with a free platform like Wordpress or go for a paid option? There are so many choices out there that I'm completely confused .. Any recommendations? Cheers! north face outlet http://zqlqbcnbrk.webnode.com/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2011-05-04 14:30 Message: Thanks! Patch committed to SVN as revision 1584 (branch devel). ---------------------------------------------------------------------- Comment By: Gilles Casse (gcasse) Date: 2011-05-04 05:48 Message: The attached patch enables the use of several serial devices (ttySx) (diff from coserial.c, rev svn 1545, kernel 2.6.33.7). The whole coserial.c file is also attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=3291398&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2012-11-04 00:49:12
|
Bugs item #2890857, was opened at 2009-11-02 10:32 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Peter Kuznetsov (peter_kuznetsov) Assigned to: Nobody/Anonymous (nobody) Summary: SCSI: Kernel panic - "response: use_sg (2) > 1" Initial Comment: Summary. ======= Version 0.8.0 with kernel 2.6.25.20: ... Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods ... scsi1: unhandled opcode: 51 ... Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! Version 0.8.0 with kernel 2.6.22.18: Version 0.7.5: Version 0.7.4: ... scsi1: unhandled opcode: 5a scsi1: unhandled opcode: 51 ... (System continue working) Version 0.7.3: Version 0.7.2: Don't work. Some details. ============ File "run.bat": -------------- set COLINUX_CONSOLE_FONT=Lucida Console:12 set COLINUX_CONSOLE_EXIT_ON_DETACH=1 colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver colinux-daemon.exe @config.cfg -v 3 -t nt colinux-daemon.exe --remove-driver File "config.cfg": ---------------- cocon=160x79 mem=512 kernel=vmlinux initrd=initrd.gz # Flat part of vmdk (with MBR) scsi0=disk,"Debian-5.0.3-KDE-00.flat" scsi1=disk,"O:\VIRT_DISK\VDISKS\swap_scsi_0.flat" # flat part of vmdk scsi2=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso" root=/dev/sda1 ro eth0=slirp File "/etc/fstab" (without editing after installation): ---------------- # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/sda1 / ext3 errors=remount-ro 0 1 /dev/sdb1 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 In whole system after installation I've edited only one file "/etc/X11/default-display-manager": #/usr/bin/kdm echo "null" > /etc/X11/default-display-manager Relevant output. =============== Version 0.8.0 with kernel 2.6.25.20 (kernel panic): -------------------------------------------------- scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:2:0: CD-ROM coLinux COCD 1.01 PQ: 0 ANSI: 2 Driver 'sd' needs updating - please use bus_type methods <----------------------PK!!! sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sdb: sdb1 sd 0:0:1:0: [sdb] Attached SCSI disk Driver 'sr' needs updating - please use bus_type methods <----------------------PK!!! sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:2:0: Attached scsi CD-ROM sr0 ... scsi2: unhandled opcode: 51 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:1:0: Attached scsi generic sg1 type 0 sr 0:0:2:0: Attached scsi generic sg2 type 5 scsi2: unhandled opcode: 51 ... Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! <-------------------PK!!! colinux: Linux VM terminated colinux: Kernel panic: COSCSI: response: use_sg (2) > 1! console: Monitor3116: Detached Q:\coLinux\$Debian\Debian\5.0.3-co-080_2.6.25.20>colinux-daemon.exe --remove-driver Cooperative Linux Daemon, 0.8.0 Daemon compiled on Sun Sep 27 12:50:20 2009 ============================================================================ Version 0.8.0 with kernel 2.6.22.18 (working): --------------------------------------------- scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:2:0: CD-ROM coLinux COCD 1.01 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:1:0: [sdb] 4194304 512-byte hardware sectors (2147 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 1f 00 10 08 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sdb: sdb1 sd 0:0:1:0: [sdb] Attached SCSI disk sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:2:0: Attached scsi CD-ROM sr0 ....................................... scsi2: unhandled opcode: 51 <-------------------PK!!! sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:1:0: Attached scsi generic sg1 type 0 sr 0:0:2:0: Attached scsi generic sg2 type 5 ....................................... scsi2: unhandled opcode: 5a <-------------------PK!!! scsi2: unhandled opcode: 51 scsi2: unhandled opcode: 51 scsi2: unhandled opcode: 5a scsi2: unhandled opcode: 5a ... sd 0:0:1:0: [sdb] Synchronizing SCSI cache sd 0:0:0:0: [sda] Synchronizing SCSI cache =============================================================================== If you need some additional testing of coLinux-0.8.0 with kernel 2.6.25.20, mail me, I can do it. Many thanks for very usefull system!!! With best regards, Peter. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2012-11-03 17:49 Message: Hey there just wanted to give you a quick heads up. The text in your post seem to be running off the screen in Ie. I'm not sure if this is a format issue or something to do with internet browser compatibility but I figured I'd post to let you know. The style and design look great though! Hope you get the issue resolved soon. Thanks north face jackets cheap http://northfacemetropolisenhanced.webspawner.com/blog/1021264-north-face-apex-bionic-womens-the-fruition-of-my-love-for-colour/ ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-06 13:30 Message: SVN revisions r1282 fixed this bug in Kernel 2.6.25.20, and r1284 in 2.6.22.18. ---------------------------------------------------------------------- Comment By: Peter Kuznetsov (peter_kuznetsov) Date: 2009-11-03 13:39 Message: Henry, I close this tracker and will wait for next autobuild with kernel 2.6.25.20 (it is closer to 2.6.26.2, which is used in Debian 5.0.3). With many thanks, Peter. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-03 12:58 Message: The warnings Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods are harmless. The Bug at COSCSI: response: use_sg (2) > 1! is more a real problem. There a variable has two buffers, but the caller of function only should fill a single buffer, and the function can only run with a single buffer. If that bug line was triggered, then something is real wrong. I will try to replace the "panic" into a "warning". So we would see the stack backtrace from callers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2890857&group_id=98788 |
|
From: n s. <nsc...@ya...> - 2012-10-16 16:12:53
|
I recommend the site: http://jadecom.net/work.group.google.php?fortune=jhuzuguwokyxjf |
|
From: yin s. <sun...@gm...> - 2012-09-28 00:42:24
|
I had thought about this. the two approaches we can learn from is lguest and paravirt. basically colinux could be another architecture in kernel tree on host and guest implement something similar to paravirt-ops. On Thu, Sep 27, 2012 at 4:47 PM, Shao Miller <sha...@gm...> wrote: > What is the Linux kernel upstream position on any coLinux changes getting > merged, or has there been any discussion about this? > > I'm sure some of the #ifndef CONFIG_COOPERATIVE changes might be considered > to spaghettify the code, but have alternative strategies been pondered or > proposed? > > - 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Shao M. <sha...@gm...> - 2012-09-27 23:47:38
|
What is the Linux kernel upstream position on any coLinux changes getting merged, or has there been any discussion about this? I'm sure some of the #ifndef CONFIG_COOPERATIVE changes might be considered to spaghettify the code, but have alternative strategies been pondered or proposed? - Shao |
|
From: Shao M. <sha...@gm...> - 2012-09-26 08:15:18
|
Did you ever find a strategy in regards to using i686-w64-mingw32 and the ntddk.h -> wdm.h #inclusion problem[1]? I'm now using a 32-bit Fedora 17 instead of a 64-bit Fedora 15 and trying 'make colinux'. - Shao [1] http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTikR1c9vBySfL7 CNu4JXmtVsLNGgThmmbuhhKYbv%40mail.gmail.com&forum_name=mingw-w64-public |
|
From: H. N. <hen...@ar...> - 2012-09-25 11:32:46
|
Forgotten to say: I used "quilt" for handling kernel patches. Henry ----- Original Nachricht ---- Von: "H. Nestler" <hen...@ar...> An: sha...@gm... Datum: 24.09.2012 20:18 Betreff: Re: [coLinux-devel] [coLinux-users] Porting a Kernel > You need the FLTK version that was supported by coLinux, and for the coLinux > under Linux you need a patched FLTK version (with a additional hook > function, see > http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/patch/fltk- > 1.1.10-linux-patch.diff). For simple build of coLinux it was better to have > our one FLTK, separated from system, which was known and configured with > minimalistic features with only used functions and only static lib, and > compatible to the source code. Often under /usr/local/... a newer FLTK > version was installed, and that mostly not works. FLTK has changed arguments > for function between major versions. > > So, if you have a running Cross compiler, just build the FLTK lib with > coLinux build process, and than build the daemons and FLTK-console. > > To build FLTK you needs to run "make libs" or bin/build-colinux-libs.sh > > Henry > > ----- Original Nachricht ---- > Von: Shao Miller <sha...@gm...> > An: 'yin sun' <sun...@gm...> > Datum: 24.09.2012 19:08 > Betreff: Re: [coLinux-devel] [coLinux-users] Porting a Kernel > > > Right. In my notes, you can see that I spoofed the build system into > using > > the MinGW that I already have. > > > > Although 'make download' downloaded a particular version of FLTK, > > apparently > > it didn't build it prior to the 'make colinux' business. I don't quite > > know > > why, as I suspect 'make colinux' is looking for <FL/Fl.H> wherever the > > downloaded package is supposed to be built. > > > > I had to laugh, though... When testing the kernel with coLinux > 0.7.8.1525, > > I realized that the Linux installation was x86_64, so I don't think > that'll > > work! I got some lines from the kernel when it tried to load the init > > program about a runaway loop for modprobing a particular binfmt, which I > > assume must've been because the init program was x86_64. > > > > - Shao > > > > ________________________________________ > > From: yin sun [mailto:sun...@gm...] > > Sent: Monday, September 24, 2012 12:08 > > To: Shao Miller > > Cc: col...@li... > > Subject: Re: [coLinux-users] Porting a Kernel > > > > no, you can just download a precompiled 0.7.10 colinux gz file from > Henry's > > page then replace the vmlinux to test. > > to compile fltk console, you need the mingw-gcc cross compilation tool > set. > > this is to compile a exe for windows. > > also, very likely you may need to compile a new device driver for windows > > with the new kernel later on. > > On Sun, Sep 23, 2012 at 11:05 PM, Shao Miller <sha...@gm...> > > wrote: > > Yes, well... > > > > I've got the following notes[1], which have allowed me to compile the > > 2.6.33.7-co-0.7.10 kernel using the tools from Fedora 15. I haven't > tested > > the kernel in coLinux yet. > > > > Right now I'm stuck trying to figure out why #include <FL/Fl.H> isn't > > working, when I certainly have /usr/include/FL/Fl.H. I suppose I don't > > really need to compile the rest of coLinux in order to test the kernel... > > Or maybe I do. > > > > - Shao > > > > [1] > > cd /usr/src/colinux-devel/colinux > > > > # Then edited ./configure so that: > > # > > # case $GCC_VERSION in > > # 4.5.*|4.3.*|4.2.*|4.1.*|4.0.*|3.4.*) > > > > ./configure > > make download > > > > # Then edited bin/build-common.sh so that: > > # > > # BINUTILS_VERSION="2.21" > > # GCC_VERSION="4.5.3" > > > > cd /usr/src/colinux-devel/mingw32 > > mkdir bin > > cd bin > > ln -s /usr/bin/i686-pc-mingw32-gcc i686-pc-mingw32-gcc > > ln -s /usr/bin/i686-pc-mingw32-ld i686-pc-mingw32-ld > > ln -s /usr/bin/i686-pc-mingw32-windres i686-pc-mingw32-windres > > ln -s /usr/bin/i686-pc-mingw32-strip i686-pc-mingw32-strip > > > > # Then edited > > /usr/src/colinux-devel/build/linux-2.6.33.7-source/arch/x86/vdso/Makefile > > so > > that: > > # > > # VDSO_LDFLAGS_vdso32.lds = -m32 -Wl,-soname=linux-gate.so.1 > > > > cd /usr/src/colinux-devel/colinux > > export CFLAGS=-Wno-unused-but-set-variable > > make > > > > ________________________________________ > > From: yin sun [mailto:sun...@gm...] > > Sent: Monday, September 24, 2012 00:17 > > To: Shao Miller > > Cc: col...@li... > > Subject: Re: [coLinux-users] Porting a Kernel > > > > and look at the error again, "error: parameter 'buffer' set but not used > > [-Werror=unused-but-set-parameter]" > > if you don't want to change gcc, maybe you can disable warning as error > > flag. and try again. > > On Sun, Sep 23, 2012 at 9:01 PM, yin sun <sun...@gm...> wrote: > > your error looks like a gcc problem. try use gcc 4.4 > > since we are building kernel program/device driver, the compiler > > version/flags is important. > > in this case, I think gcc 4.6 never been tested to work. > > > > On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...> > wrote: > > Thanks again. > > > > Here is my scenario: > > > > - Development system for building coLinux and coLinux kernel: Fedora 15 > > - GCC ver. 4.6.3 > > - MinGW GCC ver. 4.5.3 > > > > The 'make' process appears to wish to build particular versions of tools, > > but I don't quite understand why. Why is it that it cannot use whatever > > tools I have installed? After reading doc/building.txt, I still am not > > clear on why. > > > > I did download all of the particular versions via 'make download'. But > > when > > I run 'make', it fails to build the binutils-2.19.1 that was downloaded. > > There are a few errors[1], but "fixing" them would seem to be > out-of-scope > > for coLinux. So again, can I just use the tools that I have? I tried > > './configure --gcc-guest-build', but that didn't seem to do the trick. > > > > Thanks for your time, once more. > > > > - Shao > > > > [1] > > > > --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: > > In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: > > ../../binutils-2.19.1/libiberty/regex.c: In function > > byte_re_match_2_internal: > > ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable > > sdummy set but not used [-Wunused-but-set-variable] > > ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable > > pdummy set but not used [-Wunused-but-set-variable] > > ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips > > variable initialization [-Wjump-misses-init] > > ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label > > restore_best_regs defined here > > ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: same_str_p > > declared here > > ../../binutils-2.19.1/bfd/compress.c: In function > > 'bfd_uncompress_section_contents': > > ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' > set > > but not used [-Werror=unused-but-set-parameter] > > ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set > > but not used [-Werror=unused-but-set-parameter] > > cc1: all warnings being treated as errors > > make[5]: *** [compress.lo] Error 1 > > make[4]: *** [all-recursive] Error 1 > > make[3]: *** [all] Error 2 > > make[2]: *** [all-bfd] Error 2 > > make[1]: *** [all] Error 2 > > make binutils failed > > make: *** [cross] Error 1 > > > > ________________________________________ > > From: yin sun [mailto:sun...@gm...] > > Sent: Sunday, September 23, 2012 22:54 > > To: Shao Miller > > Subject: Re: [coLinux-users] Porting a Kernel > > > > patches are what colinux releases. the build process will download the > > original linux kernel code from the kernel official site first. > > once you download the svn devel branch. > > ./configure > > make > > will take care all of these. this topic should be discussed on dev > mailing > > list. > > 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-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > -- Gruss Henry --------------------------------------------------------- |
|
From: H. N. <hen...@ar...> - 2012-09-24 18:18:15
|
You need the FLTK version that was supported by coLinux, and for the coLinux under Linux you need a patched FLTK version (with a additional hook function, see http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/patch/fltk-1.1.10-linux-patch.diff). For simple build of coLinux it was better to have our one FLTK, separated from system, which was known and configured with minimalistic features with only used functions and only static lib, and compatible to the source code. Often under /usr/local/... a newer FLTK version was installed, and that mostly not works. FLTK has changed arguments for function between major versions. So, if you have a running Cross compiler, just build the FLTK lib with coLinux build process, and than build the daemons and FLTK-console. To build FLTK you needs to run "make libs" or bin/build-colinux-libs.sh Henry ----- Original Nachricht ---- Von: Shao Miller <sha...@gm...> An: 'yin sun' <sun...@gm...> Datum: 24.09.2012 19:08 Betreff: Re: [coLinux-devel] [coLinux-users] Porting a Kernel > Right. In my notes, you can see that I spoofed the build system into using > the MinGW that I already have. > > Although 'make download' downloaded a particular version of FLTK, > apparently > it didn't build it prior to the 'make colinux' business. I don't quite > know > why, as I suspect 'make colinux' is looking for <FL/Fl.H> wherever the > downloaded package is supposed to be built. > > I had to laugh, though... When testing the kernel with coLinux 0.7.8.1525, > I realized that the Linux installation was x86_64, so I don't think that'll > work! I got some lines from the kernel when it tried to load the init > program about a runaway loop for modprobing a particular binfmt, which I > assume must've been because the init program was x86_64. > > - Shao > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Monday, September 24, 2012 12:08 > To: Shao Miller > Cc: col...@li... > Subject: Re: [coLinux-users] Porting a Kernel > > no, you can just download a precompiled 0.7.10 colinux gz file from Henry's > page then replace the vmlinux to test. > to compile fltk console, you need the mingw-gcc cross compilation tool set. > this is to compile a exe for windows. > also, very likely you may need to compile a new device driver for windows > with the new kernel later on. > On Sun, Sep 23, 2012 at 11:05 PM, Shao Miller <sha...@gm...> > wrote: > Yes, well... > > I've got the following notes[1], which have allowed me to compile the > 2.6.33.7-co-0.7.10 kernel using the tools from Fedora 15. I haven't tested > the kernel in coLinux yet. > > Right now I'm stuck trying to figure out why #include <FL/Fl.H> isn't > working, when I certainly have /usr/include/FL/Fl.H. I suppose I don't > really need to compile the rest of coLinux in order to test the kernel... > Or maybe I do. > > - Shao > > [1] > cd /usr/src/colinux-devel/colinux > > # Then edited ./configure so that: > # > # case $GCC_VERSION in > # 4.5.*|4.3.*|4.2.*|4.1.*|4.0.*|3.4.*) > > ./configure > make download > > # Then edited bin/build-common.sh so that: > # > # BINUTILS_VERSION="2.21" > # GCC_VERSION="4.5.3" > > cd /usr/src/colinux-devel/mingw32 > mkdir bin > cd bin > ln -s /usr/bin/i686-pc-mingw32-gcc i686-pc-mingw32-gcc > ln -s /usr/bin/i686-pc-mingw32-ld i686-pc-mingw32-ld > ln -s /usr/bin/i686-pc-mingw32-windres i686-pc-mingw32-windres > ln -s /usr/bin/i686-pc-mingw32-strip i686-pc-mingw32-strip > > # Then edited > /usr/src/colinux-devel/build/linux-2.6.33.7-source/arch/x86/vdso/Makefile > so > that: > # > # VDSO_LDFLAGS_vdso32.lds = -m32 -Wl,-soname=linux-gate.so.1 > > cd /usr/src/colinux-devel/colinux > export CFLAGS=-Wno-unused-but-set-variable > make > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Monday, September 24, 2012 00:17 > To: Shao Miller > Cc: col...@li... > Subject: Re: [coLinux-users] Porting a Kernel > > and look at the error again, "error: parameter 'buffer' set but not used > [-Werror=unused-but-set-parameter]" > if you don't want to change gcc, maybe you can disable warning as error > flag. and try again. > On Sun, Sep 23, 2012 at 9:01 PM, yin sun <sun...@gm...> wrote: > your error looks like a gcc problem. try use gcc 4.4 > since we are building kernel program/device driver, the compiler > version/flags is important. > in this case, I think gcc 4.6 never been tested to work. > > On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...> wrote: > Thanks again. > > Here is my scenario: > > - Development system for building coLinux and coLinux kernel: Fedora 15 > - GCC ver. 4.6.3 > - MinGW GCC ver. 4.5.3 > > The 'make' process appears to wish to build particular versions of tools, > but I don't quite understand why. Why is it that it cannot use whatever > tools I have installed? After reading doc/building.txt, I still am not > clear on why. > > I did download all of the particular versions via 'make download'. But > when > I run 'make', it fails to build the binutils-2.19.1 that was downloaded. > There are a few errors[1], but "fixing" them would seem to be out-of-scope > for coLinux. So again, can I just use the tools that I have? I tried > './configure --gcc-guest-build', but that didn't seem to do the trick. > > Thanks for your time, once more. > > - Shao > > [1] > > --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: > In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: > ../../binutils-2.19.1/libiberty/regex.c: In function > byte_re_match_2_internal: > ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable > sdummy set but not used [-Wunused-but-set-variable] > ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable > pdummy set but not used [-Wunused-but-set-variable] > ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips > variable initialization [-Wjump-misses-init] > ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label > restore_best_regs defined here > ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: same_str_p > declared here > ../../binutils-2.19.1/bfd/compress.c: In function > 'bfd_uncompress_section_contents': > ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' set > but not used [-Werror=unused-but-set-parameter] > ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set > but not used [-Werror=unused-but-set-parameter] > cc1: all warnings being treated as errors > make[5]: *** [compress.lo] Error 1 > make[4]: *** [all-recursive] Error 1 > make[3]: *** [all] Error 2 > make[2]: *** [all-bfd] Error 2 > make[1]: *** [all] Error 2 > make binutils failed > make: *** [cross] Error 1 > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Sunday, September 23, 2012 22:54 > To: Shao Miller > Subject: Re: [coLinux-users] Porting a Kernel > > patches are what colinux releases. the build process will download the > original linux kernel code from the kernel official site first. > once you download the svn devel branch. > ./configure > make > will take care all of these. this topic should be discussed on dev mailing > list. > 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > -- Gruss Henry --------------------------------------------------------- |
|
From: Shao M. <sha...@gm...> - 2012-09-24 17:08:58
|
Right. In my notes, you can see that I spoofed the build system into using the MinGW that I already have. Although 'make download' downloaded a particular version of FLTK, apparently it didn't build it prior to the 'make colinux' business. I don't quite know why, as I suspect 'make colinux' is looking for <FL/Fl.H> wherever the downloaded package is supposed to be built. I had to laugh, though... When testing the kernel with coLinux 0.7.8.1525, I realized that the Linux installation was x86_64, so I don't think that'll work! I got some lines from the kernel when it tried to load the init program about a runaway loop for modprobing a particular binfmt, which I assume must've been because the init program was x86_64. - Shao ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Monday, September 24, 2012 12:08 To: Shao Miller Cc: col...@li... Subject: Re: [coLinux-users] Porting a Kernel no, you can just download a precompiled 0.7.10 colinux gz file from Henry's page then replace the vmlinux to test. to compile fltk console, you need the mingw-gcc cross compilation tool set. this is to compile a exe for windows. also, very likely you may need to compile a new device driver for windows with the new kernel later on. On Sun, Sep 23, 2012 at 11:05 PM, Shao Miller <sha...@gm...> wrote: Yes, well... I've got the following notes[1], which have allowed me to compile the 2.6.33.7-co-0.7.10 kernel using the tools from Fedora 15. I haven't tested the kernel in coLinux yet. Right now I'm stuck trying to figure out why #include <FL/Fl.H> isn't working, when I certainly have /usr/include/FL/Fl.H. I suppose I don't really need to compile the rest of coLinux in order to test the kernel... Or maybe I do. - Shao [1] cd /usr/src/colinux-devel/colinux # Then edited ./configure so that: # # case $GCC_VERSION in # 4.5.*|4.3.*|4.2.*|4.1.*|4.0.*|3.4.*) ./configure make download # Then edited bin/build-common.sh so that: # # BINUTILS_VERSION="2.21" # GCC_VERSION="4.5.3" cd /usr/src/colinux-devel/mingw32 mkdir bin cd bin ln -s /usr/bin/i686-pc-mingw32-gcc i686-pc-mingw32-gcc ln -s /usr/bin/i686-pc-mingw32-ld i686-pc-mingw32-ld ln -s /usr/bin/i686-pc-mingw32-windres i686-pc-mingw32-windres ln -s /usr/bin/i686-pc-mingw32-strip i686-pc-mingw32-strip # Then edited /usr/src/colinux-devel/build/linux-2.6.33.7-source/arch/x86/vdso/Makefile so that: # # VDSO_LDFLAGS_vdso32.lds = -m32 -Wl,-soname=linux-gate.so.1 cd /usr/src/colinux-devel/colinux export CFLAGS=-Wno-unused-but-set-variable make ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Monday, September 24, 2012 00:17 To: Shao Miller Cc: col...@li... Subject: Re: [coLinux-users] Porting a Kernel and look at the error again, "error: parameter 'buffer' set but not used [-Werror=unused-but-set-parameter]" if you don't want to change gcc, maybe you can disable warning as error flag. and try again. On Sun, Sep 23, 2012 at 9:01 PM, yin sun <sun...@gm...> wrote: your error looks like a gcc problem. try use gcc 4.4 since we are building kernel program/device driver, the compiler version/flags is important. in this case, I think gcc 4.6 never been tested to work. On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...> wrote: Thanks again. Here is my scenario: - Development system for building coLinux and coLinux kernel: Fedora 15 - GCC ver. 4.6.3 - MinGW GCC ver. 4.5.3 The 'make' process appears to wish to build particular versions of tools, but I don't quite understand why. Why is it that it cannot use whatever tools I have installed? After reading doc/building.txt, I still am not clear on why. I did download all of the particular versions via 'make download'. But when I run 'make', it fails to build the binutils-2.19.1 that was downloaded. There are a few errors[1], but "fixing" them would seem to be out-of-scope for coLinux. So again, can I just use the tools that I have? I tried './configure --gcc-guest-build', but that didn't seem to do the trick. Thanks for your time, once more. - Shao [1] --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: ../../binutils-2.19.1/libiberty/regex.c: In function byte_re_match_2_internal: ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable sdummy set but not used [-Wunused-but-set-variable] ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable pdummy set but not used [-Wunused-but-set-variable] ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips variable initialization [-Wjump-misses-init] ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label restore_best_regs defined here ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: same_str_p declared here ../../binutils-2.19.1/bfd/compress.c: In function 'bfd_uncompress_section_contents': ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' set but not used [-Werror=unused-but-set-parameter] ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set but not used [-Werror=unused-but-set-parameter] cc1: all warnings being treated as errors make[5]: *** [compress.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-bfd] Error 2 make[1]: *** [all] Error 2 make binutils failed make: *** [cross] Error 1 ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Sunday, September 23, 2012 22:54 To: Shao Miller Subject: Re: [coLinux-users] Porting a Kernel patches are what colinux releases. the build process will download the original linux kernel code from the kernel official site first. once you download the svn devel branch. ./configure make will take care all of these. this topic should be discussed on dev mailing list. 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 |
|
From: yin s. <sun...@gm...> - 2012-09-24 16:08:21
|
no, you can just download a precompiled 0.7.10 colinux gz file from Henry's page then replace the vmlinux to test. to compile fltk console, you need the mingw-gcc cross compilation tool set. this is to compile a exe for windows. also, very likely you may need to compile a new device driver for windows with the new kernel later on. On Sun, Sep 23, 2012 at 11:05 PM, Shao Miller <sha...@gm...> wrote: > Yes, well... > > I've got the following notes[1], which have allowed me to compile the > 2.6.33.7-co-0.7.10 kernel using the tools from Fedora 15. I haven't tested > the kernel in coLinux yet. > > Right now I'm stuck trying to figure out why #include <FL/Fl.H> isn't > working, when I certainly have /usr/include/FL/Fl.H. I suppose I don't > really need to compile the rest of coLinux in order to test the kernel... > Or maybe I do. > > - Shao > > [1] > cd /usr/src/colinux-devel/colinux > > # Then edited ./configure so that: > # > # case $GCC_VERSION in > # 4.5.*|4.3.*|4.2.*|4.1.*|4.0.*|3.4.*) > > ./configure > make download > > # Then edited bin/build-common.sh so that: > # > # BINUTILS_VERSION="2.21" > # GCC_VERSION="4.5.3" > > cd /usr/src/colinux-devel/mingw32 > mkdir bin > cd bin > ln -s /usr/bin/i686-pc-mingw32-gcc i686-pc-mingw32-gcc > ln -s /usr/bin/i686-pc-mingw32-ld i686-pc-mingw32-ld > ln -s /usr/bin/i686-pc-mingw32-windres i686-pc-mingw32-windres > ln -s /usr/bin/i686-pc-mingw32-strip i686-pc-mingw32-strip > > # Then edited > /usr/src/colinux-devel/build/linux-2.6.33.7-source/arch/x86/vdso/Makefile > so > that: > # > # VDSO_LDFLAGS_vdso32.lds = -m32 -Wl,-soname=linux-gate.so.1 > > cd /usr/src/colinux-devel/colinux > export CFLAGS=-Wno-unused-but-set-variable > make > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Monday, September 24, 2012 00:17 > To: Shao Miller > Cc: col...@li... > Subject: Re: [coLinux-users] Porting a Kernel > > and look at the error again, "error: parameter 'buffer' set but not used > [-Werror=unused-but-set-parameter]" > if you don't want to change gcc, maybe you can disable warning as error > flag. and try again. > On Sun, Sep 23, 2012 at 9:01 PM, yin sun <sun...@gm...> wrote: > your error looks like a gcc problem. try use gcc 4.4 > since we are building kernel program/device driver, the compiler > version/flags is important. > in this case, I think gcc 4.6 never been tested to work. > > On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...> > wrote: > Thanks again. > > Here is my scenario: > > - Development system for building coLinux and coLinux kernel: Fedora 15 > - GCC ver. 4.6.3 > - MinGW GCC ver. 4.5.3 > > The 'make' process appears to wish to build particular versions of tools, > but I don't quite understand why. Why is it that it cannot use whatever > tools I have installed? After reading doc/building.txt, I still am not > clear on why. > > I did download all of the particular versions via 'make download'. But > when > I run 'make', it fails to build the binutils-2.19.1 that was downloaded. > There are a few errors[1], but "fixing" them would seem to be out-of-scope > for coLinux. So again, can I just use the tools that I have? I tried > './configure --gcc-guest-build', but that didn't seem to do the trick. > > Thanks for your time, once more. > > - Shao > > [1] > > --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: > In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: > ../../binutils-2.19.1/libiberty/regex.c: In function > ‘byte_re_match_2_internal’: > ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable > ‘sdummy’ set but not used [-Wunused-but-set-variable] > ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable > ‘pdummy’ set but not used [-Wunused-but-set-variable] > ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips > variable initialization [-Wjump-misses-init] > ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label > ‘restore_best_regs’ defined here > ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: ‘same_str_p’ > declared here > ../../binutils-2.19.1/bfd/compress.c: In function > 'bfd_uncompress_section_contents': > ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' set > but not used [-Werror=unused-but-set-parameter] > ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set > but not used [-Werror=unused-but-set-parameter] > cc1: all warnings being treated as errors > make[5]: *** [compress.lo] Error 1 > make[4]: *** [all-recursive] Error 1 > make[3]: *** [all] Error 2 > make[2]: *** [all-bfd] Error 2 > make[1]: *** [all] Error 2 > make binutils failed > make: *** [cross] Error 1 > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Sunday, September 23, 2012 22:54 > To: Shao Miller > Subject: Re: [coLinux-users] Porting a Kernel > > patches are what colinux releases. the build process will download the > original linux kernel code from the kernel official site first. > once you download the svn devel branch. > ./configure > make > will take care all of these. this topic should be discussed on dev mailing > list. > 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 > > > > > > |
|
From: Shao M. <sha...@gm...> - 2012-09-24 06:05:48
|
Yes, well... I've got the following notes[1], which have allowed me to compile the 2.6.33.7-co-0.7.10 kernel using the tools from Fedora 15. I haven't tested the kernel in coLinux yet. Right now I'm stuck trying to figure out why #include <FL/Fl.H> isn't working, when I certainly have /usr/include/FL/Fl.H. I suppose I don't really need to compile the rest of coLinux in order to test the kernel... Or maybe I do. - Shao [1] cd /usr/src/colinux-devel/colinux # Then edited ./configure so that: # # case $GCC_VERSION in # 4.5.*|4.3.*|4.2.*|4.1.*|4.0.*|3.4.*) ./configure make download # Then edited bin/build-common.sh so that: # # BINUTILS_VERSION="2.21" # GCC_VERSION="4.5.3" cd /usr/src/colinux-devel/mingw32 mkdir bin cd bin ln -s /usr/bin/i686-pc-mingw32-gcc i686-pc-mingw32-gcc ln -s /usr/bin/i686-pc-mingw32-ld i686-pc-mingw32-ld ln -s /usr/bin/i686-pc-mingw32-windres i686-pc-mingw32-windres ln -s /usr/bin/i686-pc-mingw32-strip i686-pc-mingw32-strip # Then edited /usr/src/colinux-devel/build/linux-2.6.33.7-source/arch/x86/vdso/Makefile so that: # # VDSO_LDFLAGS_vdso32.lds = -m32 -Wl,-soname=linux-gate.so.1 cd /usr/src/colinux-devel/colinux export CFLAGS=-Wno-unused-but-set-variable make ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Monday, September 24, 2012 00:17 To: Shao Miller Cc: col...@li... Subject: Re: [coLinux-users] Porting a Kernel and look at the error again, "error: parameter 'buffer' set but not used [-Werror=unused-but-set-parameter]" if you don't want to change gcc, maybe you can disable warning as error flag. and try again. On Sun, Sep 23, 2012 at 9:01 PM, yin sun <sun...@gm...> wrote: your error looks like a gcc problem. try use gcc 4.4 since we are building kernel program/device driver, the compiler version/flags is important. in this case, I think gcc 4.6 never been tested to work. On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...> wrote: Thanks again. Here is my scenario: - Development system for building coLinux and coLinux kernel: Fedora 15 - GCC ver. 4.6.3 - MinGW GCC ver. 4.5.3 The 'make' process appears to wish to build particular versions of tools, but I don't quite understand why. Why is it that it cannot use whatever tools I have installed? After reading doc/building.txt, I still am not clear on why. I did download all of the particular versions via 'make download'. But when I run 'make', it fails to build the binutils-2.19.1 that was downloaded. There are a few errors[1], but "fixing" them would seem to be out-of-scope for coLinux. So again, can I just use the tools that I have? I tried './configure --gcc-guest-build', but that didn't seem to do the trick. Thanks for your time, once more. - Shao [1] --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: ../../binutils-2.19.1/libiberty/regex.c: In function byte_re_match_2_internal: ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable sdummy set but not used [-Wunused-but-set-variable] ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable pdummy set but not used [-Wunused-but-set-variable] ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips variable initialization [-Wjump-misses-init] ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label restore_best_regs defined here ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: same_str_p declared here ../../binutils-2.19.1/bfd/compress.c: In function 'bfd_uncompress_section_contents': ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' set but not used [-Werror=unused-but-set-parameter] ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set but not used [-Werror=unused-but-set-parameter] cc1: all warnings being treated as errors make[5]: *** [compress.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-bfd] Error 2 make[1]: *** [all] Error 2 make binutils failed make: *** [cross] Error 1 ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Sunday, September 23, 2012 22:54 To: Shao Miller Subject: Re: [coLinux-users] Porting a Kernel patches are what colinux releases. the build process will download the original linux kernel code from the kernel official site first. once you download the svn devel branch. ./configure make will take care all of these. this topic should be discussed on dev mailing list. 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 |
|
From: yin s. <sun...@gm...> - 2012-09-24 04:17:04
|
and look at the error again, "error: parameter 'buffer' set but not used [-Werror=unused-but-set-parameter]" if you don't want to change gcc, maybe you can disable warning as error flag. and try again. On Sun, Sep 23, 2012 at 9:01 PM, yin sun <sun...@gm...> wrote: > your error looks like a gcc problem. try use gcc 4.4 > since we are building kernel program/device driver, the compiler > version/flags is important. > in this case, I think gcc 4.6 never been tested to work. > > > On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...>wrote: > >> Thanks again. >> >> Here is my scenario: >> >> - Development system for building coLinux and coLinux kernel: Fedora 15 >> - GCC ver. 4.6.3 >> - MinGW GCC ver. 4.5.3 >> >> The 'make' process appears to wish to build particular versions of tools, >> but I don't quite understand why. Why is it that it cannot use whatever >> tools I have installed? After reading doc/building.txt, I still am not >> clear on why. >> >> I did download all of the particular versions via 'make download'. But >> when >> I run 'make', it fails to build the binutils-2.19.1 that was downloaded. >> There are a few errors[1], but "fixing" them would seem to be out-of-scope >> for coLinux. So again, can I just use the tools that I have? I tried >> './configure --gcc-guest-build', but that didn't seem to do the trick. >> >> Thanks for your time, once more. >> >> - Shao >> >> [1] >> >> --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: >> In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: >> ../../binutils-2.19.1/libiberty/regex.c: In function >> ‘byte_re_match_2_internal’: >> ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable >> ‘sdummy’ set but not used [-Wunused-but-set-variable] >> ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable >> ‘pdummy’ set but not used [-Wunused-but-set-variable] >> ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips >> variable initialization [-Wjump-misses-init] >> ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label >> ‘restore_best_regs’ defined here >> ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: ‘same_str_p’ >> declared here >> ../../binutils-2.19.1/bfd/compress.c: In function >> 'bfd_uncompress_section_contents': >> ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' >> set >> but not used [-Werror=unused-but-set-parameter] >> ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set >> but not used [-Werror=unused-but-set-parameter] >> cc1: all warnings being treated as errors >> make[5]: *** [compress.lo] Error 1 >> make[4]: *** [all-recursive] Error 1 >> make[3]: *** [all] Error 2 >> make[2]: *** [all-bfd] Error 2 >> make[1]: *** [all] Error 2 >> make binutils failed >> make: *** [cross] Error 1 >> >> ________________________________________ >> From: yin sun [mailto:sun...@gm...] >> Sent: Sunday, September 23, 2012 22:54 >> To: Shao Miller >> Subject: Re: [coLinux-users] Porting a Kernel >> >> patches are what colinux releases. the build process will download the >> original linux kernel code from the kernel official site first. >> once you download the svn devel branch. >> ./configure >> make >> will take care all of these. this topic should be discussed on dev mailing >> list. >> 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 >> >> >> >> > |
|
From: yin s. <sun...@gm...> - 2012-09-24 04:02:24
|
your error looks like a gcc problem. try use gcc 4.4 since we are building kernel program/device driver, the compiler version/flags is important. in this case, I think gcc 4.6 never been tested to work. On Sun, Sep 23, 2012 at 8:47 PM, Shao Miller <sha...@gm...> wrote: > Thanks again. > > Here is my scenario: > > - Development system for building coLinux and coLinux kernel: Fedora 15 > - GCC ver. 4.6.3 > - MinGW GCC ver. 4.5.3 > > The 'make' process appears to wish to build particular versions of tools, > but I don't quite understand why. Why is it that it cannot use whatever > tools I have installed? After reading doc/building.txt, I still am not > clear on why. > > I did download all of the particular versions via 'make download'. But > when > I run 'make', it fails to build the binutils-2.19.1 that was downloaded. > There are a few errors[1], but "fixing" them would seem to be out-of-scope > for coLinux. So again, can I just use the tools that I have? I tried > './configure --gcc-guest-build', but that didn't seem to do the trick. > > Thanks for your time, once more. > > - Shao > > [1] > > --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: > In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: > ../../binutils-2.19.1/libiberty/regex.c: In function > ‘byte_re_match_2_internal’: > ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable > ‘sdummy’ set but not used [-Wunused-but-set-variable] > ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable > ‘pdummy’ set but not used [-Wunused-but-set-variable] > ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips > variable initialization [-Wjump-misses-init] > ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label > ‘restore_best_regs’ defined here > ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: ‘same_str_p’ > declared here > ../../binutils-2.19.1/bfd/compress.c: In function > 'bfd_uncompress_section_contents': > ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' set > but not used [-Werror=unused-but-set-parameter] > ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set > but not used [-Werror=unused-but-set-parameter] > cc1: all warnings being treated as errors > make[5]: *** [compress.lo] Error 1 > make[4]: *** [all-recursive] Error 1 > make[3]: *** [all] Error 2 > make[2]: *** [all-bfd] Error 2 > make[1]: *** [all] Error 2 > make binutils failed > make: *** [cross] Error 1 > > ________________________________________ > From: yin sun [mailto:sun...@gm...] > Sent: Sunday, September 23, 2012 22:54 > To: Shao Miller > Subject: Re: [coLinux-users] Porting a Kernel > > patches are what colinux releases. the build process will download the > original linux kernel code from the kernel official site first. > once you download the svn devel branch. > ./configure > make > will take care all of these. this topic should be discussed on dev mailing > list. > 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 > > > > |
|
From: Shao M. <sha...@gm...> - 2012-09-24 03:47:47
|
Thanks again. Here is my scenario: - Development system for building coLinux and coLinux kernel: Fedora 15 - GCC ver. 4.6.3 - MinGW GCC ver. 4.5.3 The 'make' process appears to wish to build particular versions of tools, but I don't quite understand why. Why is it that it cannot use whatever tools I have installed? After reading doc/building.txt, I still am not clear on why. I did download all of the particular versions via 'make download'. But when I run 'make', it fails to build the binutils-2.19.1 that was downloaded. There are a few errors[1], but "fixing" them would seem to be out-of-scope for coLinux. So again, can I just use the tools that I have? I tried './configure --gcc-guest-build', but that didn't seem to do the trick. Thanks for your time, once more. - Shao [1] --- ERROR LOG /usr/src/colinux-devel/log/build-colinux-25679.err: In file included from ../../binutils-2.19.1/libiberty/regex.c:638:0: ../../binutils-2.19.1/libiberty/regex.c: In function byte_re_match_2_internal: ../../binutils-2.19.1/libiberty/regex.c:7141:27: warning: variable sdummy set but not used [-Wunused-but-set-variable] ../../binutils-2.19.1/libiberty/regex.c:7140:22: warning: variable pdummy set but not used [-Wunused-but-set-variable] ../../binutils-2.19.1/libiberty/regex.c:7476:5: warning: jump skips variable initialization [-Wjump-misses-init] ../../binutils-2.19.1/libiberty/regex.c:5952:12: note: label restore_best_regs defined here ../../binutils-2.19.1/libiberty/regex.c:5913:16: note: same_str_p declared here ../../binutils-2.19.1/bfd/compress.c: In function 'bfd_uncompress_section_contents': ../../binutils-2.19.1/bfd/compress.c:54:45: error: parameter 'buffer' set but not used [-Werror=unused-but-set-parameter] ../../binutils-2.19.1/bfd/compress.c:54:68: error: parameter 'size' set but not used [-Werror=unused-but-set-parameter] cc1: all warnings being treated as errors make[5]: *** [compress.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-bfd] Error 2 make[1]: *** [all] Error 2 make binutils failed make: *** [cross] Error 1 ________________________________________ From: yin sun [mailto:sun...@gm...] Sent: Sunday, September 23, 2012 22:54 To: Shao Miller Subject: Re: [coLinux-users] Porting a Kernel patches are what colinux releases. the build process will download the original linux kernel code from the kernel official site first. once you download the svn devel branch. ./configure make will take care all of these. this topic should be discussed on dev mailing list. 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 |
|
From: yin s. <sun...@gm...> - 2012-08-23 02:26:39
|
performance of colinux is for sure much greater than UML. In theory, for a 32bit x86 cpu colinux should be faster than any other VMs (virtualbox, vmware etc) I see many reasons why no binaries, 1. lack of demand, hence developer frequently neglect the compatibility when introducing new code, and this breaks the compilation 2. requires rebuild for each host kernel level. 3. colinux only works in 32bit mode ... /yin On Wed, Aug 22, 2012 at 12:29 PM, me sdkie <me...@gm...> wrote: > > > On Wed, Aug 22, 2012 at 11:30 PM, yin sun <sun...@gm...> wrote: > >> colinux can also run under 32bit linux even though the main purpose is >> for colinux is to run linux inside of windows. >> >> @yin sun- If we are able to get the performance of colinux greater than > UML then probably we have better chance to go upstream. > Have you compared those ? > And If it is also supporting running under Linux why binaries are not > available on website? > |
|
From: me s. <me...@gm...> - 2012-08-22 19:29:24
|
On Wed, Aug 22, 2012 at 11:30 PM, yin sun <sun...@gm...> wrote: > colinux can also run under 32bit linux even though the main purpose is for > colinux is to run linux inside of windows. > > @yin sun- If we are able to get the performance of colinux greater than UML then probably we have better chance to go upstream. Have you compared those ? And If it is also supporting running under Linux why binaries are not available on website? |
81 messages has been excluded from this view by a project administrator.
