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: <ch...@to...> - 2004-03-15 16:13:52
|
No problem runing as another user with admin privliges. So you do not need to be administrator just be part of the administrators group. This would be a good reason to have coLinux run as a service and start automaticly at bootup so non admin users can login through the networking. I have not looked into if this is possible with the current version. chris > re: > http://sourceforge.net/forum/forum.php?thread_id=1039485&forum_id=342355 > > Quite a lot of people are finding thet coLinux will only run as > administrator. Can someone please confirm this for us? > > The only error message people get is "Error, unable to determine if driver > is installed (rc -19)" which is very confusing. It would be nice if > something about admin rights was mentioned. Shall I submit a patch that > changes this error message to "Error, unable to determine if driver is > installed (rc -19), you need to be Administrator at present to run > coLinux" > or is this inaccurate? > > ----- > Thank you for your time. (Please Type "REPLY:" in subject field if you > wish > to highlight your response, thx). jag...@ca... is just my email > provider of choice, that's all; I agree with thier policies over email. > > _________________________________________________________________ > It's fast, it's easy and it's free. Get MSN Messenger today! > http://www.msn.co.uk/messenger > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: peter g. <plu...@p1...> - 2004-03-15 14:46:03
|
for those who read how colinux works it is obvious it will need admin privs basically the linux kernel is run in kernel space and multitasks somehow with the windows kernel to get it there a kernel mode driver is loaded (docs refer to it as install even though no files are copied) loading this driver requires admin privilages -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Jago Pearce Sent: 15 March 2004 13:26 To: col...@li... Subject: [coLinux-devel] Running as non-admin re: http://sourceforge.net/forum/forum.php?thread_id=1039485&forum_id=342355 Quite a lot of people are finding thet coLinux will only run as administrator. Can someone please confirm this for us? The only error message people get is "Error, unable to determine if driver is installed (rc -19)" which is very confusing. It would be nice if something about admin rights was mentioned. Shall I submit a patch that changes this error message to "Error, unable to determine if driver is installed (rc -19), you need to be Administrator at present to run coLinux" or is this inaccurate? ----- Thank you for your time. (Please Type "REPLY:" in subject field if you wish to highlight your response, thx). jag...@ca... is just my email provider of choice, that's all; I agree with thier policies over email. _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004 |
|
From: Jago P. <jag...@ho...> - 2004-03-15 13:26:22
|
re: http://sourceforge.net/forum/forum.php?thread_id=1039485&forum_id=342355 Quite a lot of people are finding thet coLinux will only run as administrator. Can someone please confirm this for us? The only error message people get is "Error, unable to determine if driver is installed (rc -19)" which is very confusing. It would be nice if something about admin rights was mentioned. Shall I submit a patch that changes this error message to "Error, unable to determine if driver is installed (rc -19), you need to be Administrator at present to run coLinux" or is this inaccurate? ----- Thank you for your time. (Please Type "REPLY:" in subject field if you wish to highlight your response, thx). jag...@ca... is just my email provider of choice, that's all; I agree with thier policies over email. _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger |
|
From: Anton P. <cyb...@na...> - 2004-03-15 11:08:04
|
Hello colinux-devel, I have created very small and simple image (700KB). http://cyberspas.narod.ru/files/costart.img.gz IMHO that appending this or another image to coLinux distribution will be nice. Current distribution not allow "VERY QUICK START". -- Best regards, Anton mailto:cyb...@na... |
|
From: Thomas F. <tf...@no...> - 2004-03-15 09:23:45
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dan, could you please post this w32api-2.4.patch to the list (or wiki or in the next release). Thx, Thomas >> > Plus, you need to recompile a patched version of w32api from >> > sources, with fixed declarations for the two newly imported >> > functions (look in ntoskrnl.def). >> Great stuff. Thanks for the pointer. I made a new patch and it >> compiled no problems. I made a new w32api-2.4.patch and >> attached it to this mail. > > Cool, I was about to produce the same patch. I forwarded this to the > author of w32api. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAVXZxnwJBIFTVIqwRAoRBAJ99B1QkN/grMDukO29KyPL994Zp1QCdE/Iv 3fUerevZg0304E1Zhl7TSLw= =ldJM -----END PGP SIGNATURE----- |
|
From: Sean B. <sea...@so...> - 2004-03-14 21:35:12
|
> > Any advice on where to put the winpcap dev kit so I can > > build conet-bridged-daemon? > > The files should be put in your $PREFIX/i686-pc-cygwin/lib and > $PREFIX/i686-pc-cygwin/include directories. Yes I presumed as much but the last time I looked there were name collisions with headers and definitions. I want to know how you did it. |
|
From: Dan A. <da...@co...> - 2004-03-14 21:19:34
|
On Sun, Mar 14, 2004 at 11:09:19AM +0000, Sean Brook wrote: > On Sunday 14 March 2004 16:57, Dan Aloni wrote: > > On Sun, Mar 14, 2004 at 06:31:33AM -0000, Sean Brook wrote: > > > Hi, > > > > > > Attempting to build the 20040313 snapshot. > > > > It looks like you forgot to apply the new version of linux patch. > Yes I forgot to apply the new version of the patch to the kernel > tree I use with cobuld.sh My gentoo ebuilds automatically patch > a vanilla source tarball which is completely separate from the > tree I use with cobuild.sh > > > > > Plus, you need to recompile a patched version of w32api from > > sources, with fixed declarations for the two newly imported > > functions (look in ntoskrnl.def). > Great stuff. Thanks for the pointer. I made a new patch and it > compiled no problems. I made a new w32api-2.4.patch and > attached it to this mail. Cool, I was about to produce the same patch. I forwarded this to the author of w32api. > Any advice on where to put the winpcap dev kit so I can > build conet-bridged-daemon? The files should be put in your $PREFIX/i686-pc-cygwin/lib and $PREFIX/i686-pc-cygwin/include directories. -- Dan Aloni da...@co... |
|
From: Alejandro R. S. <as...@MI...> - 2004-03-14 21:19:08
|
I've been working on this on and off, will get to it more once my laptop gets back from Dell. My build env has it i686-pc-cygwin/include, folded in with everything else there. It's really a hack. What I'd like to see is it in i686-pc-cygwin/include/wpcap or the like, I just don't have the make/gcc foo to get that added to the include path. Alternativly, and the option I'm leaning more towards now, is to patch the pcap include files so they know they're in wpcap/, and deal appropriatly. Things to note: the wpcap sdk looks like it was meant for windows, the zip file has case issues in three files if I recall correctly. Also, there's a types file that redefines some types (bittypes.h), which should be replaced with a symlink to the cygwin stdint.h file. -Alejandro On Sun, 2004-03-14 at 06:09, Sean Brook wrote: > On Sunday 14 March 2004 16:57, Dan Aloni wrote: > > On Sun, Mar 14, 2004 at 06:31:33AM -0000, Sean Brook wrote: > > > Hi, > > > > > > Attempting to build the 20040313 snapshot. > > > > It looks like you forgot to apply the new version of linux patch. > Yes I forgot to apply the new version of the patch to the kernel > tree I use with cobuld.sh My gentoo ebuilds automatically patch > a vanilla source tarball which is completely separate from the > tree I use with cobuild.sh > > > > > Plus, you need to recompile a patched version of w32api from > > sources, with fixed declarations for the two newly imported > > functions (look in ntoskrnl.def). > Great stuff. Thanks for the pointer. I made a new patch and it > compiled no problems. I made a new w32api-2.4.patch and > attached it to this mail. > > Any advice on where to put the winpcap dev kit so I can > build conet-bridged-daemon? > > Cheers, > > Sean. |
|
From: Sean B. <sea...@so...> - 2004-03-14 20:13:44
|
On Sunday 14 March 2004 16:57, Dan Aloni wrote: > On Sun, Mar 14, 2004 at 06:31:33AM -0000, Sean Brook wrote: > > Hi, > > > > Attempting to build the 20040313 snapshot. > > It looks like you forgot to apply the new version of linux patch. Yes I forgot to apply the new version of the patch to the kernel tree I use with cobuld.sh My gentoo ebuilds automatically patch a vanilla source tarball which is completely separate from the tree I use with cobuild.sh > > Plus, you need to recompile a patched version of w32api from > sources, with fixed declarations for the two newly imported > functions (look in ntoskrnl.def). Great stuff. Thanks for the pointer. I made a new patch and it compiled no problems. I made a new w32api-2.4.patch and attached it to this mail. Any advice on where to put the winpcap dev kit so I can build conet-bridged-daemon? Cheers, Sean. |
|
From: Dan A. <da...@co...> - 2004-03-14 16:57:30
|
On Sun, Mar 14, 2004 at 06:31:33AM -0000, Sean Brook wrote: > Hi, > > Attempting to build the 20040313 snapshot. It looks like you forgot to apply the new version of linux patch. Plus, you need to recompile a patched version of w32api from sources, with fixed declarations for the two newly imported functions (look in ntoskrnl.def). -- Dan Aloni da...@co... |
|
From: Sean B. <sea...@so...> - 2004-03-14 16:53:47
|
Hello, Thank you very much for that information. While I am at it, thanks for cobuild.sh too :) Cheers, Sean. > -----Original Message----- > From: col...@li... > [mailto:col...@li...] On Behalf > Of Thomas Fritzsche > Sent: Sunday, March 14, 2004 11:35 AM > To: col...@li... > Subject: Re: [coLinux-devel] building 20040313/cannot build > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I don't have system access now to check this out in detail, > but it looks like a problem in colinux. Also the name for the > symbols looks like the parts of the program where Dan is > currently working. > > Greetings, Thomas > > > > Hi, > > > > Attempting to build the 20040313 snapshot. > > > > Using tool chain created from cobuild.sh the make fails with: > > > > i686-pc-cygwin-gcc colinux/common/common.o > > colinux/os/current/user/user.o > > colinux/os/current/user/conet-daemon/main.o colinux > > /os/current/user/conet-daemon/tap-win32.o colinux/user/user.a -o > > colinux/os/current/user/conet-daemon/colinux-net-daemon.exe > > -L/usr/src/colinux/cygwin/target/i686-pc-cygwin/lib/w32api -luser32 > > -lgdi32 -lkernel32 -lmxml i686-pc-cygwin-gcc -mpush-args > > -mno-accumulate-outgoing-args -Wno-trigraphs -O2 > -fno-strict-aliasing > > -Wall -D__KERNEL__ -DCO _KERNEL -DCO_HOST_KERNEL > -DWINVER=0x05000 -I. > > -I./../../linux/include > > -I/usr/src/colinux/cygwin/target/i686-pc-cygwin/include > > /w32api -c colinux/kernel/monitor.c -o colinux/kernel/monitor.o > > colinux/kernel/monitor.c: In function `colinux_init': > > colinux/kernel/monitor.c:140: error: > `CO_VPTR_PSEUDO_RAM_PAGE_TABLES' > > undeclared (first use in this function) > > colinux/kernel/monitor.c:140: error: (Each undeclared identifier is > > reported only once > > colinux/kernel/monitor.c:140: error: for each function it > appears in.) > > colinux/kernel/monitor.c:153: error: > > `CO_VPTR_PHYSICAL_TO_PSEUDO_PFN_MAP' undeclared (first use in this > > function) > > colinux/kernel/monitor.c:165: error: `CO_VPTR_SELF_MAP' undeclared > > (first use in this function) > > colinux/kernel/monitor.c:191: error: `CO_VPTR_PASSAGE_PAGE' > undeclared > > (first use in this function) > > colinux/kernel/monitor.c: In function `co_monitor_iteration': > > colinux/kernel/monitor.c:408: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c:409: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c:410: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c:411: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c:412: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c:413: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c:414: error: structure has no member named > > `linuxvm_state' > > colinux/kernel/monitor.c: In function > `alloc_pseudo_physical_memory': > > colinux/kernel/monitor.c:585: error: > `CO_VPTR_PSEUDO_RAM_PAGE_TABLES' > > undeclared (first use in this function) > > colinux/kernel/monitor.c: In function `co_monitor_create': > > colinux/kernel/monitor.c:704: error: `CO_VPTR_PASSAGE_PAGE' > undeclared > > (first use in this function) > > colinux/kernel/monitor.c: At top level: > > colinux/kernel/monitor.c:100: warning: > `colinux_dump_page_at_address' > > defined but not used > > make: *** [colinux/kernel/monitor.o] Error 1 > > > > I have also created gentoo ebuilds for the toolchain as well as > > colinux. Using these builds the make fails with: > > > > i686-pc-cygwin-gcc > > -Wl,--base-file,colinux/os/current/build/driver.base.tmp \ > > -Wl,--entry,_DriverEntry@8 \ -nostartfiles -nostdlib \ > > -o junk.tmp colinux/os/current/build/driver.o > -lntoskrnl -lhal > > -lgcc > > colinux/os/current/build/driver.o(.text+0x43f2):alloc.c: undefined > > reference to `__imp__MmAllocatePagesForMdl@28' > > colinux/os/current/build/driver.o(.text+0x44b9):alloc.c: undefined > > reference to `__imp__MmMapIoSpace@16' > > collect2: ld returned 1 exit status > > make: *** [colinux/os/current/build/driver.base.tmp] Error 1 > > > > With the environment created with cobuild.sh and my ebuilds I have > > been able to build all snapshots and releases up until this > snapshot. > > Any ideas of what is happening? I think it may be possible that the > > tool chain needs to be updated in some way. I also think it > may be to > > do with the linker but I have no idea and as far as I can > tell it is > > finding the w32api libs ie notoskrnl. > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President > and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > coLinux-devel mailing list coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFAVENFnwJBIFTVIqwRAvrLAJwOefATrqqjNDf3gjShy760OvOyWQCffsF3 > Q791vzal7UhDyLpkSYDAW0A= > =wRCj > -----END PGP SIGNATURE----- > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President > and CEO of GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Thomas F. <tf...@no...> - 2004-03-14 11:33:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I don't have system access now to check this out in detail, but it looks like a problem in colinux. Also the name for the symbols looks like the parts of the program where Dan is currently working. Greetings, Thomas > Hi, > > Attempting to build the 20040313 snapshot. > > Using tool chain created from cobuild.sh the make fails with: > > i686-pc-cygwin-gcc colinux/common/common.o > colinux/os/current/user/user.o > colinux/os/current/user/conet-daemon/main.o colinux > /os/current/user/conet-daemon/tap-win32.o colinux/user/user.a -o > colinux/os/current/user/conet-daemon/colinux-net-daemon.exe > -L/usr/src/colinux/cygwin/target/i686-pc-cygwin/lib/w32api -luser32 > -lgdi32 -lkernel32 -lmxml > i686-pc-cygwin-gcc -mpush-args -mno-accumulate-outgoing-args > -Wno-trigraphs -O2 -fno-strict-aliasing -Wall -D__KERNEL__ -DCO > _KERNEL -DCO_HOST_KERNEL -DWINVER=0x05000 -I. -I./../../linux/include > -I/usr/src/colinux/cygwin/target/i686-pc-cygwin/include > /w32api -c colinux/kernel/monitor.c -o colinux/kernel/monitor.o > colinux/kernel/monitor.c: In function `colinux_init': > colinux/kernel/monitor.c:140: error: `CO_VPTR_PSEUDO_RAM_PAGE_TABLES' > undeclared (first use in this function) > colinux/kernel/monitor.c:140: error: (Each undeclared identifier is > reported only once > colinux/kernel/monitor.c:140: error: for each function it appears in.) > colinux/kernel/monitor.c:153: error: > `CO_VPTR_PHYSICAL_TO_PSEUDO_PFN_MAP' undeclared (first use in this > function) > colinux/kernel/monitor.c:165: error: `CO_VPTR_SELF_MAP' undeclared > (first use in this function) > colinux/kernel/monitor.c:191: error: `CO_VPTR_PASSAGE_PAGE' undeclared > (first use in this function) > colinux/kernel/monitor.c: In function `co_monitor_iteration': > colinux/kernel/monitor.c:408: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c:409: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c:410: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c:411: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c:412: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c:413: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c:414: error: structure has no member named > `linuxvm_state' > colinux/kernel/monitor.c: In function `alloc_pseudo_physical_memory': > colinux/kernel/monitor.c:585: error: `CO_VPTR_PSEUDO_RAM_PAGE_TABLES' > undeclared (first use in this function) > colinux/kernel/monitor.c: In function `co_monitor_create': > colinux/kernel/monitor.c:704: error: `CO_VPTR_PASSAGE_PAGE' undeclared > (first use in this function) > colinux/kernel/monitor.c: At top level: > colinux/kernel/monitor.c:100: warning: `colinux_dump_page_at_address' > defined but not used > make: *** [colinux/kernel/monitor.o] Error 1 > > I have also created gentoo ebuilds for the toolchain as well as colinux. > Using these builds the make fails with: > > i686-pc-cygwin-gcc > -Wl,--base-file,colinux/os/current/build/driver.base.tmp \ > -Wl,--entry,_DriverEntry@8 \ > -nostartfiles -nostdlib \ > -o junk.tmp colinux/os/current/build/driver.o -lntoskrnl -lhal > -lgcc > colinux/os/current/build/driver.o(.text+0x43f2):alloc.c: undefined > reference to `__imp__MmAllocatePagesForMdl@28' > colinux/os/current/build/driver.o(.text+0x44b9):alloc.c: undefined > reference to `__imp__MmMapIoSpace@16' > collect2: ld returned 1 exit status > make: *** [colinux/os/current/build/driver.base.tmp] Error 1 > > With the environment created with cobuild.sh and my ebuilds I have been > able to build all snapshots and releases up until this snapshot. Any > ideas of what is happening? > I think it may be possible that the tool chain needs to be updated in > some way. I also think it may be to do with the linker but I have no > idea and as far as I can tell it is finding the w32api libs ie > notoskrnl. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAVENFnwJBIFTVIqwRAvrLAJwOefATrqqjNDf3gjShy760OvOyWQCffsF3 Q791vzal7UhDyLpkSYDAW0A= =wRCj -----END PGP SIGNATURE----- |
|
From: IWAMURO M. <vm...@ni...> - 2004-03-14 09:39:01
|
At Sun, 14 Mar 2004 07:25:23 +0200, Dan Aloni wrote: > On Sun, Mar 14, 2004 at 12:30:46PM +0900, IWAMURO Motonori wrote: > > I found that SMP system freeze completely at boot time of coLinux > > with TAP-Win32. (If disable TAP-Win32, then not freeze) <snip> > Can you please try again with the latest TAP-Win32 driver from > the OpenVPN package? By your suggestion, I tried again with TAP-Win32 from OpenVPN 1.6_rc2. But, the problem was not solved. The timing of system crash is not fixed. occasionally, crash after coLinux shutdown. |
|
From: Sean B. <sea...@so...> - 2004-03-14 07:26:54
|
Hi,
Attempting to build the 20040313 snapshot.
Using tool chain created from cobuild.sh the make fails with:
i686-pc-cygwin-gcc colinux/common/common.o
colinux/os/current/user/user.o
colinux/os/current/user/conet-daemon/main.o colinux
/os/current/user/conet-daemon/tap-win32.o colinux/user/user.a -o
colinux/os/current/user/conet-daemon/colinux-net-daemon.exe
-L/usr/src/colinux/cygwin/target/i686-pc-cygwin/lib/w32api -luser32
-lgdi32 -lkernel32 -lmxml
i686-pc-cygwin-gcc -mpush-args -mno-accumulate-outgoing-args
-Wno-trigraphs -O2 -fno-strict-aliasing -Wall -D__KERNEL__ -DCO
_KERNEL -DCO_HOST_KERNEL -DWINVER=0x05000 -I. -I./../../linux/include
-I/usr/src/colinux/cygwin/target/i686-pc-cygwin/include
/w32api -c colinux/kernel/monitor.c -o colinux/kernel/monitor.o
colinux/kernel/monitor.c: In function `colinux_init':
colinux/kernel/monitor.c:140: error: `CO_VPTR_PSEUDO_RAM_PAGE_TABLES'
undeclared (first use in this function)
colinux/kernel/monitor.c:140: error: (Each undeclared identifier is
reported only once
colinux/kernel/monitor.c:140: error: for each function it appears in.)
colinux/kernel/monitor.c:153: error:
`CO_VPTR_PHYSICAL_TO_PSEUDO_PFN_MAP' undeclared (first use in this
function)
colinux/kernel/monitor.c:165: error: `CO_VPTR_SELF_MAP' undeclared
(first use in this function)
colinux/kernel/monitor.c:191: error: `CO_VPTR_PASSAGE_PAGE' undeclared
(first use in this function)
colinux/kernel/monitor.c: In function `co_monitor_iteration':
colinux/kernel/monitor.c:408: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c:409: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c:410: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c:411: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c:412: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c:413: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c:414: error: structure has no member named
`linuxvm_state'
colinux/kernel/monitor.c: In function `alloc_pseudo_physical_memory':
colinux/kernel/monitor.c:585: error: `CO_VPTR_PSEUDO_RAM_PAGE_TABLES'
undeclared (first use in this function)
colinux/kernel/monitor.c: In function `co_monitor_create':
colinux/kernel/monitor.c:704: error: `CO_VPTR_PASSAGE_PAGE' undeclared
(first use in this function)
colinux/kernel/monitor.c: At top level:
colinux/kernel/monitor.c:100: warning: `colinux_dump_page_at_address'
defined but not used
make: *** [colinux/kernel/monitor.o] Error 1
I have also created gentoo ebuilds for the toolchain as well as colinux.
Using these builds the make fails with:
i686-pc-cygwin-gcc
-Wl,--base-file,colinux/os/current/build/driver.base.tmp \
-Wl,--entry,_DriverEntry@8 \
-nostartfiles -nostdlib \
-o junk.tmp colinux/os/current/build/driver.o -lntoskrnl -lhal
-lgcc
colinux/os/current/build/driver.o(.text+0x43f2):alloc.c: undefined
reference to `__imp__MmAllocatePagesForMdl@28'
colinux/os/current/build/driver.o(.text+0x44b9):alloc.c: undefined
reference to `__imp__MmMapIoSpace@16'
collect2: ld returned 1 exit status
make: *** [colinux/os/current/build/driver.base.tmp] Error 1
With the environment created with cobuild.sh and my ebuilds I have been
able to build all snapshots and releases up until this snapshot. Any
ideas of what is happening?
I think it may be possible that the tool chain needs to be updated in
some way. I also think it may be to do with the linker but I have no
idea and as far as I can tell it is finding the w32api libs ie
notoskrnl.
|
|
From: Dan A. <da...@co...> - 2004-03-14 05:25:33
|
On Sun, Mar 14, 2004 at 12:30:46PM +0900, IWAMURO Motonori wrote: > Hello, > > I found that SMP system freeze completely at boot time of coLinux > with TAP-Win32. (If disable TAP-Win32, then not freeze) > > http://sourceforge.net/tracker/index.php?func=detail&aid=915488&group_id=98788&atid=622063 Can you please try again with the latest TAP-Win32 driver from the OpenVPN package? -- Dan Aloni da...@co... |
|
From: IWAMURO M. <vm...@ni...> - 2004-03-14 03:30:57
|
Hello, I found that SMP system freeze completely at boot time of coLinux with TAP-Win32. (If disable TAP-Win32, then not freeze) http://sourceforge.net/tracker/index.php?func=detail&aid=915488&group_id=98788&atid=622063 |
|
From: Dan A. <da...@co...> - 2004-03-13 17:44:06
|
Hello, The last version in snapshots (which I added today) contains the reimplemented allocation method. I'm delaying the release since one issue needs to be resolved with this allocation method. There is a shortcoming with Windows' cache memory policy. On my 256MB setup, Windows sometimes refuses to release cache pages that could accommodate memory for coLinux. This means that with large memory settings, it is hard to tell whether the next coLinux boot would succeed. On that machine, the 128MB setting reaches that limit, and I am forced to bring it down to somewhat 110MB for it to boot. Another issue is that I don't have machines with more than 256MB of RAM to test this version with. I'd like to know about the typical behavior on setups with bigger amounts of RAM. So, try the snapshot with various RAM settings and send results. -- Dan Aloni da...@co... |
|
From: SatRookie <Sat...@ho...> - 2004-03-13 06:15:40
|
There are pictures of Knoppix running on coLinux.=20 Could someone post detailed instructions on how to do that? |
|
From: Clemmitt M. S. <sig...@bl...> - 2004-03-12 19:53:23
|
Hi, On Sat, 13 Mar 2004, [big5] wu fred wrote: > ****error***** > daemon failed: -1 Please read this thread in the Help forum: http://sourceforge.net/forum/forum.php?thread_id=1037285&forum_id=342355 and follow my suggestions at the end. I may be completely wrong with the solution I propose, but two other people reported problems caused by CR/LF line terminations here: http://sourceforge.net/forum/forum.php?thread_id=1033590&forum_id=342355 I also added this info as Q&A #12 in the FAQ in the Wiki: http://www.colinux.org/wiki/ If I'm wrong, please e-mail me privately and I'll fix this info so it doesn't confuse anyone else. HTH. Clemmitt |
|
From: <thi...@ya...> - 2004-03-12 19:33:44
|
Hi All!
I am new to colinux. I have followed the instruction from wiki to install colinux. However, I still encountered some problems. Could anyone help me?
****installtion steps*****
1. install the new adapter and it seems no problem
2. create directoryu c:\colinux
3. untar the contents of colinux-20040225/ and colinux-20040225-bin/ to c:\colinux
4. in CMD, type colinux-daemon.exe
****default.colinux**********
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
<block_device index="0" path="\DosDevices\c:\colinux\Debian-3.0r0.ext3.1gb" enabled="true"> </block_device>
<block_device index="1" path="\DosDevices\c:\colinux\swap_device" enabled="false"> </block_device>
<bootparams>root=/dev/cobd0</bootparams>
<image path="vmlinux"></image>
<memory size="64"></memory>
<network index="0" type="tap" name="TAP"></network>
</colinux>
****error*****
........
Manager not opened
........
daemon failed: -1
I will be appreciate for any kinds of help!
Thanks a lot for reading!
Best,
Fred
必殺技、飲歌、小星星...
浪漫鈴聲 情心連繫
http://ringtone.yahoo.com.hk/
|
|
From: Nathan C. <nat...@ya...> - 2004-03-12 00:36:05
|
I am glad to hear that the refresh issue with the console has been resolved, though it only slowed me down slightly while I was getting sshd installed and running. Once that is up, I just use putty. It would be nice to run the application as a service. I was never able to get Gentoo linux to boot on my desktop (IBM MPro), but it runs very well on CoLinux. I love this application! I am running on Windows XP and have Internet Connection Sharing configured to forward port 22 (and a few others) to the Linux box. So I can connect to my desktop's address from anywhere on my company's network with Putty and end up inside the linux box. I love it! Much thanks to Dan Aloni!!! Thanks also to those who suggested to install Gentoo from scratch (stage 2) and compile everything for i386 -- no more segmentation faults! Regards, Nathan Chilton Folsom, CA --- Ballard Jonathan <sac...@ho...> wrote: > > ----- Original Message ----- > BUGreport: > > - the gui console "forget" the text, we need to > press [ENTER] to force > > a refresh of text. > > Reported and fixed. > > > - the gui font is very small. > > - the build method is not ready for absolutelly > idiots like me (I admit) > > > > Will provide more detailed info if needed. > > Please submit each item individually to the project > tracker for such good > suggestions and any details that would make it > easier! > For more information: > http://www.colinux.org/wiki/index.php/SupportIssue > > > WishList: > > - Fullscreen alike mode. EXACTLY like putty. > > Done. Try colinux-console-nt.exe. > > > - or.. better gui console. > > You have two choices. > > > - or the ability of change the font size > > Works with colinux-console-nt.exe. > > > - or a easyer build system (for deep idiots like > me) > > Try cobuild.sh located in the bin directory under > the coLinux sources. > > Thanks for your input. > > Jonathan > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux > Tutorials > Free Linux tutorial presented by Daniel Robbins, > President and CEO of > GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel __________________________________ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com |
|
From: tei <42...@in...> - 2004-03-11 23:20:06
|
Pat Erley escribió: > On Thu, 11 Mar 2004 22:40:01 +0100 > tei <42...@in...> wrote: > >> - Fullscreen alike mode. EXACTLY like putty. > > > you could start sshd and use putty. > > Pat Erley > LOL!!... *Excellent* idea. Thanks for you fast reply! the wiki suggest a method to enable networking that use ICS (window software nat), or something similar, and thats break my system beyond recognition (we already use a fragile setup with a nat router). Will retry has your suggestion can become amazingly interesting.. Humm... Its this work, the next cool thing can be to run the machine in background, and connect/disconnect putty has neeeded.. Will future versions minimice has a icon or run has a NT service? .. I am very idiot, so detach from desktop is a good idea, or I will click close the wrong taskbutton. |
|
From: Ballard J. <sac...@ho...> - 2004-03-11 23:05:34
|
----- Original Message ----- > BUGreport: > - the gui console "forget" the text, we need to press [ENTER] to force > a refresh of text. Reported and fixed. > - the gui font is very small. > - the build method is not ready for absolutelly idiots like me (I admit) > > Will provide more detailed info if needed. Please submit each item individually to the project tracker for such good suggestions and any details that would make it easier! For more information: http://www.colinux.org/wiki/index.php/SupportIssue > WishList: > - Fullscreen alike mode. EXACTLY like putty. Done. Try colinux-console-nt.exe. > - or.. better gui console. You have two choices. > - or the ability of change the font size Works with colinux-console-nt.exe. > - or a easyer build system (for deep idiots like me) Try cobuild.sh located in the bin directory under the coLinux sources. Thanks for your input. Jonathan |
|
From: Pat E. <pat...@ma...> - 2004-03-11 22:34:56
|
On Thu, 11 Mar 2004 22:40:01 +0100 tei <42...@in...> wrote: > - Fullscreen alike mode. EXACTLY like putty. you could start sshd and use putty. Pat Erley |
|
From: tei <42...@in...> - 2004-03-11 21:59:40
|
User suggestion: Hello. I think this project is very interesting, this my feedback/bugreport/wishlist: FeedBack: - We have download this stuff because sound fun. After a number of test looks like very stable, and use much fewer resources than VMWARE so.. can ve a replacement to some task or able strong majik here, at my w2k box. - Thanks for this nice effort!!!! BUGreport: - the gui console "forget" the text, we need to press [ENTER] to force a refresh of text. - the gui font is very small. - the build method is not ready for absolutelly idiots like me (I admit) Will provide more detailed info if needed. WishList: - Fullscreen alike mode. EXACTLY like putty. - or.. better gui console. - or the ability of change the font size - or a easyer build system (for deep idiots like me) Thats all, for now. Thanks! Tei _:D |
81 messages has been excluded from this view by a project administrator.
