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: Remy P. <t3k...@fa...> - 2004-02-01 14:31:11
|
I just joined the mailinglist, and am still stuck with the failure under XP pro where the kernel driver bails with an exit code -1. There was mention of a patch attatched, and it was stated that the patch had been added to the distro- but the distro I downloaded still doesn't work. I wasn't sure from reading the archives though, whether or not this was resolved, or still being worked on. Thanks, Remy |
From: Hero <l10...@in...> - 2004-02-01 13:11:07
|
hi i have problem whit runing daemon it's starts after that is write:=20 monitor shutting down closing monitor removing kernel driver stoping driver service removing driver service i hawe win 2k Polis version on machine whit 512 ddr mainboard asus a7v8x and radeon 9700 128 ddr pro FIC=20 i need Help :) |
From: Sat R. <sat...@ho...> - 2004-02-01 12:25:28
|
Hi Dan! First of all: Genious idea and Great work!!! Let me ask dummy question: Is it possible to use native linux drivers to access REAL hardware without writing special wrappers for every device type? PS: I mean not 'Windows-Must-Have' hardware like keyboard or mouse but ADDITIONAL hardware like MPEG Capture card, DVB TV Card,... _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Dan A. <da...@gm...> - 2004-02-01 12:01:55
|
On Sun, Feb 01, 2004 at 05:03:09PM +1000, Ian Latter wrote: > Is it possible to configure the TAP interface to be on the same > network as the ethernet interface? I didn't get very far doing > this (kepy coming up with duplicate IP errors, when there > wasn't another host using that address prior to TAP > configuration). AFAIK what you are talking about is called Bridged Ethernet. It is it is done by activating the promiscuous mode of one Ethernet card and let it recieve packets for two or MAC addresses. Thus, the other operating systems "shares" the NIC with the host. -- Dan Aloni da...@gm... |
From: Dan A. <da...@gm...> - 2004-02-01 10:56:50
|
On Sun, Feb 01, 2004 at 05:12:43PM +1000, Ian Latter wrote: > Noted :) So the virtual system "boots" as soon as the coloinux > daemon is executed? And, if your virtual system didn't require > input, you would not need the console at all? As soon as the colinux-daemon is running, the Linux machine boots. The attachable console is therefore *optional*. Detaching it doesn't stop the daemon from running. > > If Linux terminates, the driver sleeps uninterruptedly until you > > detach the console, that could be the reason why you couldn't > > kill the driver or restart the system. > > Ok - I'll do more testing and get back to you with real data. > > One other thing that I've found ... I was in a "cmd" prompt when > I first started the daemon, last time. This time I ran it from explorer > and I just flashes a window up and disappears again. I think there's > an error message in there, but I can't see it - its too fast. Running > the daemon from the cmd prompt again, it works without a hitch. The current run directory of the daemon needs to be the directory that contains default.colinux.xml, otherwise the daemon finds no configuration file and exits. -- Dan Aloni da...@gm... |
From: Ivan W. <em...@iv...> - 2004-02-01 10:32:42
|
Sorry I think the problem has been raised earlier and I should read thr the archive before posting. Rgrds, Ivan. ----- Original Message ----- From: "Ivan Wong" <em...@iv...> To: <col...@li...> Sent: Sunday, February 01, 2004 14:57 Subject: [coLinux-devel] fsck failed > Hi! > > The daemon on my box is up and running but I have got fsck failed. (figure > attached) > > I am using winxpsp1 and the directory list is like this: > > Directory of C:\coLinux > > 02/01/2004 03:26 AM <DIR> . > 02/01/2004 03:26 AM <DIR> .. > 01/27/2004 07:20 PM 121,517 colinux-20040119.tar.gz > 02/01/2004 03:16 AM 1,480,948 colinux-20040131-bin.tar.gz > 02/01/2004 12:59 AM 523,746 colinux-console.exe > 02/01/2004 12:59 AM 80,099 colinux-daemon.exe > 01/31/2004 06:23 AM 971,618 cygwin1.dll > 02/01/2004 04:04 AM 1,073,741,824 Debian-3.0r0.ext3.1gb > 02/01/2004 01:19 AM 255 default.colinux.xml > 01/27/2004 07:47 PM 37,009,983 linux-2.4.24.tar.gz > 02/01/2004 01:59 AM 41,280 linux.sys > 02/01/2004 02:11 AM 2,874 README > 02/01/2004 12:59 AM 1,624,545 vmlinux > 11 File(s) 1,115,598,689 bytes > 2 Dir(s) 29,030,588,416 bytes free > > Have I done anything wrong? > > With Rgrds, > Ivan. > |
From: Ian L. <Ian...@mq...> - 2004-02-01 07:27:58
|
> Use the DDK that closely matches the running system, i.e, the last one. Ok, I'll see what I can organise. > Note that the console implementation is incomplete. Noted :) So the virtual system "boots" as soon as the coloinux daemon is executed? And, if your virtual system didn't require input, you would not need the console at all? > Was the console still attached after the virtual system shutdown? The shutdown I did was the "shutdown -g0 -y -i0" ... hmm maybe I did i6 ... I'll check these and get back to you tomorrow some time. > If Linux terminates, the driver sleeps uninterruptedly until you > detach the console, that could be the reason why you couldn't > kill the driver or restart the system. Ok - I'll do more testing and get back to you with real data. One other thing that I've found ... I was in a "cmd" prompt when I first started the daemon, last time. This time I ran it from explorer and I just flashes a window up and disappears again. I think there's an error message in there, but I can't see it - its too fast. Running the daemon from the cmd prompt again, it works without a hitch. Hope that helps others. -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
From: Ian L. <Ian...@mq...> - 2004-02-01 07:20:05
|
> Please use gcc version 3. This is *very* good to know .. I'll build a new dev host tomorrow. > You can define it as data[0] and it may fix the problem for your compiler. It passed that error .. I came across to more .. its not worth it. I'll get the right compiler and move on. Thanks for the help on this one. -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
From: Ian L. <Ian...@mq...> - 2004-02-01 07:18:23
|
Ok, I think I see how this TAP interface works ... its equivalent to a windows interface, a crossover cable, and a linux interface all rolled into one. It looks like windows (XP Pro) doesn't do forwarding by default - without Internet Connection sharing. Funny thing is that Windows looks like it will only do connection sharing such that the internal network interface is 192.168.0.1, which is what my "external" network is on this host ;-) Aint gunna happen. No matter. With an external interface of 192.168.0.x/24 and an internal interface (TAP) of 192.168.1.1/24 and a colinux interface of 192.168.1.2/24 I can ping from colinux to windows, and from windows to colinux. colinux times out going anywhere else due to a suspected lack of forwarding in windows. I still get a "sendto" error if I try to ping the colinux interface address from colinux. But I'm still pretty happy with what I'm seeing. Is it possible to configure the TAP interface to be on the same network as the ethernet interface? I didn't get very far doing this (kepy coming up with duplicate IP errors, when there wasn't another host using that address prior to TAP configuration). ----- Original Message ----- >From: "Dan Aloni" <da...@gm...> >To: "Nigel Spowage" <Nig...@BT...> >Subject: Re: [coLinux-devel] networking question >Date: Sun, 01 Feb 2004 07:35:20 +0200 > > On Sat, Jan 31, 2004 at 11:29:54PM +0000, Nigel Spowage wrote: > > > the colinux instance think's it's interface is up, and is > > configured the private ip of 192.168.0.40. pinging this ip > > causes ping to report: > > ping: sendto: Invalid argument > > ping: wrote 192.168.0.40 64 chars, ret=-1 > > > > have i missed a configuration step of the Tap-win32 driver ? > > In Windows, if you configure an IP address for your TAP-Win32 > driver it would fix this. 192.168.0.1 netmask 255.255.255.0. > > Or optionally, if you enable Internet Connection Sharing this > subnet will automatically be used and you will able to access > the Internet from within coLinux. (apt-get !). > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
From: Ivan W. <em...@iv...> - 2004-02-01 06:45:37
|
Hi! The daemon on my box is up and running but I have got fsck failed. (figure attached) I am using winxpsp1 and the directory list is like this: Directory of C:\coLinux 02/01/2004 03:26 AM <DIR> . 02/01/2004 03:26 AM <DIR> .. 01/27/2004 07:20 PM 121,517 colinux-20040119.tar.gz 02/01/2004 03:16 AM 1,480,948 colinux-20040131-bin.tar.gz 02/01/2004 12:59 AM 523,746 colinux-console.exe 02/01/2004 12:59 AM 80,099 colinux-daemon.exe 01/31/2004 06:23 AM 971,618 cygwin1.dll 02/01/2004 04:04 AM 1,073,741,824 Debian-3.0r0.ext3.1gb 02/01/2004 01:19 AM 255 default.colinux.xml 01/27/2004 07:47 PM 37,009,983 linux-2.4.24.tar.gz 02/01/2004 01:59 AM 41,280 linux.sys 02/01/2004 02:11 AM 2,874 README 02/01/2004 12:59 AM 1,624,545 vmlinux 11 File(s) 1,115,598,689 bytes 2 Dir(s) 29,030,588,416 bytes free Have I done anything wrong? With Rgrds, Ivan. |
From: Dan A. <da...@gm...> - 2004-02-01 05:37:31
|
On Sun, Feb 01, 2004 at 09:35:48AM +1000, Ian Latter wrote: > Hi Dan, > > See below, using the colinux-20040131 patch, I am getting a kernel > compile error, regarding the variable "data" in cooperative.h ("putcs" > structure within the co_console_message_t structure). > > I have decided that if you haven't seen this in your compiles, then it > may be compiler related - this is my compiler version; > > [root@host]# gcc --version > 2.96 > > Has anyone else seen this issue? If not, which compiler version > are you using? Please use gcc version 3. [07:35 pts/5,callisto ~]% gcc -v Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux Thread model: posix gcc version 3.3.3 20040125 (prerelease) (Debian) > Alternatively, if this is supposed to be a single char (put-char-screen?) > then how about redefining data[] as data[2]? You can define it as data[0] and it may fix the problem for your compiler. -- Dan Aloni da...@gm... |
From: Dan A. <da...@gm...> - 2004-02-01 05:35:39
|
On Sat, Jan 31, 2004 at 11:29:54PM +0000, Nigel Spowage wrote: > the colinux instance think's it's interface is up, and is > configured the private ip of 192.168.0.40. pinging this ip > causes ping to report: > ping: sendto: Invalid argument > ping: wrote 192.168.0.40 64 chars, ret=-1 > > have i missed a configuration step of the Tap-win32 driver ? In Windows, if you configure an IP address for your TAP-Win32 driver it would fix this. 192.168.0.1 netmask 255.255.255.0. Or optionally, if you enable Internet Connection Sharing this subnet will automatically be used and you will able to access the Internet from within coLinux. (apt-get !). -- Dan Aloni da...@gm... |
From: Dan A. <da...@gm...> - 2004-02-01 05:29:07
|
On Sun, Feb 01, 2004 at 10:37:25AM +1000, Ian Latter wrote: > Windows XP SP1 Driver Development Kit (DDK) (English) > Date Posted 11/14/2002 12:16:00 PM > File en_winxp_sp1_ddk.exe, Self-Extracting Compressed File > Size 137.81 MB Use the DDK that closely matches the running system, i.e, the last one. > There seems to be a little terminal emulation issue under the > console (this may be a TERM env issue tho, didn't check) - but > no realy problem. And, once I shut down the virtual system, I > was unable to kill off the windows driver, or restart the system. Note that the console implementation is incomplete. Was the console still attached after the virtual system shutdown? If Linux terminates, the driver sleeps uninterruptedly until you detach the console, that could be the reason why you couldn't kill the driver or restart the system. -- Dan Aloni da...@gm... |
From: Ballard J. <sac...@ho...> - 2004-02-01 03:50:09
|
Hello. The first time I installed the package into C:\coLinux on XP Pro and ran the colinux-daemon I got: Cooperative Linux daemon Installing kernel driver Creating monitor Monitor is running Right after that message the system went down without any further messages and immediately rebooted. I ran the the colinux-daemon again right after boot and got the messages like: > > D:\colinux>colinux-daemon > > Cooperative Linux daemon > > Manager is already running > > Manager not initialized (0) > > Removing driver leftover > > Stopping driver service > > Removing driver service > > Installing kernel driver > > Error installing kernel driver: -15 That was similar to a mail thread: >Matt Behrens wrote: > | > | Was this your first time? I got similar messages earlier when I > | was playing around, but did not think to record them. The catch > | was that I was trying to kill the first daemon and left myself > | needing a reboot. > > This was straight after a boot. > I ran the colinux-daemon again and the let system reboot itself. Then I ran the colinux-console. It saw Monitor 0 and allowed me to connect, but it immediately stackdumped. Hope that helps where to look. |
From: Ian L. <Ian...@mq...> - 2004-02-01 01:07:09
|
I should clarify this; > There seems to be a little terminal emulation issue under the > console (this may be a TERM env issue tho, didn't check) - but > no realy problem. And, once I shut down the virtual system, I > was unable to kill off the windows driver, or restart the system. .. or restarted the "linux" system (not the windows system) ... there is no "boot the virtual instance" option while the initial console-daemon.exe instance is running. Cheers, -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
From: Maxious(Alex Sadleir) <ma...@la...> - 2004-02-01 01:06:24
|
Started off with the broken daemon so i had to get the modified one just to be able to start up, now I am getting the fsck problems and i have noticed that it isn't redrawing the screen properly. I use nano for text editing and it gets interlanced with whatever was on the screen before. Lets hope that fsck will be the final hurdle.... |
From: Ian L. <Ian...@mq...> - 2004-02-01 00:52:39
|
Hello Dan, Thanks for the binary test version. Its good to be attacking the problem from both ends at once :) I've included my test system specification below. I have had success under WinXP SP1 with "booting coLinux straight out of the box (colinux-20040131-bin.tar.gz). I haven't tried the fsck test/issue reported here, but I have had the network configurtion issue as reported here. (In windows, I can configure and ping any IP address I choose, In Linux I get sendto errors). Included here is a replacement "step 1" for the README, for Windows XP. I laughed when I saw the number of additional steps over 2k .. certainly got to consider the TCO when upgrading Windows versions, hehe, go MS; 1. Install TAP-Win32 (WinXP) Control Panel -> Add Hardware -> Next -> Yes, I have already connected the hardware, Next -> Add a new hardware device, Next -> Install the hardware that I manually select from a list (Advanced), Next -> Network Adapters, Next -> Have Disk -> Go to the supplied TAP-Win32 directory and choose OemWin2k, Open -> Ok -> Next -> Next -> Finish I have also been advised that a friend of mine can probably compile your driver for you. He has access to the following DDK's; Windows Server 2003 DDK (English) Date Posted 4/9/2003 10:16:00 AM File en_windows_server_2003_ddk.exe, Self-Extracting Compressed File Size 183.53 MB Windows XP Driver Development Kit (DDK) (English) Date Posted 9/21/2001 File WINXP_DDK.exe, Self-Extracting Compressed File Size 130.43 MB Windows XP SP1 Driver Development Kit (DDK) (English) Date Posted 11/14/2002 12:16:00 PM File en_winxp_sp1_ddk.exe, Self-Extracting Compressed File Size 137.81 MB Let me know what you want him to run with ... There seems to be a little terminal emulation issue under the console (this may be a TERM env issue tho, didn't check) - but no realy problem. And, once I shut down the virtual system, I was unable to kill off the windows driver, or restart the system. Love this project, Dan you're a dude. SYSTEM SPECIFICATION System; Microsoft Windows XP Professional Version 2002 Service Pack 1 Computer; Intel(R) Pentium(R) 4 CPU 2.00GHz 1.99 GHz 504 MB of RAM ----- Original Message ----- >From: "Dan Aloni" <da...@gm...> >To: <col...@li...> >Subject: [coLinux-devel] coLinux 0.5.2 >Date: Sat, 31 Jan 2004 20:51:46 +0200 > > Good evening, > > I just released version 0.5.2 of Cooperative Linux. > > This release include a binary snapshot FOR TESTING PURPOSES, although it > can actully be used to run a stable Linux system on your Windows setups, > considering it doesn't crash ;) > > Please read the included README file before running. > > Changes: > * Added some missing files to the build tree > * doc/cygwin-cross-build - How to build a cygwin cross compilation tools > on Linux. > * Made the daemon more proofed to mistakes. It's logic about loading/ > unloading the driver is much more sane now. > * Added a cursor support to the console. > > Good luck, > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
From: Matt B. <ma...@zi...> - 2004-02-01 00:13:39
|
On Sun, Feb 01, 2004 at 12:26:31AM +0200, Dan Aloni wrote: > On Sat, Jan 31, 2004 at 04:55:57PM -0500, Matt Behrens wrote: > > I can't find the above DebugView message anywhere in the 0.5.2 > > colinux source I pulled today. > It's in colinux/os/winnt/kernel/block.c. Well, at this stage I think I'm sunk; my admittedly virgin eyeballs I don't see anything obviously wrong with anything there, and I can't throw in more debug calls to track down the problem because I'm missing a cross-compile environment and a DDK. :-) Sorry. Maybe in the future. --=20 Matt Behrens <ma...@zi...> <http://www.zigg.com/> Life's too short to recompile what you don't hack. <http://www.debian.org/> |
From: Ian L. <Ian...@mq...> - 2004-01-31 23:51:22
|
Hi Dan, See below, using the colinux-20040131 patch, I am getting a kernel compile error, regarding the variable "data" in cooperative.h ("putcs" structure within the co_console_message_t structure). I have decided that if you haven't seen this in your compiles, then it may be compiler related - this is my compiler version; [root@host]# gcc --version 2.96 Has anyone else seen this issue? If not, which compiler version are you using? Alternatively, if this is supposed to be a single char (put-char-screen?) then how about redefining data[] as data[2]? COMPILE ERROR; gcc -D__KERNEL__ -I/usr/src/linux-2.4.24/include -Wall -Wstrict-prototypes -Wno-trigraphs - O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack- boundary=2 -march=i586 -DKBUILD_BASENAME=main -c -o init/main.o init/main.c In file included from /usr/src/linux-2.4.24/include/linux/cooperative.h:15, from /usr/src/linux-2.4.24/include/asm/io.h:5, from /usr/src/linux-2.4.24/include/linux/blkdev.h:11, from /usr/src/linux-2.4.24/include/linux/blk.h:4, from init/main.c:25: /usr/src/linux-2.4.24/include/asm/cooperative.h:73: array size missing in `params' In file included from /usr/src/linux-2.4.24/include/asm/io.h:5, from /usr/src/linux-2.4.24/include/linux/blkdev.h:11, from /usr/src/linux-2.4.24/include/linux/blk.h:4, from init/main.c:25: /usr/src/linux-2.4.24/include/linux/cooperative.h:103: array size missing in `data' make: *** [init/main.o] Error 1 INCLUDE FILE typedef struct { unsigned long size; co_operation_console_t type; union { struct { long t; /* Start of scroll region (row) */ long b; /* End of scroll region (row) */ long dir; /* End of scroll region (row) */ long lines; /* Number of lines to scroll */ } scroll; struct { long x; long y; long count; char data[]; <-- line 103 } putcs; struct { long x; long y; unsigned short charattr; } putc; co_cursor_pos_t cursor; }; } co_console_message_t; -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
From: Nigel S. <Nig...@BT...> - 2004-01-31 23:34:21
|
using the latest binaries provided colinux is working for me on win2k. I got the 'fsck' problem on startup but i've hacked the scripts so the check is ignored, and linux starts up nicely. however, the linux machine doesn't seem to be able to communicate to the win2k through tcp/ip. the tap-win32 driver becomes 'connected' when the linux daemon is started, and windows reports that it gets a autoconfig ip address (169.253.x.x). the colinux instance think's it's interface is up, and is configured the private ip of 192.168.0.40. pinging this ip causes ping to report: ping: sendto: Invalid argument ping: wrote 192.168.0.40 64 chars, ret=-1 have i missed a configuration step of the Tap-win32 driver ? thanks nigel |
From: Tony H. <tm...@no...> - 2004-01-31 23:05:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ePAc wrote: | is there anyone on the list who has access to the newer DDK (2003/XP | version), and that could compile the linux.sys with that OS. It would make | sense that the linux.sys driver need to be compiled for the proper target | OS. is there any success on XP ? In theory I've got access to it but not enough disk space to install it. ~ I doubt that's the problem though as from the readme the compilation is done under cygwin and just the final link is done using the DDK. It's possible, though, that cygwin is making some assumption about userspace that's simply not true at the driver level... compiling the source under visual studio might be worth it. Tony -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAHDSf5UdHDk9LaRcRArJdAJ4wDZMHEAXyl5wCDR9lkGEELbjAhACePzzO 4GIaHqJEOwHbobC3hW7zpMQ= =LE8u -----END PGP SIGNATURE----- |
From: ePAc <ep...@ko...> - 2004-01-31 22:54:31
|
> > > IRQL_NOT_LESS_OR_EQUAL > > > > > > Larry > > > > I got this as well, and i'm now waiting for the system to dump the whole > > memory. would any kind of processing on the memdump be useful to anyone ? > > These memory dumps sound useful. Do you know some reference about how to > enable them and other info that might be useful? right click on "My Computer" select "Properties" select "Advanced" tab under "Startup And Recovery" there is some option to setup different type of memory dump (minidump, kernel dump, full memory dump). i had mine setup as "Full Memory Dump" (512M). as for analysis, there used to be some tools on the MS web site, i'll track those down. DebugView was able to "process" that memdump and give me 3 messages: 1 - 2:06:06 PM - Driver Unloaded (*) 2 - 2:07:38 PM - Driver Loaded 3 - 2:07:38 PM - Allocated cmon0 (*) might be from the first attempt for which Memdump wasn't enabled during the previous boot or something [/me clueless]... this was running under XP. Have you done any kind of testing with XP ? or was it all win2k ? my other machine (win2K) is loading properly, and the console is coming up, and i'm having the same set of problem with the e2fsck (i will write down those numbers next time). All in all, "This is fantastic !"(TM). You have now access to probably a couple dozen different config (mine included) which will allow us all to run linux on our poor windows machine :o) is there anyone on the list who has access to the newer DDK (2003/XP version), and that could compile the linux.sys with that OS. It would make sense that the linux.sys driver need to be compiled for the proper target OS. is there any success on XP ? Thanks, Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
From: Tony H. <tm...@no...> - 2004-01-31 22:50:25
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Aloni wrote: | I disagree. Running in a debug/checked Windows XP might help to spot | other issue, not only explaining this one. Not much help, I'm afraid. The debug build I have is a very minimal configuration so whatever's conflicting isn't installed there - It started initialising and vmware blew up... I'd half expect it not to work under vmware anyway so that's no surprise. Driver LoadedAllocated cmon0 cocon: cocon_startup cocon: cocon_init cocon: cocon_set_palette cocon: cocon_set_origin cocon: cocon_save_screen cocon: cocon_dummy cocon: cocon_dummy cocon: cocon_set_origin cocon: cocon_switch cocon: cocon_set_palette Reported size: 1073741824 bytes cobd opened (\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb) Search Route #2: Route not found Search Route #2: Route not found Search Route #2: Route not found Search Route #2: Route not found Search Route #2: Route not found Search Route #2: Route not found Search Route #2: Route not found Search Route #2: Route not found Delete Route #3: Route not found Delete Route #3: Route not found Delete Route #3: Route not found MsgErrorLogWrite: COMPONENT = MESSENGER MsgErrorLogWrite: An unexpected network control block (NCB) was received. The NCB is the data. 0x000C54CC 912301020C550C0000002A2020202020.#...U....* -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAHDEb5UdHDk9LaRcRAsXfAJ9oswF9LctE4b2MgxWCY6E72unKAgCfSUHZ kTW41mBZ+TIqT66nSEI/ddQ= =Dvqv -----END PGP SIGNATURE----- |
From: Dan A. <da...@gm...> - 2004-01-31 22:34:01
|
On Sat, Jan 31, 2004 at 02:25:45PM -0800, ePAc wrote: > > OK, that was different - it didn't work for me. I get a blue-screen when I > > run the modified colinux-daemon.exe, due to: > > > > IRQL_NOT_LESS_OR_EQUAL > > > > Larry > > I got this as well, and i'm now waiting for the system to dump the whole > memory. would any kind of processing on the memdump be useful to anyone ? These memory dumps sound useful. Do you know some reference about how to enable them and other info that might be useful? -- Dan Aloni da...@gm... |
From: Tony H. <tm...@no...> - 2004-01-31 22:31:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Aloni wrote: | Did the daemon run before the run you sent above? It couldn't have | reached 'Manager is already running' if it isn't so. It would be very | interesting to know what it spitted out in the very first run. No, not at all... It's obviously detecting the daemon when it's not there. Tony -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAHCyh5UdHDk9LaRcRAkcDAJ9rWj3+jOVdBvMpx26ArvLlHGQn5wCePfI2 siE4VjPQSx9LSMtx1TjWql4= =im6R -----END PGP SIGNATURE----- |