colinux-users

[coLinux-users] boot from seperate physical drive

[Kristopher Y. <kri...@ho...>]

Hi

I would like to run this software but can't figure out how to config the XML 
properly.  Can anyone help?  Here is my configuration:

I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on 
my primary slave drive.

/dev/hda1 = swap

/dev/hda2 = root

/boot/vmlinuz is my kernel location.


Normally, I boot up to the grub boot-loader screen.  I can select linux or 
XP.  Each OS is on its own seperate physical hard drive.

Thank you,

Kris

_________________________________________________________________
Be seen and heard with Windows Live Messenger and Microsoft LifeCams 
http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://www.microsoft.com/hardware/digitalcommunication/default.mspx?locale=en-us&source=hmtagline

Re: [coLinux-users] boot from seperate physical drive

[Holger K. <hol...@gm...>]

Kristopher Yates schrieb:

> I would like to run this software but can't figure out how to config the XML 
> properly.  Can anyone help?  Here is my configuration:
> 
> I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on 
> my primary slave drive.
> 
> /dev/hda1 = swap
> 
> /dev/hda2 = root
> 
> /boot/vmlinuz is my kernel location.

First: Do you want to boot your existing Suse 10.1 in colinux?
Which colinux version do you use?

The kernel that gets started with colinux will always be the colinux kernel, not the suse kernel.
The config for the raw device access most likely will be 
<block_device index="0" path="\Device\Harddisk0\Partition1" enabled="true"/> 
<block_device index="1" path="\Device\Harddisk0\Partition2" enabled="true"/>

But i don't know if the partition numbering starts at 0 or 1.

Look at http://wiki.colinux.org/wiki/WindowsDevicePaths

Re: [coLinux-users] boot from seperate physical drive

[Henry N. <Hen...@Ar...>]

Holger Krull wrote:
> Kristopher Yates schrieb:
> 
>> I would like to run this software but can't figure out how to config the XML 
>> properly.  Can anyone help?  Here is my configuration:
>>
>> I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on 
>> my primary slave drive.
>>
>> /dev/hda1 = swap
>>
>> /dev/hda2 = root
>>
>> /boot/vmlinuz is my kernel location.
> 
> First: Do you want to boot your existing Suse 10.1 in colinux?
> Which colinux version do you use?
> 
> The kernel that gets started with colinux will always be the colinux kernel, not the suse kernel.
> The config for the raw device access most likely will be 
> <block_device index="0" path="\Device\Harddisk0\Partition1" enabled="true"/> 
> <block_device index="1" path="\Device\Harddisk0\Partition2" enabled="true"/>
> 
> But i don't know if the partition numbering starts at 0 or 1.
> 
> Look at http://wiki.colinux.org/wiki/WindowsDevicePaths

With your informatitions about your disk, it's better to set the index 
for your hdaX to the same index as your native installation, than the 
cobdX is the same as hdaX.  And better, you use alias to real hdaX, that 
makes the /etc/fstab more easy.

This should work for you (coLinux 0.6.4):

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
     <!-- cobd1 is your SWAP partition -->
     <block_device index="1" path="\Device\Harddisk0\Partition1"
     alias="hda1" enabled="true" />

     <!-- cobd2 is your SuSE Root -->
     <block_device index="2" path="\Device\Harddisk0\Partition2"
     alias="hda2" enabled="true" />

     <!-- Define your Root partition (not the Boot) -->
     <!-- Lets start a runlevel without graphic -->
     <bootparams>root=/dev/hda2 ro init 3</bootparams>

     <!-- Initial RamDISK (initrd) and Kernel from coLinux -->
     <initrd path="initrd.gz" />
     <image path="vmlinux" />

     <!-- this line allows you to specify the amount of memory
          available to coLinux -->
     <memory size="128" />
</colinux>

This all is in assumtion, that you would run your native Linux under 
colinux.  Is this right?

Please remember, that you need some changes on boot scripts in your 
SuSE, before it would be run properly.  Follow the title in wiki:

http://wiki.colinux.org/wiki/Converting_Distributions
http://wiki.colinux.org/wiki/Dual_boot_system#Skipping_some_scripts_under_coLinux_boot

-- 
Henry Nestler

Re: [coLinux-users] boot from seperate physical drive

