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: Ballard J. <sac...@ho...> - 2004-03-02 17:22:57
|
The snapshot is of two machines that both ran coLinux. Academix-g = hosts the "production" version of coLinux. The console for that machine = can be seen in the remote desktop. The xterm sessions are connected to = the academix-g coLinux. The MSVC session accesses files from the = coLinux on the academix-g; it sends remote commands via SSH, like the = makefile compilation. The files are accessed via the Samba server, K: = drive. My frontend machine, Academix, runs a test version of coLinux. = The newer console is shown on the screen for the frontend coLinux. Just another cooperative day... http://atomatrix.sf.net/colinux20040302.JPG |
|
From: Gregor M. <mi...@ra...> - 2004-03-02 16:59:27
|
Hi, this is probably a silly question: How can make the kernel modules of coLinux to be available? I'd like to modprobe 'smbfs' Thank's for any answers. --Gregor |
|
From: Sean B. <sea...@so...> - 2004-03-02 16:56:07
|
----- Original Message ----- From: "Erlend Slettevoll" <sle...@st...> To: "Sean Brook" <sea...@so...> Cc: "keksov" <ke...@gm...>; <col...@li...> Sent: Tuesday, March 02, 2004 4:01 PM Subject: Re: [coLinux-devel] Re: mounting cdrom | > | You claim it's possible to mount devices in a non-raw way using | > | \DosDevices\<drive letter>, but I've not been able to do this. | > This is the only way I can do it. I think that it is interesting that our | > experience is the complete opposite. Again, AFAIK this is not raw | > access. | | Ok. And you are then able to access the drive from both XP and linux at | the same time? No I cannot. | | Anyone else had experiences with mounting non-raw devices? | | > If it's | > | then mounted through some windows-driver, shouldn't it be able to access | > | drives already mounted by XP in that way too (both harddisks and cdroms)? | > Exactly. Though I personally wont be doing that on a hard disk. | | If windows is managing the reading/writing to the disk, this shouldn't be | a problem, should it? Anyway, I'm just experimenting on a non-important | drive. I think that is a big 'should'. It is Windows after all. Personally I do not think that it works exactly like that. ie. it is not as concrete as raw and not raw as in Linux IMO. I hope that I am proved wrong and you can tell me how you get on ;) | | --Erlend | | | ------------------------------------------------------- | SF.Net is sponsored by: Speed Start Your Linux Apps Now. | Build and deploy apps & Web services for Linux with | a free DVD software kit from IBM. Click Now! | http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | _______________________________________________ | coLinux-devel mailing list | coL...@li... | https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Erlend S. <sle...@st...> - 2004-03-02 16:14:43
|
> | You claim it's possible to mount devices in a non-raw way using > | \DosDevices\<drive letter>, but I've not been able to do this. > This is the only way I can do it. I think that it is interesting that our > experience is the complete opposite. Again, AFAIK this is not raw > access. Ok. And you are then able to access the drive from both XP and linux at the same time? Anyone else had experiences with mounting non-raw devices? > If it's > | then mounted through some windows-driver, shouldn't it be able to access > | drives already mounted by XP in that way too (both harddisks and cdroms)? > Exactly. Though I personally wont be doing that on a hard disk. If windows is managing the reading/writing to the disk, this shouldn't be a problem, should it? Anyway, I'm just experimenting on a non-important drive. --Erlend |
|
From: Sean B. <sea...@so...> - 2004-03-02 16:10:08
|
| | You claim it's possible to mount devices in a non-raw way using | | \DosDevices\<drive letter>, but I've not been able to do this. Forgot to mention to take a look at HKLM\SYSTEM\MountedDevices |
|
From: Sean B. <sea...@so...> - 2004-03-02 16:05:28
|
----- Original Message ----- From: "Erlend Slettevoll" <sle...@st...> To: "Sean Brook" <sea...@so...> Cc: "keksov" <ke...@gm...>; <col...@li...> Sent: Tuesday, March 02, 2004 3:38 PM Subject: [coLinux-devel] Re: mounting cdrom | > With iso9660 support I can mount a cdrom using a path through | > \DosDevices\<drive letter> | > This is not raw access AFAIK | > Windows has lots of keys to access the same value with lots of | > redundancy in the registry. | > AFAIK the raw way to a cdrom is accessed through: | > \Device\Cdrom<x> | > When I try to mount a cdrom through that device my system | > just reboots. I think this is to expected because NT does not | > let software access hardware directly (at least it did not used | > too, ie HAL). | | Ok... I'm back with a little update. I'm now able to mount raw | cdrom-devices using \Device\Cdrom<x>. I had some problems with my | DVD-drive at first, but when I turned off autoplay I would prefer if my system allowed me access to \Device\Cdrom<x> but again, it reboots. I have autoplay off btw | (http://www.microsoft.com/windowsxp/expertzone/tips/february/knox1.asp), | everything goes smooth. I'm unable to mount if the drive is accessed by | explorer or any other program, and the drive is inaccessable from XP when | mounted in linux (no surprises here). | | You claim it's possible to mount devices in a non-raw way using | \DosDevices\<drive letter>, but I've not been able to do this. This is the only way I can do it. I think that it is interesting that our experience is the complete opposite. Again, AFAIK this is not raw access. If it's | then mounted through some windows-driver, shouldn't it be able to access | drives already mounted by XP in that way too (both harddisks and cdroms)? Exactly. Though I personally wont be doing that on a hard disk. | | --Erlend | | | ------------------------------------------------------- | SF.Net is sponsored by: Speed Start Your Linux Apps Now. | Build and deploy apps & Web services for Linux with | a free DVD software kit from IBM. Click Now! | http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | _______________________________________________ | coLinux-devel mailing list | coL...@li... | https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Erlend S. <sle...@st...> - 2004-03-02 15:50:51
|
> With iso9660 support I can mount a cdrom using a path through > \DosDevices\<drive letter> > This is not raw access AFAIK > Windows has lots of keys to access the same value with lots of > redundancy in the registry. > AFAIK the raw way to a cdrom is accessed through: > \Device\Cdrom<x> > When I try to mount a cdrom through that device my system > just reboots. I think this is to expected because NT does not > let software access hardware directly (at least it did not used > too, ie HAL). Ok... I'm back with a little update. I'm now able to mount raw cdrom-devices using \Device\Cdrom<x>. I had some problems with my DVD-drive at first, but when I turned off autoplay (http://www.microsoft.com/windowsxp/expertzone/tips/february/knox1.asp), everything goes smooth. I'm unable to mount if the drive is accessed by explorer or any other program, and the drive is inaccessable from XP when mounted in linux (no surprises here). You claim it's possible to mount devices in a non-raw way using \DosDevices\<drive letter>, but I've not been able to do this. If it's then mounted through some windows-driver, shouldn't it be able to access drives already mounted by XP in that way too (both harddisks and cdroms)? --Erlend |
|
From: Bart K. <Bar...@su...> - 2004-03-02 15:35:50
|
Hi, I have tried to get IPv6 up and running with cL in bridged mode, but cL doesn't get the IPv6 address from the autoconfiguration (based on the IPv6 prefex broadcasted by the router). The routing-table is set allright (correct prefix is in the routing table for IPv6), but the IPv6-address is'n related to the eth0. The console reports: conet0: initialized IPv6 v0.8 for NET4.0 IPv6 over IPv4 tunneling driver eth0: duplicate address detected! IPv4 works fine, tcpdump for IPv6 traffic works fine too (I can see broadcasts) but the eth0 doesn't get the right IPv6 address. As far as I know WinPCAP is already in promiscious mode (cL network mode is bridged) and should therefore already receive the (IPv6-) packets with the prefix. The desktop is running IPv6 and that is on autoconfiguration. Anyone who has this up and running, I use a adapted kernel + modules from Matus Horvath. Best Regards, Bart |
|
From: Clemmitt M. S. <sig...@bl...> - 2004-03-02 15:30:06
|
Hi, On Tue, 2 Mar 2004, Sean Brook wrote: > | Is it path="\Device\HarddiskVolumeX", or is it > | path="\Device\HarddiskVolumeX\PartitionY", or what? > The value in 'path' is not a coLinux thing. It is a Windows thing. Oh, dear me. My bad! I'll google for some info and try to fix anything I got wrong. > I agree. Though I think first we just started posting back here what > works and what doesnt. There is already incorrect information in > the wiki ;) Well, this is just my opinion, but I think we should edit the Wiki to correct misinformation. If I wrote anything wrong (I've tried not to, but I am well known to mess up ;^) I certain hope someone would correct it. And I'd hope anyone who wrote something inaccurate wouldn't mind having the record set straight. Please let me know where the incorrect info is and, if I can, I'll correct it. Thanks :^) Clemmitt |
|
From: Sean B. <sea...@so...> - 2004-03-02 15:24:58
|
----- Original Message ----- From: "Clemmitt M. Sigler" <sig...@bl...> To: "Sean Brook" <sea...@so...> Cc: "keksov" <ke...@gm...>; "Erlend Slettevoll" <sle...@st...>; <col...@li...> Sent: Tuesday, March 02, 2004 2:47 PM Subject: Re: [coLinux-devel] mounting cdrom | On Tue, 2 Mar 2004, Sean Brook wrote: | > With iso9660 support I can mount a cdrom using a path through | > \DosDevices\<drive letter> | > This is not raw access AFAIK. Windows has lots of keys to access the | > same value with lots of redundancy in the registry. | > AFAIK the raw way to a cdrom is accessed through: | > \Device\Cdrom<x> | | I haven't had time to get elbow-deep in the source yet, so I don't | understand this. However, it would be a *big* help if someone who | groks the XML config format could post a few sentences here or in | the Wiki. The biggest need I see is explaining access to raw hard | disk partitions, CD-ROM and other IDE devices, and similar. Is | it path="\Device\HarddiskVolumeX", or is it | path="\Device\HarddiskVolumeX\PartitionY", or what? The value in 'path' is not a coLinux thing. It is a Windows thing. Also: | > Windows has lots of keys to access the | > same value with lots of redundancy in the registry. Whole branches of redundancy in fact. | | A great place to post this would be: | | http://www.colinux.org/wiki/index.php/index.php/coLinuxFAQ#A3 | http://www.colinux.org/wiki/index.php/index.php/ConfigurationXMLFormat I agree. Though I think first we just started posting back here what works and what doesnt. There is already incorrect information in the wiki ;) | | Thanks in advance :^D | | Clemmitt | | | | ------------------------------------------------------- | SF.Net is sponsored by: Speed Start Your Linux Apps Now. | Build and deploy apps & Web services for Linux with | a free DVD software kit from IBM. Click Now! | http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | _______________________________________________ | coLinux-devel mailing list | coL...@li... | https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Digital I. Inc. <ok...@di...> - 2004-03-02 15:20:17
|
Hello
BTW, Why you have an interest about coLinux on NT4?
Just your hobby? or you have real usage?
but, at least, I welcome your effort very much.
because, with your effort, we can collect more hints to
stabilize coLinux. thanks Benoit!.
and please give us your history of BSOD with a stack trace.
--- Okajima.
|
|
From: Benoit M. <ben...@cg...> - 2004-03-02 15:14:38
|
try to find your card name in the daemon windows I had the same pb with my XP SP1, netgear FA311, my system is french, the name of my card is the french one under windows and the name scanned by colinux was the english one..... replacing it and all goes nearly well (there was also "(microsoft packet...)" in my card name found by colinux and I had to cut it out to have bridge working) Ben ----- Original Message ----- From: "Marko Bozikovic" <bo...@ks...> To: "coLinux" <col...@li...> Sent: Tuesday, March 02, 2004 3:29 PM Subject: [coLinux-devel] Bridged networking problem followup > Regarding the STATUS_ACCESS_VIOLATION error some people get when using bridged > networking: > > I have installed both Win2k and WinXP under VMWare, installed Winpcap and > copied coLinux (with the Debian image I'm using) coLinux works fine on both > systems. The only relevant difference is the network cards used. Here's a > short summary of systems I've tried running linux on: > > Win2k SP4 (native), SMC EZ Card 10/100 (SMC1255TX) ethernet card - works fine > > WinXP SP1 (native), SMC EZ 10/100 Fast Ethernet - doesn't work > > Win2k (VMWare), VMWare's virtual network card (don't have the name here) - > works fine > > WinXP (VMWare), VMWare's virtual network card (don't have the name here) - > works fine > > > I get the same error and identical stack dump file when I use bridged > networking and set a random name for the network card on a system that usually > works. Could it be that there's a problem with detecting the network card? > > -- > Marko > ICQ: 5990814 > > I'm not under the alkafluence of inkahol > that some thinkle peep I am. > It's just the drunker I sit here the longer I get. > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Benoit M. <ben...@cg...> - 2004-03-02 15:08:35
|
Compiled with GetGlobalStatus instead of GetGlobalStatusEx, no problem but I've another problem, it's about lynux.sys, the daemon can't find ExFreePoolWithTag entry point in ntoskrnl.exe when installing kernel driver. and the only doc I found about this api says nt4 supported. any Idea?? thx Ben ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Cooperative Linux Development" <col...@li...> Sent: Monday, March 01, 2004 12:00 PM Subject: [coLinux-devel] coLinux on NT4? > Hi all > > could someone compile recompile the daemon and console with his file plz? > and then send back binaries to me (don't have net access, just mails.....) > I can't do it myself, i'm on nt4 :( > it goes in src/colinux/os/winnt/user/ > based on 20040227 > > thanks > > Ben > > |
|
From: Marko B. <bo...@ks...> - 2004-03-02 15:05:10
|
Regarding the STATUS_ACCESS_VIOLATION error some people get when using bridged networking: I have installed both Win2k and WinXP under VMWare, installed Winpcap and copied coLinux (with the Debian image I'm using) coLinux works fine on both systems. The only relevant difference is the network cards used. Here's a short summary of systems I've tried running linux on: Win2k SP4 (native), SMC EZ Card 10/100 (SMC1255TX) ethernet card - works fine WinXP SP1 (native), SMC EZ 10/100 Fast Ethernet - doesn't work Win2k (VMWare), VMWare's virtual network card (don't have the name here) - works fine WinXP (VMWare), VMWare's virtual network card (don't have the name here) - works fine I get the same error and identical stack dump file when I use bridged networking and set a random name for the network card on a system that usually works. Could it be that there's a problem with detecting the network card? -- Marko ICQ: 5990814 I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get. |
|
From: Clemmitt M. S. <sig...@bl...> - 2004-03-02 15:00:51
|
On Tue, 2 Mar 2004, Sean Brook wrote: > With iso9660 support I can mount a cdrom using a path through > \DosDevices\<drive letter> > This is not raw access AFAIK. Windows has lots of keys to access the > same value with lots of redundancy in the registry. > AFAIK the raw way to a cdrom is accessed through: > \Device\Cdrom<x> I haven't had time to get elbow-deep in the source yet, so I don't understand this. However, it would be a *big* help if someone who groks the XML config format could post a few sentences here or in the Wiki. The biggest need I see is explaining access to raw hard disk partitions, CD-ROM and other IDE devices, and similar. Is it path="\Device\HarddiskVolumeX", or is it path="\Device\HarddiskVolumeX\PartitionY", or what? A great place to post this would be: http://www.colinux.org/wiki/index.php/index.php/coLinuxFAQ#A3 http://www.colinux.org/wiki/index.php/index.php/ConfigurationXMLFormat Thanks in advance :^D Clemmitt |
|
From: Sean B. <sea...@so...> - 2004-03-02 14:45:59
|
With iso9660 support I can mount a cdrom using a path through \DosDevices\<drive letter> This is not raw access AFAIK Windows has lots of keys to access the same value with lots of redundancy in the registry. AFAIK the raw way to a cdrom is accessed through: \Device\Cdrom<x> When I try to mount a cdrom through that device my system just reboots. I think this is to expected because NT does not let software access hardware directly (at least it did not used too, ie HAL). ----- Original Message ----- From: "keksov" <ke...@gm...> To: "Erlend Slettevoll" <sle...@st...> Cc: <col...@li...> Sent: Tuesday, March 02, 2004 1:20 PM Subject: Re[3]: [coLinux-devel] mounting ntfs | Just let us know about your results. | | Thank you, | Dim | | | | Tuesday, March 2, 2004, 1:59:17 PM, you wrote: | | >> Hello, | >> | >> I was able to access my Linux partition on second HDD with the following line: | >> <block_device index="1" path="\DEVICE\Harddisk1\Partition3" enabled="true"/> | >> | >> Try to use \Device\Ide\IdePort0 for atapi... Unfortunately, it looks like | >> default coLinux kernel has no supoort for iso9660. | >> | >> Dim | | ES> Thanks! That was exactly the info I was looking for. I'll check it out | ES> when I get home. I've already compiled a new kernel with support for more | ES> filesystems, so iso9660-support won't be a problem | | ES> --Erlend | | | ES> ------------------------------------------------------- | ES> SF.Net is sponsored by: Speed Start Your Linux Apps Now. | ES> Build and deploy apps & Web services for Linux with | ES> a free DVD software kit from IBM. Click Now! | ES> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | ES> _______________________________________________ | ES> coLinux-devel mailing list | ES> coL...@li... | ES> https://lists.sourceforge.net/lists/listinfo/colinux-devel | | | | ------------------------------------------------------- | SF.Net is sponsored by: Speed Start Your Linux Apps Now. | Build and deploy apps & Web services for Linux with | a free DVD software kit from IBM. Click Now! | http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | _______________________________________________ | coLinux-devel mailing list | coL...@li... | https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: <ch...@to...> - 2004-03-02 14:27:41
|
I put a page on the wiki that is a howto for using topologilinux with coLinux. This is an easy way to setup a custom slackware system without a seperate partition. My setup in the how to automagicly reconfigures itself depending on if it is booted normally or under coLinux. hopefully this howto is very newbie friendly. http://www.colinux.org/wiki/index.php/TopoHowTo chris |
|
From: keksov <ke...@gm...> - 2004-03-02 13:33:49
|
Just let us know about your results. Thank you, Dim Tuesday, March 2, 2004, 1:59:17 PM, you wrote: >> Hello, >> >> I was able to access my Linux partition on second HDD with the following line: >> <block_device index="1" path="\DEVICE\Harddisk1\Partition3" enabled="true"/> >> >> Try to use \Device\Ide\IdePort0 for atapi... Unfortunately, it looks like >> default coLinux kernel has no supoort for iso9660. >> >> Dim ES> Thanks! That was exactly the info I was looking for. I'll check it out ES> when I get home. I've already compiled a new kernel with support for more ES> filesystems, so iso9660-support won't be a problem ES> --Erlend ES> ------------------------------------------------------- ES> SF.Net is sponsored by: Speed Start Your Linux Apps Now. ES> Build and deploy apps & Web services for Linux with ES> a free DVD software kit from IBM. Click Now! ES> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ES> _______________________________________________ ES> coLinux-devel mailing list ES> coL...@li... ES> https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Sean B. <sea...@so...> - 2004-03-02 13:18:37
|
----- Original Message ----- From: "Sonnie Hook" <son...@ho...> To: <col...@li...> Sent: Tuesday, March 02, 2004 8:59 AM Subject: [coLinux-devel] ISO9660 not supported by kernel | I added an entry into default.xml as shown below: | <block_device index="1" | path="\DosDevices\d:\coLinux\KNOPPIX_V3.3-2004-02-16-EN.iso" | enabled="true"></block_device> | | After booting the debian image, `dmesg' told: | cobd1 size: 716702 kb | While `mount /dev/cobd1 /mnt' told: | fs type iso9660 not supported by kernel This is your answer^ The kernel you are using does not have iso9660 compiled in. You need to compile your own kernel with iso9660 support. I am able to mount iso images in this way. | | Does it mean that ISO image can't be mounted this way? | | sonnie | | _________________________________________________________________ | 免费下载 MSN Explorer: http://explorer.msn.com/lccn/ | | | | ------------------------------------------------------- | SF.Net is sponsored by: Speed Start Your Linux Apps Now. | Build and deploy apps & Web services for Linux with | a free DVD software kit from IBM. Click Now! | http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | _______________________________________________ | coLinux-devel mailing list | coL...@li... | https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Erlend S. <sle...@st...> - 2004-03-02 13:12:05
|
> Hello, > > I was able to access my Linux partition on second HDD with the following line: > <block_device index="1" path="\DEVICE\Harddisk1\Partition3" enabled="true"/> > > Try to use \Device\Ide\IdePort0 for atapi... Unfortunately, it looks like > default coLinux kernel has no supoort for iso9660. > > Dim Thanks! That was exactly the info I was looking for. I'll check it out when I get home. I've already compiled a new kernel with support for more filesystems, so iso9660-support won't be a problem --Erlend |
|
From: Mark O. <mp...@th...> - 2004-03-02 11:05:21
|
Hi All I am interested in helping with / using different distributions on colinux. I may need a hand to start with to get some of the basic ideas. I have downloaded and tried the Debain image and am looking at trying a few others. I do have one question though. How can I specify which tap adapter colinux should like to on my xp computer. As I am currently running openvpn most of the time which also uses tap but I have it connected to a specific device. However, colinux seamed to like that tap interface. I also thought it might be usefull for the distribution to have an irc room, as I can not presently find one, hope this is ok. But I have created one on irc.freenode.net #colinux . Later in the day I will put a bot in the room to keep it open and hopefully start answering questions when it learns some of the answers. Thanks Mark -- Mark Olliver Thermeon Europe Ltd. e-Card: http://www.thermeoneurope.com/e-Card/mpo Email mp...@th... Web www.thermeoneurope.com Support 0906 515 0908 Int. Support +44 1293 864 341 Support Email su...@th... Sales +44 1293 864 334 Sales Email sa...@th... |
|
From: Sonnie H. <son...@ho...> - 2004-03-02 09:13:20
|
I added an entry into default.xml as shown below:
<block_device index="1"
path="\DosDevices\d:\coLinux\KNOPPIX_V3.3-2004-02-16-EN.iso"
enabled="true"></block_device>
After booting the debian image, `dmesg' told:
cobd1 size: 716702 kb
While `mount /dev/cobd1 /mnt' told:
fs type iso9660 not supported by kernel
Does it mean that ISO image can't be mounted this way?
sonnie
_________________________________________________________________
免费下载 MSN Explorer: http://explorer.msn.com/lccn/
|
|
From: morfic <mo...@bb...> - 2004-03-02 04:24:07
|
i suspended debian on my winxp laptop for about 8 hours last night, no problem, i was actually surprised it worked, but it did, no idea about hibernation, but maybe this helps? btw it was since suspended for another 10 while i was at work still worked Gregor Mitsch wrote: >> I've had success with Windows' hibernation and coLinux, but for short >> times only. For how long the machine was suspended? > > > About 8 hours. > > --Gregor > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: keksov <ke...@gm...> - 2004-03-02 00:46:22
|
Hello, I was able to access my Linux partition on second HDD with the following line: <block_device index="1" path="\DEVICE\Harddisk1\Partition3" enabled="true"/> Try to use \Device\Ide\IdePort0 for atapi... Unfortunately, it looks like default coLinux kernel has no supoort for iso9660. Dim Monday, March 1, 2004, 4:52:14 PM, you wrote: >> This is another message warning you against that. You may possibly >> be able to get concurrent read access to the drive but writing to the >> drive will corrupt your file system. There would certainlybe weird >> results reading the drive over time when the partition is updated for the >> drive from Windows. Also consider that ntfs support in Linux is and >> probably always will be expermental code. I would go with samba too >> but try checking this out: http://winscp.sourceforge.net/ ES> I am aware of the state of the ntfs-support in the linux kernel. I ES> understand samba or ssh will be a safer way to transfer data between the ES> systems, but I was curious how the mounting of RAW-devices is in coLinux. ES> This could be useful for example to access CD/DVD-readers or -writers. ES> --Erlend ES> ------------------------------------------------------- ES> SF.Net is sponsored by: Speed Start Your Linux Apps Now. ES> Build and deploy apps & Web services for Linux with ES> a free DVD software kit from IBM. Click Now! ES> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ES> _______________________________________________ ES> coLinux-devel mailing list ES> coL...@li... ES> https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Alejandro R. S. <as...@MI...> - 2004-03-01 21:54:58
|
This one confused me for a moment too. :p Dan set the bridged daemon aside in the makefile. From the colinux/src dir: make bridged_net_daemon You may also need the winpcap headers, those are available on the winpcap site (google for link). I've been using the 3.0 Developer's Pack. Careful how you integrate these with the existing includes, make a backup of what's there since pcap includes some different versions of what's already there. Good luck! -Alejandro On Mon, 2004-03-01 at 16:25, Sean Brook wrote: > I want to try the colinux-bridged-net-daemon but it is not being built as > part of make colinux > > What is the build process for colinux-bridged-net-daemon? > > Cheers. > |
81 messages has been excluded from this view by a project administrator.
