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: John L. <jo...@su...> - 2004-02-04 00:37:48
|
I've seen very similar problems when using apt-get to install large files(like kernel-source-2.4.24) The download completes, then dpkg fails because the md5sum doesn't match. Sounds like corrupted packets getting passed around, which makes me think it's the tap drivers, or the connection between colinux and the tap driver... It seems to be only associated with large transfers, and not network load. But at least apache works. and php. and postgres. John Ian Latter wrote: >Hello Vlad, > > I haven't seen the issues that you've reported - but I've seen some- >thing else that's not right in the networking. > > The only application included in the CHAOS file system is setiathome, >and it fails to acquire a new workunit from the Berkeley servers. What >we see here is an ESTablished connection to their web server >(which suggests that networking "works") but we never retrieve any >data (not even up to the first Mbyte). Instead the connection hangs >with a send-q of about 350 or so. > > We're testing this over two PCs (XP Pro SP1) with Bridging (mini mac) >as the connection/networking mechanism. > > I think it was the other Ian who mentioned a much later TAP driver >from the openVPN project; maybe its worth trying that out .. I might >give that ago sometime in the next couple of days - see if it helps. > > > > >----- Original Message ----- > > >>From: "Vlad Doubrov" <vl...@w-...> >>To: <col...@li...> >>Subject: Re: [coLinux-devel] Strange problem with Win-TAP and coLinux >>Date: Tue, 03 Feb 2004 15:05:03 +0300 >> >>Dan Aloni wrote: >> >> >> >>>>The same happens when I try to transfer that file via SMB (smbd and >>>>smbclient is installed on coLinux) - except that the file is getting >>>>corrupted after "successful" download. >>>> >>>>Small files (less than 1 MB in size) get transferred very well. >>>> >>>>So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible? >>>>Or may be it's my misunderstood? >>>> >>>> >>>My guess is to try to using ifconfig to change eth0's MAC address. >>> >>> >>It doesn't help. According to SSH docs, "corrupted MAC on input" message >>means that some packet was corrupted during data transfer, it doesn't >>mean anything to ethernet MAC addresses. And as I already wrote, when I >>try to transfer the same large file via samba it gets corrupted the >>same way. >> >>I'm completely stuck out as I couldn't transfer anything larger than 1Mb >>to the virtual linux. Does this problem appear in your enviroment? Or >>perhaps some workarounds are possible? >> >>-- vlad >> >> >> >> >> >>------------------------------------------------------- >>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/ > > > >------------------------------------------------------- >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 > > |
|
From: Ian L. <Ian...@mq...> - 2004-02-03 23:13:55
|
Hello Vlad, I haven't seen the issues that you've reported - but I've seen some- thing else that's not right in the networking. The only application included in the CHAOS file system is setiathome, and it fails to acquire a new workunit from the Berkeley servers. What we see here is an ESTablished connection to their web server (which suggests that networking "works") but we never retrieve any data (not even up to the first Mbyte). Instead the connection hangs with a send-q of about 350 or so. We're testing this over two PCs (XP Pro SP1) with Bridging (mini mac) as the connection/networking mechanism. I think it was the other Ian who mentioned a much later TAP driver from the openVPN project; maybe its worth trying that out .. I might give that ago sometime in the next couple of days - see if it helps. ----- Original Message ----- >From: "Vlad Doubrov" <vl...@w-...> >To: <col...@li...> >Subject: Re: [coLinux-devel] Strange problem with Win-TAP and coLinux >Date: Tue, 03 Feb 2004 15:05:03 +0300 > > Dan Aloni wrote: > > >>The same happens when I try to transfer that file via SMB (smbd and > >>smbclient is installed on coLinux) - except that the file is getting > >>corrupted after "successful" download. > >> > >>Small files (less than 1 MB in size) get transferred very well. > >> > >>So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible? > >>Or may be it's my misunderstood? > > > My guess is to try to using ifconfig to change eth0's MAC address. > > It doesn't help. According to SSH docs, "corrupted MAC on input" message > means that some packet was corrupted during data transfer, it doesn't > mean anything to ethernet MAC addresses. And as I already wrote, when I > try to transfer the same large file via samba it gets corrupted the > same way. > > I'm completely stuck out as I couldn't transfer anything larger than 1Mb > to the virtual linux. Does this problem appear in your enviroment? Or > perhaps some workarounds are possible? > > -- vlad > > > > > > ------------------------------------------------------- > 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: Bjorn S. <sw...@in...> - 2004-02-03 23:06:48
|
I'm using Windows XP Pro with all the latest patches. Latest binary colinux release and the colinux-daemon patch. I have installed the TAP-Win32 driver Starting colinux-daemon.exe from c:\colinux I get the following C:\colinux>colinux-daemon.exe Cooperative Linux daemon Error opening TAP-Win32 C:\colinux> Does anyone know what I might be forgetting ? Thanks Bjorn |
|
From: Dan A. <da...@gm...> - 2004-02-03 19:40:18
|
On Tue, Feb 03, 2004 at 08:06:53PM +1000, Ian Latter wrote: > Hello, > > 2.4.24+openMosix+FreeSWAN compiles (once you've jiggied > FreeSWAN's Makefile around to remove its enforced "make > bzImage"). However, when I go to run colniux-daemon.exe > I get; > > Cooperative Linux daemon > Installing kernel driver > Creating monitor > Monitor is running > <network interface comes up> > <1 second pause> > <network interface goes down> > Monitor is shutting down > Closing monitor > Removing kernel driver > Stopping driver service > Removing driver service > > This is repeatable (so no bad mojo from the colinux-daemon > process). Is there any way to have colinux-daemon produce > more or debugging output, to help me see where the new > kernel falls apart? (I can see the irony of this request after > asking to have the window removed altogether - but that was > for production usage ;-) > > My initial thought for the kernel issue is probably its size. As the > kernels can't be compressed they're going to be pretty big. The > one I've just built is 2,288,062 bytes -- is there an upper limit for > the kernel size? (have I gone over it?). > > A second thought is that my prioritisation for the conflicting patch > with oM is wrong .. I'll build a version without openMosix and see > where I get. What happens here is probably that Linux boots, and then exists for some reason from one of the co_terminate() calls, maybe due to a panic. At this stage, you can trying writing a script that attaches the console just when the daemon starts booting Linux in order to catch it. My initial intention was that the daemon itself would be given a switch that would instruct it to launch a console when the boot starts. -- Dan Aloni da...@gm... |
|
From: Vlad D. <vl...@w-...> - 2004-02-03 12:10:47
|
Dan Aloni wrote: >>The same happens when I try to transfer that file via SMB (smbd and >>smbclient is installed on coLinux) - except that the file is getting >>corrupted after "successful" download. >> >>Small files (less than 1 MB in size) get transferred very well. >> >>So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible? >>Or may be it's my misunderstood? > My guess is to try to using ifconfig to change eth0's MAC address. It doesn't help. According to SSH docs, "corrupted MAC on input" message means that some packet was corrupted during data transfer, it doesn't mean anything to ethernet MAC addresses. And as I already wrote, when I try to transfer the same large file via samba it gets corrupted the same way. I'm completely stuck out as I couldn't transfer anything larger than 1Mb to the virtual linux. Does this problem appear in your enviroment? Or perhaps some workarounds are possible? -- vlad |
|
From: Ian L. <Ian...@mq...> - 2004-02-03 11:31:44
|
> AFAIK, EXE files in Windows has a it which says if it is > has a console or not. Perhaps I could supply 2 EXE files. Hmm .. that's a pain (having to manage two exe's) .. > Try: colinux-console.exe -a 0 Excellent - works well (very fast) - thanks. I'll add that to the Console.lnk. > > -- If its not there already (I can't be sure), to have the "file > > -> quit" (or window close) option of the colinux-console.exe > > automatically detach from the current console. > > I think it's already there, I'll check it out. > Be good if a user can knock the interface around roughly without upsetting the daemon. > /sbin/init is currently hardcoded. The next version will take that info > from the XML. Ok, cool - this is the most important one for our testing, as this one impacts on our ability to preconfigure the kernel before the system is booted. -- 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-03 11:26:04
|
Hello,
I feel like a total noob. I haven't needed this much support building
linux kernels ever .. even when I was a noob the first time round I
did it better than this.
Appologies, too, for missing the "vmlinux vs bzImage" problem,
as you've got that clearly doc'd in the doc/building file (I've been
back through all of your docs this evening)..
I forwarded and reversed all of my software until I came back to
where I started. I am currently using the default (colinux supplied)
.config, a fresh/clean/virgin 2.4.24 kernel source and a I'm
producing a kernel, that is neither the same size as the orginal [1]
nor is it working as a direct drop-in replacement for the precompiled
version that you've shipped in your binary release.
Each of the kernels I've built have compiled fine, but failed to leave
the daemon running for more than a second. I wondered if I was
missing a map file, or some other include/supporting file, but I don't
see the binary distribution using any such thing. Once you've
made the vmlinux file, you just copy it over to the Windows host,
right? No need to set any of its boot options or anything?
[1] - I wouldn't have expected them to be identical in size, but
each time I compile it on this system it comes out to the same size;
Mine; 1,646,244 vmlinux
coLinux-bin; 1,624,545 vmlinux
I have diff'd the config files and they are identical .. the patch is
clean .. but its doesn't patch cleanly (I feel this is odd - but
acceptable - depending on the line that I'm missing).
patching file CREDITS
patching file Documentation/devices.txt
patching file Makefile
Hunk #1 succeeded at 27 (offset -1 lines).
Hunk #3 succeeded at 289 (offset -1 lines).
patching file arch/i386/config.in
patching file arch/i386/kernel/Makefile
patching file arch/i386/kernel/cooperative.c
patching file arch/i386/kernel/entry.S
patching file arch/i386/kernel/head.S
patching file arch/i386/kernel/i8259.c
patching file arch/i386/kernel/process.c
patching file arch/i386/kernel/setup.c
patching file arch/i386/kernel/time.c
patching file arch/i386/kernel/traps.c
patching file arch/i386/mm/fault.c
patching file arch/i386/mm/init.c
patching file arch/i386/vmlinux.lds
patching file drivers/block/Config.in
patching file drivers/block/Makefile
patching file drivers/block/cobd.c
patching file drivers/block/ll_rw_blk.c
patching file drivers/char/Makefile
patching file drivers/char/colx_keyb.c
patching file drivers/char/vt.c
patching file drivers/net/Config.in
patching file drivers/net/Makefile
patching file drivers/net/conet.c
patching file drivers/video/Makefile
patching file drivers/video/cocon.c
patching file include/asm-i386/cooperative.h
patching file include/asm-i386/desc.h
patching file include/asm-i386/dma.h
patching file include/asm-i386/io.h
patching file include/asm-i386/irq.h
patching file include/asm-i386/mmu_context.h
patching file include/asm-i386/page.h
patching file include/asm-i386/pgalloc.h
patching file include/asm-i386/pgtable-2level.h
patching file include/asm-i386/pgtable.h
patching file include/asm-i386/processor.h
patching file include/asm-i386/segment.h
patching file include/linux/console.h
patching file include/linux/cooperative.h
patching file include/linux/major.h
patching file init/do_mounts.c
patching file init/main.c
patching file kernel/Makefile
patching file kernel/cooperative.c
patching file kernel/import.c
patching file kernel/panic.c
patching file kernel/printk.c
patching file mm/page_alloc.c
patching file mm/vmalloc.c
The kernel verifies under gpg .. I have md5sum'd the tar.gz
version that I have - if anyone can verify this it would rule out
an odd-kernel;
fc365a4d55826c605ff25f6227036dbb linux-2.4.24.tar.gz
647e29c582965987219859097ffdc7f8 linux-2.4.24.tar.gz.sign
I'm still not using the same compiler as Dan .. but I am using a GCC
v3 compiler (per previous thread).
Is there anything else that I could be doing wrong? Happy to
provide any additional info required to diagnose this problem.
Thanks,
--
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: Dan A. <da...@gm...> - 2004-02-03 10:55:51
|
On Tue, Feb 03, 2004 at 04:07:00PM +1000, Ian Latter wrote: > This is early days - I understand that the project is currently active > as a "beta only, test and feed back please" system, but I've got a > couple of requests, from my testing, for when the time is appropriate. > > > For future consideration; > > -- A commandline switch to disable the diagnostic screen > from starting automatically, when colinux-daemon.exe is > launched. AFAIK, EXE files in Windows has a it which says if it is has a console or not. Perhaps I could supply 2 EXE files. > -- A commandline switch to enable colinux-console.exe to > connect to either the default console (console0), or the > specified console. Try: colinux-console.exe -a 0 > -- If its not there already (I can't be sure), to have the "file > -> quit" (or window close) option of the colinux-console.exe > automatically detach from the current console. I think it's already there, I'll check it out. > > > Also, when I booted the CHAOS file system under the coLinux > kernel, I first configured the default.colinux.xml file with; > <bootparams>init=/bin/sh</bootparams> .. but it still booted with > the init at /sbin/init (I was quite surprised to see the OS ready > when I got there - I didn't expect it to port cleanly the first time; > the reason behind the experiment). > Is this feature currently hardcoded, or ignored, in the config file? /sbin/init is currently hardcoded. The next version will take that info from the XML. -- Dan Aloni da...@gm... |
|
From: Ian L. <Ian...@mq...> - 2004-02-03 10:22:06
|
Hello, 2.4.24+openMosix+FreeSWAN compiles (once you've jiggied FreeSWAN's Makefile around to remove its enforced "make bzImage"). However, when I go to run colniux-daemon.exe I get; Cooperative Linux daemon Installing kernel driver Creating monitor Monitor is running <network interface comes up> <1 second pause> <network interface goes down> Monitor is shutting down Closing monitor Removing kernel driver Stopping driver service Removing driver service This is repeatable (so no bad mojo from the colinux-daemon process). Is there any way to have colinux-daemon produce more or debugging output, to help me see where the new kernel falls apart? (I can see the irony of this request after asking to have the window removed altogether - but that was for production usage ;-) My initial thought for the kernel issue is probably its size. As the kernels can't be compressed they're going to be pretty big. The one I've just built is 2,288,062 bytes -- is there an upper limit for the kernel size? (have I gone over it?). A second thought is that my prioritisation for the conflicting patch with oM is wrong .. I'll build a version without openMosix and see where I get. Thanks, -- 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: Vlad D. <vl...@w-...> - 2004-02-03 10:07:20
|
Dan Aloni wrote: >>The same happens when I try to transfer that file via SMB (smbd and >>smbclient is installed on coLinux) - except that the file is getting >>corrupted after "successful" download. >> >>Small files (less than 1 MB in size) get transferred very well. >> >>So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible? >>Or may be it's my misunderstood? > My guess is to try to using ifconfig to change eth0's MAC address. It doesn't help. According to SSH docs, "corrupted MAC on input" message means that some packet was corrupted during data transfer, it doesn't mean anything to ethernet MAC addresses. And as I already wrote, when I try to transfer the same large file via samba it gets corrupted the same way. I'm completely stuck out as I couldn't transfer anything larger than 1Mb to the virtual linux. Does this problem appear in your enviroment? Or perhaps some workarounds are possible? -- vlad |
|
From: Ballard J. <sac...@ho...> - 2004-02-03 08:34:24
|
Use GlobalMemoryStatusEx() for more consistency across NT platforms.
unsigned long co_os_get_physical_ram_size( void )
{
MEMORYSTATUSEX m ;
m.dwLength = sizeof( m ) ;
GlobalMemoryStatusEx( &m ) ;
if( m.ullTotalPhys > (DWORDLONG) 0xFFF00000 )
return 0xFFF00000 ;
// avoids 64bit to 32bit overflow conversion
return 0xFFF00000 & (unsigned long) m.ullTotalPhys ;
}
----- Original Message -----
From: "Dan Aloni" da...@gm...
>[...]
> Look at this:
>
> unsigned long co_os_get_physical_ram_size()
> {
> MEMORYSTATUS memstat;
>
> GlobalMemoryStatus(&memstat);
>
> /* Round up in MBs: */
>
> return (memstat.dwTotalPhys + 0xFFFFF) & 0xFFF00000;
> }
>
> It's BAD.
>
> Does anyone know a better way to get this information?
|
|
From: Ballard J. <sac...@ho...> - 2004-02-03 07:50:44
|
From: "Richard Goodwin" <ric...@ri...> [...] > One thing I haven't figured out with bridging or ICS.. Will I be able to > send incoming packets to the bridge connection? [...] The ICS connection can be directed to the network bridge with all the devices on bridge. The ICS normally does not display the option to select the bridge until the bridge is created. |
|
From: Ian L. <Ian...@mq...> - 2004-02-03 07:21:20
|
I don't know what I'm smokin'! .. your bsod patch is, of course, for windows .. not linux .. I've emailled my mate on that earlier memory (physmem) enquiry to see if he has any info from the windows side. ----- Original Message ----- >From: "Ian Latter" <Ian...@mq...> >To: "Dan Aloni" <da...@gm...> >Subject: Re: [coLinux-devel] linux kernel; array size missing in `data' >Date: Tue, 03 Feb 2004 16:42:07 +1000 > > > This worked - thank you. I'll look at adding the BSOD mini patch that you > emailled through this morning, and then get back into adding openMosix > and FreeSWAN ... many hours of fun :) > > > > ----- Original Message ----- > >From: "Dan Aloni" <da...@gm...> > >To: "Ian Latter" <Ian...@mq...> > >Subject: Re: [coLinux-devel] linux kernel; array size missing in `data' > >Date: Mon, 02 Feb 2004 22:53:07 +0200 > > > > > - 20040131 .config (from coLinux download site @ sourceforge) > > > - 20040131 linux patch (from same download). > > > > > > > > > At this stage the kernel build fails in the very last stage of the > > > build process (see below). > > > > > > The build process is very simple ... patch it .. make mrproper .. cp in > > > the .config .. make oldconfig .. make dep .. make bzImage .. nothing > > > fancy at all (no openMosix, no IPSec, no other drivers, etc). > > > > There's no need to 'make bzImage'. > > > > 'make vmlinux' does the job without causing the problem you mentioned. > > > > > > -- > > 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/ > > > > ------------------------------------------------------- > 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: Ian L. <Ian...@mq...> - 2004-02-03 06:57:25
|
This worked - thank you. I'll look at adding the BSOD mini patch that you emailled through this morning, and then get back into adding openMosix and FreeSWAN ... many hours of fun :) ----- Original Message ----- >From: "Dan Aloni" <da...@gm...> >To: "Ian Latter" <Ian...@mq...> >Subject: Re: [coLinux-devel] linux kernel; array size missing in `data' >Date: Mon, 02 Feb 2004 22:53:07 +0200 > > > - 20040131 .config (from coLinux download site @ sourceforge) > > - 20040131 linux patch (from same download). > > > > > > At this stage the kernel build fails in the very last stage of the > > build process (see below). > > > > The build process is very simple ... patch it .. make mrproper .. cp in > > the .config .. make oldconfig .. make dep .. make bzImage .. nothing > > fancy at all (no openMosix, no IPSec, no other drivers, etc). > > There's no need to 'make bzImage'. > > 'make vmlinux' does the job without causing the problem you mentioned. > > > -- > 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: Ian L. <Ian...@mq...> - 2004-02-03 06:56:20
|
> My guess is to try to using ifconfig to change eth0's MAC address. > > I didn't give much thought about the MAC address when I wrote the conet > driver. So the Linux MAC is the same as the ethernet's physical MAC (and the same as the Windows MAC) ? Should make DHCP interesting :)) -- 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: Dan A. <da...@gm...> - 2004-02-03 06:28:28
|
On Mon, Feb 02, 2004 at 03:28:57PM -0800, Steven Edwards wrote: > NtQuerySystemInformation may give you what you need. Also you could > look at using PSAPI or the toolhelp APIs. I looked at its documentation and it doesn't appear to give me what I need. Other solutions? -- Dan Aloni da...@gm... |
|
From: Ian L. <Ian...@mq...> - 2004-02-03 06:22:15
|
This is early days - I understand that the project is currently active
as a "beta only, test and feed back please" system, but I've got a
couple of requests, from my testing, for when the time is appropriate.
For future consideration;
-- A commandline switch to disable the diagnostic screen
from starting automatically, when colinux-daemon.exe is
launched.
-- A commandline switch to enable colinux-console.exe to
connect to either the default console (console0), or the
specified console.
-- If its not there already (I can't be sure), to have the "file
-> quit" (or window close) option of the colinux-console.exe
automatically detach from the current console.
Also, when I booted the CHAOS file system under the coLinux
kernel, I first configured the default.colinux.xml file with;
<bootparams>init=/bin/sh</bootparams> .. but it still booted with
the init at /sbin/init (I was quite surprised to see the OS ready
when I got there - I didn't expect it to port cleanly the first time;
the reason behind the experiment).
Is this feature currently hardcoded, or ignored, in the config file?
Thanks,
--
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-03 05:37:51
|
Thanks for this info. This was very close to one of the 200-odd commands that I tried .. in fact I can't see the difference ... maybe I had that 128 missing when I had TAP.ndi ... and TAP.ndi missing when I tried the 128 ... Is "netsh" going to assist in building the bridge or you think there's a more graceful way ..? The other thing I'll be looking for is a way to input the IP address of the child OS during the install .. CHAOS takes the IP paramaters from the kernel command line, so I'd like to be able to build the xml file from installer. ----- Original Message ----- >From: "Ballard Jonathan" <sac...@ho...> >To: "Ian Latter" <Ian...@mq...> >Subject: Installer [ was: file/dir in use ] >Date: Mon, 02 Feb 2004 21:42:49 -0800 > > I got the the files to install but did not get the service to register. The > command used: > > ...colinux-20040131-binTAP-Win32>rundll32 setupapi.dll,InstallHinfSection > TAP.ndi 128 .OemWin2k.inf > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/se > tup/installhinfsection.asp > > There is better method that gets them both. > > ----- Original Message ----- > From: "Ian Latter" <Ian...@mq...> > To: "Ballard Jonathan" <sac...@ho...> > Cc: <col...@li...> > Sent: Monday, February 02, 2004 2:46 PM > Subject: Re: Re:[coLinux-devel] file/dir in use > > > > > > Yeah, I built a package last night .. its the CHAOS minix file system, > ported > > across to an ext2 file system, mounted under the coLinux kernel. I did a > > few things when I bundled it last night; > > > > - Build a "Power-On" pif/lnk file to get the pwd right before exec, and > to > > run the process minimised > > - Built a "Console" pif/lnk to match the pair. > > - Installer checks for XP > > - Installs to c:galileo with the files required to run it > > - Installs to c:galileonet with the TAP drivers > > - Adds start menu guff .. includes Power-On and Console .. link to site > > and uninstall > > > > You can check it out at http://itsecurity.mq.edu.au/chaos/isos/beta/ > > > > Beware, if you're going to run this image that CHAOS comes with > "certaintyd" > > that checksums the file system every 2 seconds ... kill it if you want to > change > > anything. > > > > All I need now is a method of detecting/installing TAP and > detecting/installing > > the Bridge. And from last night, I now have a couple of minor feature > requests > > to post back. > > -- 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: Ballard J. <sac...@ho...> - 2004-02-03 05:24:52
|
I got the the files to install but did not get the service to register. The command used: ..\colinux-20040131-bin\TAP-Win32>rundll32 setupapi.dll,InstallHinfSection TAP.ndi 128 .\OemWin2k.inf http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/se tup/installhinfsection.asp There is better method that gets them both. ----- Original Message ----- From: "Ian Latter" <Ian...@mq...> To: "Ballard Jonathan" <sac...@ho...> Cc: <col...@li...> Sent: Monday, February 02, 2004 2:46 PM Subject: Re: Re:[coLinux-devel] file/dir in use > > Yeah, I built a package last night .. its the CHAOS minix file system, ported > across to an ext2 file system, mounted under the coLinux kernel. I did a > few things when I bundled it last night; > > - Build a "Power-On" pif/lnk file to get the pwd right before exec, and to > run the process minimised > - Built a "Console" pif/lnk to match the pair. > - Installer checks for XP > - Installs to c:galileo with the files required to run it > - Installs to c:galileonet with the TAP drivers > - Adds start menu guff .. includes Power-On and Console .. link to site > and uninstall > > You can check it out at http://itsecurity.mq.edu.au/chaos/isos/beta/ > > Beware, if you're going to run this image that CHAOS comes with "certaintyd" > that checksums the file system every 2 seconds ... kill it if you want to change > anything. > > All I need now is a method of detecting/installing TAP and detecting/installing > the Bridge. And from last night, I now have a couple of minor feature requests > to post back. |
|
From: ePAc <ep...@ko...> - 2004-02-03 01:34:52
|
> and i'm on my way to get this working.. :o) and this is the output of "r" "kv" and "!analyze -v" ... anyone want to take a stab at this ? :o) (and optionally i can run this with the pdb files, if they are available somewhere :o) Thanks, Jok ------------------------------8<-------------------------------- Microsoft (R) Windows Debugger Version 6.2.0013.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\colinux\memory1.dmp] Kernel Dump File: Full address space is available Symbol search path is: SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp2.030422-1633 Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530 Debug session time: Mon Feb 02 14:34:10 2004 System Uptime: 0 days 0:06:55.211 Loading Kernel Symbols ......................................................................................................................................... Loading unloaded module list ............. Loading User Symbols ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {eea5e000, 81ec1b38, eebe0aa8, e} *** ERROR: Module load completed but symbols could not be loaded for linux.sys *** ERROR: Module load completed but symbols could not be loaded for colinux-daemon.exe *** ERROR: Symbol file could not be found. Defaulted to export symbols for cygwin1.dll - Probably caused by : linux.sys ( linux+1926 ) Followup: MachineOwner --------- kd> r eax=ffdff13c ebx=000000be ecx=00000000 edx=40000000 esi=c03ba978 edi=806abfac eip=804f4103 esp=eebe0a2c ebp=eebe0a44 iopl=0 nv up ei ng nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286 nt!KeBugCheckEx+0x19: 804f4103 5d pop ebp kd> KV ChildEBP RetAddr Args to Child eebe0a44 80511b47 000000be eea5e000 81ec1b38 nt!KeBugCheckEx+0x19 (FPO: [Non-Fpo]) eebe0a90 80530140 00000001 eea5e000 00000000 nt!MmAccessFault+0x6cf (FPO: [Non-Fpo]) eebe0a90 eeda2926 00000001 eea5e000 00000000 nt!KiTrap0E+0xb8 (FPO: [0,0] TrapFrame @ eebe0aa8) WARNING: Stack unwind information not available. Following frames may be wrong. eebe0b24 eeda32c7 ef28c000 00000000 00000000 linux+0x1926 eebe0b44 eeda3b31 ef28c000 00000000 00000000 linux+0x22c7 eebe0b64 eeda513e ef28c000 001f03ff 00000000 linux+0x2b31 eebe0ba4 eeda5675 ef28c000 81e89938 00000000 linux+0x413e eebe0be4 eeda5da4 81d8a9e8 00000013 81e89938 linux+0x4675 eebe0c34 804ea221 81d8a930 81ca6930 806abfe0 linux+0x4da4 eebe0c44 8055d0fe 81ca69a0 81d54d60 81ca6930 nt!IopfCallDriver+0x31 (FPO: [0,0,1]) eebe0c58 8055de46 81d8a930 81ca6930 81d54d60 nt!IopSynchronousServiceTail+0x5e (FPO: [Non-Fpo]) eebe0d00 80556cea 0000072c 00000000 00000000 nt!IopXxxControlFile+0x5c2 eebe0d34 8052d571 0000072c 00000000 00000000 nt!NtDeviceIoControlFile+0x28 (FPO: [Non-Fpo]) eebe0d34 7ffe0304 0000072c 00000000 00000000 nt!KiSystemService+0xc4 (FPO: [0,0] TrapFrame @ eebe0d64) 0022fba4 77f5b864 77e75630 0000072c 00000000 SharedUserData!SystemCallStub+0x4 (FPO: [0,0,0]) 0022fba8 77e75630 0000072c 00000000 00000000 ntdll!ZwDeviceIoControlFile+0xc (FPO: [10,0,0]) 0022fc08 00402f27 0000072c 8300004c 0022fcc0 kernel32!DeviceIoControl+0xdd (FPO: [Non-Fpo]) 0022fc38 00401b7e 0a040458 00000013 0022fcc0 colinux_daemon+0x2f27 0022fc68 00401bb0 0a040458 00000000 00000002 colinux_daemon+0x1b7e 0022fc98 0040158d 0a040458 00000000 00000002 colinux_daemon+0x1bb0 kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: eea5e000, Virtual address for the attempted write. Arg2: 81ec1b38, PTE contents. Arg3: eebe0aa8, (reserved) Arg4: 0000000e, (reserved) Debugging Details: ------------------ DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xBE TRAP_FRAME: eebe0aa8 -- (.trap ffffffffeebe0aa8) ErrCode = 00000002 eax=ee9df000 ebx=ef28c000 ecx=00000000 edx=0001fc00 esi=00000000 edi=00000000 eip=eeda2926 esp=eebe0b1c ebp=eebe0b24 iopl=0 nv up ei ng nz na po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287 linux+0x1926: eeda2926 c7049000000000 mov dword ptr [eax+edx*4],0x0 ds:0023:eea5e000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from eeda32c7 to eeda2926 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. eebe0b24 eeda32c7 ef28c000 00000000 00000000 linux+0x1926 eebe0b44 eeda3b31 ef28c000 00000000 00000000 linux+0x22c7 eebe0b64 eeda513e ef28c000 001f03ff 00000000 linux+0x2b31 eebe0ba4 eeda5675 ef28c000 81e89938 00000000 linux+0x413e eebe0be4 eeda5da4 81d8a9e8 00000013 81e89938 linux+0x4675 eebe0c34 804ea221 81d8a930 81ca6930 806abfe0 linux+0x4da4 eebe0c44 8055d0fe 81ca69a0 81d54d60 81ca6930 nt!IopfCallDriver+0x31 eebe0c58 8055de46 81d8a930 81ca6930 81d54d60 nt!IopSynchronousServiceTail+0x5e eebe0d00 80556cea 0000072c 00000000 00000000 nt!IopXxxControlFile+0x5c2 eebe0d34 8052d571 0000072c 00000000 00000000 nt!NtDeviceIoControlFile+0x28 eebe0d34 7ffe0304 0000072c 00000000 00000000 nt!KiSystemService+0xc4 0022fba4 77f5b864 77e75630 0000072c 00000000 SharedUserData!SystemCallStub+0x4 0022fba8 77e75630 0000072c 00000000 00000000 ntdll!ZwDeviceIoControlFile+0xc 0022fc08 00402f27 0000072c 8300004c 0022fcc0 kernel32!DeviceIoControl+0xdd 0022fc38 00401b7e 0a040458 00000013 0022fcc0 colinux_daemon+0x2f27 0022fc68 00401bb0 0a040458 00000000 00000002 colinux_daemon+0x1b7e 0022fc98 0040158d 0a040458 00000000 00000002 colinux_daemon+0x1bb0 0022fcd8 00401767 0a040458 00000000 00000002 colinux_daemon+0x158d 0022fcf8 0040401a 0a040448 0022fd18 0022fe58 colinux_daemon+0x1767 0022fe58 00407400 00400000 00000000 00242372 colinux_daemon+0x401a 0022fed0 61005018 00000001 0a040418 0a040330 colinux_daemon+0x7400 0022ff40 610052ed 610cfee0 fffffffe 000007d0 cygwin1!forkpty+0x3688 0022ff90 00407453 00000000 00000000 00000001 cygwin1!dll_crt0+0x1ad 0022ffb0 0040103c 00407380 037f0009 0022fff0 colinux_daemon+0x7453 0022ffc0 77e814c7 00000000 00000002 7ffdf000 colinux_daemon+0x103c 0022fff0 00000000 00401000 00000000 78746341 kernel32!BaseProcessStart+0x23 FOLLOWUP_IP: linux+1926 eeda2926 c7049000000000 mov dword ptr [eax+edx*4],0x0 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: linux+1926 MODULE_NAME: linux IMAGE_NAME: linux.sys DEBUG_FLR_IMAGE_TIMESTAMP: 401becfb STACK_COMMAND: .trap ffffffffeebe0aa8 ; kb BUCKET_ID: 0xBE_linux+1926 Followup: MachineOwner --------- --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
From: ePAc <ep...@ko...> - 2004-02-03 01:00:51
|
> Here's the link for the tools: > > http://www.microsoft.com/whdc/ddk/debugging/default.mspx > > Read the bit about "how to get symbols" and try out the "symbol server" > method. MUCH faster than pulling down the whole symbol package. > > When in the debugger, use the command "KV" for a stack trace, "analyze -v" > for general info, and "r" for a register dump. Then use the Edit....Write > Window text to file to save out the info. > > Someone correct any misleading info ;-) It may be time for someone to put up > a Wiki or FAQ-o-matic... This looks right... and i'm on my way to get this working.. :o) Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
From: Richard G. <ric...@ri...> - 2004-02-03 00:22:00
|
Here's the link for the tools: http://www.microsoft.com/whdc/ddk/debugging/default.mspx Read the bit about "how to get symbols" and try out the "symbol server" method. MUCH faster than pulling down the whole symbol package. When in the debugger, use the command "KV" for a stack trace, "analyze -v" for general info, and "r" for a register dump. Then use the Edit....Write Window text to file to save out the info. Someone correct any misleading info ;-) It may be time for someone to put up a Wiki or FAQ-o-matic... |
|
From: Nathan C. <nat...@ya...> - 2004-02-03 00:02:20
|
I was very excited when I launched colinux-daemon.exe
and my system didn't dump (like it did on my Centrino
laptop)... but the monitor started and then stopped
without error
Any thoughts?
=================================
C:\>cd coLinux
C:\coLinux>dir
Volume in drive C has no label.
Volume Serial Number is 189E-245F
Directory of C:\coLinux
02/02/2004 09:09 AM <DIR> .
02/02/2004 09:09 AM <DIR> ..
01/31/2004 08:59 AM 523,746
colinux-console.exe
01/31/2004 11:57 AM 80,099
colinux-daemon.exe
01/30/2004 02:23 PM 971,618 cygwin1.dll
02/02/2004 10:06 AM 1,073,741,824
Debian-3.0r0.ext3.1gb
01/31/2004 09:19 AM 262
default.colinux.xml
01/31/2004 09:59 AM 41,280 linux.sys
01/31/2004 10:11 AM 2,953 README
01/31/2004 09:56 AM 3,005 README~
02/02/2004 07:55 AM <DIR> TAP-Win32
01/31/2004 08:59 AM 1,624,545 vmlinux
01/31/2004 08:59 AM 80,099
_colinux-daemon.exe
10 File(s) 1,077,069,431 bytes
3 Dir(s) 10,105,753,600 bytes free
C:\coLinux>colinux-daemon.exe
Cooperative Linux daemon
Installing kernel driver
Creating monitor
Monitor is running
Monitor shutting down
Closing monitor
Removing kernel driver
Stopping driver service
Removing driver service
C:\coLinux>
=================================
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
|
|
From: Dan A. <da...@gm...> - 2004-02-02 23:30:21
|
On Mon, Feb 02, 2004 at 03:13:17PM -0800, ePAc wrote: > I hope this makes more sense to some of you than to me... I'll try to make the most of it. > this the the bugcheck i got after a clean boot, running it once, and got a > error -15 (as mentioned in other posts), and on the second try, a couple > of minutes later, this BSOD. Just to make it clear about what happens in the case described above: When the daemon terminates normally, it uninstalls the linux.sys service. If you get a BSOD, linux.sys is left installed as a service, and when the daemon is ran again after reboot, it returns -15 since the service is already installed. It then removes the service and exits. On the second try, it runs normally. Yeah, it could be made more simple. Please send patches :) -- Dan Aloni da...@gm... |
|
From: Steven E. <ste...@ya...> - 2004-02-02 23:28:58
|
NtQuerySystemInformation may give you what you need. Also you could look at using PSAPI or the toolhelp APIs. Thanks Steven --- Dan Aloni <da...@gm...> wrote: > It's BAD. > > Does anyone know a better way to get this information? __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |
81 messages has been excluded from this view by a project administrator.
