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: Régis N. <rn...@ho...> - 2004-02-09 04:04:58
|
Hi I made one: 1,17 Mb , nsis lzma compression (best) , no image, the files are from the last sourceforge drop, devcon.exe is from openvpn and is used to install/remove the network service. http://www.ultrabigmailbox.com/colinux.nsi http://www.ultrabigmailbox.com/colinux.exe for tests (upload it in sourceforge maybe , it won't last) NOTE: I named prefixed TAP stuff with CO so that people using OpenVpn can run both TAP-WIN32 and COTAP-WIN32 Keep up the good work guys Regis _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus |
|
From: Ballard J. <sac...@ho...> - 2004-02-09 03:24:49
|
I added an #include to os/winnt/kernel/lowlevel/alloc.c. There was no specific definition of PAGE_SIZE except in asm/page.h. It could have conflicted with the PAGE_SIZE from the DDK, and I think the linux one is preferred: #include <asm/page.h> |
|
From: Richard G. <rgo...@nu...> - 2004-02-09 02:13:39
|
Here's a handy tip for those of you (us!) Windows only guys that need more space and swap memory in the cL session. Here's how I did it: 1. Copy the Debian disk image and rename it in Windows (like extra-partition.image or whatever) 2. Edit the XML file from coLinux and add a new line that points to the new image; be sure to increase the Index to 1 (or 2, or 3, as you add things). 3. (Re)boot cL, and create a partition on /dev/cobd1 (assuming that this is the first new image you added. The next will be at /dev/cobd2, etc). Use fdisk to create a type 83 partition. 4. Reboot cL to recognize the new partition, and mke2fs (or whatever filesystem you want) on /dev/cobd1. 5. I then mounted the new partition to /usr2, copied /usr contents to it, then deleted /usr. Then rename /usr2 to /usr, and edit /etc/fstab to mount /usr at /dev/cobd1. Then, to add swap space: 1. In cL, do "dd if=/dev/zero of=swapfile.image bs=1024 count=250000" for a 256mb swapfile, or 128000 for 128mb, etc. 2. In cL do "mkswap swapfile.image". 3. Copy the swapfile.image to your Windows partition (I used smbclient on one machine, and ftp on another...) 4. Add a new line to the XML to make sure it gets mounted, and edit the /etc/fstab to include it as a swap partition so it gets mounted at boot time! I used "/dev/cobd2 swap swap defaults 0 0" Hope this helps someone...let me know so I'm not wasting everyone's time! :-) Richard |
|
From: andre <avb...@gm...> - 2004-02-09 01:42:43
|
On Monday 09 February 2004 01:42, Tony Hoyle wrote: > my...@gm... wrote: > > I am having some problems with the cygwin dlls. My installation of Cygwin > > doesn't match the dll version distributed with cL and I haven't had any > > luck compiling colinux-console and colinux-daemon under cygwin. > > I deleted the cygwin1.dll that came with colinux and used the global one > (since that was what the error message was telling me to do anyway). It > seemed to be OK. > > Tony > Will that also work with a future cygwin1.dll? Better is to rename it during build to another name and use that |
|
From: <my...@gm...> - 2004-02-09 00:49:26
|
I could have sworn I tried that. Well, I tried it again and it worked. I musta done something wrong the first time. Thanks, Tony. Now to apt-get some X-windows clients! Larry. > my...@gm... wrote: > > >> I am having some problems with the cygwin dlls. My installation of >> Cygwin >> doesn't match the dll version distributed with cL and I haven't had any >> luck compiling colinux-console and colinux-daemon under cygwin. >> > I deleted the cygwin1.dll that came with colinux and used the global one > (since that was what the error message was telling me to do anyway). It > seemed to be OK. > > Tony > > > > ------------------------------------------------------- > 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: Tony H. <tm...@no...> - 2004-02-09 00:45:53
|
Ballard Jonathan wrote: > About the "long long," it is unfortunate that such C syntax is not > standardized. I imagine it is one of the reasons why Intel and other It is... It's in the C99 standard (ratified in 1999, funnily enough). http://home.tiscalinet.ch/t_wolf/tw/c/c9x_changes.html What compiler are you using that doesn't support this? Tony |
|
From: Tony H. <tm...@no...> - 2004-02-09 00:42:43
|
my...@gm... wrote: > I am having some problems with the cygwin dlls. My installation of Cygwin > doesn't match the dll version distributed with cL and I haven't had any > luck compiling colinux-console and colinux-daemon under cygwin. > I deleted the cygwin1.dll that came with colinux and used the global one (since that was what the error message was telling me to do anyway). It seemed to be OK. Tony |
|
From: <my...@gm...> - 2004-02-09 00:37:07
|
Dan, Great work! I now have a Win-XP Pro system running coLinux with networking. This stuff is "off da hook"! I am having some problems with the cygwin dlls. My installation of Cygwin doesn't match the dll version distributed with cL and I haven't had any luck compiling colinux-console and colinux-daemon under cygwin. Is there a simpler build process I could use just for the colinux-daemon that would have fewer (or no) cygwin dependencies? Especially since colinux-console is not really required, once you've got cL set up. Or is there something else I should look at? Larry. |
|
From: Ballard J. <sac...@ho...> - 2004-02-09 00:36:50
|
I was curious about the intention of the packed data structures. There are
many of them. I wondered if they are required to be packed or if they just
save space being packed. Packed structures are great at size but at the
cost of speed being non-aligned. If there is no requirement for them to be
packed, then would an option that optimizes for speed be pratical?
About the "long long," it is unfortunate that such C syntax is not
standardized. I imagine it is one of the reasons why Intel and other
manufacturers hold back their 64 bit processors. That is one of the reasons
why a header file is usually made to standardized the syntax at the project
level. Most variables within functions do not need a project level syntax,
yet it is helpful. The data structures, however, need a standard. An
example:
In the project level header:
#define coLinuxNatural8bit unsigned char
#define coLinuxNatural16bit unsigned short
#define coLinuxNatural32bit unsigned long
#define coLinuxNatural64bit unsigned long long
In a specific structure definition header:
struct _coLinuxExample {
coLinuxNatural16bit one ;
coLinuxNatural16bit two ;
coLinuxNatural64bit three ;
} ;
That works for GNUC but what if my compiler does not support it because
"long long is not standardized, insert:
#undef coLinuxNatural64bit
#define coLinuxNatural64bit unsigned _int64
The structure definition stays the same without a bunch of #ifdefs.
Those longer names get tedious to type but they document the code well. For
the procedure level or module level:
typedef coLinuxNatural8bit NATURAL8
typedef coLinuxNatural16bit NATURAL16
typedef coLinuxNatural32bit NATURAL32
typedef coLinuxNatural64bit NATURAL64
NATURAL64 function( NATURAL32 NUMBER )
{
NATURAL16 blah, blah, blah ;
..
The typedef dereferences the macro and allows the compilers to easily
cooperate between types or warn otherwise.
Jonathan
|
|
From: Bjorn S. <sw...@in...> - 2004-02-09 00:12:54
|
What I did was download the -bin.tar.gz package, and the Debian disk = image. Extract them into c:\colinux Control Panel -> Add Hardware -> Select Yes, I have connected the = hardware -> Scroll all the way down to Add a new hardware device ->=20 Install the hardware that I manually select from a list -> Network Adapters -> Click on have disk, browse to C:\colinux\TAP-Win32 Select the TAP-Win32 adapter and click next Then, just start colinux-daemon.exe=20 -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Jeff = Smith Sent: Sunday, February 08, 2004 5:40 PM To: col...@li... Subject: [coLinux-devel] how do I... this is porbably asked all the time, but how can I install Cooperative = Linux on Windows XP? I don't see an installer... =20 |
|
From: Régis N. <rn...@ho...> - 2004-02-08 23:46:57
|
Hi
I just got it to work on a real debian 3.0 installation ( which was in my
/dev/hda2 )
(system = XP Home edition)
Here is the config file:
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
<block_device index="0" path="\Device\HarddiskVolume2" enabled="true">
</block_device>
<block_device index="1" path="\DosDevices\D:" enabled="true">
</block_device>
<bootparams>root=/dev/cobd0</bootparams>
<image path="vmlinux"></image>
</colinux>
As you can see I also tried to mount my CD drive ( D: ) but iso9660 was not
supported on the minimal install.
Feature request: add a node or attrib for device mapping :
I had to modify my fstab line where /dev/hda2 / to /dev/codb0 /
how about a node like this: <block_device map="/dev/hda2/" ...> ?
This way the same system can run for real (dual boot) or emulated in
windows !!
No Network still.
Would you mind joining irc.freenode.org #colinux ?
Regis
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
|
|
From: Dan A. <da...@gm...> - 2004-02-08 21:36:30
|
On Sun, Feb 08, 2004 at 11:28:30PM +0200, Dan Aloni wrote:
> Hello,
>
> It turns out that sending network interrupts before the conet driver is
> initialized causes it to malfunction. That's why in 0.5.3-pre1 you
> sometimes can't ping the machine, since colinux-net-daemon starts sending
> ethernet frames to Linux before conet is initialized.
>
> I got this fixed quite easily, by making co_handle_device_interrupt()
> aware to the initialization status of conet, not sending the interrupts
> when it is not initialized.
A patch, for those of you who compile vmlinux from sources. Apply this
after patch/linux.
diff -u linux/arch/i386/kernel/cooperative.c linux/arch/i386/kernel/cooperative.c
--- linux/arch/i386/kernel/cooperative.c 2004-02-07 23:41:53.000000000 +0200
+++ linux/arch/i386/kernel/cooperative.c 2004-02-08 23:18:32.000000000 +0200
@@ -29,6 +29,7 @@
unsigned char kbd_scancode = 0;
unsigned char conet_frame[1600] = {0, };
unsigned long conet_frame_len = 0;
+unsigned long conet_enabled = 0;
void co_handle_device_interrupt(co_linux_message_t *message)
{
@@ -75,6 +76,9 @@
break;
}
+ if (!conet_enabled)
+ break;
+
if (conet_frame_len == 0) {
conet_frame_len = message->size;
memcpy(conet_frame, message->data, conet_frame_len);
diff -u linux/drivers/net/conet.c linux/drivers/net/conet.c
--- linux/drivers/net/conet.c 2004-02-07 19:42:19.000000000 +0200
+++ linux/drivers/net/conet.c 2004-02-08 23:18:09.000000000 +0200
@@ -19,6 +19,10 @@
struct net_device conet_dev;
+extern unsigned char conet_frame[1600];
+extern unsigned long conet_frame_len;
+extern unsigned long conet_enabled;
+
void conet_interrupt(int irq, void *dev_id, struct pt_regs *reg_ptr);
int conet_open(struct net_device *dev)
@@ -33,6 +37,8 @@
printk("conet: initialized\n");
+ conet_enabled = 1;
+
netif_start_queue(dev);
return 0;
@@ -44,6 +50,8 @@
netif_stop_queue(dev); /* can't transmit any more */
+ conet_enabled = 0;
+
MOD_DEC_USE_COUNT;
return 0;
@@ -73,9 +81,6 @@
return 0;
}
-extern unsigned char conet_frame[1600];
-extern unsigned long conet_frame_len;
-
void conet_rx(struct net_device *dev)
{
struct sk_buff *skb;
--
Dan Aloni
da...@gm...
|
|
From: 3DoFF <3D...@ma...> - 2004-02-08 21:35:02
|
Hello, Dan, Monday, February 9, 2004, 12:21:32 AM, you wrote: DA> Any distribution can run under coLinux with some minimal tweakings. DA> Knoopix is just a useful example. Thank you, that is what I wanted to hear. As soon as I can, I'll test the Morphix 0.3.5 and post my report here. -- 3DoFF |
|
From: Dan A. <da...@gm...> - 2004-02-08 21:28:37
|
Hello, It turns out that sending network interrupts before the conet driver is initialized causes it to malfunction. That's why in 0.5.3-pre1 you sometimes can't ping the machine, since colinux-net-daemon starts sending ethernet frames to Linux before conet is initialized. I got this fixed quite easily, by making co_handle_device_interrupt() aware to the initialization status of conet, not sending the interrupts when it is not initialized. -- Dan Aloni da...@gm... |
|
From: Richard G. <ric...@ri...> - 2004-02-08 21:24:22
|
3DoFF, Download it and try other disk images :-) You'll see there is a Debian disk image right on the sourceforge download page. KNOPPIX is just an example. ----- Original Message ----- From: "3DoFF" <3D...@ma...> To: <col...@li...> Sent: Sunday, February 08, 2004 3:15 PM Subject: [coLinux-devel] Only Knoppix? > Hello, colinux-devel, > > First of all i'd like to thank the dev team for such a nice project! > > Text from coLinux.org: > > "In its current condition, it allows us to run the KNOPPIX Japanese > Edition on Windows..." > > Here goes my questions: Is only Knoppix supported? How soon will other > unix-based systems support be added to coLinux? > > Sorry for my poor english. > > -- > 3DoFF > > > > ------------------------------------------------------- > 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: Dan A. <da...@gm...> - 2004-02-08 21:21:39
|
On Mon, Feb 09, 2004 at 12:15:12AM +0300, 3DoFF wrote: > Here goes my questions: Is only Knoppix supported? How soon will other > unix-based systems support be added to coLinux? Any distribution can run under coLinux with some minimal tweakings. Knoopix is just a useful example. -- Dan Aloni da...@gm... |
|
From: 3DoFF <3D...@ma...> - 2004-02-08 21:18:22
|
Hello, colinux-devel, First of all i'd like to thank the dev team for such a nice project! Text from coLinux.org: "In its current condition, it allows us to run the KNOPPIX Japanese Edition on Windows..." Here goes my questions: Is only Knoppix supported? How soon will other unix-based systems support be added to coLinux? Sorry for my poor english. -- 3DoFF |
|
From: Dan A. <da...@gm...> - 2004-02-08 20:36:33
|
On Sun, Feb 08, 2004 at 12:16:39PM -0500, Evan Danaher wrote: > I ran colinux-daemon, and a console popped up and booted nicely. Next I > ran colinux-net-daemon, and it displayed "Enabling TAP-Win32...", followed > by "Connecting to daemon", while colinux-daemon displayed "Module > connected: conet0" followed by "co_message_switch: setting callback rule > for 8". However, within the console, ping is unsuccessful (I also tried > IP addresses in case only DNS was broken). Also, I checked "status" on > the TAP-win32 adapter, and it said some (under a hundred) bytes had been > sent, and the number seemed to go up sporadically, independent of when I > tried to ping. You don't need to run the colinux-net-dameon.exe yourself. Open the Task Manager, and see: colinux-daemon.exe automatically launches colinux-net-daemon on startup. This would be configurable in the future. > I understand that this is only a very early pre-release, but I thought it > was worth letting you know - either someone will let me know what I'm > doing wrong, or else a bug may be fixed. > > Also, this is probably unrelated, but under control panel->network > connections, when I right-click on the TAP-win32 adapter, the "delete" > option is grayed out. I was hoping to reinstall this to see if that was > the problem, but I can't get rid of it! Any suggestions? Go to Properties -> Uninstall. -- Dan Aloni da...@gm... |
|
From: Richard G. <ric...@ri...> - 2004-02-08 17:35:18
|
What are the IP addresses of all the involved adapters? (dialup, TAP, coLinux eth0) Delete is missing for me too, when I wanted to remove it last time I just deleted it from Device Manager. ----- Original Message ----- From: "Evan Danaher" <eda...@tj...> To: <col...@li...> Sent: Sunday, February 08, 2004 11:16 AM Subject: [coLinux-devel] Another not-quite-perfect installation > First, I'd like to say I love the idea of this project - I've been using > Cygwin for years, and would love to get away from it's "most things just > compile, but a few just don't." (Not to say I don't like it - it's just > that I don't want to spend the effort to patch code to get it to compile). > > However, I'm having a problem with coLinux - today's build runs nicely, > but I can't connect to the Internet. I installed the TAP-win32 adapter, > however I cannot get it to work. I'm not sure if this is due to my error, > an error with my computer, or the fact that I have dialup. > > I ran colinux-daemon, and a console popped up and booted nicely. Next I > ran colinux-net-daemon, and it displayed "Enabling TAP-Win32...", followed > by "Connecting to daemon", while colinux-daemon displayed "Module > connected: conet0" followed by "co_message_switch: setting callback rule > for 8". However, within the console, ping is unsuccessful (I also tried > IP addresses in case only DNS was broken). Also, I checked "status" on > the TAP-win32 adapter, and it said some (under a hundred) bytes had been > sent, and the number seemed to go up sporadically, independent of when I > tried to ping. > > I understand that this is only a very early pre-release, but I thought it > was worth letting you know - either someone will let me know what I'm > doing wrong, or else a bug may be fixed. > > Also, this is probably unrelated, but under control panel->network > connections, when I right-click on the TAP-win32 adapter, the "delete" > option is grayed out. I was hoping to reinstall this to see if that was > the problem, but I can't get rid of it! Any suggestions? > > > > ------------------------------------------------------- > 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: Evan D. <eda...@tj...> - 2004-02-08 17:28:25
|
First, I'd like to say I love the idea of this project - I've been using Cygwin for years, and would love to get away from it's "most things just compile, but a few just don't." (Not to say I don't like it - it's just that I don't want to spend the effort to patch code to get it to compile). However, I'm having a problem with coLinux - today's build runs nicely, but I can't connect to the Internet. I installed the TAP-win32 adapter, however I cannot get it to work. I'm not sure if this is due to my error, an error with my computer, or the fact that I have dialup. I ran colinux-daemon, and a console popped up and booted nicely. Next I ran colinux-net-daemon, and it displayed "Enabling TAP-Win32...", followed by "Connecting to daemon", while colinux-daemon displayed "Module connected: conet0" followed by "co_message_switch: setting callback rule for 8". However, within the console, ping is unsuccessful (I also tried IP addresses in case only DNS was broken). Also, I checked "status" on the TAP-win32 adapter, and it said some (under a hundred) bytes had been sent, and the number seemed to go up sporadically, independent of when I tried to ping. I understand that this is only a very early pre-release, but I thought it was worth letting you know - either someone will let me know what I'm doing wrong, or else a bug may be fixed. Also, this is probably unrelated, but under control panel->network connections, when I right-click on the TAP-win32 adapter, the "delete" option is grayed out. I was hoping to reinstall this to see if that was the problem, but I can't get rid of it! Any suggestions? |
|
From: Dan A. <da...@gm...> - 2004-02-08 06:34:55
|
On Sat, Feb 07, 2004 at 07:23:19PM -0600, Richard Goodwin wrote: > Something appeared to be odd with the networking (at least the first few > times I tried). If I started with -d, I could ping the cL session, but if I > let the console autostart, I can't. > > AFter some more playing around, it seems like when I close the console > sometimes networking dies. (killing console with the X). Yep, there was a bug in the daemon, this should fix it: --- colinux-20040208/src/colinux/user/daemon.c 2004-02-08 01:20:19.000000000 +0200 +++ colinux-main/src/colinux/user/daemon.c 2004-02-08 08:32:12.000000000 +0200 @@ -556,7 +556,7 @@ message.message.type = CO_MESSAGE_TYPE_OTHER; message.message.size = sizeof(message.switchm); message.switchm.type = CO_SWITCH_MESSAGE_FREE_RULE; - message.switchm.destination = CO_MODULE_CONET0; + message.switchm.destination = module->id; co_message_switch_dup_message(&module->daemon->message_switch, &message.message); co_message_switch_free_rule(&module->daemon->message_switch, module->id); -- Dan Aloni da...@gm... |
|
From: Dan A. <da...@gm...> - 2004-02-08 06:08:26
|
On Sat, Feb 07, 2004 at 07:23:19PM -0600, Richard Goodwin wrote: > Something appeared to be odd with the networking (at least the first few > times I tried). If I started with -d, I could ping the cL session, but if I > let the console autostart, I can't. > > AFter some more playing around, it seems like when I close the console > sometimes networking dies. (killing console with the X). > > Anyone else? I knew there was something I missed. I'll look into this, thanks. What about the network packet corruption problem? Does anyone still experience it with 0.5.3-pre1? -- Dan Aloni da...@gm... |
|
From: Dan A. <da...@gm...> - 2004-02-08 06:06:21
|
On Sat, Feb 07, 2004 at 09:08:07PM -0800, Chris Dahl wrote: > Anyway... to my question... I guess I am wondering if the TAP driver is ONLY > needed for networking. That is, I know that if you try to run colinux without > it, it dies. Could colinux be configured to continue "booting" even if the > driver is not installed? Why? I was just thinking about how cool it would be > if I had colinux and a small disk image on my keychain flash drive. Then I > could just plug it into whatever Windows computer I happen to have handy, click > an icon and have linux up and running. No drivers required. (nice if it not > YOUR computer) I realize that the xml configuration file has the location of > the disk image hard coded, but it would be easy enough to address that. And > yes, I know that flash has a "limited" number of write cycles... Just wondering > if it can be done. Thoughts? > > Again, thank you for such a great project. Latest version of coLinux (0.5.3-pre1) can work without the TAP driver, since I separated the colinux net daemon from the main daemon. And about Windows drivers, coLinux must use its own driver (linux.sys) in order to run. -- Dan Aloni da...@gm... |
|
From: Chris D. <da...@ya...> - 2004-02-08 05:08:16
|
First off, let me say thanks to everone working on this project. I have played with it a bit and it is quite cool. I did some VERY informal benchmarking with some neural network stuff that I wrote and got some nice numbers. I ran the program under cygwin and then recompiled and ran it under colinux. It looked like there was only a 15% performance hit under colinux. (the program uses a mix of floats, ints, arrays and linked lists with a little bit of file I/O if you were wondering) Anyway... to my question... I guess I am wondering if the TAP driver is ONLY needed for networking. That is, I know that if you try to run colinux without it, it dies. Could colinux be configured to continue "booting" even if the driver is not installed? Why? I was just thinking about how cool it would be if I had colinux and a small disk image on my keychain flash drive. Then I could just plug it into whatever Windows computer I happen to have handy, click an icon and have linux up and running. No drivers required. (nice if it not YOUR computer) I realize that the xml configuration file has the location of the disk image hard coded, but it would be easy enough to address that. And yes, I know that flash has a "limited" number of write cycles... Just wondering if it can be done. Thoughts? Again, thank you for such a great project. --Chris ===== There is a very fine line between "hobby" and "mental illness." --Dave Barry home: http://www.dahlweb.net |
|
From: Richard G. <rgo...@nu...> - 2004-02-08 04:34:04
|
Is it possible for someone to compile resize2fs for use under Cygwin? I tried my darndest, but I get libiconv link errors that I can't resolve. That+dd should allow us mere mortals to resize their Debian root images :-) Also, I'm still not able to run KDE or GNOME from Debian/unstable...KDE hangs at various stages of initialization, and gnome (running gnome-session) just sits at the splash screen. Is it an unstable problem, user error, or cL quirk? Thanks! |
81 messages has been excluded from this view by a project administrator.
