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: Olivier S. <co...@a-...> - 2004-03-23 00:31:09
|
----- Original Message ----- From: "Carlos A.S. Oliveira" <oli...@uf...> To: <col...@li...> Sent: Tuesday, March 23, 2004 12:44 AM Subject: [coLinux-devel] accessing files > Hi everyone, > > Let me explain my situation. I have a XP machine in a NT domain. > I am trying to access the XP files from colinux. > However, everytime I try to access these files using samba or > NFS (using windows services for unix), I have problems with proper > permissions, since I cannot autenticate on the NT server. > On the other hand, I want to be in the domain, in order to access > all my other files. > I lack knowledge of XP/NT to solve this. Do you have any suggestion? > Thanks, > -Carlos for the record, since I had a local web server (Apache) and a a ftp server (war-ftpd, unused for months), I just used them before thinking of using samba or NFS. O. Souiry |
|
From: Carlos A.S. O. <oli...@uf...> - 2004-03-22 23:43:33
|
Hi everyone, Let me explain my situation. I have a XP machine in a NT domain. I am trying to access the XP files from colinux. However, everytime I try to access these files using samba or NFS (using windows services for unix), I have problems with proper permissions, since I cannot autenticate on the NT server. On the other hand, I want to be in the domain, in order to access all my other files. I lack knowledge of XP/NT to solve this. Do you have any suggestion? Could anyone contribute an entry in the wiki to solve this type of problem, or an example of your own data transfer configuration? Thanks, -Carlos |
|
From: Dan A. <da...@co...> - 2004-03-22 18:47:18
|
On Mon, Mar 22, 2004 at 10:53:44AM -0500, Clemmitt M. Sigler wrote: > Sonnie Hook triggered an apparent bug using vi to edit his > /etc/apt/sources.list file. He posted a report to the Help > forum and I decided to see if I could recreate it. I can :^P > > If you edit a file with vi (doesn't matter what file except I > only tried plain text files, of course) you can reproduce the > crash by going into insert mode, moving the cursor to the > top-leftmost position, then typing the character '#'. I've > gotten a few crash messages such as these: Okay, this was just a console code bug (it doesn't bring down the coLinux system, though). Considered it fixed in the next snapshot/release. -- Dan Aloni da...@co... |
|
From: Olivier S. <co...@a-...> - 2004-03-22 16:15:33
|
----- Original Message ----- From: "Clemmitt M. Sigler" <sig...@bl...> To: <col...@li...> Sent: Monday, March 22, 2004 4:53 PM Subject: [coLinux-devel] Crash caused by vi. > Hi, > > Sonnie Hook triggered an apparent bug using vi to edit his > /etc/apt/sources.list file. He posted a report to the Help > forum and I decided to see if I could recreate it. I can :^P > > If you edit a file with vi (doesn't matter what file except I > only tried plain text files, of course) you can reproduce the > crash by going into insert mode, moving the cursor to the > top-leftmost position, then typing the character '#'. I've > gotten a few crash messages such as these: confirmed, I just got it under gentoo, while editing a file. I was at top-left corner of the colinux-console-fltk window but in the middle of a file, then I was punching some 'x'. the version I use is colinux-20040319-bin.tar.gz, not patched or rebuild. O. Souiry |
|
From: Clemmitt M. S. <sig...@bl...> - 2004-03-22 16:08:44
|
Hi again, On Mon, 22 Mar 2004, Clemmitt M. Sigler wrote: > If you edit a file with vi (doesn't matter what file except I > only tried plain text files, of course) you can reproduce the > crash by going into insert mode, moving the cursor to the > top-leftmost position, then typing the character '#'. My apologies! I forgot to post my config info. Sorry. Running coLinux snapshop 20040319-bin on the Debian-3.0r0.ext3.1gb image. Mounting the root filesystem image and a swap device image. I've set my networking up for a static IP address of 192.168.0.40. No other special configuration that I can think of (but I could be wrong). Please let me know if you have any questions. Clemmitt |
|
From: Clemmitt M. S. <sig...@bl...> - 2004-03-22 15:53:58
|
Hi,
Sonnie Hook triggered an apparent bug using vi to edit his
/etc/apt/sources.list file. He posted a report to the Help
forum and I decided to see if I could recreate it. I can :^P
If you edit a file with vi (doesn't matter what file except I
only tried plain text files, of course) you can reproduce the
crash by going into insert mode, moving the cursor to the
top-leftmost position, then typing the character '#'. I've
gotten a few crash messages such as these:
----------------------------------------------------------------------
50 [main] colinux-console-fltk 1384 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
36173 [main] colinux-console-fltk 1384 open_stackdumpfile: Dumping stack
trace to colinux-console-fltk.exe.stackdump
co_message_switch: freeing rule for 6
daemon: module disconnected: console
----------------------------------------------------------------------
52 [main] colinux-console-fltk 1124 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
33449 [main] colinux-console-fltk 1124 open_stackdumpfile: Dumping stack
trace to colinux-console-fltk.exe.stackdump
co_os_daemon_thread() error [ 6 , RE0001 ]
co_message_switch: freeing rule for 6
daemon: module disconnected: console
----------------------------------------------------------------------
I've attached the stackdump from the first error above for your
perusal. Please let me know if I can help look at this any
further. And thanks to Sonnie :^)
Clemmitt Sigler
|
|
From: Crypto <cr...@dv...> - 2004-03-22 06:51:55
|
Hi Dan, I have a P4HT PC and I am not suffering of hang-ups. I think it is not a general problem. I have not set an affinity. Do the users, reporting the problem, have tried to get a smp kernel running or do they have a regular setup? -- Crypto >Date: Sun, 21 Mar 2004 16:27:46 +0200 >From: Dan Aloni <da...@co...> >To: Cooperative Linux Development <col...@li...> >Subject: [coLinux-devel] coLinux on SMP/HT setups > >Hello, > >I send this message because I need help debugging coLinux on SMP or >HT-enabled setups, since currently I don't have access to that kind of >hardware. As you know, there's a problem which prevents it from running >stable on these kind of machines. > >I'd be happy to receive stack analysis of crash dumps, or anything that >can help. > >-- >Dan Aloni >da...@co... |
|
From: morfic <mo...@bb...> - 2004-03-21 19:46:06
|
well i guess im going to have to have lots of luck consider disk1 is a firewire drive, id like to natively format a partition rather than using an image, i could do this using any sort of livecd, but if this will ever boot? well i will attempt this sometime later, got a lot of livecds to try :) but until this mysterious graphics corruption problem is solved i will have to remain linux free anyway :) thanks for clearing that up at least :) Daniel Ronald Pijnacker wrote: >>now am i supposed to be able to mkfs the cobdX or is this for existing >>linux partitions? >> >> > >This is for an existing ReiserFS partition on which my gentoo installation >resides. > >However, by now I've found out that I am able to mount the first partition >(ext3). So the problem lies in the ReiserFS / swap device area. > >Sorry about that... > >Ronald. > > > >------------------------------------------------------- >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_id70&alloc_id638&op=click >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > |
|
From: Ronald P. <pij...@ds...> - 2004-03-21 19:42:17
|
> Ok, yeah, this one is easy. IEEE 802.11 specs require that wireless > cards only transmit packets with a source MAC that is their own. You ca= n > ping your own machine because it's clever enough to deal with the packe= t > internally, but you can't ping the router because the packet never > leaves the card. Hmm... that explains the problem. I'll try with a cable... I do see the light on the wireless card blinking, though... > As of right now, the bridged net daemon does not support any wireless > cards. When I get some free time (I just got a job...) I'll be working > on a workaround that will allow the two machines two share the host MAC > and let the filtering happen at an IP level. This won't be perfect (dhc= p > will break for one of the two machines if you're trying to use it for > both) but it'll be better than nothing. OK. For now NAT is good enough, I'm not able to boot my Gentoo system yet= . When that happens the problem becomes a bit bigger... Thanks, Ronald. |
|
From: Ronald P. <pij...@ds...> - 2004-03-21 19:35:56
|
> now am i supposed to be able to mkfs the cobdX or is this for existin= g > linux partitions? This is for an existing ReiserFS partition on which my gentoo installatio= n resides. However, by now I've found out that I am able to mount the first partitio= n (ext3). So the problem lies in the ReiserFS / swap device area. Sorry about that... Ronald. |
|
From: Alejandro R. S. <as...@MI...> - 2004-03-21 19:32:19
|
Ok, yeah, this one is easy. IEEE 802.11 specs require that wireless cards only transmit packets with a source MAC that is their own. You can ping your own machine because it's clever enough to deal with the packet internally, but you can't ping the router because the packet never leaves the card. As of right now, the bridged net daemon does not support any wireless cards. When I get some free time (I just got a job...) I'll be working on a workaround that will allow the two machines two share the host MAC and let the filtering happen at an IP level. This won't be perfect (dhcp will break for one of the two machines if you're trying to use it for both) but it'll be better than nothing. -Alejandro On Sun, 2004-03-21 at 14:17, Ronald Pijnacker wrote: > > Hi Ronald, > > > > Can you post your complete network configuration information on both > > machines and the coLinux config file? > > > > '/sbin/ifconfig' on coLinux > > 'ipconfig /all' on windows > > the '<network...' line from default.colinux.xml or equivalent. > > > > Also, what version of WinPCap? > > Sure, here it is. Hopefully the Dutch windows installation isn't a problem. > > ---------------------------------------------------------------------- > colinux:~# ifconfig > eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > inet addr:192.168.15.4 Bcast:192.168.15.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:173 errors:0 dropped:0 overruns:0 frame:0 > TX packets:120 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:27960 (27.3 KiB) TX bytes:12892 (12.5 KiB) > Interrupt:2 > > colinux:~# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.15.0 * 255.255.255.0 U 0 0 0 eth0 > default 192.168.15.1 0.0.0.0 UG 0 0 0 eth0 > > ---------------------------------------------------------------------- > D:\>ipconfig /all > > Windows IP-configuratie > > Host-naam . . . . . . . . . . . .: windows-box > Primair DNS-achtervoegsel. . . . .: > Knooppunttype: . . . . . . . . . .: onbekend > IP-routering ingeschakeld. . . . .: ja > WINS-proxy ingeschakeld . . . . . : nee > > Ethernet-adapter Draadloze netwerkverbinding: > > Verbindingsspec. DNS-achtervoegsel: o15.ehv.nl > Beschrijving . . . . . . . . . . .: > SMC2835W 2.4GHz 54 Mbps Wireless Cardbus Adapter > Fysiek adres. . . . . . . . . . . : 00-04-E2-80-A5-2C > DHCP ingeshakeld. . . . . . . . . : ja > Autom. configuratie ingeschakeld. : ja > IP-adres. . . . . . . . . . . . . : 192.168.15.172 > Subnetmasker. . . . . . . . . . . : 255.255.255.0 > Standaardgateway. . . . . . . . . : 192.168.15.1 > DHCP-server . . . . . . . . . . . : 192.168.15.1 > DNS-servers . . . . . . . . . . . : 192.168.15.1 > Lease verkregen . . . . . . . . . : zondag 21 maart 2004 18:50:58 > Lease verlopen . . . . . . . . . : dinsdag 23 maart 2004 18:50:58 > > ---------------------------------------------------------------------- > default.colinux.xml: > > <network index="0" name="SMC2835W 2.4GHz 54 Mbps Wireless Cardbus > Adapter" type="bridged"></network> > ---------------------------------------------------------------------- > > WinPCap version is 3.0. > > > Thanks, > > Ronald. > > |
|
From: Ronald P. <pij...@ds...> - 2004-03-21 19:17:46
|
> Hi Ronald,
>
> Can you post your complete network configuration information on both
> machines and the coLinux config file?
>
> '/sbin/ifconfig' on coLinux
> 'ipconfig /all' on windows
> the '<network...' line from default.colinux.xml or equivalent.
>
> Also, what version of WinPCap?
Sure, here it is. Hopefully the Dutch windows installation isn't a proble=
m.
----------------------------------------------------------------------
colinux:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30
inet addr:192.168.15.4 Bcast:192.168.15.255 Mask:255.255.255.=
0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:173 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:27960 (27.3 KiB) TX bytes:12892 (12.5 KiB)
Interrupt:2
colinux:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use I=
face
192.168.15.0 * 255.255.255.0 U 0 0 0 e=
th0
default 192.168.15.1 0.0.0.0 UG 0 0 0 e=
th0
----------------------------------------------------------------------
D:\>ipconfig /all
Windows IP-configuratie
Host-naam . . . . . . . . . . . .: windows-box
Primair DNS-achtervoegsel. . . . .:
Knooppunttype: . . . . . . . . . .: onbekend
IP-routering ingeschakeld. . . . .: ja
WINS-proxy ingeschakeld . . . . . : nee
Ethernet-adapter Draadloze netwerkverbinding:
Verbindingsspec. DNS-achtervoegsel: o15.ehv.nl
Beschrijving . . . . . . . . . . .:
SMC2835W 2.4GHz 54 Mbps Wireless Cardbus Adapter
Fysiek adres. . . . . . . . . . . : 00-04-E2-80-A5-2C
DHCP ingeshakeld. . . . . . . . . : ja
Autom. configuratie ingeschakeld. : ja
IP-adres. . . . . . . . . . . . . : 192.168.15.172
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . : 192.168.15.1
DHCP-server . . . . . . . . . . . : 192.168.15.1
DNS-servers . . . . . . . . . . . : 192.168.15.1
Lease verkregen . . . . . . . . . : zondag 21 maart 2004 18:50:58
Lease verlopen . . . . . . . . . : dinsdag 23 maart 2004 18:50:5=
8
----------------------------------------------------------------------
default.colinux.xml:
<network index=3D"0" name=3D"SMC2835W 2.4GHz 54 Mbps Wireless Cardbus
Adapter" type=3D"bridged"></network>
----------------------------------------------------------------------
WinPCap version is 3.0.
Thanks,
Ronald.
|
|
From: morfic <mo...@bb...> - 2004-03-21 19:09:32
|
When i allow colinux to run over night on my laptop i find a corrupted mouse pointer in the morning. Do i continue to use the laptop w/o reboot i will reach a point there this corruption switches over to the whole screen, mostly triggered by use of DX/D3D. This is a P4 laptop with a Radeon 9000 Mobility 64MB this never occurs when colinux does not run. I am running the i686 gentoo image. CFLAGS=-O3 -march=pentium4 -fomit-frame-pointers -mfpmath=sse -pipe only things compiled with those flags are gcc, vim, irssi, reiserfsprogs, rest of system including glibc are run as found in image. let me know what additional information is required to be able to look into this issue. Daniel |
|
From: Dan A. <da...@co...> - 2004-03-21 14:28:00
|
Hello, I send this message because I need help debugging coLinux on SMP or HT-enabled setups, since currently I don't have access to that kind of hardware. As you know, there's a problem which prevents it from running stable on these kind of machines. I'd be happy to receive stack analysis of crash dumps, or anything that can help. -- Dan Aloni da...@co... |
|
From: morfic <mo...@bb...> - 2004-03-21 03:01:13
|
now am i supposed to be able to mkfs the cobdX or is this for existing linux partitions? Ronald Pijnacker wrote: >Hi, > >The last few evenings, I have been busy with trying to get my (dual boot) >Gentoo installation working with coLinux. As instructed on the Wiki, I >tried \Device\HarddiskVolume4, which should be the swap partition, and >...Volume5 which is the root partition. I've also tried >\Device\Harddisk0\PartitionX. > >However, inside colinux, the only thing I get from the /dev/cobd? device >is "IO error". Using the Debian file system and the swap-file works fine. > >I'm pretty sure I've got the right volume numbers (others also don't work >anyway). Is there something I'm missing? > >Thanks, > >Ronald. > > > >------------------------------------------------------- >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_id70&alloc_id638&op=click >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > |
|
From: Alejandro R. S. <as...@MI...> - 2004-03-20 21:12:54
|
Hi Ronald, Can you post your complete network configuration information on both machines and the coLinux config file? '/sbin/ifconfig' on coLinux 'ipconfig /all' on windows the '<network...' line from default.colinux.xml or equivalent. Also, what version of WinPCap? Thanks, -Alejandro On Sat, 2004-03-20 at 15:43, Ronald Pijnacker wrote: > Hi, > > I've got the following network setup: > > router: 192.168.15.1 > windows: 192.168.15.172 (dhcp) > colinux: 192.168.15.4 (static) > > with gateway 192.168.15.1 on both windows and colinux. > > When I use the winpcap bridge, I am able to ping to windows from colinux, > but I can't seem to ping the router, which works fine from windows. As I > far as I understand the winpcap setup, this should go without any further > configuration, right? > > Any ideas on how to tackle this problem? > > Ronald. > > > > > ------------------------------------------------------- > 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_id70&alloc_id638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Ronald P. <pij...@ds...> - 2004-03-20 20:43:47
|
Hi, I've got the following network setup: router: 192.168.15.1 windows: 192.168.15.172 (dhcp) colinux: 192.168.15.4 (static) with gateway 192.168.15.1 on both windows and colinux. When I use the winpcap bridge, I am able to ping to windows from colinux, but I can't seem to ping the router, which works fine from windows. As I far as I understand the winpcap setup, this should go without any further configuration, right? Any ideas on how to tackle this problem? Ronald. |
|
From: Ronald P. <pij...@ds...> - 2004-03-20 20:37:08
|
Hi, I just downloaded the 0319 snapshot to see if my problems with the pcap bridge are solved (they are :-). However, it seems that now the cursor is gone... Ronald. |
|
From: Ronald P. <pij...@ds...> - 2004-03-20 20:35:17
|
Hi, FYI: It seems that the forum for colinux on sf is broken. Ronald |
|
From: Sean B. <sea...@so...> - 2004-03-19 23:19:46
|
> > If you cannot boot from a native partion then > > there does seem to be an issue there (I have this problem) though I > > can boot ie it does in fact recognise the partition. > > I'm afraid I can't help with this because I just have Windows > partitions on the workstation I'm using (at my office). > Might the entry in the Wiki on TopologiLinux help? > Thats ok. AFAIAC it is a bug. I just havent logged it yet. |
|
From: keksov <ke...@gm...> - 2004-03-19 22:45:34
|
Sorry for not answering your question earlier, just was at work. But looks like you solved it already by yourself. Congratulations !!! :) Happy weekend, Dim Friday, March 19, 2004, 9:48:06 PM, you wrote: CMS> Hi guys, CMS> I just wanted to say thanks to the three of you for e-mailing me CMS> privately with help with raw partition/device access. I worked on it, CMS> and the answer is... -->> I'm a moron :^D <-- CMS> I can mount my tiny VFAT partition fine by referring to it as CMS> \Device\HarddiskVolume1 or \Device\Harddisk0\Partition1. I can CMS> mount my CD-ROM in raw access mode using \Device\CdRom0, too. CMS> What confused me so much I didn't try anything beyond booting up CMS> (like an idiot!) was that cobd0 (root image) and cobd1 (swap CMS> image) were detected and reported during the boot sequence, but CMS> cobd2 was *never* reported. I thought it hadn't "connected." CMS> Do you consider this a bug to be fixed? If so, I'll take a crack CMS> at getting coLinux to report the block_device entries in the XML CMS> file other than root and swap when it boots. CMS> Thanks for your help and patience :^) CMS> Clemmitt |
|
From: Clemmitt M. S. <sig...@bl...> - 2004-03-19 22:11:13
|
Hi Sean, Well, I was unusually dense on this problem, I'm afraid :^( Short version -- all is well. There was no problem for me except the end-user was screwing up! I can access and mount raw devices like \Device\HarddiskVolume1, \Device\Harddisk0\Partition1, \Device\CdRom0, just fine. What was causing my confusion? Well, in the boot-time messages coLinux/the Linux kernel prints, if a block_device entry refers to a filesystem image (like a root filesystem image file or a swap file), a line is printed out like this: cobd0 size: 1048576 kb cobd1 size: 262080 kb *BUT* if a block_device refers to a raw partition or device, there is no message printed. I'm afraid I was dumb and thought that these block_devices weren't "connecting" on boot-up. I hope these hints will help others with raw device access :^) On Fri, 19 Mar 2004, Sean Brook wrote: > If you cannot boot from a native partion then > there does seem to be an issue there (I have this problem) > though I can boot ie it does in fact recognise the partition. I'm afraid I can't help with this because I just have Windows partitions on the workstation I'm using (at my office). Might the entry in the Wiki on TopologiLinux help? > - I think I sussed the \Device\HarddiskVolume? convention. It > also seems quite simple. Looking at logical disk manager > literally count the partitions starting from 1 from the first > disk left to right and down through the second etc to the partition > you want. All partitions should be included in the count. I did a quick test that I believe confirms your analysis of how \Device\HarddiskVolumeX names are assigned by the Logical Disk Manager. Well done :^) Clemmitt |
|
From: Sean B. <sea...@so...> - 2004-03-19 21:21:34
|
> I've been trying to get some more information by creating some test > programs. None of them worked of course :-( . Later I > realized that the > \\?\ convention only works with the unicode version of the file > functions. I assume that is known information? Pass. I have no idea what you are getting at. Just a user. How about trying \Device\HarddiskVolume? if you have not already. |
|
From: Sean B. <sea...@so...> - 2004-03-19 21:14:28
|
> I included a MSFT link in an earlier post. That page tries > to explain > SCSI and IDE drive numbering for W2K. Cheers, I will have a look. > I haven't been able to access raw partitions in coLinux as > \Device\HarddiskVolumeX or as \Device\HarddiskX\PartitionY. > I'd love to fully grok the naming scheme to see if I'm > doing something bogus in my XML config file. I don't think > I am. ok, didnt realise. What do you mean by you cannot access the raw partitions in colinux? What type of partitions exactly? For me at least I need to specify the partition type with -t inside colinx eg mount -t ext3 /dev/cobd? ... whereas in native linux it is recognised automatically. If you are wanting to mount one of your windows drives then are you sure you have support for the partition types in your kernel or compiled as a module? If you cannot boot from a native partion then there does seem to be an issue there (I have this problem) though I can boot ie it does in fact recognise the partition. Some thoughts: - I am guessing you are using w2k. A cursory search suggests that there were issues with diskperf and volume names. Are you using the latest service pack? - I think I sussed the \Device\HarddiskVolume? convention. It also seems quite simple. Looking at logical disk manager literally count the partitions starting from 1 from the first disk left to right and down through the second etc to the partition you want. All partitions should be included in the count. Do a search though the registry for harddiskvolume and on winxp at least it shows references to where the windows system is installed to give you an example. So maybe give that a go and add it. Cheers. |
|
From: Ronald P. <pij...@ds...> - 2004-03-19 20:55:57
|
> Hi, > > Your settings are probably correct. I have been waiting for someone > else to give feed back on using native partitions as I have problems > too :) I wont go into them yet but will post back later. Essentially > I can boot from a native partition but linux cannot read the > superblock. I too am using Gentoo so have hacked checkroot and > checkfs to boot. Also, I am not using a native swap partition as > colinux seems to have issues with swap partitions in general, though > I have not tried this again with 20040313. > > Some info which may help: > - You *must* look at your partitions from a logical(!) point of > view as opposed to physical. Use Storage/Disk Management aka > Logical Disk Manager. Just remember that Windows does its own > thing. > - The numbering of the hard disks and partitions is quite simple. > Hard disks start at 0. Partitions start at 1. Looking at things > from a logical point of view (as above) all should be clear. > - Don’t know about that IO error. Kind of worrying. Try again > with a loopback swap image. Are you sure your partitions are > clean? boot native and e2fsck -f /dev/hda? perhaps? I've been trying to get some more information by creating some test programs. None of them worked of course :-( . Later I realized that the \\?\ convention only works with the unicode version of the file functions. I assume that is known information? Ronald. |
81 messages has been excluded from this view by a project administrator.
