First you need to know the partition name seen from windows side in the
form "\Device\Harddisk0\Partition4". Remember, that Windows skip the
extended Partion, so hda4 can be \Device\Harddisk0\Partition4 or
\Device\Harddisk0\Partition3.
Use the dd.exe --list, see:
http://colinux.wikia.com/wiki/Partitions
I suggest to use the new device names as alias. Than not need to change
the /etc/fstab in dual boot. For example:
hda4=\Device\Harddisk0\Partition4
hda5=c:\coLinux\swap-file.img
root=/dev/hda4
I have SuSE started with runlevel 4 for colinux. In the colinux config a
line with "init 4" does this. Runlevel 4 is for free use under Suse, and
I have started not all the daemons there. In the end I have a text login
from coLinux and my graphical login in native boot with unchanged
runlevel 5.
The /boot partition you not need under coLinux.
You *must* use the coLinux kernel file "vmlinux". A native kernel can
not boot under coLinux.
Some boot scripts have modifired for error clean boot. For example the
access to 'hwclock' have scipped with an "if". see: "Fixup error mesage
from hwclock" in http://colinux.wikia.com/wiki/FedoraHowTo
Non working scripts have removed from runlevel 4. But some scripts have
dependencies to others, but can or would not start under coLinux. They I
have exied in top of script with the example from
http://colinux.wikia.com/wiki/Dual_boot_system#Skipping_some_scripts_under_coLinux_boot
Nambi J U wrote:
> Hi Prakash,
>
> Yes this is possible, please go to the colinux wiki and search for dual
> boot and you would get some good documents to do this.
>
> I have done this and it works fine for me. Let me know if you require
> more information.
>
> Regards,
> Nambi
>
> On 1/31/08, *Prakash Saivasan* <pra...@gm...
> <mailto:pra...@gm...>> wrote:
>
> Hi All,
> Does coLinux help in a situation where i want to boot a already
> installed linux (in my case a SUSE) from windows ? I have a dual
> boot setup where linux resides on a seperate partition (partition 4)
> of my hard disk. I understand from FAQ that this is possible.
> However some mention about coLinux requiring a modified linux kernel
> really confuses me. I tried to boot an existing suse kernel (on a
> reiserFS filesystem) but was not very successful. Before i try my
> hands on this, I would like to know from experts around if such a
> kind of setup is possible at all. Also please do let me know if
> there are any documents that describe this in more detail.
>
>
> Thanking you
> Prakash S
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> <mailto:coL...@li...>
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
--
Henry N.
|