[Michelangelo <mic...@gm...>]

 kernel=c:\colinux\vmlinux initrd=c:\colinux\initrd.gz
kernel=c:\colinux\vmlinux root=/dev/cobd/0
cobd0=\Device\HardDisk0\Partition1

Syntax using  when using commandline parameters. Just adapt it for yr XML.
It starts colinux using first partition of first hard disk as root
partition. As for the kernel Aand the initrd, you have to specify the ones
shipped with colinux (or recompile a new one with colinux patches, a feat
which I'd like to have some feedback on), obviously using paths relative to
yr windows install.
If I'm not horribly mistaken, Disk numbering starts at 0, partition
numbering starts at 1 (it is windows naming schema).

Ciao
Michelangelo


On 9/19/06, Kristopher Yates <kri...@ho...> wrote:
>
> Hi
>
> I would like to run this software but can't figure out how to config the
> XML
> properly.  Can anyone help?  Here is my configuration:
>
> I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on
> my primary slave drive.
>
> /dev/hda1 = swap
>
> /dev/hda2 = root
>
> /boot/vmlinuz is my kernel location.
>
>
> Normally, I boot up to the grub boot-loader screen.  I can select linux or
> XP.  Each OS is on its own seperate physical hard drive.
>
> Thank you,
>
> Kris
>
> _________________________________________________________________
> Be seen and heard with Windows Live Messenger and Microsoft LifeCams
>
> http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://www.microsoft.com/hardware/digitalcommunication/default.mspx?locale=en-us&source=hmtagline
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] boot from seperate physical drive

[Michelangelo <mic...@gm...>]

Please ignore previous mail, some mistakes there. follows correct command
line


 kernel=c:\colinux\vmlinux initrd=c:\colinux\initrd.gz root=/dev/cobd/0
> cobd0=\Device\HardDisk0\Partition1
>
> Syntax to use when starting colinux via commandline parameters. Just adapt
> it for yr XML. It starts colinux using first partition of first hard disk as
> root partition. As for the kernel and the initrd, you have to specify the
> ones shipped with colinux (or recompile a new one with colinux patches, a
> feat which I'd like to have some feedback on), obviously using paths
> relative to yr windows install.
> If I'm not horribly mistaken, disk numbering starts at 0, partition
> numbering starts at 1 (it is windows naming schema).
>
> Ciao
> Michelangelo
>
>
>
> On 9/19/06, Kristopher Yates <kri...@ho...> wrote:
> >
> > Hi
> >
> > I would like to run this software but can't figure out how to config the
> > XML
> > properly.  Can anyone help?  Here is my configuration:
> >
> > I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is
> > on
> > my primary slave drive.
> >
> > /dev/hda1 = swap
> >
> > /dev/hda2 = root
> >
> > /boot/vmlinuz is my kernel location.
> >
> >
> > Normally, I boot up to the grub boot-loader screen.  I can select linux
> > or
> > XP.  Each OS is on its own seperate physical hard drive.
> >
> > Thank you,
> >
> > Kris
> >
> > _________________________________________________________________
> > Be seen and heard with Windows Live Messenger and Microsoft LifeCams
> >
> > http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://www.microsoft.com/hardware/digitalcommunication/default.mspx?locale=en-us&source=hmtagline
> >
> >
> > -------------------------------------------------------------------------
> >
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your
> > opinions on IT & business topics through brief surveys -- and earn cash
> >
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
>
>

Re: [coLinux-users] boot from seperate physical drive

[George P B. <geo...@gm...>]

On 9/19/06, Michelangelo <mic...@gm...> wrote:

> partition. As for the kernel Aand the initrd, you have to specify the ones
> shipped with colinux (or recompile a new one with colinux patches, a feat
> which I'd like to have some feedback on), obviously using paths relative to
> yr windows install.

Yes, always use the colinux kernel, the initrd for coLinux is more or
less options, if you don't use it or if it fails to do what it's
designed to do, you can avoid it's use by manually unarchiving the
contents of vmlinux-modules.tar.gz from the colinux install directory
into the root partition on SuSe 10.1 (basically initrd just tries to
automagically install the colinux kernel modules for you)

What specifically about compiling your own kernel did you want/need
feedback on.  I do this regularly as do many users.  There are a few
'gotchas' you have to be aware of though.

-- 
George