You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Oscar U. <osc...@pr...> - 2007-09-07 18:03:05
|
Folks, I am attempting to install 0.6.4-linux-2.6.11 with Debian Etch[*1] accordin= g to the wiki instructions[*2] on WinXp Pro[*3]. I used fltk console invoke= d from cmd.exe after starting the colinux service. I was able to get most o= f the way with "Install the base system", then selected linux-image-2.6-686= at 79% complete. A little later I am prompted for "Configuring popularity-= contest" install option which said, "The system may anonymously supply the = distribution developers with statistics about the most used packages on thi= s system...." I switched to virtual console 1, and issued the mknod command= s to create /target/dev/cobd[0123] block device nodes, and modified /target= /etc/fstab. In virtual screen 4, I observed the final lines as follows. The= n responding either "Yes" or "No" results in the colinux-daemon crashing wi= thout completing the base system install (additional backtrace included bel= ow in dpkg.log), at this point the fltk windows console process would detac= h.=20 I can boot via the image it does create, but the image represents an incomp= lete install, e.g. some /etc/init.d/ scripts will not run (/etc/init.d/ssh = start =3D> 'Warning: Fake start-stop-daemon called, doing nothing'), user a= ccounts are not created (root password not set). The default.colinux.xml I = used for the daemon is included below. I can ssh into the installed image. = Any ideas how to correct or complete a good install? Thanks, OSC in-target: Building dependency tree... in-target:=20 in-target: Suggested packages: in-target: anacron in-target: Recommended packages: in-target: exim4 mail-transport-agent mime-construct in-target: The following NEW packages will be installed: in-target: popularity-contest .... <?xml version=3D"1.0" encoding=3D"UTF-8"?> <colinux> <block_device index=3D"0" path=3D"\DosDevices\c:\coLinux\root.fs" enabl= ed=3D"true" /> <block_device index=3D"1" path=3D"\DosDevices\c:\coLinux\swap_device" e= nabled=3D"true" /> <block_device index=3D"2" path=3D"\DosDevices\c:\coLinux\debian-40r1-i3= 86-businesscard.iso" enabled=3D"true" /> <block_device index=3D"3" path=3D"\DosDevices\c:\coLinux\debian-40r1-in= itrd" enabled=3D"true" /> <bootparams>root=3D/dev/cobd2</bootparams> <initrd path=3D"debian-40r1-initrd.gz" /> <image path=3D"vmlinux" /> <memory size=3D"512" /> <network index=3D"0" type=3D"tap"/> <network index=3D"1" name=3D"Local Area Connection" type=3D"bridged" /> </colinux> [*1] http://cdimage.debian.org/debian-cd/4.0_r1/i386/iso-cd/ debian-40r1-i3= 86-businesscard.iso [*2] http://colinux.wikia.com/wiki/InstallDebianFromIsoShort [*3] WinXp Pro Version 5.1 (Build 2600.xpsp_sp2_qfe.070227-2300 : Service P= ack 2) Additional log info : debian:/var/log# cat dmesg Linux version 2.6.11-co-0.6.4 (george@CoDebianDevel) (gcc version 3.4.4 200= 50314 (prerelease) (Debian 3.4.3-13)) #1 Mon Jun 19 05:36:13 UTC 2006 512MB LOWMEM available. initrd enabled: start: 0xdfe07000 size: 0x001f812b) On node 0 totalpages: 131072 DMA zone: 0 pages, LIFO batch:1 Normal zone: 131072 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: root=3D/dev/cobd0 Initializing CPU#0 Setting proxy interrupt vectors PID hash table entries: 4096 (order: 12, 65536 bytes) Using cooperative for high-res timesource Console: colour CoCON 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 513536k/524288k available (1537k kernel code, 0k reserved, 521k dat= a, 108k init, 0k highmem) Calibrating delay loop... 548.86 BogoMIPS (lpj=3D2744320) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000= e3bd 00000000 00000001 CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000e= 3bd 00000000 00000001 monitor/mwait feature present. using mwait in idle threads. CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU: After all inits, caps: bfebfbff 20100000 00000000 00000040 0000e3bd 00= 000000 00000001 CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz stepping 02 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. checking if image is initramfs...it isn't (no cpio magic); looks like an in= itrd Freeing initrd memory: 2016k freed NET: Registered protocol family 16 devfs: 2004-01-31 Richard Gooch (rg...@at...) devfs: boot_options: 0x0 cofuse init 0.1 (API version 2.2) Initializing Cryptographic API serio: cokbd at irq 1 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize cobd: loaded (max 32 devices) loop: loaded (max 8 devices) conet: loaded (max 16 devices) conet0: initialized conet1: initialized mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard on cokbd NET: Registered protocol family 2 IP: routing cache hash table of 4096 buckets, 32Kbytes TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 131072 bind 65536) NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 EXT2-fs warning: checktime reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiser= fs on cobd0 kjournald starting. Commit interval 5 seconds EXT3 FS on cobd0, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on cobd0, internal journal EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Trying to move old root to /initrd ... okay Freeing unused kernel memory: 108k freed kjournald starting. Commit interval 5 seconds Adding 524280k swap on /dev/cobd1. Priority:-1 extents:1 EXT3 FS on cobd0, internal journal debian:/var/log# tail -n 100 dpkg.log=20 2007-09-07 13:21:02 status unpacked initramfs-tools 0.85h 2007-09-07 13:21:02 status unpacked initramfs-tools 0.85h 2007-09-07 13:21:02 status half-configured initramfs-tools 0.85h 2007-09-07 13:21:02 status installed initramfs-tools 0.85h 2007-09-07 13:22:48 install linux-image-2.6.18-5-686 <none> 2.6.18.dfsg.1-13 2007-09-07 13:22:48 status half-installed linux-image-2.6.18-5-686 2.6.18.d= fsg.1-13 2007-09-07 13:22:52 status unpacked linux-image-2.6.18-5-686 2.6.18.dfsg.1-= 13 2007-09-07 13:22:52 status unpacked linux-image-2.6.18-5-686 2.6.18.dfsg.1-= 13 2007-09-07 13:22:52 install linux-image-2.6-686 <none> 2.6.18+6etch1 2007-09-07 13:22:52 status half-installed linux-image-2.6-686 2.6.18+6etch1 2007-09-07 13:22:52 status unpacked linux-image-2.6-686 2.6.18+6etch1 2007-09-07 13:22:52 status unpacked linux-image-2.6-686 2.6.18+6etch1 2007-09-07 13:22:52 status unpacked linux-image-2.6.18-5-686 2.6.18.dfsg.1-= 13 2007-09-07 13:22:52 status half-configured linux-image-2.6.18-5-686 2.6.18.= dfsg.1-13 2007-09-07 13:23:05 status installed linux-image-2.6.18-5-686 2.6.18.dfsg.1= -13 2007-09-07 13:23:05 status unpacked linux-image-2.6-686 2.6.18+6etch1 2007-09-07 13:23:05 status half-configured linux-image-2.6-686 2.6.18+6etch1 2007-09-07 13:23:05 status installed linux-image-2.6-686 2.6.18+6etch1 2007-09-07 13:23:14 install libc6-i686 <none> 2.3.6.ds1-13etch2 2007-09-07 13:23:14 status half-installed libc6-i686 2.3.6.ds1-13etch2 2007-09-07 13:23:14 status unpacked libc6-i686 2.3.6.ds1-13etch2 2007-09-07 13:23:14 status unpacked libc6-i686 2.3.6.ds1-13etch2 2007-09-07 13:23:14 status unpacked libc6-i686 2.3.6.ds1-13etch2 2007-09-07 13:23:14 status half-configured libc6-i686 2.3.6.ds1-13etch2 2007-09-07 13:23:14 status installed libc6-i686 2.3.6.ds1-13etch2 2007-09-07 13:23:16 install eject <none> 2.1.4-3 2007-09-07 13:23:16 status half-installed eject 2.1.4-3 2007-09-07 13:23:16 status unpacked eject 2.1.4-3 2007-09-07 13:23:16 status unpacked eject 2.1.4-3 2007-09-07 13:23:16 status unpacked eject 2.1.4-3 2007-09-07 13:23:16 status half-configured eject 2.1.4-3 2007-09-07 13:23:16 status installed eject 2.1.4-3 2007-09-07 13:41:08 install popularity-contest <none> 1.41 2007-09-07 13:41:08 status half-installed popularity-contest 1.41 2007-09-07 13:41:08 status unpacked popularity-contest 1.41 2007-09-07 13:41:08 status unpacked popularity-contest 1.41 2007-09-07 13:41:08 status unpacked popularity-contest 1.41 2007-09-07 13:41:08 status unpacked popularity-contest 1.41 2007-09-07 13:41:08 status half-configured popularity-contest 1.41 2007-09-07 13:41:08 status installed popularity-contest 1.41 2007-09-07 13:41:09 status installed popularity-contest 1.41 2007-09-07 13:41:09 remove popularity-contest 1.41 1.41 2007-09-07 13:41:09 status half-configured popularity-contest 1.41 2007-09-07 13:41:09 status half-installed popularity-contest 1.41 2007-09-07 13:41:09 status config-files popularity-contest 1.41 2007-09-07 13:41:09 purge popularity-contest 1.41 1.41 2007-09-07 13:41:09 status config-files popularity-contest 1.41 2007-09-07 13:41:09 status config-files popularity-contest 1.41 2007-09-07 13:41:09 status config-files popularity-contest 1.41 2007-09-07 13:41:09 status config-files popularity-contest 1.41 2007-09-07 13:41:09 status config-files popularity-contest 1.41 2007-09-07 13:41:09 status not-installed popularity-contest <none> 2007-09-07 13:50:08 install libkrb53 <none> 1.4.4-7etch4 2007-09-07 13:50:08 status half-installed libkrb53 1.4.4-7etch4 2007-09-07 13:50:08 status unpacked libkrb53 1.4.4-7etch4 2007-09-07 13:50:08 status unpacked libkrb53 1.4.4-7etch4 2007-09-07 13:50:08 install libedit2 <none> 2.9.cvs.20050518-2.2 2007-09-07 13:50:08 status half-installed libedit2 2.9.cvs.20050518-2.2 2007-09-07 13:50:08 status unpacked libedit2 2.9.cvs.20050518-2.2 2007-09-07 13:50:08 status unpacked libedit2 2.9.cvs.20050518-2.2 ---->> install/colinux daemon crashed here.... Booting into system allowed = me to install additional packages afterwards. 2007-09-07 13:50:08 install openssh-client <none> 1:4.3p2-9 2007-09-07 13:50:08 status half-installed openssh-client 1:4.3p2-9 2007-09-07 13:50:08 status unpacked openssh-client 1:4.3p2-9 2007-09-07 13:50:08 status unpacked openssh-client 1:4.3p2-9 2007-09-07 13:50:08 install openssh-server <none> 1:4.3p2-9 2007-09-07 13:50:08 status half-installed openssh-server 1:4.3p2-9 2007-09-07 13:50:09 status unpacked openssh-server 1:4.3p2-9 2007-09-07 13:50:09 status unpacked openssh-server 1:4.3p2-9 2007-09-07 13:50:09 status unpacked libkrb53 1.4.4-7etch4 2007-09-07 13:50:09 status half-configured libkrb53 1.4.4-7etch4 2007-09-07 13:50:09 status installed libkrb53 1.4.4-7etch4 2007-09-07 13:50:09 status unpacked libedit2 2.9.cvs.20050518-2.2 2007-09-07 13:50:09 status half-configured libedit2 2.9.cvs.20050518-2.2 2007-09-07 13:50:09 status installed libedit2 2.9.cvs.20050518-2.2 2007-09-07 13:50:09 status unpacked openssh-client 1:4.3p2-9 2007-09-07 13:50:09 status unpacked openssh-client 1:4.3p2-9 2007-09-07 13:50:09 status unpacked openssh-client 1:4.3p2-9 2007-09-07 13:50:09 status half-configured openssh-client 1:4.3p2-9 2007-09-07 13:50:11 status installed openssh-client 1:4.3p2-9 2007-09-07 13:50:11 status unpacked openssh-server 1:4.3p2-9 2007-09-07 13:50:11 status unpacked openssh-server 1:4.3p2-9 2007-09-07 13:50:11 status unpacked openssh-server 1:4.3p2-9 2007-09-07 13:50:11 status unpacked openssh-server 1:4.3p2-9 2007-09-07 13:50:11 status half-configured openssh-server 1:4.3p2-9 2007-09-07 13:50:14 status installed openssh-server 1:4.3p2-9 2007-09-07 13:57:53 install libmagic1 <none> 4.17-5etch2 2007-09-07 13:57:53 status half-installed libmagic1 4.17-5etch2 2007-09-07 13:57:54 status unpacked libmagic1 4.17-5etch2 2007-09-07 13:57:54 status unpacked libmagic1 4.17-5etch2 2007-09-07 13:57:54 install file <none> 4.17-5etch2 2007-09-07 13:57:54 status half-installed file 4.17-5etch2 2007-09-07 13:57:54 status unpacked file 4.17-5etch2 2007-09-07 13:57:54 status unpacked file 4.17-5etch2 2007-09-07 13:57:54 status unpacked libmagic1 4.17-5etch2 2007-09-07 13:57:54 status half-configured libmagic1 4.17-5etch2 2007-09-07 13:57:54 status installed libmagic1 4.17-5etch2 2007-09-07 13:57:54 status unpacked file 4.17-5etch2 2007-09-07 13:57:54 status unpacked file 4.17-5etch2 2007-09-07 13:57:54 status half-configured file 4.17-5etch2 2007-09-07 13:57:54 status installed file 4.17-5etch2 debian:/var/log#=20 --=20 We've Got Your Name @ www.mail.com!!! Get a FREE E-mail Account Today - Choose From 100+ Domains |
From: Henry N. <Hen...@Ar...> - 2007-09-07 17:57:57
|
George P Boutwell wrote: > Josep Ma [JAZ] wrote: >> Yes, I did install over the old directory in all cases. >> > I don't know that this is the problem... I tend to use the same > directory for all my version, but I'm constantly running manually the > --remove-driver & --install-driver commands when I change/switch out > versions for any reason on my machines... Same directory is not the problem. Have tested both snapsots, run the one, and installed the other, back to the other and runs. No problems. In very old mails found, that an old swap between different kernel versions does an problem and reboots/crashed the host some times. I never seen such problem, and I have also a swap partition (from native Linux). The solving was, to renew the swap partition with mkswap before using in new kernel. I tend to use a file as swap for coLinux - this is also faster, as a partition. If you have such problem again, try to boot without swap - simple disable the cobd in the config. What is the size of swap partition? Please check it under coLinux and under native Linux. Detects coLinux the size correctly? -- Henry |
From: THEyoshi <1ko...@te...> - 2007-09-07 14:52:37
|
The files exist, this is not the problem. -- View this message in context: http://www.nabble.com/Compile-Error-with-GCC-tf4384228.html#a12556844 Sent from the colinux-users mailing list archive at Nabble.com. |
From: George P B. <geo...@gm...> - 2007-09-07 03:42:21
|
Josep Ma [JAZ] wrote: > Yes, I did install over the old directory in all cases. > * > Henry Nestler wrote:* > >Do you used the same install directory on install page for both? > >I use differ diretories for every install. So, it can be a problem. > > > >-- > >Henry > > I don't know that this is the problem... I tend to use the same directory for all my version, but I'm constantly running manually the --remove-driver & --install-driver commands when I change/switch out versions for any reason on my machines... George |
From: Josep Ma [JAZ] <jo...@gm...> - 2007-09-06 16:29:56
|
Yes, I did install over the old directory in all cases. * Henry Nestler wrote:* >Do you used the same install directory on install page for both? >I use differ diretories for every install. So, it can be a problem. > >-- >Henry -- _ _ /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\ o o | Josep Ma [JAZ] | * | ICQ UIN: 7014661 | '-' | Messenger: ja...@ho... | \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/ |
From: Henry N. <Hen...@Ar...> - 2007-09-06 16:25:46
|
THEyoshi wrote: > I have got a problem with the GCC Compiler in my Cooperative Linux. > I am able to compile programms like "hello world" but if it gets a little > more > complicated there is an error, always with the pattern: > > usr/include/<header-file>: parse error before 'size_t' Think, you have not completly installed GCC. Some programms needs also to install "kernel headers" or "kernel source". The definition for size_t should be in the include /usr/include/asm/posix_types.h and /usr/include/linux/types.h Check that the files exists. If not, locate how to install they for your distribution. -- Henry |
From: Henry N. <Hen...@Ar...> - 2007-09-06 16:02:40
|
Josep Ma [JAZ] wrote: > Seems the bug is less repeatable than what i initially thought. I > reinstalled august release over july release after a (normal) system > reboot, and all went fine. > Then, i thought it could be that i had been using colinux before > installing it, so I decided to reinstall july release, launch colinux > (july), stop it (the installer checks that it is so), reinstall august > release and launch colinux (august). > Done this, and system restart again. Do you used the same install directory on install page for both? I use differ diretories for every install. So, it can be a problem. -- Henry |
From: Henry N. <Hen...@Ar...> - 2007-09-06 15:55:30
|
Josep Ma [JAZ] wrote: >> kernel=vmlinux >> cobd0=\DosDevices\I:\coLinux80\Debian-etch.ext3.3gb >> cobd1=\Device\Harddisk0\Partition5 >> cobd3=\Device\Harddisk0\Partition3 >> cobd4=\Device\Harddisk0\Partition4 >> cofs0=\DosDevices\C:\ >> cofs1=\DosDevices\I:\ >> cofs2=\DosDevices\G:\ >> mem=128 >> eth0=tuntap >> eth1=pcap-bridge,ethernet >> root=/dev/cobd0 >> > (Actually, the "kernel" line was the last one at the test time, but i've > moved back to top) Your config does no matter for your problem, but would say here: The position of kernel= can be in all lines. Only the old coLinux 0.6.4 needs it as first command line prameter to switch from XML file to the Command line args. You can remove the text "\DosDevices\" from your configuration. The config has such lines than: kernel=vmlinux cobd0=I:\coLinux80\Debian-etch.ext3.3gb cobd1=\Device\Harddisk0\Partition5 ... cofs0=C:\ ... Users from 0.6.x can use the tool XML2CFG to convert the XML file into new format: http://sourceforge.net/project/showfiles.php?group_id=98788&package_id=217177&release_id=476227 > I'm unsure what other information might be relevant to the problem, or > if i could enable anything to get more information. I saw the > colinux-debug-daemon, but i guess that gives information once it is > launched, not while it launches. Yes, colinux-debug-daemon is more to watch the background daemons. You can run it before you runs "net start colinux". But in the crashing case it can not save the datas to file. You can use it over Ethernet and catch all datas on a second PC. But this is some times also not helpful: The network dosn't send the last packets... After colinux debugging is enabled (misc=31,prints=31) all debugs from inside coLinux-NT-Kernel (linux.sys) will also be see on DebugView from www.sysinternals.com "Miscellaneous Utilities". This tool can also run over network on second PC. -- Henry |
From: Henry N. <Hen...@Ar...> - 2007-09-06 15:27:53
|
Rainer Zocholl wrote: > A very nice text about debugging colinux you find'll here: > > http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070818-Bugcheck/debugging.txt This file is temporaly only for an special build. Will later find on http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging > ... > http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Rainer, thanks for your links, will add some in the text. :-) -- Henry |
From: Josep Ma [JAZ] <jo...@gm...> - 2007-09-06 14:22:48
|
Hello, Seems the bug is less repeatable than what i initially thought. I reinstalled august release over july release after a (normal) system reboot, and all went fine. Then, i thought it could be that i had been using colinux before installing it, so I decided to reinstall july release, launch colinux (july), stop it (the installer checks that it is so), reinstall august release and launch colinux (august). Done this, and system restart again. "Restart?" I thought. "I've changed the settings." I went to check and effectively i had the "automatic reboot on failure" disabled. I went to SYSTEMFOLDER\minidump, and nothing was there. I have a special system configuration so something could have gone wrong. I don't have the swap on the system partition, but on a specific partition (a-la linux), and windows warned that it wouldn't generate minidumps if there wasn't a swap file in there. So i setup an additional 2MB swap on it, rebooted, reinstalled july, started, reinstalled august, started, and no crash. Tried running it several times, no crash. Redone the installation several times, and still no crash. I don't completely discard the driver going wrongly installed (although the setup has always said that it installed the corresponding version). I'll continue running the august version in the following days to see if I eventually get another system crash and report it if so. En/na George P Boutwell ha escrit: > Something to try... Not sure if it'll fix your particular problem or > not... Run the august snapshot install, then before running any > instance of colinux run colinux-deamon --remove-driver, colinux-daemon > ---install-driver > > I know this should be taken care of in the install, but maybe something > went awry and it wasn't able to as part of the install... > > George > > -- _ _ /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\ o o | Josep Ma [JAZ] | * | ICQ UIN: 7014661 | '-' | Messenger: ja...@ho... | \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/ |
From: El T. <ca...@gm...> - 2007-09-05 21:43:18
|
You might want to try user mode linux on your rootfs: http://user-mode-linux.sourceforge.net/ user mode linux is similar to colinux but it runs in a Linux system. > Date: Tue, 4 Sep 2007 12:18:48 +0800 > From: "Samir Kuthiala" <sam...@gm...> > Subject: [coLinux-users] Install colinux on Linux? > To: col...@li... > Message-ID: > <21f...@ma...> > Content-Type: text/plain; charset="iso-8859-1" > > Hi all, > > I have a colinux installation on windows xp. However I am thinking of moving > it to my usb hard-disk so that I am able to run my colinux either in office > or home. My only problem is that I use linux (ubuntu) at home. I was > wondering if anyone has any pointers on getting colinux to work with a linux > host system. I guess it should be possible but am a little stuck on how to > go about it. > > Thanks > > Samir |
From: <Use...@zo...> - 2007-09-05 21:10:06
|
jo...@gm...(Josep Ma [JAZ]) 05.09.07 21:01 >Hello, >Yesterday i tried the august snapshot compile of the 0.8.0 release >with some unexpected results. >I am happily using the july compile (with a minimal debian testing, >with xfce and developer tools), but when i installed the august >release (using the installer), launching the daemon caused an install >machine reboot (i gues a BSOD, but windows reboots). In less than two >seconds. Marketing said: "BSODs are not good" so XP is installed default to do an instant reboot instead of a BSOD which the typical windows user would not understand anyway. But you can change that behaviour easily. See link below. >When the machine rebooted, i tried again with the same >result. I reinstalled the july compile again, and stopped crashing. >This is on a windows xp sp2 machine with all updates, colinux >installed as a service, launching it manually with "net start colinux" >I'm unsure what other information might be relevant to the problem, or >if i could enable anything to get more information. I saw the >colinux-debug-daemon, but i guess that gives information once it is >launched, not while it launches. A very nice text about debugging colinux you find'll here: http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070818-Bugcheck/debugging.txt Especially in your case go to: "Howto use Windows crash dump" ... Enable minidump (the small option, 64KB). Not need a full core dump. Don't set the ckeckbox for "automatic reboot after crash dump". The menu find via keys Windows+Pause [or Control panel] "System properties"] * Register: Extentions * Frame: Start and Recover * Button: Configure * Frame: System errors ... The mentioned program "kd" used to anylze the dump can be downloaded at MS. i386.exe kd.exe "Download the Debugging Tools for Windows" http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.7.05.1.exe approx. 15MB. It usuallay makes sense to always the most recent version. If the problem is maybe deep inside windows, installed symbols may give further help. http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx "Download Windows Symbol Packages" approx. 200MB but worth downloading and installing IMHO. more readings: "How to read the small memory dump files that Windows creates for debugging" http://support.microsoft.com/kb/315263/EN-US/ http://www.microsoft.com/whdc/devtools/debugging/default.mspx http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Rainer |
From: Josep Ma [JAZ] <jo...@gm...> - 2007-09-05 19:01:18
|
Hello, Yesterday i tried the august snapshot compile of the 0.8.0 release with some unexpected results. I am happily using the july compile (with a minimal debian testing, with xfce and developer tools), but when i installed the august release (using the installer), launching the daemon caused an install machine reboot (i gues a BSOD, but windows reboots). In less than two seconds. When the machine rebooted, i tried again with the same result. I reinstalled the july compile again, and stopped crashing. This is on a windows xp sp2 machine with all updates, colinux installed as a service, launching it manually with "net start colinux" and my configuration is as follows: > kernel=vmlinux > cobd0=\DosDevices\I:\coLinux80\Debian-etch.ext3.3gb > cobd1=\Device\Harddisk0\Partition5 > cobd3=\Device\Harddisk0\Partition3 > cobd4=\Device\Harddisk0\Partition4 > cofs0=\DosDevices\C:\ > cofs1=\DosDevices\I:\ > cofs2=\DosDevices\G:\ > mem=128 > eth0=tuntap > eth1=pcap-bridge,ethernet > root=/dev/cobd0 > (Actually, the "kernel" line was the last one at the test time, but i've moved back to top) I'm unsure what other information might be relevant to the problem, or if i could enable anything to get more information. I saw the colinux-debug-daemon, but i guess that gives information once it is launched, not while it launches. -- _ _ /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\ o o | Josep Ma [JAZ] | * | ICQ UIN: 7014661 | '-' | Messenger: ja...@ho... | \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/ |
From: THEyoshi <1ko...@te...> - 2007-09-05 13:54:56
|
I have got a problem with the GCC Compiler in my Cooperative Linux. I am able to compile programms like "hello world" but if it gets a little more complicated there is an error, always with the pattern: usr/include/<header-file>: parse error before 'size_t' Please Help me! -- View this message in context: http://www.nabble.com/Compile-Error-with-GCC-tf4384228.html#a12498533 Sent from the colinux-users mailing list archive at Nabble.com. |
From: George P B. <geo...@gm...> - 2007-09-05 03:25:30
|
Agustin Pizarro wrote: > from colinux 0.7 you need to pass configuration as parameters on the command line, XML configuration file does not work. > > something like: > > colinux-daemon.exe kernel=vmlinux initrd=initrd.gz cobd0="Debian-20040605-mit.ext3.1610mb" cobd1="fs_768Mb" mem=512 eth0=pcap-bridge,"Local Area Connection",00:ff:75:39:D3:C1 eth1=tuntap root=/dev/cobd0 > change parameters to fit your setup or needs. > > AFAIK, from colinux 0.8 you can also create a file with those parameters (one parameter per line) and execute this way: > > colinux-daemon.exe @configfile.txt > > > You can actually do the colinux-daemon.exe @configfile.txt in 0.7, there may be a bug or two in it that has been fixed/resolved in 0.8, but other than that the using a config file has pretty much always been there. George |
From: Henry N. <Hen...@Ar...> - 2007-09-04 10:11:38
|
Eric DECORNOD wrote: > Le mardi 4 septembre 2007 10:26, Samir Kuthiala a écrit : >> So I guess there is no way of using co-linux on linux? > I didn't know it was possible. Thanks Henry. > >> I like the idea of using vserver but can vserver run >> colinux images directly? > If you can mount (either loopback or directly) you should be able to run any > linux bin. hold on the mount point. > > As a quick test, you can try to mount your colinux images, chroot inside (as > root) and run some applications : ls, man, ... Yes loop mount and chroot works also very good. For example: mkdir /mnt/colinux mount rootfs.img /mnt/colinux -o loop,rw,exec,dev mount --bind /proc /mnt/colinux/proc mount --bind /dev /mnt/colinux/proc chroot /mnt/colinux /bin/sh inside chroot colinux switch to your coLinuxUser: cd /home/coLinuxUser su coLinuxUser Without the bind mount for /dev, you need to create some basic devices (null, zero, tty1, tty2...) This way I use to create and check coLinux image files. -- Henry |
From: Eric D. <eri...@iu...> - 2007-09-04 09:18:16
|
Le mardi 4 septembre 2007 10:26, Samir Kuthiala a =C3=A9crit=C2=A0: > So I guess there is no way of using co-linux on linux? I didn't know it was possible. Thanks Henry. > I like the idea of using vserver but can vserver run > colinux images directly?=20 If you can mount (either loopback or directly) you should be able to run an= y=20 linux bin. hold on the mount point. As a quick test, you can try to mount your colinux images, chroot inside (a= s=20 root) and run some applications : ls, man, ... If you can do that, running vserver shouldn't be very difficult. > ~Samir =2D-=20 Eric D=C3=89CORNOD Ing=C3=A9nieur d'=C3=89tudes SCICS - Facult=C3=A9 des Sciences Universit=C3=A9 Henri Poincar=C3=A9 |
From: Samir K. <sam...@gm...> - 2007-09-04 09:14:30
|
Thanks. This looks promising. Will try it out. ~Samir On 9/4/07, Henry Nestler <Hen...@ar...> wrote: > > Samir Kuthiala wrote: > > So I guess there is no way of using co-linux on linux? I like the idea > > of using vserver but can vserver run colinux images directly? > > Read this "5.3. For Linux as host": > > http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/building > > You need to compile the module colinux.ko from source. > Kernels with REGPARM enabled dosn't work as host. Current kernel 2.6.22 > does only work, if you remove the regparm parameter from host kernel > Makefile (and recompile the host kernel!). > > -- > Henry > |
From: Henry N. <Hen...@Ar...> - 2007-09-04 09:02:50
|
Samir Kuthiala wrote: > So I guess there is no way of using co-linux on linux? I like the idea > of using vserver but can vserver run colinux images directly? Read this "5.3. For Linux as host": http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/building You need to compile the module colinux.ko from source. Kernels with REGPARM enabled dosn't work as host. Current kernel 2.6.22 does only work, if you remove the regparm parameter from host kernel Makefile (and recompile the host kernel!). -- Henry |
From: Samir K. <sam...@gm...> - 2007-09-04 08:26:55
|
So I guess there is no way of using co-linux on linux? I like the idea of using vserver but can vserver run colinux images directly? ~Samir On 9/4/07, Eric DECORNOD <eri...@iu...> wrote: > > Le mardi 4 septembre 2007 06:18, Samir Kuthiala a =E9crit: > > Hi all, > > I have a colinux installation on windows xp. However I am thinking of > > moving it to my usb hard-disk so that I am able to run my colinux eithe= r > in > > office or home. My only problem is that I use linux (ubuntu) at home. I > was > > wondering if anyone has any pointers on getting colinux to work with a > > linux host system. I guess it should be possible but am a little stuck > on > > how to go about it. > > Thanks Samir > IMHO, you should be able to run your partitions under kvm in a similar wa= y > as > in coLinux. (but only if you own a recent processor with some virtual > tech. > inside otherwise it's like qemu : slow). > > An other clue, would be linux vserver. It may be even a better solution a= s > it's more like a super-chroot. > Precompiled kernels exists under Debian, so it should be easy under > ubuntu. > > PS: if you're skilled, you may write udev scripts to start the stuff on > device > plug. > > PPS: it may be difficult to specify your devices names in coLinux config, > I've > never tried to host colinux partitions on an USB device. > > Cheers, > -- > Eric D=C9CORNOD > Ing=E9nieur d'=C9tudes > SCICS - Facult=E9 des Sciences > Universit=E9 Henri Poincar=E9 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Eric D. <eri...@iu...> - 2007-09-04 07:30:33
|
Le mardi 4 septembre 2007 06:18, Samir Kuthiala a =C3=A9crit=C2=A0: > Hi all, > I have a colinux installation on windows xp. However I am thinking of > moving it to my usb hard-disk so that I am able to run my colinux either = in > office or home. My only problem is that I use linux (ubuntu) at home. I w= as > wondering if anyone has any pointers on getting colinux to work with a > linux host system. I guess it should be possible but am a little stuck on > how to go about it. > Thanks Samir IMHO, you should be able to run your partitions under kvm in a similar way = as=20 in coLinux. (but only if you own a recent processor with some virtual tech.= =20 inside otherwise it's like qemu : slow). An other clue, would be linux vserver. It may be even a better solution as= =20 it's more like a super-chroot. Precompiled kernels exists under Debian, so it should be easy under ubuntu. PS: if you're skilled, you may write udev scripts to start the stuff on dev= ice=20 plug. PPS: it may be difficult to specify your devices names in coLinux config, I= 've=20 never tried to host colinux partitions on an USB device. Cheers, =2D-=20 Eric D=C3=89CORNOD Ing=C3=A9nieur d'=C3=89tudes SCICS - Facult=C3=A9 des Sciences Universit=C3=A9 Henri Poincar=C3=A9 |
From: Samir K. <sam...@gm...> - 2007-09-04 04:18:51
|
Hi all, I have a colinux installation on windows xp. However I am thinking of moving it to my usb hard-disk so that I am able to run my colinux either in office or home. My only problem is that I use linux (ubuntu) at home. I was wondering if anyone has any pointers on getting colinux to work with a linux host system. I guess it should be possible but am a little stuck on how to go about it. Thanks Samir |
From: Agustin P. <agu...@ya...> - 2007-08-29 17:04:57
|
from colinux 0.7 you need to pass configuration as parameters on the command line, XML configuration file does not work. something like: colinux-daemon.exe kernel=vmlinux initrd=initrd.gz cobd0="Debian-20040605-mit.ext3.1610mb" cobd1="fs_768Mb" mem=512 eth0=pcap-bridge,"Local Area Connection",00:ff:75:39:D3:C1 eth1=tuntap root=/dev/cobd0 change parameters to fit your setup or needs. AFAIK, from colinux 0.8 you can also create a file with those parameters (one parameter per line) and execute this way: colinux-daemon.exe @configfile.txt Clément Fontana <cle...@un...> escribió: Hi everyone, I have an error why i launch .bat : "XML configuration files are obsolete. Please pass command line etc." Does anyone know how to fix it? Thanks clement -- *********************************************************************** Clement Fontana tel. : + 33 4 91 04 16 41 Doctorant / Ingénieur d'Etudes fax : + 33 4 91 04 16 35/43 Station Marine Endoume UMR 6535 CNRS - LOB Chemin Batterie des Lions F13007 Marseille http://www.com.univ-mrs.fr/~fontana/ *********************************************************************** ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --------------------------------- Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. |
From: <cle...@un...> - 2007-08-29 09:56:05
|
Re-hi everyone, I have now an error when i launch colinux : "initrd: umount rootfs failed " Does anyone know something about it? Thanks, clement. -- *********************************************************************** Clement Fontana tel. : + 33 4 91 04 16 41 Doctorant / Ingénieur d'Etudes fax : + 33 4 91 04 16 35/43 Station Marine Endoume UMR 6535 CNRS - LOB Chemin Batterie des Lions F13007 Marseille http://www.com.univ-mrs.fr/~fontana/ *********************************************************************** |
From: <cle...@un...> - 2007-08-29 09:25:37
|
Hi everyone, I have an error why i launch .bat : "XML configuration files are obsolete. Please pass command line etc." Does anyone know how to fix it? Thanks clement -- *********************************************************************** Clement Fontana tel. : + 33 4 91 04 16 41 Doctorant / Ingénieur d'Etudes fax : + 33 4 91 04 16 35/43 Station Marine Endoume UMR 6535 CNRS - LOB Chemin Batterie des Lions F13007 Marseille http://www.com.univ-mrs.fr/~fontana/ *********************************************************************** |