colinux-users

[coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

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

Re: [coLinux-users] help setting up a dual boot system

[Peng <rin...@gm...>]

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
>

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

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
> >
>

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

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
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [coLinux-users] help setting up a dual boot system

[Patrick W. <pa...@im...>]

	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

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

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
>

Re: [coLinux-users] help setting up a dual boot system

[Peng <rin...@gm...>]

I once attempted to do some hack with the "init=" boot option to make
colinux boot with a different init script. But it turns out that
colinux is running so well that I never needed to boot my "real" linux
again... so I haven't actually tried it yet :P

On Fri, 2 Jul 2004 01:03:59 +0800, Samir Kuthiala
<sam...@gm...> 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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

hmmm sounds like a good idea. it should be quite straight forward.
i'll try it :)


On Thu, 1 Jul 2004 17:30:21 -0400, Peng <rin...@gm...> wrote:
> 
> I once attempted to do some hack with the "init=" boot option to make
> colinux boot with a different init script. But it turns out that
> colinux is running so well that I never needed to boot my "real" linux
> again... so I haven't actually tried it yet :P
> 
> On Fri, 2 Jul 2004 01:03:59 +0800, Samir Kuthiala
> 
> <sam...@gm...> 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
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [coLinux-users] help setting up a dual boot system

[A. A. A. <alp...@tt...>]

On Fri, Jul 02, 2004 at 01:03:59AM +0800, Samir Kuthiala wrote:
> 
> There are still some errors regarding some fonts, 

that must be console fonts, I guess it's related to the way colinux kernel 
is configured

> inability to load usb drivers 

colinux kernel does not have usb drivers, but your /etc/modules.conf has 
references to it, so you get errors


> and at every bootup my system keeps prompting me to change
> hardware config etc. 

turn off kudzu, your hardware config is not the same anymore


> 
> 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.
> 

AFAIK, some work has been started on it, you'll be able to specify a mapping 
between /dev/hdX and /dev/cobdX in config.xml. Note that version of colinux 
will be based on 2.6.x kernel.

Re: [coLinux-users] help setting up a dual boot system

[Dwight C. <da...@po...>]

Eh, here's the cheap-n-nasty solution I'm using for that....

(colinux 20040622, slackware 10.0)

First thing in /etc/rc.d/rc.S is add at the top

/sbin/mount -o remount,rw /
/etc/rc.d/rc.VerHack
/sbin/mount -o remount,ro /

the contents of rc.VerHack are

#!/bin/sh
# version workarounds.  Bah!

echo "Applying ugly kernel version hacks (colinux vs. real linux)"
/bin/rm /etc/fstab
/bin/rm /etc/lilo.conf
/bin/rm /opt/kde/share/config/kdm/Xservers
/bin/rm /usr/src/linux

if uname -r | grep "co-" ; then
  ln -s /etc/fstab.colinux /etc/fstab
  ln -s /etc/lilo.conf.colinux /etc/lilo.conf
  ln -s /opt/kde/share/config/kdm/Xservers.colinux /opt/kde/share/config/kdm/Xservers
  ln -s /usr/src/linux-2.6.7-co-0.6.2 /usr/src/linux
else
  ln -s /etc/fstab.reallinux /etc/fstab
  ln -s /etc/lilo.conf.reallinux /etc/lilo.conf
  ln -s /opt/kde/share/config/kdm/Xservers.reallinux /opt/kde/share/config/kdm/Xservers
  ln -s /usr/src/linux-2.6.7 /usr/src/linux
fi


Substitute config files as needed for differrences between real hardware and
colinux boot.  This approach has a few downsides, such as possibly borking
system sanity checks at boot time.  Wouldn't want to use anything even vaguely
resembling in a production environment, etc etc.


Hope this helps,
d.c.

On Thu, 1 Jul 2004, Samir Kuthiala 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
>

| dwight a. campbell : da...@po...  : http://rats.darktech.org/ |
| linux guru in training : reality avoidance therapist for hire : KD7KJG |
| when you live in a sick society, just about everything you do is wrong |

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

thx. i'll definitely try this. 

on a side note, can i just install a new version of colinux over my
existing ver or do I need to uninstall and then install?

~Samir


On Fri, 2 Jul 2004 11:45:30 -0700 (PDT), Dwight Campbell
<da...@po...> wrote:
> 
> Eh, here's the cheap-n-nasty solution I'm using for that....
> 
> (colinux 20040622, slackware 10.0)
> 
> First thing in /etc/rc.d/rc.S is add at the top
> 
> /sbin/mount -o remount,rw /
> /etc/rc.d/rc.VerHack
> /sbin/mount -o remount,ro /
> 
> the contents of rc.VerHack are
> 
> #!/bin/sh
> # version workarounds.  Bah!
> 
> echo "Applying ugly kernel version hacks (colinux vs. real linux)"
> /bin/rm /etc/fstab
> /bin/rm /etc/lilo.conf
> /bin/rm /opt/kde/share/config/kdm/Xservers
> /bin/rm /usr/src/linux
> 
> if uname -r | grep "co-" ; then
>  ln -s /etc/fstab.colinux /etc/fstab
>  ln -s /etc/lilo.conf.colinux /etc/lilo.conf
>  ln -s /opt/kde/share/config/kdm/Xservers.colinux /opt/kde/share/config/kdm/Xservers
>  ln -s /usr/src/linux-2.6.7-co-0.6.2 /usr/src/linux
> else
>  ln -s /etc/fstab.reallinux /etc/fstab
>  ln -s /etc/lilo.conf.reallinux /etc/lilo.conf
>  ln -s /opt/kde/share/config/kdm/Xservers.reallinux /opt/kde/share/config/kdm/Xservers
>  ln -s /usr/src/linux-2.6.7 /usr/src/linux
> fi
> 
> Substitute config files as needed for differrences between real hardware and
> colinux boot.  This approach has a few downsides, such as possibly borking
> system sanity checks at boot time.  Wouldn't want to use anything even vaguely
> resembling in a production environment, etc etc.
> 
> Hope this helps,
> d.c.
> 
> On Thu, 1 Jul 2004, Samir Kuthiala 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
> >
> 
> | dwight a. campbell : da...@po...  : http://rats.darktech.org/ |
> | linux guru in training : reality avoidance therapist for hire : KD7KJG |
> | when you live in a sick society, just about everything you do is wrong |
> 
> 
> 
> 
> -------------------------------------------------------
> 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
>

Re: [coLinux-users] help setting up a dual boot system

[Dwight C. <da...@po...>]

I've had no real issues with upgrading colinux in-place, your mileage may vary.

d.c.

On Sun, 4 Jul 2004, Samir Kuthiala wrote:

>thx. i'll definitely try this.
>
>on a side note, can i just install a new version of colinux over my
>existing ver or do I need to uninstall and then install?
>
>~Samir
>


| dwight a. campbell : da...@po...  : http://rats.darktech.org/ |
| linux guru in training : reality avoidance therapist for hire : KD7KJG |
| when you live in a sick society, just about everything you do is wrong |