Menu
▾
▴
Re: [coLinux-users] help setting up a dual boot system
|
From: Samir K. <sam...@gm...> - 2004-07-02 00:48:53
|
hmmm I am using 0.6.1 Isnt that the latest version? On Thu, 1 Jul 2004 17:40:30 +0000, Patrick White <pa...@im...> wrote: > > > I ran into similar probelms with Win2000, colinux 0.6.0 and RH EL3.. tracked > it down to the size of the physical partition being reported to colinux as 0. > The zero size causes fsck of root to fail (even through the blocks can > actually be accessed), which causes the boot to fail. I think the physical > partition size reporting problem has been fixed in later versions. Fastboot > skips the fsck on root, so that's probably why it makes things work. > This solution would worry me because if the root partition ever gets > corrupted, you'll never be able to fix it without booting natively. Might be > worthwhile upgrading to a version with the physical partition size reporting > fix. > > later, > patbob > > > On Thursday 01 July 2004 5:03 pm, Samir Kuthiala wrote: > > Hi > > > > Thanks for all the suggestions. I finally got it to work... sort of. > > basically in short I had to remove allr eferences in /etc/fstab to > > /dev/*. Also I had to enable fastboot in /etc/rc.d/rc/sysinit > > > > There are still some errors regarding some fonts, inability to load > > usb drivers and at every bootup my system keeps prompting me to change > > hardware config etc. but the system as such is working fine. I am able > > to connect to an external Xserver and run my programs. > > > > However I had to modify my fstab quite a bit to make my dual boot > > work. (to a point where I am unable to load linux normally :( > > > > Does anyone know of a way to switch fstabs depending on which kernel > > is loaded? or maybe another mechanism to handle device differences > > between different bootup sequences. > > > > Thanks > > Samir > > > > On Thu, 1 Jul 2004 06:41:59 -0400, Peng <rin...@gm...> wrote: > > > I am pretty sure that the problem is caused by fsck attempting to > > > access /dev/hda3. Try to find out where this hda3 comes from, and > > > change it to /dev/cobd0. > > > > > > On Thu, 1 Jul 2004 18:33:15 +0800, Samir Kuthiala > > > > > > <sam...@gm...> wrote: > > > > tried both /dev/cobd0 and /dev/cobd/0. no change. in the repair fs i > > > > tried doing cat /etc/mtab and the partition which is mounted is > > > > /dev/hda3 > > > > > > > > On Thu, 1 Jul 2004 05:55:36 -0400, Peng <rin...@gm...> wrote: > > > > > Oops. Try the following: > > > > > > > > > > give root password and enter the "repair fs" shell > > > > > > > > > > ls -l /dev/cobd0 > > > > > > > > > > see if that device exists.... sometime devfs put that device into > > > > > /dev/cobd/0 if that's the case, you can either modify fstab or create > > > > > a symbolic link from /dev/cobd0 --> /dev/cobd/0 > > > > > > > > > > let me know if it works... > > > > > > > > > > -- Peng > > > > > > > > > > On Thu, 1 Jul 2004 17:51:19 +0800, Samir Kuthiala > > > > > > > > > > <sam...@gm...> wrote: > > > > > > I have already tried that. no difference. It stops at loading the > > > > > > root partition which is pretty funny considering that afterwards it > > > > > > throws me into the "Repair Filesystem" shell. And I can see the > > > > > > entire linux partition and browse through it from within co-linux. > > > > > > > > > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > > > > Try: > > > > > > > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume3" > > > > > > > enabled="true" /> > > > > > > > > > > > > > > And disable your swap partition. Once the basic system works you > > > > > > > can keep going and add the swap thing... > > > > > > > > > > > > > > Good luck, > > > > > > > > > > > > > > Peng > > > > > > > > > > > > > > > > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > > > > > > > > > > > > > <sam...@gm...> wrote: > > > > > > > > Hi > > > > > > > > > > > > > > > > I have been trying to get the colinux to work on my dual boot > > > > > > > > system (win2k pro + RH9) for the last few days but with no > > > > > > > > success. heres a summary of what I have done so far > > > > > > > > > > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > > > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo > > > > > > > > image. modified the config file to this... > > > > > > > > =============================================== > > > > > > > > <colinux> > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > > > > > > enabled="true" /> <block_device index="1" > > > > > > > > path="\Device\HarddiskVolume3" enabled="true" /> > > > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > > > <image path="vmlinux" /> > > > > > > > > <memory size="64" /> > > > > > > > > <network index="0" type="tap" name="tap" /> > > > > > > > > </colinux> > > > > > > > > =============================================== > > > > > > > > 3. copied the kernel modules packaged along with colinux into > > > > > > > > the /lib/modules dir > > > > > > > > > > > > > > > > I then tried to boot the colinux. failed with some error about > > > > > > > > unable to locate /dev/hda3 (thats my root partition). I assumed > > > > > > > > this was due to me not having modified fstab. I then modified > > > > > > > > fstab to remove all references to /dev/hd* and added in > > > > > > > > /dev/cobd0 (as root) and /dev/cobd1 as swap. However the bootup > > > > > > > > sequence still fails with some error message about invalid > > > > > > > > superblock. > > > > > > > > > > > > > > > > I have gone through the website/forums/wiki and am just about > > > > > > > > to give up. Can somebody help me figure out whats going wrong? > > > > > > > > > > > > > > > > Thanks > > > > > > > > Samir > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > > > > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > > > > > > digital self defense, top technical experts, no vendor pitches, > > > > > > > > unmatched networking opportunities. Visit www.blackhat.com > > > > > > > > _______________________________________________ > > > > > > > > coLinux-users mailing list > > > > > > > > coL...@li... > > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
