From: Ronald P. <pij...@ds...> - 2004-03-19 07:44:21
|
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. |
From: keksov <ke...@gm...> - 2004-03-19 09:02:17
|
Please, post your exact disks configuration with partions and OS installed. Friday, March 19, 2004, 8:44:15 AM, you wrote: RP> Hi, RP> The last few evenings, I have been busy with trying to get my (dual boo= t) RP> Gentoo installation working with coLinux. As instructed on the Wiki, I RP> tried \Device\HarddiskVolume4, which should be the swap partition, and RP> ...Volume5 which is the root partition. I've also tried RP> \Device\Harddisk0\PartitionX. RP> However, inside colinux, the only thing I get from the /dev/cobd? device RP> is "IO error". Using the Debian file system and the swap-file works fin= e. RP> I'm pretty sure I've got the right volume numbers (others also don't wo= rk RP> anyway). Is there something I'm missing? RP> Thanks, RP> Ronald. RP> ------------------------------------------------------- RP> This SF.Net email is sponsored by: IBM Linux Tutorials RP> Free Linux tutorial presented by Daniel Robbins, President and CEO of RP> GenToo technologies. Learn everything from fundamentals to system RP> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&oplick RP> _______________________________________________ RP> coLinux-devel mailing list RP> coL...@li... RP> https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Ronald P. <pij...@ds...> - 2004-03-19 10:18:14
|
> Please, post your exact disks configuration with partions and OS > installed. One disk: /dev/hda1: ext2 /dev/hda2: ntfs (windows c: disk) /dev/hda3: extended /dev/hda5: swap /dev/hda6: reiserfs (root for gentoo) /dev/hda7: ntfs (windows d: disk) I am using Windows XP, it reports the following: \Device\Harddisk0\Partition0 (entire disk) \Device\Harddisk0\Partition1 ... \Device\Harddisk0\Partition5 I have confirmed that Windows uses \Device\Harddisk0\Partition2 as C: and \Device\Harddisk0\Partition5 as D: . Ronald. > Friday, March 19, 2004, 8:44:15 AM, you wrote: > > RP> Hi, > > RP> The last few evenings, I have been busy with trying to get my (dual > boot) > RP> Gentoo installation working with coLinux. As instructed on the Wiki= , I > RP> tried \Device\HarddiskVolume4, which should be the swap partition, = and > RP> ...Volume5 which is the root partition. I've also tried > RP> \Device\Harddisk0\PartitionX. > > RP> However, inside colinux, the only thing I get from the /dev/cobd? > device > RP> is "IO error". Using the Debian file system and the swap-file works > fine. > > RP> I'm pretty sure I've got the right volume numbers (others also don'= t > work > RP> anyway). Is there something I'm missing? > > RP> Thanks, > > RP> Ronald. > > > > RP> ------------------------------------------------------- > RP> This SF.Net email is sponsored by: IBM Linux Tutorials > RP> Free Linux tutorial presented by Daniel Robbins, President and CEO = of > RP> GenToo technologies. Learn everything from fundamentals to system > RP> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&oplick > RP> _______________________________________________ > RP> coLinux-devel mailing list > RP> coL...@li... > RP> https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
From: Clemmitt M. S. <sig...@bl...> - 2004-03-19 13:46:35
|
Hi, On Fri, 19 Mar 2004, Ronald Pijnacker wrote: > /dev/hda1: ext2 /dev/hda2: ntfs (windows c: disk) > /dev/hda3: extended /dev/hda5: swap > /dev/hda6: reiserfs (root for gentoo) /dev/hda7: ntfs (windows d: disk) <snip> > \Device\Harddisk0\Partition0 (entire disk) > \Device\Harddisk0\Partition1 > ... > \Device\Harddisk0\Partition5 > I have confirmed that Windows uses \Device\Harddisk0\Partition2 as C: and > \Device\Harddisk0\Partition5 as D: . I'm still trying to wrap my poor mind around this stuff, because I can't get any raw partitions to work under Windows :^( I've received a number of helpful private e-mails which I haven't had time to follow up on (you know who you are, thank you :^). If I understand, Windows doesn't "count" /dev/hda3 a.k.a. the Extended partition. \D\H\P0 is the whole disk, then it assigns the devices from \D\H\P1 through 5 in order of the partition table's numbering, but skipping the Extended partition. Can someone with more experience please confirm this is the way Windows assigns \Device\HarddiskX\PartitionY? Two other newbie-type questions: 1.) Is the primary master IDE disk Harddisk0, the primary slave Harddisk1, the secondary master Harddisk2, and the secondary slave Harddisk3? This would agree with the info on this MS Technet page: http://www.microsoft.com/technet/prodtechnol/winntas/maintain/manag.mspx (except for the typo under "IDE Drives" where they say the first drive on the second controller would be designated 3, not 2 -- oops). 2.) Do the \Device\HarddiskVolumeX designations come from the Logical Disk Manager? And how do you figure out the mapping of \D\HarddiskVolumeX to \D\HarddiskY\PartitionZ? The port of dd to Windows with the --list option available here: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm doesn't list the HarddiskVolumeX designations. (Another place to get a dd port to Windows is: http://users.erols.com/gmgarner/forensics/). If this is a FAQ or RTFM, please say so and I apologize in advance :^P Clemmitt Sigler |
From: Sean B. <sea...@so...> - 2004-03-19 14:32:27
|
> -----Original Message----- > From: col...@li... > [mailto:col...@li...] On Behalf > Of Clemmitt M. Sigler > Sent: Friday, March 19, 2004 1:46 PM > To: Ronald Pijnacker > Cc: keksov; col...@li... > Subject: Re: [coLinux-devel] Problems with \Device\HarddiskVolumeX > > > Hi, > > On Fri, 19 Mar 2004, Ronald Pijnacker wrote: > > /dev/hda1: ext2 /dev/hda2: ntfs > (windows c: disk) > > /dev/hda3: extended /dev/hda5: swap > > /dev/hda6: reiserfs (root for gentoo) /dev/hda7: ntfs (windows d: > > disk) > <snip> > > \Device\Harddisk0\Partition0 (entire disk) > > \Device\Harddisk0\Partition1 ... > > \Device\Harddisk0\Partition5 > > I have confirmed that Windows uses > \Device\Harddisk0\Partition2 as C: and > > \Device\Harddisk0\Partition5 as D: . > > I'm still trying to wrap my poor mind around this stuff, > because I can't get any raw partitions to work under Windows > :^( I've received a number of helpful private e-mails which > I haven't had time to follow up on (you know who you are, > thank you :^). > > If I understand, Windows doesn't "count" /dev/hda3 a.k.a. the > Extended partition. \D\H\P0 is the whole disk, then it > assigns the devices from > \D\H\P1 through 5 in order of the partition table's numbering, but > skipping the Extended partition. Can someone with more > experience please > confirm this is the way Windows assigns \Device\HarddiskX\PartitionY? You need to look at things from a logical point of view and not physical. > > Two other newbie-type questions: > > 1.) Is the primary master IDE disk Harddisk0, the primary > slave Harddisk1, > the secondary master Harddisk2, and the secondary slave > Harddisk3? This > would agree with the info on this MS Technet page: Yes. But logical, not physical. > http://www.microsoft.com/technet/prodtechnol/winntas/maintain/manag.mspx (except for the typo under "IDE Drives" where they say the first drive on the second controller would be designated 3, not 2 -- oops). 2.) Do the \Device\HarddiskVolumeX designations come from the Logical Disk Manager? And how do you figure out the mapping of \D\HarddiskVolumeX to \D\HarddiskY\PartitionZ? The port of dd to Windows with the --list option available here: Yes, use logical disk manager. Hard disks start at 0. Partitions start at 1. Personally I dont see how using a *nix orientated utility can help in this matter. http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm doesn't list the HarddiskVolumeX designations. (Another place to get a dd port to Windows is: http://users.erols.com/gmgarner/forensics/). If this is a FAQ or RTFM, please say so and I apologize in advance :^P Clemmitt Sigler ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Clemmitt M. S. <sig...@bl...> - 2004-03-19 16:18:59
|
Hi Sean, On Fri, 19 Mar 2004, Sean Brook wrote: > You need to look at things from a logical point of view and not > physical. <snip> > > 1.) Is the primary master IDE disk Harddisk0, the primary slave Harddisk1, > > the secondary master Harddisk2, and the secondary slave Harddisk3? > Yes. But logical, not physical. Thank you for your feedback. Perhaps what I meant to ask is, "What is the logic behind the assignment/naming of the logical disk devices in Windows 2K/XP?" As I say, I just don't fully understand. I've spent a few hours searching on Google and MSDN trying to find an answer, to no avail :^( TIA. Clemmitt |
From: Sean B. <sea...@so...> - 2004-03-19 18:12:08
|
> -----Original Message----- > From: col...@li... > [mailto:col...@li...] On Behalf > Of Clemmitt M. Sigler > Sent: Friday, March 19, 2004 4:19 PM > To: Sean Brook > Cc: col...@li... > Subject: RE: [coLinux-devel] Problems with \Device\HarddiskVolumeX > > > Hi Sean, > > On Fri, 19 Mar 2004, Sean Brook wrote: > > You need to look at things from a logical point of view and not > > physical. > <snip> > > > 1.) Is the primary master IDE disk Harddisk0, the primary slave > > > Harddisk1, > > > the secondary master Harddisk2, and the secondary slave Harddisk3? > > Yes. But logical, not physical. > > Thank you for your feedback. Perhaps what I meant to ask is, > "What is the logic behind the assignment/naming of the > logical disk devices in Windows 2K/XP?" I really dont know. I have never needed to know what the scheme is behind numbering of logical disk drives. From what I know with IDE drives only the numbering would be as above. AFAIAC the drive numbering would be what you would expect in a physical sense. When you take into account other storage technologies eg scsi included with others it could change things again. All depends what the boot drive is I suppose. As a side point Windows NT considers all drives to be scsi and supported partitions can be mapped to different drive letters. Throw fault tolerance into it and it would get really confusing to predict. Anyhoo, why do you want to know the logic behind this? > > As I say, I just don't fully understand. I've spent a few > hours searching on Google and MSDN trying to find an answer, > to no avail :^( > TIA. IMO just follow whats in logical disk manager and save your sanity ;) > > Clemmitt > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President > and CEO of GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Clemmitt M. S. <sig...@bl...> - 2004-03-19 19:04:52
|
On Fri, 19 Mar 2004, Sean Brook wrote: > When you take into account other storage technologies eg scsi > included with others it could change things again. I included a MSFT link in an earlier post. That page tries to explain SCSI and IDE drive numbering for W2K. > All depends what the boot drive is I suppose. I wish this were the clue I needed to buy myself. But I have a totally vanilla HD setup and partitioning scheme :^( > Anyhoo, why do you want to know the logic behind this? 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. > IMO just follow whats in logical disk manager and save your sanity ;) *chuckle* I'll try. Clemmitt |
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: 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 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: Sean B. <sea...@so...> - 2004-03-19 14:27:25
|
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=20 colinux seems to have issues with swap partitions in general, though=20 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=92t 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? Cheers. > -----Original Message----- > From: col...@li...=20 > [mailto:col...@li...] On Behalf=20 > Of Ronald Pijnacker > Sent: Friday, March 19, 2004 10:18 AM > To: keksov > Cc: Ronald Pijnacker; col...@li... > Subject: Re: [coLinux-devel] Problems with \Device\HarddiskVolumeX >=20 >=20 > > Please, post your exact disks configuration with partions and OS=20 > > installed. >=20 > One disk: >=20 > /dev/hda1: ext2 > /dev/hda2: ntfs (windows c: disk) > /dev/hda3: extended > /dev/hda5: swap > /dev/hda6: reiserfs (root for gentoo) > /dev/hda7: ntfs (windows d: disk) >=20 > I am using Windows XP, it reports the following: >=20 > \Device\Harddisk0\Partition0 (entire disk)=20 > \Device\Harddisk0\Partition1 ... \Device\Harddisk0\Partition5 >=20 > I have confirmed that Windows uses=20 > \Device\Harddisk0\Partition2 as C: and=20 > \Device\Harddisk0\Partition5 as D: . >=20 > Ronald. >=20 > > Friday, March 19, 2004, 8:44:15 AM, you wrote: > > > > RP> Hi, > > > > RP> The last few evenings, I have been busy with trying to get my=20 > > RP> (dual > > boot) > > RP> Gentoo installation working with coLinux. As instructed on the=20 > > RP> Wiki, I tried \Device\HarddiskVolume4, which should be the swap=20 > > RP> partition, and ...Volume5 which is the root partition.=20 > I've also=20 > > RP> tried \Device\Harddisk0\PartitionX. > > > > RP> However, inside colinux, the only thing I get from the=20 > /dev/cobd? > > device > > RP> is "IO error". Using the Debian file system and the swap-file=20 > > RP> works > > fine. > > > > RP> I'm pretty sure I've got the right volume numbers (others also=20 > > RP> don't > > work > > RP> anyway). Is there something I'm missing? > > > > RP> Thanks, > > > > RP> Ronald. > > > > > > > > RP> ------------------------------------------------------- > > RP> This SF.Net email is sponsored by: IBM Linux Tutorials=20 > Free Linux=20 > > RP> tutorial presented by Daniel Robbins, President and CEO=20 > of GenToo=20 > > RP> technologies. Learn everything from fundamentals to system=20 > > RP> = administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&oplick > > RP> _______________________________________________ > > RP> coLinux-devel mailing list coL...@li... > > RP> https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President=20 > and CEO of=20 > > GenToo technologies. Learn everything from fundamentals to system=20 > > = administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick > > _______________________________________________ > > coLinux-devel mailing list coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President=20 > and CEO of GenToo technologies. Learn everything from=20 > fundamentals to system=20 > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel >=20 |
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. |
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: 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: 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: 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 > > > > |