From: Robert C. <rw...@al...> - 2004-05-18 00:47:27
|
Hello Sean, On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote: > I'd appreciate any information you have. I'm on Win2k, coLinux=20 > 20040509, and the Gentoo "delux" image. I can't find my notes anywhere. Off the top of my head, you need to=20 get the tool called dmdiag.exe. IIRC, you get this from Microsoft but=20= google to be sure. Install it and run it. Then insert your USB stick=20= and run it again. Here's an example when I use my USB stick. Here's a very abbreviated=20 portions of dmdiag.exe output before: ---------- Drive letter to device name, QueryDosDevice() ---------- D: \Device\CdRom0 A: \Device\Floppy0 C: \Device\HarddiskVolume1 Here's a very abbreviated portions of dmdiag.exe output after: ---------- Drive letter to device name, QueryDosDevice() ---------- D: \Device\CdRom0 E: \Device\Harddisk1\DP(1)0-0+3 A: \Device\Floppy0 C: \Device\HarddiskVolume1 =00 Notice the new device E:\. That's my USB stick. I then add this line=20= to my defaults.colinux.xml: =00 <block_device index=3D"2" path=3D"\Device\Harddisk1\DP(1)0-0+3"=20= enabled=3D"true" />=00 The index number will change depending on how many devices you already=20= have defined and will be accessible within colinux as /dev/cobd2 (as=20 in _co_linux _b_lock _d_evice 2. After I start colinux, I can mount=20 the usb stick like so: # mkdir /mnt/usb # mount /dev/cobd2 /mnt/usb UMSDOS 0.86k (compatibility level 0.4, fast msdos) # dir /mnt/usb/ total 2620 drwxr--r-- 3 root root 16896 Jan 1 1970 . drwxr-xr-x 5 root root 4096 May 18 00:32 ..=00 ... # umount /mnt/usb This is a simple way for Windows to communicate with coLinux. However,=20= only one system can be accessing the device at a time. So, you will=20 need to unmount before Windows can see it and all Windows or files that=20= are accessing the device must be closed on the Windows side before you=20= can mount it again. Hope this helps. The above is tested on a Win2K machine running=20 coLinux 20040509 with the Debian image. If you get USB to work for=20 you, I'd like to encourage you to write up your experiences and post=20 them on the wiki, especially if you are using a different host OS,=20 snapshot, or image. Regards, - Robert |
From: Robert C. <rw...@al...> - 2004-05-18 00:54:12
|
On Monday, May 17, 2004, at 19:46 US/Central, Robert Citek wrote: > # mount /dev/cobd2 /mnt/usb > UMSDOS 0.86k (compatibility level 0.4, fast msdos) > # dir /mnt/usb/ > total 2620 > drwxr--r-- 3 root root 16896 Jan 1 1970 . > drwxr-xr-x 5 root root 4096 May 18 00:32 ..=00 > ... Chances are your USB stick has a fat32 and not a DOS filesystem. If=20 so, you probably want to specify the filesystem type: # mount -t vfat /dev/cobd2 /mnt/usb Regards, - Robert |
From: Sean C. <sea...@co...> - 2004-05-19 12:42:49
|
Robert, I finally had a chance to look at this again. The line you added to your xml file seems to be missing the beginning. dmdiage.exe reported my usb device as K:\Device\HardDisk1\DP(1)0-0+3 I added: <block_device index="2" enabled="true" /> I then started coLinux and did the following: mkdir /mnt/usb mount -t vfat /dev/cobd2 /mnt/usb I got the following error: mount: /dev/cobd2: Can't read Superblock Its formatted Fat32. Any thoughts? Thanks, Sean Robert Citek wrote: > > Hello Sean, > > On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote: > >> I'd appreciate any information you have. I'm on Win2k, coLinux >> 20040509, and the Gentoo "delux" image. > > > I can't find my notes anywhere. Off the top of my head, you need to get > the tool called dmdiag.exe. IIRC, you get this from Microsoft but > google to be sure. Install it and run it. Then insert your USB stick > and run it again. > > Here's an example when I use my USB stick. Here's a very abbreviated > portions of dmdiag.exe output before: > > ---------- Drive letter to device name, QueryDosDevice() ---------- > > D: \Device\CdRom0 > A: \Device\Floppy0 > C: \Device\HarddiskVolume1 > > Here's a very abbreviated portions of dmdiag.exe output after: > > ---------- Drive letter to device name, QueryDosDevice() ---------- > > D: \Device\CdRom0 > E: \Device\Harddisk1\DP(1)0-0+3 > A: \Device\Floppy0 > C: \Device\HarddiskVolume1 > > Notice the new device E:\. That's my USB stick. I then add this line > to my defaults.colinux.xml: > > enabled="true" /> > > The index number will change depending on how many devices you already > have defined and will be accessible within colinux as /dev/cobd2 (as in > _co_linux _b_lock _d_evice 2. After I start colinux, I can mount the > usb stick like so: > > # mkdir /mnt/usb > # mount /dev/cobd2 /mnt/usb > UMSDOS 0.86k (compatibility level 0.4, fast msdos) > # dir /mnt/usb/ > total 2620 > drwxr--r-- 3 root root 16896 Jan 1 1970 . > drwxr-xr-x 5 root root 4096 May 18 00:32 .. > ... > # umount /mnt/usb > > This is a simple way for Windows to communicate with coLinux. However, > only one system can be accessing the device at a time. So, you will > need to unmount before Windows can see it and all Windows or files that > are accessing the device must be closed on the Windows side before you > can mount it again. > > Hope this helps. The above is tested on a Win2K machine running coLinux > 20040509 with the Debian image. If you get USB to work for you, I'd > like to encourage you to write up your experiences and post them on the > wiki, especially if you are using a different host OS, snapshot, or image. > > Regards, > - Robert > > |
From: steelgunner <ste...@in...> - 2004-05-19 12:50:15
|
Hello, How to start many co-linux instances in the same computer?? |
From: Tim H. <ti...@br...> - 2004-05-19 16:09:30
|
steelgunner wrote: > Hello, > > How to start many co-linux instances in the same computer?? > In short, just read the instructions, but try looking at the output from "colinux-daemon.exe -h" and notice the way you can use different config files > > |
From: Robert C. <rw...@al...> - 2004-05-19 22:33:39
|
On Wednesday, May 19, 2004, at 11:09 US/Central, Tim Hunter wrote: > In short, just read the instructions, but try looking at the output > from > "colinux-daemon.exe -h" > and notice the way you can use different config files And where might one find the instructions on how to start multiple colinux instances? A quick browse through the wiki: http://colinux.org/wiki/index.php/FullTextSearch?s=instance showed this item: http://colinux.org/wiki/index.php/NextRelease which mentioned that future versions of colinux will support multiple instances, but no instructions on how. Do you know of a URL for instructions? Regards, - Robert |
From: Tim H. <ti...@br...> - 2004-05-20 01:08:17
|
Robert Citek wrote: > On Wednesday, May 19, 2004, at 11:09 US/Central, Tim Hunter wrote: >> In short, just read the instructions, but try looking at the output >> from >> "colinux-daemon.exe -h" >> and notice the way you can use different config files > > And where might one find the instructions on how to start multiple > colinux instances? > > A quick browse through the wiki: > http://colinux.org/wiki/index.php/FullTextSearch?s=instance > showed this item: > http://colinux.org/wiki/index.php/NextRelease > which mentioned that future versions of colinux will support multiple > instances, but no instructions on how. > > Do you know of a URL for instructions? from the HomePage there is a link titled: Running As A Service - and how to run two coLinux instances at the same time. http://colinux.org/wiki/index.php/RunningAsAService > > Regards, > - Robert |
From: tei <42...@in...> - 2004-05-19 12:52:20
|
Sean Covel wrote: > Robert, > > I finally had a chance to look at this again. The line you added to > your xml file seems to be missing the beginning. > > dmdiage.exe reported my usb device as K:\Device\HardDisk1\DP(1)0-0+3 > > I added: > > <block_device index="2" enabled="true" /> > where is the path? you need the "windows-ish" name, and the result like will be something like this (not exactly this, I suspect): <block_device index="2" path="\Device\Harddisk1\DP(1)0-0+3" enabled="true" /> > I then started coLinux and did the following: > > mkdir /mnt/usb > mount -t vfat /dev/cobd2 /mnt/usb > > I got the following error: > > mount: /dev/cobd2: Can't read Superblock > > Its formatted Fat32. > > Any thoughts? > > Thanks, > > Sean > > Robert Citek wrote: > >> >> Hello Sean, >> >> On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote: >> >>> I'd appreciate any information you have. I'm on Win2k, coLinux >>> 20040509, and the Gentoo "delux" image. >> >> >> >> I can't find my notes anywhere. Off the top of my head, you need to >> get the tool called dmdiag.exe. IIRC, you get this from Microsoft but >> google to be sure. Install it and run it. Then insert your USB stick >> and run it again. >> >> Here's an example when I use my USB stick. Here's a very abbreviated >> portions of dmdiag.exe output before: >> >> ---------- Drive letter to device name, QueryDosDevice() ---------- >> >> D: \Device\CdRom0 >> A: \Device\Floppy0 >> C: \Device\HarddiskVolume1 >> >> Here's a very abbreviated portions of dmdiag.exe output after: >> >> ---------- Drive letter to device name, QueryDosDevice() ---------- >> >> D: \Device\CdRom0 >> E: \Device\Harddisk1\DP(1)0-0+3 >> A: \Device\Floppy0 >> C: \Device\HarddiskVolume1 >> >> Notice the new device E:\. That's my USB stick. I then add this line >> to my defaults.colinux.xml: >> >> enabled="true" /> >> >> The index number will change depending on how many devices you already >> have defined and will be accessible within colinux as /dev/cobd2 (as >> in _co_linux _b_lock _d_evice 2. After I start colinux, I can mount >> the usb stick like so: >> >> # mkdir /mnt/usb >> # mount /dev/cobd2 /mnt/usb >> UMSDOS 0.86k (compatibility level 0.4, fast msdos) >> # dir /mnt/usb/ >> total 2620 >> drwxr--r-- 3 root root 16896 Jan 1 1970 . >> drwxr-xr-x 5 root root 4096 May 18 00:32 .. >> ... >> # umount /mnt/usb >> >> This is a simple way for Windows to communicate with coLinux. >> However, only one system can be accessing the device at a time. So, >> you will need to unmount before Windows can see it and all Windows or >> files that are accessing the device must be closed on the Windows side >> before you can mount it again. >> >> Hope this helps. The above is tested on a Win2K machine running >> coLinux 20040509 with the Debian image. If you get USB to work for >> you, I'd like to encourage you to write up your experiences and post >> them on the wiki, especially if you are using a different host OS, >> snapshot, or image. >> >> Regards, >> - Robert >> >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Sean C. <sea...@co...> - 2004-05-19 17:10:29
|
Ok, I added the path. I tried a few different variations from the dmdiag.exe output. No joy. Which of the various ways of referring to the USB Stick should I be using? BTW, it looks to me like the stick has 2 paritions on it. Very odd. Sean tei wrote: > Sean Covel wrote: > >> Robert, >> >> I finally had a chance to look at this again. The line you added to >> your xml file seems to be missing the beginning. >> >> dmdiage.exe reported my usb device as K:\Device\HardDisk1\DP(1)0-0+3 >> >> I added: >> >> <block_device index="2" enabled="true" /> >> > > where is the path? > > you need the "windows-ish" name, and the result like will be something > like this (not exactly this, I suspect): > > <block_device index="2" path="\Device\Harddisk1\DP(1)0-0+3" > enabled="true" /> > > >> I then started coLinux and did the following: >> >> mkdir /mnt/usb >> mount -t vfat /dev/cobd2 /mnt/usb >> >> I got the following error: >> >> mount: /dev/cobd2: Can't read Superblock >> >> Its formatted Fat32. >> >> Any thoughts? >> >> Thanks, >> >> Sean >> >> Robert Citek wrote: >> >>> >>> Hello Sean, >>> >>> On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote: >>> >>>> I'd appreciate any information you have. I'm on Win2k, coLinux >>>> 20040509, and the Gentoo "delux" image. >>> >>> >>> >>> >>> I can't find my notes anywhere. Off the top of my head, you need to >>> get the tool called dmdiag.exe. IIRC, you get this from Microsoft >>> but google to be sure. Install it and run it. Then insert your USB >>> stick and run it again. >>> >>> Here's an example when I use my USB stick. Here's a very abbreviated >>> portions of dmdiag.exe output before: >>> >>> ---------- Drive letter to device name, QueryDosDevice() ---------- >>> >>> D: \Device\CdRom0 >>> A: \Device\Floppy0 >>> C: \Device\HarddiskVolume1 >>> >>> Here's a very abbreviated portions of dmdiag.exe output after: >>> >>> ---------- Drive letter to device name, QueryDosDevice() ---------- >>> >>> D: \Device\CdRom0 >>> E: \Device\Harddisk1\DP(1)0-0+3 >>> A: \Device\Floppy0 >>> C: \Device\HarddiskVolume1 >>> >>> Notice the new device E:\. That's my USB stick. I then add this >>> line to my defaults.colinux.xml: >>> >>> enabled="true" /> >>> >>> The index number will change depending on how many devices you >>> already have defined and will be accessible within colinux as >>> /dev/cobd2 (as in _co_linux _b_lock _d_evice 2. After I start >>> colinux, I can mount the usb stick like so: >>> >>> # mkdir /mnt/usb >>> # mount /dev/cobd2 /mnt/usb >>> UMSDOS 0.86k (compatibility level 0.4, fast msdos) >>> # dir /mnt/usb/ >>> total 2620 >>> drwxr--r-- 3 root root 16896 Jan 1 1970 . >>> drwxr-xr-x 5 root root 4096 May 18 00:32 .. >>> ... >>> # umount /mnt/usb >>> >>> This is a simple way for Windows to communicate with coLinux. >>> However, only one system can be accessing the device at a time. So, >>> you will need to unmount before Windows can see it and all Windows or >>> files that are accessing the device must be closed on the Windows >>> side before you can mount it again. >>> >>> Hope this helps. The above is tested on a Win2K machine running >>> coLinux 20040509 with the Debian image. If you get USB to work for >>> you, I'd like to encourage you to write up your experiences and post >>> them on the wiki, especially if you are using a different host OS, >>> snapshot, or image. >>> >>> Regards, >>> - Robert >>> >>> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: SourceForge.net Broadband >> Sign-up now for SourceForge Broadband and get the fastest >> 6.0/768 connection for only $19.95/mo for the first 3 months! >> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: tei <42...@in...> - 2004-05-19 18:24:50
|
Sean Covel wrote: > Ok, > > I added the path. I tried a few different variations from the > dmdiag.exe output. No joy. Which of the various ways of referring to > the USB Stick should I be using? BTW, it looks to me like the stick > has 2 paritions on it. Very odd. > > Sean > Hummm... and the device mount Ok with a no-colinux linux? |
From: Sean C. <sea...@co...> - 2004-05-19 19:18:32
|
Works just fine. I reformatted it just in case, and it still doesn't work. tei wrote: > Sean Covel wrote: > >> Ok, >> >> I added the path. I tried a few different variations from the >> dmdiag.exe output. No joy. Which of the various ways of referring to >> the USB Stick should I be using? BTW, it looks to me like the stick >> has 2 paritions on it. Very odd. >> >> Sean >> > > Hummm... and the device mount Ok with a no-colinux linux? > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |