From: Sarah T. <sar...@ya...> - 2004-07-03 13:20:47
|
Perhaps you coLinux guru can help me out for the following: Suppose that I have dual boot machine, Windows(partition1) and Linux(partition2). I know that I can convert the Linux installation to work with coLinux within Windows, but with many things to alter such as the fstab entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? and disable loading modules of some devices such as USB, etc ...(dunno how yet). My question is that is it possible that coLinux do the automatic reconfiguration for such environment e,g: detect the devices in fstab and convert them to coLinux compatible devices? Will it require core Linux kernel to be modified to implement such features? I think this ability to adapt to any virtualization software would ease the implementation` isn't it? Sorry if what I'm talking about does not make any sense. Thanks |
From: Dan A. <da...@co...> - 2004-07-03 13:46:23
|
On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: > Perhaps you coLinux guru can help me out for the following: > > Suppose that I have dual boot machine, Windows(partition1) and > Linux(partition2). I know that I can convert the Linux installation to work > with coLinux within Windows, but with many things to alter such as the fstab > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? and > disable loading modules of some devices such as USB, etc ...(dunno how yet). You don't actually need to disable module loading, but rather put the right modules for the running coLinux kernel under the /lib/modules directory. > My question is that is it possible that coLinux do the automatic > reconfiguration for such environment e,g: The next snapshot version of coLinux will include device node aliasing, which means that you can configure any cobd to appear as a hd or sda partition, and even boot from it (e.g. root=/dev/hda4). Theoretically it would be possible to probe the Linux partitions in the Windows side and create a proper configuration file. This way you don't need to change /ect/fstab. -- Dan Aloni da...@co... |
From: Sarah T. <sar...@ya...> - 2004-07-03 15:11:33
|
First of all, thank you for answering my question. I'm sure this will not be the last as I'm quite intrique with this virtualization stuff. > > Perhaps you coLinux guru can help me out for the following: > > > > Suppose that I have dual boot machine, Windows(partition1) and > > Linux(partition2). I know that I can convert the Linux installation to work > > with coLinux within Windows, but with many things to alter such as the fstab > > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? and > > disable loading modules of some devices such as USB, etc ...(dunno how yet). > > You don't actually need to disable module loading, but rather put the right > modules for the running coLinux kernel under the /lib/modules directory. Will coLinux kernel will be able to know which /lib/modules/<kernel-version> to use or manual changes still have to be done? > > > My question is that is it possible that coLinux do the automatic > > reconfiguration for such environment e,g: > > The next snapshot version of coLinux will include device node aliasing, > which means that you can configure any cobd to appear as a hd or sda > partition, and even boot from it (e.g. root=/dev/hda4). Theoretically it > would be possible to probe the Linux partitions in the Windows side and > create a proper configuration file. This way you don't need to change > /ect/fstab. Cool. I could not wait to try it out. |
From: Jaroslaw K. <ja...@zd...> - 2004-07-04 19:46:02
|
Dual booting is possible today using the LABEL feature that most distros supports (fedora being one of them): It works like this: 1. Mount has a special syntax that lets you specify device labels instead of real device names. Labels are parts of filesystems (ext2,ext3, probably others too). Assuming your /dev/hda1 has a label "XXX" you can mount it using either mount /dev/hda1 mountpoint mount LABEL=XXX mountpoint 2. Same syntax can be used in /etc/fstab: ----------------------- LABEL=XXX / ext2 defaults 0 0 ----------------------- can be used instead of: ----------------------- /dev/hda1 / ext2 defaults 0 0 ----------------------- 3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" which is required for LABELs to work. Previous version had a problem where /proc/partitions didn't contain cobdX devices so "mount" didn't know what to scan for labels. 4. In theory it should be possible to even pass root=LABEL=XXX to kernel at boot time (this requires initrd), but I was never able to do it. 5. Labels can be assigned using "e2label" utility. For other FSs there should be appropriate utilities. So assuming you assign all your devices the appropriate labels (this isn't possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab entries, you should have a clean dual-bootable linux distro. I use it daily, and have no problems with this setup. Jarek ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Sarah Tanembaum" <sar...@ya...> Cc: <col...@li...> Sent: Saturday, July 03, 2004 3:48 PM Subject: Re: [coLinux-devel] wish list > On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: > > Perhaps you coLinux guru can help me out for the following: > > > > Suppose that I have dual boot machine, Windows(partition1) and > > Linux(partition2). I know that I can convert the Linux installation to work > > with coLinux within Windows, but with many things to alter such as the fstab > > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? and > > disable loading modules of some devices such as USB, etc ...(dunno how yet). > > You don't actually need to disable module loading, but rather put the right > modules for the running coLinux kernel under the /lib/modules directory. > > > My question is that is it possible that coLinux do the automatic > > reconfiguration for such environment e,g: > > The next snapshot version of coLinux will include device node aliasing, > which means that you can configure any cobd to appear as a hd or sda > partition, and even boot from it (e.g. root=/dev/hda4). Theoretically it > would be possible to probe the Linux partitions in the Windows side and > create a proper configuration file. This way you don't need to change > /ect/fstab. > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Sarah T. <sar...@ya...> - 2004-07-06 06:07:39
|
Thanks Jaroslaw. Forgive my little knowledge about coLinux. Perhaps you can elaborate the explanation below. Is it to be done on the distribution(e.g Fedora 2) outside the coLinux or it it within coLinux virtual machine? I have the following on my disk: Partition1 Primary FAT32 Win98 Partition2 Primary Solaris Partition3 Primary Linux - Fedora1 Partition4 Extended FAT32 Partition5 Extended Windows Server 2003 Partition6 Extended Linux Swap Free space Extended I can boot on each one of them but now I'd like to make my Linux to be bootable within coLinux running under W2K. So far I can get the coLinux running using the Fedora distribution from the download site. Perhaps it would be super if I know how to make my Linux installation on partition 3 be bootable from coLinux. Anyone? Thanks "Jaroslaw Kowalski" <ja...@zd...> wrote in message news:002701c461f6$e8af53f0$0221a8c0@jarekxp... > Dual booting is possible today using the LABEL feature that most distros > supports (fedora being one of them): > > It works like this: > > 1. Mount has a special syntax that lets you specify device labels instead of > real device names. Labels are parts of filesystems (ext2,ext3, probably > others too). > > Assuming your /dev/hda1 has a label "XXX" you can mount it using either > > mount /dev/hda1 mountpoint > mount LABEL=XXX mountpoint > > 2. Same syntax can be used in /etc/fstab: > > ----------------------- > LABEL=XXX / ext2 defaults 0 0 > ----------------------- > can be used instead of: > ----------------------- > /dev/hda1 / ext2 defaults 0 0 > ----------------------- > > 3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" > which is required for LABELs to work. Previous version had a problem where > /proc/partitions didn't contain cobdX devices so "mount" didn't know what to > scan for labels. > > 4. In theory it should be possible to even pass root=LABEL=XXX to kernel at > boot time (this requires initrd), but I was never able to do it. > > 5. Labels can be assigned using "e2label" utility. For other FSs there > should be appropriate utilities. > > So assuming you assign all your devices the appropriate labels (this isn't > possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab > entries, you should have a clean dual-bootable linux distro. > > I use it daily, and have no problems with this setup. > > Jarek > ----- Original Message ----- > From: "Dan Aloni" <da...@co...> > To: "Sarah Tanembaum" <sar...@ya...> > Cc: <col...@li...> > Sent: Saturday, July 03, 2004 3:48 PM > Subject: Re: [coLinux-devel] wish list > > > > On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: > > > Perhaps you coLinux guru can help me out for the following: > > > > > > Suppose that I have dual boot machine, Windows(partition1) and > > > Linux(partition2). I know that I can convert the Linux installation to > work > > > with coLinux within Windows, but with many things to alter such as the > fstab > > > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? > and > > > disable loading modules of some devices such as USB, etc ...(dunno how > yet). > > > > You don't actually need to disable module loading, but rather put the > right > > modules for the running coLinux kernel under the /lib/modules directory. > > > > > My question is that is it possible that coLinux do the automatic > > > reconfiguration for such environment e,g: > > > > The next snapshot version of coLinux will include device node aliasing, > > which means that you can configure any cobd to appear as a hd or sda > > partition, and even boot from it (e.g. root=/dev/hda4). Theoretically it > > would be possible to probe the Linux partitions in the Windows side and > > create a proper configuration file. This way you don't need to change > > /ect/fstab. > > > > -- > > Dan Aloni > > da...@co... > > > > > > ------------------------------------------------------- > > 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-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > ------------------------------------------------------- > 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 |
From: Jaroslaw K. <ja...@zd...> - 2004-07-06 06:48:40
|
This is my config - I use it to dual boot my Fedora Core 2: ====================================== <?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\Device\HardDisk0\Partition5" enabled="true" /> <block_device index="1" path="\Device\HardDisk0\Partition4" enabled="true" /> <image path="vmlinux" /> <initrd path="initrd-2.6.7-co-0.6.2.img" /> <bootparams>ro nousb root=/dev/cobd0</bootparams> <memory size="160" /> <network index="0" type="tap" name="CoLinux TAP" /> </colinux> ====================================== The following things have to be done under Fedora: 1. Create devices # mknod /dev/cobd0 b 117 0 # mknod /dev/cobd1 b 117 1 # mknod /dev/cobd2 b 117 2 # mknod /dev/cobd3 b 117 3 ... (repeat as needed up to cobd31) 2. Make sure the default runlevel is set to "3" to prevent X from booting. You can change it in "/etc/inittab" by modifying the first uncommented line to read: id:3:initdefault: 3. To allow single /etc/fstab you need to assign labels to your block devices: For each partition that you have mounted run: # e2fslabel /dev/hdaX MYPARTITIONX and modify your /etc/fstab by replacing each occurence of "/dev/hdaX" with "LABEL=MYPARTITIONX" As for the swap partitions: you cannot assign labels to them, but you can put more than one swap in /etc/fstab. Fedora will just ignore the ones that aren't present. In my case I have: ==== /dev/hda5 swap swap defaults 0 0 /dev/cobd1 swap swap defaults 0 0 ====== When running under colinux - /dev/hda5 is not found, when running native - /dev/cobd1 is not found, but they point to the same physical partition. That's it. You can try running "ntsysv" and disabling unnecessary services which don't make sense under colinux. Hope it helps. Jarek ----- Original Message ----- From: "Sarah Tanembaum" <sar...@ya...> To: <col...@li...> Cc: <col...@li...> Sent: Tuesday, July 06, 2004 8:07 AM Subject: [coLinux-devel] Re: wish list > Thanks Jaroslaw. Forgive my little knowledge about coLinux. > > Perhaps you can elaborate the explanation below. > Is it to be done on the distribution(e.g Fedora 2) outside the coLinux or it > it within coLinux virtual machine? > > I have the following on my disk: > > Partition1 Primary FAT32 Win98 > Partition2 Primary Solaris > Partition3 Primary Linux - Fedora1 > Partition4 Extended FAT32 > Partition5 Extended Windows Server 2003 > Partition6 Extended Linux Swap > Free space Extended > > I can boot on each one of them but now I'd like to make my Linux to be > bootable within coLinux running under W2 K. > > So far I can get the coLinux running using the Fedora distribution from the > download site. Perhaps it would be super if I know how to make my Linux > installation on partition 3 be bootable from coLinux. Anyone? > > Thanks > > > "Jaroslaw Kowalski" <ja...@zd...> wrote in message > news:002701c461f6$e8af53f0$0221a8c0@jarekxp... > > Dual booting is possible today using the LABEL feature that most distros > > supports (fedora being one of them): > > > > It works like this: > > > > 1. Mount has a special syntax that lets you specify device labels instead > of > > real device names. Labels are parts of filesystems (ext2,ext3, probably > > others too). > > > > Assuming your /dev/hda1 has a label "XXX" you can mount it using either > > > > mount /dev/hda1 mountpoint > > mount LABEL=XXX mountpoint > > > > 2. Same syntax can be used in /etc/fstab: > > > > ----------------------- > > LABEL=XXX / ext2 defaults 0 0 > > ----------------------- > > can be used instead of: > > ----------------------- > > /dev/hda1 / ext2 defaults 0 0 > > ----------------------- > > > > 3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" > > which is required for LABELs to work. Previous version had a problem where > > /proc/partitions didn't contain cobdX devices so "mount" didn't know what > to > > scan for labels. > > > > 4. In theory it should be possible to even pass root=LABEL=XXX to kernel > at > > boot time (this requires initrd), but I was never able to do it. > > > > 5. Labels can be assigned using "e2label" utility. For other FSs there > > should be appropriate utilities. > > > > So assuming you assign all your devices the appropriate labels (this isn't > > possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab > > entries, you should have a clean dual-bootable linux distro. > > > > I use it daily, and have no problems with this setup. > > > > Jarek > > ----- Original Message ----- > > From: "Dan Aloni" <da...@co...> > > To: "Sarah Tanembaum" <sar...@ya...> > > Cc: <col...@li...> > > Sent: Saturday, July 03, 2004 3:48 PM > > Subject: Re: [coLinux-devel] wish list > > > > > > > On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: > > > > Perhaps you coLinux guru can help me out for the following: > > > > > > > > Suppose that I have dual boot machine, Windows(partition1) and > > > > Linux(partition2). I know that I can convert the Linux installation to > > work > > > > with coLinux within Windows, but with many things to alter such as the > > fstab > > > > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? > > and > > > > disable loading modules of some devices such as USB, etc ...(dunno how > > yet). > > > > > > You don't actually need to disable module loading, but rather put the > > right > > > modules for the running coLinux kernel under the /lib/modules directory. > > > > > > > My question is that is it possible that coLinux do the automatic > > > > reconfiguration for such environment e,g: > > > > > > The next snapshot version of coLinux will include device node aliasing, > > > which means that you can configure any cobd to appear as a hd or sda > > > partition, and even boot from it (e.g. root=/dev/hda4). Theoretically it > > > would be possible to probe the Linux partitions in the Windows side and > > > create a proper configuration file. This way you don't need to change > > > /ect/fstab. > > > > > > -- > > > Dan Aloni > > > da...@co... > > > > > > > > > ------------------------------------------------------- > > > 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-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > ------------------------------------------------------- > > 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 > > > > > > ------------------------------------------------------- > 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: A. A. A. <alp...@tt...> - 2004-07-06 08:19:28
|
On Tue, Jul 06, 2004 at 08:48:31AM +0200, Jaroslaw Kowalski wrote: > > This is my config - I use it to dual boot my Fedora Core 2: > Ah, I think you're missing a crucial detail in all those verbose output: What version of colinux is it that you suggest to this newbie in this case? |
From: Jaroslaw K. <ja...@zd...> - 2004-07-06 08:31:07
|
Sorry. I used 06.22 snapshot available at: http://colinux.org/snapshots/coLinux-20040622.exe 0.6.1 will not work because it doesn't support /proc/partitions and initrd. Jarek ----- Original Message ----- From: "A. Alper Atici" <alp...@tt...> To: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, July 06, 2004 10:20 AM Subject: Re: ... Re: [coLinux-devel] Re: wish list > > On Tue, Jul 06, 2004 at 08:48:31AM +0200, Jaroslaw Kowalski wrote: > > > > This is my config - I use it to dual boot my Fedora Core 2: > > > > Ah, I think you're missing a crucial detail in all those verbose output: > What version of colinux is it that you suggest to this newbie in this case? > > > ------------------------------------------------------- > 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Sarah T. <sar...@ya...> - 2004-07-06 14:42:54
|
Thanks. I will give it a try. By the way, under your config, <image path="vmlinux"> -- is this native vmlinux or what's comes with distribution? if not, how do it build it from scratch? <initrd path="initrd-2.6.7-co-0.6.2.img> -- how do I build this kernel image to run under coLinux? How about the /lib/modules under native installation, will coLinux detect it or do I have to repackage it to be able to run under coLinux. Thanks again --- "Jaroslaw Kowalski" <ja...@zd...> wrote in message news:000e01c46325$40720310$0221a8c0@jarekxp... > > This is my config - I use it to dual boot my Fedora Core 2: > > ====================================== > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > <block_device index="0" path="\Device\HardDisk0\Partition5" > enabled="true" /> > <block_device index="1" path="\Device\HardDisk0\Partition4" > enabled="true" /> > <image path="vmlinux" /> > <initrd path="initrd-2.6.7-co-0.6.2.img" /> > <bootparams>ro nousb root=/dev/cobd0</bootparams> > <memory size="160" /> > <network index="0" type="tap" name="CoLinux TAP" /> > </colinux> > ====================================== > > The following things have to be done under Fedora: > > 1. Create devices > > # mknod /dev/cobd0 b 117 0 > # mknod /dev/cobd1 b 117 1 > # mknod /dev/cobd2 b 117 2 > # mknod /dev/cobd3 b 117 3 > > ... (repeat as needed up to cobd31) > > 2. Make sure the default runlevel is set to "3" to prevent X from booting. > You can change it in "/etc/inittab" by modifying the first uncommented line > to read: > > id:3:initdefault: > > 3. To allow single /etc/fstab you need to assign labels to your block > devices: > > For each partition that you have mounted run: > > # e2fslabel /dev/hdaX MYPARTITIONX > > and modify your /etc/fstab by replacing each occurence of "/dev/hdaX" with > "LABEL=MYPARTITIONX" > > As for the swap partitions: you cannot assign labels to them, but you can > put more than one swap in /etc/fstab. Fedora will just ignore the ones that > aren't present. > In my case I have: > > ==== > /dev/hda5 swap swap defaults 0 0 > /dev/cobd1 swap swap defaults 0 0 > ====== > > When running under colinux - /dev/hda5 is not found, when running native - > /dev/cobd1 is not found, but they point to the same physical partition. > > That's it. You can try running "ntsysv" and disabling unnecessary services > which don't make sense under colinux. > > Hope it helps. > > Jarek > > ----- Original Message ----- > From: "Sarah Tanembaum" <sar...@ya...> > To: <col...@li...> > Cc: <col...@li...> > Sent: Tuesday, July 06, 2004 8:07 AM > Subject: [coLinux-devel] Re: wish list > > > > Thanks Jaroslaw. Forgive my little knowledge about coLinux. > > > > Perhaps you can elaborate the explanation below. > > Is it to be done on the distribution(e.g Fedora 2) outside the coLinux or > it > > it within coLinux virtual machine? > > > > I have the following on my disk: > > > > Partition1 Primary FAT32 Win98 > > Partition2 Primary Solaris > > Partition3 Primary Linux - Fedora1 > > Partition4 Extended FAT32 > > Partition5 Extended Windows Server 2003 > > Partition6 Extended Linux Swap > > Free space Extended > > > > I can boot on each one of them but now I'd like to make my Linux to be > > bootable within coLinux running under W2 K. > > > > So far I can get the coLinux running using the Fedora distribution from > the > > download site. Perhaps it would be super if I know how to make my Linux > > installation on partition 3 be bootable from coLinux. Anyone? > > > > Thanks > > > > > > "Jaroslaw Kowalski" <ja...@zd...> wrote in message > > news:002701c461f6$e8af53f0$0221a8c0@jarekxp... > > > Dual booting is possible today using the LABEL feature that most distros > > > supports (fedora being one of them): > > > > > > It works like this: > > > > > > 1. Mount has a special syntax that lets you specify device labels > instead > > of > > > real device names. Labels are parts of filesystems (ext2,ext3, probably > > > others too). > > > > > > Assuming your /dev/hda1 has a label "XXX" you can mount it using either > > > > > > mount /dev/hda1 mountpoint > > > mount LABEL=XXX mountpoint > > > > > > 2. Same syntax can be used in /etc/fstab: > > > > > > ----------------------- > > > LABEL=XXX / ext2 defaults 0 0 > > > ----------------------- > > > can be used instead of: > > > ----------------------- > > > /dev/hda1 / ext2 defaults 0 0 > > > ----------------------- > > > > > > 3. With the introduction of 2.6 kernel colinux supports > "/proc/partitions" > > > which is required for LABELs to work. Previous version had a problem > where > > > /proc/partitions didn't contain cobdX devices so "mount" didn't know > what > > to > > > scan for labels. > > > > > > 4. In theory it should be possible to even pass root=LABEL=XXX to kernel > > at > > > boot time (this requires initrd), but I was never able to do it. > > > > > > 5. Labels can be assigned using "e2label" utility. For other FSs there > > > should be appropriate utilities. > > > > > > So assuming you assign all your devices the appropriate labels (this > isn't > > > possible for SWAP partitions, afaik) and modify the appropriate > /etc/fstab > > > entries, you should have a clean dual-bootable linux distro. > > > > > > I use it daily, and have no problems with this setup. > > > > > > Jarek > > > ----- Original Message ----- > > > From: "Dan Aloni" <da...@co...> > > > To: "Sarah Tanembaum" <sar...@ya...> > > > Cc: <col...@li...> > > > Sent: Saturday, July 03, 2004 3:48 PM > > > Subject: Re: [coLinux-devel] wish list > > > > > > > > > > On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: > > > > > Perhaps you coLinux guru can help me out for the following: > > > > > > > > > > Suppose that I have dual boot machine, Windows(partition1) and > > > > > Linux(partition2). I know that I can convert the Linux installation > to > > > work > > > > > with coLinux within Windows, but with many things to alter such as > the > > > fstab > > > > > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or > /dev/cobd/? > > > and > > > > > disable loading modules of some devices such as USB, etc ...(dunno > how > > > yet). > > > > > > > > You don't actually need to disable module loading, but rather put the > > > right > > > > modules for the running coLinux kernel under the /lib/modules > directory. > > > > > > > > > My question is that is it possible that coLinux do the automatic > > > > > reconfiguration for such environment e,g: > > > > > > > > The next snapshot version of coLinux will include device node > aliasing, > > > > which means that you can configure any cobd to appear as a hd or sda > > > > partition, and even boot from it (e.g. root=/dev/hda4). Theoretically > it > > > > would be possible to probe the Linux partitions in the Windows side > and > > > > create a proper configuration file. This way you don't need to change > > > > /ect/fstab. > > > > > > > > -- > > > > Dan Aloni > > > > da...@co... > > > > > > > > > > > > ------------------------------------------------------- > > > > 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-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > > > > > > > > > > ------------------------------------------------------- > > 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-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > ------------------------------------------------------- > 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 |
From: Jaroslaw K. <ja...@zd...> - 2004-07-06 15:31:10
|
1. Use "vmlinux" that comes with colinux. Alternatively you may want to recompile it using colinux patch but this is an advanced option. 2. You can safely remove <initrd> tag - it is not necessary to run Fedora under colinux. 3. After you have colinux up and running, use scp, smbclient, ftp, wget or other networking tool to fetch vmlinux-modules.tar.gz that comes with colinux. Unpack it to your root directory and reboot colinux - this lets you run iptables firewall and provides some more filesystems. This step is not necessary, but iptables won't be functional and you'll get a lot of warnings about unresolved module dependencies - they are safe to ignore. Jarek ----- Original Message ----- From: "Sarah Tanembaum" <sar...@ya...> To: <col...@li...> Sent: Tuesday, July 06, 2004 4:42 PM Subject: [coLinux-devel] Re: Re: wish list > Thanks. I will give it a try. > > By the way, under your config, > > <image path="vmlinux"> -- is this native vmlinux or what's comes with > distribution? if not, how do it build it > from scratch? > > <initrd path="initrd-2.6.7-co-0.6.2.img> -- how do I build this kernel image > to run under coLinux? How about > the /lib/modules under native installation, will coLinux detect it or do I > have to repackage it to be able to run under coLinux. > > Thanks again --- > > "Jaroslaw Kowalski" <ja...@zd...> wrote in message > news:000e01c46325$40720310$0221a8c0@jarekxp... > > > > This is my config - I use it to dual boot my Fedora Core 2: > > > > ====================================== > > <?xml version="1.0" encoding="UTF-8"?> > > <colinux> > > <block_device index="0" path="\Device\HardDisk0\Partition5" > > enabled="true" /> > > <block_device index="1" path="\Device\HardDisk0\Partition4" > > enabled="true" /> > > <image path="vmlinux" /> > > <initrd path="initrd-2.6.7-co-0.6.2.img" /> > > <bootparams>ro nousb root=/dev/cobd0</bootparams> > > <memory size="160" /> > > <network index="0" type="tap" name="CoLinux TAP" /> > > </colinux> > > ====================================== > > > > The following things have to be done under Fedora: > > > > 1. Create devices > > > > # mknod /dev/cobd0 b 117 0 > > # mknod /dev/cobd1 b 117 1 > > # mknod /dev/cobd2 b 117 2 > > # mknod /dev/cobd3 b 117 3 > > > > ... (repeat as needed up to cobd31) > > > > 2. Make sure the default runlevel is set to "3" to prevent X from booting. > > You can change it in "/etc/inittab" by modifying the first uncommented > line > > to read: > > > > id:3:initdefault: > > > > 3. To allow single /etc/fstab you need to assign labels to your block > > devices: > > > > For each partition that you have mounted run: > > > > # e2fslabel /dev/hdaX MYPARTITIONX > > > > and modify your /etc/fstab by replacing each occurence of "/dev/hdaX" with > > "LABEL=MYPARTITIONX" > > > > As for the swap partitions: you cannot assign labels to them, but you can > > put more than one swap in /etc/fstab. Fedora will just ignore the ones > that > > aren't present. > > In my case I have: > > > > ==== > > /dev/hda5 swap swap defaults 0 > 0 > > /dev/cobd1 swap swap defaults 0 > 0 > > ====== > > > > When running under colinux - /dev/hda5 is not found, when running native - > > /dev/cobd1 is not found, but they point to the same physical partition. > > > > That's it. You can try running "ntsysv" and disabling unnecessary services > > which don't make sense under colinux. > > > > Hope it helps. > > > > Jarek > > > > ----- Original Message ----- > > From: "Sarah Tanembaum" <sar...@ya...> > > To: <col...@li...> > > Cc: <col...@li...> > > Sent: Tuesday, July 06, 2004 8:07 AM > > Subject: [coLinux-devel] Re: wish list > > > > > > > Thanks Jaroslaw. Forgive my little knowledge about coLinux. > > > > > > Perhaps you can elaborate the explanation below. > > > Is it to be done on the distribution(e.g Fedora 2) outside the coLinux > or > > it > > > it within coLinux virtual machine? > > > > > > I have the following on my disk: > > > > > > Partition1 Primary FAT32 Win98 > > > Partition2 Primary Solaris > > > Partition3 Primary Linux - Fedora1 > > > Partition4 Extended FAT32 > > > Partition5 Extended Windows Server 2003 > > > Partition6 Extended Linux Swap > > > Free space Extended > > > > > > I can boot on each one of them but now I'd like to make my Linux to be > > > bootable within coLinux running under W2 K. > > > > > > So far I can get the coLinux running using the Fedora distribution from > > the > > > download site. Perhaps it would be super if I know how to make my Linux > > > installation on partition 3 be bootable from coLinux. Anyone? > > > > > > Thanks > > > > > > > > > "Jaroslaw Kowalski" <ja...@zd...> wrote in message > > > news:002701c461f6$e8af53f0$0221a8c0@jarekxp... > > > > Dual booting is possible today using the LABEL feature that most > distros > > > > supports (fedora being one of them): > > > > > > > > It works like this: > > > > > > > > 1. Mount has a special syntax that lets you specify device labels > > instead > > > of > > > > real device names. Labels are parts of filesystems (ext2,ext3, > probably > > > > others too). > > > > > > > > Assuming your /dev/hda1 has a label "XXX" you can mount it using > either > > > > > > > > mount /dev/hda1 mountpoint > > > > mount LABEL=XXX mountpoint > > > > > > > > 2. Same syntax can be used in /etc/fstab: > > > > > > > > ----------------------- > > > > LABEL=XXX / ext2 defaults 0 0 > > > > ----------------------- > > > > can be used instead of: > > > > ----------------------- > > > > /dev/hda1 / ext2 defaults 0 0 > > > > ----------------------- > > > > > > > > 3. With the introduction of 2.6 kernel colinux supports > > "/proc/partitions" > > > > which is required for LABELs to work. Previous version had a problem > > where > > > > /proc/partitions didn't contain cobdX devices so "mount" didn't know > > what > > > to > > > > scan for labels. > > > > > > > > 4. In theory it should be possible to even pass root=LABEL=XXX to > kernel > > > at > > > > boot time (this requires initrd), but I was never able to do it. > > > > > > > > 5. Labels can be assigned using "e2label" utility. For other FSs there > > > > should be appropriate utilities. > > > > > > > > So assuming you assign all your devices the appropriate labels (this > > isn't > > > > possible for SWAP partitions, afaik) and modify the appropriate > > /etc/fstab > > > > entries, you should have a clean dual-bootable linux distro. > > > > > > > > I use it daily, and have no problems with this setup. > > > > > > > > Jarek > > > > ----- Original Message ----- > > > > From: "Dan Aloni" <da...@co...> > > > > To: "Sarah Tanembaum" <sar...@ya...> > > > > Cc: <col...@li...> > > > > Sent: Saturday, July 03, 2004 3:48 PM > > > > Subject: Re: [coLinux-devel] wish list > > > > > > > > > > > > > On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: > > > > > > Perhaps you coLinux guru can help me out for the following: > > > > > > > > > > > > Suppose that I have dual boot machine, Windows(partition1) and > > > > > > Linux(partition2). I know that I can convert the Linux > installation > > to > > > > work > > > > > > with coLinux within Windows, but with many things to alter such as > > the > > > > fstab > > > > > > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or > > /dev/cobd/? > > > > and > > > > > > disable loading modules of some devices such as USB, etc ...(dunno > > how > > > > yet). > > > > > > > > > > You don't actually need to disable module loading, but rather put > the > > > > right > > > > > modules for the running coLinux kernel under the /lib/modules > > directory. > > > > > > > > > > > My question is that is it possible that coLinux do the automatic > > > > > > reconfiguration for such environment e,g: > > > > > > > > > > The next snapshot version of coLinux will include device node > > aliasing, > > > > > which means that you can configure any cobd to appear as a hd or sda > > > > > partition, and even boot from it (e.g. root=/dev/hda4). > Theoretically > > it > > > > > would be possible to probe the Linux partitions in the Windows side > > and > > > > > create a proper configuration file. This way you don't need to > change > > > > > /ect/fstab. > > > > > > > > > > -- > > > > > Dan Aloni > > > > > da...@co... > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > 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-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > 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 > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > ------------------------------------------------------- > > 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 > > > > > > ------------------------------------------------------- > 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Dan A. <da...@co...> - 2004-07-10 17:53:03
|
On Tue, Jul 06, 2004 at 08:48:31AM +0200, Jaroslaw Kowalski wrote: > This is my config - I use it to dual boot my Fedora Core 2: > > ====================================== > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > <block_device index="0" path="\Device\HardDisk0\Partition5" > enabled="true" /> > <block_device index="1" path="\Device\HardDisk0\Partition4" > enabled="true" /> > <image path="vmlinux" /> > <initrd path="initrd-2.6.7-co-0.6.2.img" /> > <bootparams>ro nousb root=/dev/cobd0</bootparams> > <memory size="160" /> > <network index="0" type="tap" name="CoLinux TAP" /> > </colinux> > ====================================== > > The following things have to be done under Fedora: > > 1. Create devices > > # mknod /dev/cobd0 b 117 0 > # mknod /dev/cobd1 b 117 1 > # mknod /dev/cobd2 b 117 2 > # mknod /dev/cobd3 b 117 3 > > ... (repeat as needed up to cobd31) Hey, I would like for more people to try the feature that I added in the latest snapshot (20040710). It should let you do something like: <block_device index="0" path="\Device\HardDisk0\Partition5" enabled="true" alias="hda1" /> And then go freely with /dev/hda1 without even creating the cobd nodes. -- Dan Aloni da...@co... |
From: Tomas F. <to...@eu...> - 2004-08-24 08:28:20
|
Dan Aloni wrote: > > Hey, I would like for more people to try the feature that I added > in the latest snapshot (20040710). > > It should let you do something like: > > <block_device index="0" path="\Device\HardDisk0\Partition5" > enabled="true" alias="hda1" /> > > And then go freely with /dev/hda1 without even creating the cobd > nodes. Nice work, Dan! Thank you for this very useful little trick. // Tomas |
From: peter g. <plu...@p1...> - 2004-08-24 16:25:19
|
if i alias a cobd to hda (rather than hda1) will i be able to partition it and use the partitions on it? > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On Behalf Of Tomas > Fasth > Sent: 24 August 2004 09:28 > To: Dan Aloni > Cc: Jaroslaw Kowalski; Sarah Tanembaum; Cooperative Linux Development > Subject: Re: [coLinux-devel] Re: wish list > > > Dan Aloni wrote: > > > > Hey, I would like for more people to try the feature that I added > > in the latest snapshot (20040710). > > > > It should let you do something like: > > > > <block_device index="0" path="\Device\HardDisk0\Partition5" > > enabled="true" alias="hda1" /> > > > > And then go freely with /dev/hda1 without even creating the cobd > > nodes. > > Nice work, Dan! Thank you for this very useful little trick. > > // Tomas > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.737 / Virus Database: 491 - Release Date: 11/08/2004 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.737 / Virus Database: 491 - Release Date: 11/08/2004 |
From: Dan A. <da...@co...> - 2004-08-24 17:34:57
|
On Tue, Aug 24, 2004 at 05:25:05PM +0100, peter green wrote: > if i alias a cobd to hda (rather than hda1) will i be able to partition it > and use the partitions on it? Yes and no. You can alias an image to hda, but without any paritioning support. I don't think that it is safe to let the guest have read/write access to the partition table. Some host operating systems assume that the partition table of hard drives doesn't change in run-time without their awareness. I'm not sure how Windows will behave in that case. -- Dan Aloni da...@co... |
From: Jaroslaw K. <ja...@zd...> - 2004-08-24 18:42:30
|
How about a virtual partition table support ? This would look and behave exactly as /dev/hda + /dev/hdaX behaves now (/dev/hda looks like "partition table" + /dev/hda1 + ... + /dev/hdaN concatenated, perhaps interleaved with some junk and/or extra partition tables). The partition table would have to be built in memory to reflect the actual sizes of /dev/hdaX devices. The partition table would be read-only, any writes would be discarded. Any reads or writes to particular regions of /dev/hda would be redirected to /dev/hdaX (which is an alias for /dev/cobdX which can be either a file or a partition, ....) Maybe this would allow us to run "smart" distro installers like anaconda from RedHat which insist on doing the partitioning using the "smart" tools. Jarek ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "peter green" <plu...@p1...> Cc: "Tomas Fasth" <to...@eu...>; "Jaroslaw Kowalski" <ja...@zd...>; "Sarah Tanembaum" <sar...@ya...>; "Cooperative Linux Development" <col...@li...> Sent: Tuesday, August 24, 2004 7:35 PM Subject: Re: [coLinux-devel] Re: wish list > On Tue, Aug 24, 2004 at 05:25:05PM +0100, peter green wrote: > > if i alias a cobd to hda (rather than hda1) will i be able to partition it > > and use the partitions on it? > > Yes and no. > > You can alias an image to hda, but without any paritioning support. I don't > think that it is safe to let the guest have read/write access to the partition > table. Some host operating systems assume that the partition table of hard > drives doesn't change in run-time without their awareness. I'm not sure how > Windows will behave in that case. > > -- > Dan Aloni > da...@co... > |
From: Digital I. Inc. <ok...@di...> - 2004-07-07 13:56:54
|
Hello. I have not checked the whole thread, nor even previous posting, so maybe same issue has been posted so far, but I think it is good that if we can share same diskimage between many VM technologies, VMware, Xen, qemu, boches, Virtual PC, etc. (UML image is same as coLinux one, unless you use CoW.) I mean, for example you can use VMWare's disk image to coLinux, or vice versa. you have two ways to do it. adding drivers to colinux is one way. the drivers can mount other diskimages. other way is making conversion utils. this is easier to implement, but a little bit waste of your HDD. in this way, you would end up with storing two same diskimages with different format. --- Okajima. >Dual booting is possible today using the LABEL feature that most distros >supports (fedora being one of them): > >It works like this: > >1. Mount has a special syntax that lets you specify device labels instead of >real device names. Labels are parts of filesystems (ext2,ext3, probably >others too). > >Assuming your /dev/hda1 has a label "XXX" you can mount it using either > >mount /dev/hda1 mountpoint >mount LABEL=XXX mountpoint > >2. Same syntax can be used in /etc/fstab: > >----------------------- >LABEL=XXX / ext2 defaults 0 0 >----------------------- >can be used instead of: >----------------------- >/dev/hda1 / ext2 defaults 0 0 >----------------------- > >3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" >which is required for LABELs to work. Previous version had a problem where >/proc/partitions didn't contain cobdX devices so "mount" didn't know what to >scan for labels. > >4. In theory it should be possible to even pass root=LABEL=XXX to kernel at >boot time (this requires initrd), but I was never able to do it. > >5. Labels can be assigned using "e2label" utility. For other FSs there >should be appropriate utilities. > >So assuming you assign all your devices the appropriate labels (this isn't >possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab >entries, you should have a clean dual-bootable linux distro. > >I use it daily, and have no problems with this setup. > >Jarek >----- Original Message ----- >From: "Dan Aloni" <da...@co...> >To: "Sarah Tanembaum" <sar...@ya...> >Cc: <col...@li...> >Sent: Saturday, July 03, 2004 3:48 PM >Subject: Re: [coLinux-devel] wish list > > >> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >> > Perhaps you coLinux guru can help me out for the following: >> > >> > Suppose that I have dual boot machine, Windows(partition1) and >> > Linux(partition2). I know that I can convert the Linux installation to >work >> > with coLinux within Windows, but with many things to alter such as the >fstab >> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? >and >> > disable loading modules of some devices such as USB, etc ...(dunno how >yet). >> >> You don't actually need to disable module loading, but rather put the >right >> modules for the running coLinux kernel under the /lib/modules directory. >> >> > My question is that is it possible that coLinux do the automatic >> > reconfiguration for such environment e,g: >> >> The next snapshot version of coLinux will include device node aliasing, >> which means that you can configure any cobd to appear as a hd or sda >> partition, and even boot from it (e.g. root=/dev/hda4). Theoretically it >> would be possible to probe the Linux partitions in the Windows side and >> create a proper configuration file. This way you don't need to change >> /ect/fstab. >> >> -- >> Dan Aloni >> da...@co... >> >> >> ------------------------------------------------------- >> 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-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > >------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Dan S. <da...@ho...> - 2004-07-07 18:23:01
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, the bochs guys did it a while ago so the source code for VMWare parsing should be easy to snatch from there.. Specifically I'm referring to the bochs/iodev/vmware3.{cpp,h} which are the relevant pieces there. I'd be happy to get my feet wet with coLinux doing something like that However, if only someone could point me to the source (hint, hint read my last post! :) ) Anyway, I'll start with compiling the latest snapshot which Dan Aloni posted a link to. Shechter. - -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Digital Infra, Inc. Sent: Wednesday, July 07, 2004 15:18 To: Jaroslaw Kowalski Cc: Sarah Tanembaum; col...@li... Subject: Re: [coLinux-devel] Diskimage sharing. Hello. I have not checked the whole thread, nor even previous posting, so maybe same issue has been posted so far, but I think it is good that if we can share same diskimage between many VM technologies, VMware, Xen, qemu, boches, Virtual PC, etc. (UML image is same as coLinux one, unless you use CoW.) I mean, for example you can use VMWare's disk image to coLinux, or vice versa. you have two ways to do it. adding drivers to colinux is one way. the drivers can mount other diskimages. other way is making conversion utils. this is easier to implement, but a little bit waste of your HDD. in this way, you would end up with storing two same diskimages with different format. --- Okajima. >Dual booting is possible today using the LABEL feature that most >distros supports (fedora being one of them): > >It works like this: > >1. Mount has a special syntax that lets you specify device labels instead of >real device names. Labels are parts of filesystems (ext2,ext3, >probably others too). > >Assuming your /dev/hda1 has a label "XXX" you can mount it using >either > >mount /dev/hda1 mountpoint >mount LABEL=XXX mountpoint > >2. Same syntax can be used in /etc/fstab: > >----------------------- >LABEL=XXX / ext2 defaults 0 0 >----------------------- >can be used instead of: >----------------------- >/dev/hda1 / ext2 defaults 0 0 >----------------------- > >3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" >which is required for LABELs to work. Previous version had a problem where >/proc/partitions didn't contain cobdX devices so "mount" didn't know what to >scan for labels. > >4. In theory it should be possible to even pass root=LABEL=XXX to >kernel at >boot time (this requires initrd), but I was never able to do it. > >5. Labels can be assigned using "e2label" utility. For other FSs >there should be appropriate utilities. > >So assuming you assign all your devices the appropriate labels (this isn't >possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab >entries, you should have a clean dual-bootable linux distro. > >I use it daily, and have no problems with this setup. > >Jarek >----- Original Message ----- >From: "Dan Aloni" <da...@co...> >To: "Sarah Tanembaum" <sar...@ya...> >Cc: <col...@li...> >Sent: Saturday, July 03, 2004 3:48 PM >Subject: Re: [coLinux-devel] wish list > > >> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >> > Perhaps you coLinux guru can help me out for the following: >> > >> > Suppose that I have dual boot machine, Windows(partition1) and >> > Linux(partition2). I know that I can convert the Linux >> > installation to >work >> > with coLinux within Windows, but with many things to alter such >> > as the >fstab >> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? >and >> > disable loading modules of some devices such as USB, etc >> > ...(dunno how >yet). >> >> You don't actually need to disable module loading, but rather put >> the >right >> modules for the running coLinux kernel under the /lib/modules directory. >> >> > My question is that is it possible that coLinux do the automatic >> > reconfiguration for such environment e,g: >> >> The next snapshot version of coLinux will include device node aliasing, >> which means that you can configure any cobd to appear as a hd or >> sda partition, and even boot from it (e.g. root=/dev/hda4). >> Theoretically it >> would be possible to probe the Linux partitions in the Windows >> side and >> create a proper configuration file. This way you don't need to >> change /ect/fstab. >> >> -- >> Dan Aloni >> da...@co... >> >> >> ------------------------------------------------------- >> 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-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > >------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > - ------------------------------------------------------- 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-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQOw/YJOAWHT6jAf5EQKh3QCg7pNWv4D7QkdHM6Rm3YkY26vsVaEAn2IW ARwgfE8+7I8SmeOtNfllBNDl =LLa1 -----END PGP SIGNATURE----- |
From: Digital I. Inc. <ok...@di...> - 2004-07-07 23:32:44
|
Hello Schechter. you may also find here interesting. http://chitchat.at.infoseek.co.jp/vmware/index.html http://gb.bbs.ws/book.php?book=chitchat he made a driver to mount VMWare image to Windows. it is ( in Linux term) a block driver, so it is necessary that an image must be formatted with NTFS/FAT32 or such, except you would write a ext2 FS driver for NT. --- Okajima. > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Well, the bochs guys did it a while ago so the source code for >VMWare parsing should be easy to snatch from there.. > >Specifically I'm referring to the bochs/iodev/vmware3.{cpp,h} which >are the relevant pieces there. > >I'd be happy to get my feet wet with coLinux doing something like >that >However, if only someone could point me to the source (hint, hint >read my last post! :) ) > >Anyway, I'll start with compiling the latest snapshot which Dan Aloni >posted a link to. > > Shechter. > > >- -----Original Message----- >From: col...@li... >[mailto:col...@li...] On Behalf Of >Digital Infra, Inc. >Sent: Wednesday, July 07, 2004 15:18 >To: Jaroslaw Kowalski >Cc: Sarah Tanembaum; col...@li... >Subject: Re: [coLinux-devel] Diskimage sharing. > > >Hello. > >I have not checked the whole thread, nor even previous posting, so >maybe same issue has been posted so far, but I think it is good that >if we can share same diskimage between many VM technologies, VMware, >Xen, qemu, boches, Virtual PC, etc. (UML image is same as coLinux >one, unless you use CoW.) I mean, for example you can use VMWare's >disk image to coLinux, or vice versa. >you have two ways to do it. adding drivers to colinux is one way. the >drivers can mount other diskimages. other way is making conversion >utils. >this is easier to implement, but a little bit waste of your HDD. in >this way, you would end up with storing two same diskimages with >different format. > > --- Okajima. > >>Dual booting is possible today using the LABEL feature that most >>distros supports (fedora being one of them): >> >>It works like this: >> >>1. Mount has a special syntax that lets you specify device labels >instead of >>real device names. Labels are parts of filesystems (ext2,ext3, >>probably others too). >> >>Assuming your /dev/hda1 has a label "XXX" you can mount it using >>either >> >>mount /dev/hda1 mountpoint >>mount LABEL=XXX mountpoint >> >>2. Same syntax can be used in /etc/fstab: >> >>----------------------- >>LABEL=XXX / ext2 defaults 0 0 >>----------------------- >>can be used instead of: >>----------------------- >>/dev/hda1 / ext2 defaults 0 0 >>----------------------- >> >>3. With the introduction of 2.6 kernel colinux supports >"/proc/partitions" >>which is required for LABELs to work. Previous version had a problem >where >>/proc/partitions didn't contain cobdX devices so "mount" didn't know >what to >>scan for labels. >> >>4. In theory it should be possible to even pass root=LABEL=XXX to >>kernel >at >>boot time (this requires initrd), but I was never able to do it. >> >>5. Labels can be assigned using "e2label" utility. For other FSs >>there should be appropriate utilities. >> >>So assuming you assign all your devices the appropriate labels (this >isn't >>possible for SWAP partitions, afaik) and modify the appropriate >/etc/fstab >>entries, you should have a clean dual-bootable linux distro. >> >>I use it daily, and have no problems with this setup. >> >>Jarek >>----- Original Message ----- >>From: "Dan Aloni" <da...@co...> >>To: "Sarah Tanembaum" <sar...@ya...> >>Cc: <col...@li...> >>Sent: Saturday, July 03, 2004 3:48 PM >>Subject: Re: [coLinux-devel] wish list >> >> >>> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >>> > Perhaps you coLinux guru can help me out for the following: >>> > >>> > Suppose that I have dual boot machine, Windows(partition1) and >>> > Linux(partition2). I know that I can convert the Linux >>> > installation >to >>work >>> > with coLinux within Windows, but with many things to alter such >>> > as >the >>fstab >>> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or >/dev/cobd/? >>and >>> > disable loading modules of some devices such as USB, etc >>> > ...(dunno >how >>yet). >>> >>> You don't actually need to disable module loading, but rather put >>> the >>right >>> modules for the running coLinux kernel under the /lib/modules >directory. >>> >>> > My question is that is it possible that coLinux do the automatic >>> > reconfiguration for such environment e,g: >>> >>> The next snapshot version of coLinux will include device node >aliasing, >>> which means that you can configure any cobd to appear as a hd or >>> sda partition, and even boot from it (e.g. root=/dev/hda4). >>> Theoretically >it >>> would be possible to probe the Linux partitions in the Windows >>> side >and >>> create a proper configuration file. This way you don't need to >>> change /ect/fstab. >>> >>> -- >>> Dan Aloni >>> da...@co... >>> >>> >>> ------------------------------------------------------- >>> 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-devel mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-devel >>> >> >> >> >>------------------------------------------------------- >>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-devel mailing list >>coL...@li... >>https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > >- ------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > >-----BEGIN PGP SIGNATURE----- >Version: PGP 8.0.3 > >iQA/AwUBQOw/YJOAWHT6jAf5EQKh3QCg7pNWv4D7QkdHM6Rm3YkY26vsVaEAn2IW >ARwgfE8+7I8SmeOtNfllBNDl >=LLa1 >-----END PGP SIGNATURE----- > > > > >------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Dan S. <da...@ho...> - 2004-07-07 18:32:09
|
*** PGP SIGNATURE VERIFICATION *** *** Status: Good Signature *** Signer: Dan Shechter <da...@ho...> (0xFA8C07F9) *** Signed: 7/7/2004 6:36:41 PM *** Verified: 7/7/2004 8:29:13 PM *** BEGIN PGP VERIFIED MESSAGE *** -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, the bochs guys did it a while ago so the source code for VMWare parsing should be easy to snatch from there.. Specifically I'm referring to the bochs/iodev/vmware3.{cpp,h} which are the relevant pieces there. I'd be happy to get my feet wet with coLinux doing something like that However, if only someone could point me to the source (hint, hint read my last post! :) ) Anyway, I'll start with compiling the latest snapshot which Dan Aloni posted a link to. Shechter. - -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Digital Infra, Inc. Sent: Wednesday, July 07, 2004 15:18 To: Jaroslaw Kowalski Cc: Sarah Tanembaum; col...@li... Subject: Re: [coLinux-devel] Diskimage sharing. Hello. I have not checked the whole thread, nor even previous posting, so maybe same issue has been posted so far, but I think it is good that if we can share same diskimage between many VM technologies, VMware, Xen, qemu, boches, Virtual PC, etc. (UML image is same as coLinux one, unless you use CoW.) I mean, for example you can use VMWare's disk image to coLinux, or vice versa. you have two ways to do it. adding drivers to colinux is one way. the drivers can mount other diskimages. other way is making conversion utils. this is easier to implement, but a little bit waste of your HDD. in this way, you would end up with storing two same diskimages with different format. --- Okajima. >Dual booting is possible today using the LABEL feature that most >distros supports (fedora being one of them): > >It works like this: > >1. Mount has a special syntax that lets you specify device labels instead of >real device names. Labels are parts of filesystems (ext2,ext3, >probably others too). > >Assuming your /dev/hda1 has a label "XXX" you can mount it using >either > >mount /dev/hda1 mountpoint >mount LABEL=XXX mountpoint > >2. Same syntax can be used in /etc/fstab: > >----------------------- >LABEL=XXX / ext2 defaults 0 0 >----------------------- >can be used instead of: >----------------------- >/dev/hda1 / ext2 defaults 0 0 >----------------------- > >3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" >which is required for LABELs to work. Previous version had a problem where >/proc/partitions didn't contain cobdX devices so "mount" didn't know what to >scan for labels. > >4. In theory it should be possible to even pass root=LABEL=XXX to >kernel at >boot time (this requires initrd), but I was never able to do it. > >5. Labels can be assigned using "e2label" utility. For other FSs >there should be appropriate utilities. > >So assuming you assign all your devices the appropriate labels (this isn't >possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab >entries, you should have a clean dual-bootable linux distro. > >I use it daily, and have no problems with this setup. > >Jarek >----- Original Message ----- >From: "Dan Aloni" <da...@co...> >To: "Sarah Tanembaum" <sar...@ya...> >Cc: <col...@li...> >Sent: Saturday, July 03, 2004 3:48 PM >Subject: Re: [coLinux-devel] wish list > > >> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >> > Perhaps you coLinux guru can help me out for the following: >> > >> > Suppose that I have dual boot machine, Windows(partition1) and >> > Linux(partition2). I know that I can convert the Linux >> > installation to >work >> > with coLinux within Windows, but with many things to alter such >> > as the >fstab >> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? >and >> > disable loading modules of some devices such as USB, etc >> > ...(dunno how >yet). >> >> You don't actually need to disable module loading, but rather put >> the >right >> modules for the running coLinux kernel under the /lib/modules directory. >> >> > My question is that is it possible that coLinux do the automatic >> > reconfiguration for such environment e,g: >> >> The next snapshot version of coLinux will include device node aliasing, >> which means that you can configure any cobd to appear as a hd or >> sda partition, and even boot from it (e.g. root=/dev/hda4). >> Theoretically it >> would be possible to probe the Linux partitions in the Windows >> side and >> create a proper configuration file. This way you don't need to >> change /ect/fstab. >> >> -- >> Dan Aloni >> da...@co... >> >> >> ------------------------------------------------------- >> 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-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > >------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > - ------------------------------------------------------- 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-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQOwiZZOAWHT6jAf5EQLYhACgn4umdUIagl2W7YKVwP1At/noj9kAn0gA nCajeGyR+K0AeyvigcZkJonn =ie6L -----END PGP SIGNATURE----- *** END PGP VERIFIED MESSAGE *** |
From: peter g. <plu...@p1...> - 2004-07-07 18:51:56
|
one other possible issue with using vmware virtual disks is partitioning a vmware virtual disk will almost certainly have partitions on it afaict cobd devices do not support partitioning got any comments on this da-x -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Dan Shechter Sent: 07 July 2004 19:31 To: col...@li... Subject: RE: [coLinux-devel] Diskimage sharing. *** PGP SIGNATURE VERIFICATION *** *** Status: Good Signature *** Signer: Dan Shechter <da...@ho...> (0xFA8C07F9) *** Signed: 7/7/2004 6:36:41 PM *** Verified: 7/7/2004 8:29:13 PM *** BEGIN PGP VERIFIED MESSAGE *** -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, the bochs guys did it a while ago so the source code for VMWare parsing should be easy to snatch from there.. Specifically I'm referring to the bochs/iodev/vmware3.{cpp,h} which are the relevant pieces there. I'd be happy to get my feet wet with coLinux doing something like that However, if only someone could point me to the source (hint, hint read my last post! :) ) Anyway, I'll start with compiling the latest snapshot which Dan Aloni posted a link to. Shechter. - -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Digital Infra, Inc. Sent: Wednesday, July 07, 2004 15:18 To: Jaroslaw Kowalski Cc: Sarah Tanembaum; col...@li... Subject: Re: [coLinux-devel] Diskimage sharing. Hello. I have not checked the whole thread, nor even previous posting, so maybe same issue has been posted so far, but I think it is good that if we can share same diskimage between many VM technologies, VMware, Xen, qemu, boches, Virtual PC, etc. (UML image is same as coLinux one, unless you use CoW.) I mean, for example you can use VMWare's disk image to coLinux, or vice versa. you have two ways to do it. adding drivers to colinux is one way. the drivers can mount other diskimages. other way is making conversion utils. this is easier to implement, but a little bit waste of your HDD. in this way, you would end up with storing two same diskimages with different format. --- Okajima. >Dual booting is possible today using the LABEL feature that most >distros supports (fedora being one of them): > >It works like this: > >1. Mount has a special syntax that lets you specify device labels instead of >real device names. Labels are parts of filesystems (ext2,ext3, >probably others too). > >Assuming your /dev/hda1 has a label "XXX" you can mount it using >either > >mount /dev/hda1 mountpoint >mount LABEL=XXX mountpoint > >2. Same syntax can be used in /etc/fstab: > >----------------------- >LABEL=XXX / ext2 defaults 0 0 >----------------------- >can be used instead of: >----------------------- >/dev/hda1 / ext2 defaults 0 0 >----------------------- > >3. With the introduction of 2.6 kernel colinux supports "/proc/partitions" >which is required for LABELs to work. Previous version had a problem where >/proc/partitions didn't contain cobdX devices so "mount" didn't know what to >scan for labels. > >4. In theory it should be possible to even pass root=LABEL=XXX to >kernel at >boot time (this requires initrd), but I was never able to do it. > >5. Labels can be assigned using "e2label" utility. For other FSs >there should be appropriate utilities. > >So assuming you assign all your devices the appropriate labels (this isn't >possible for SWAP partitions, afaik) and modify the appropriate /etc/fstab >entries, you should have a clean dual-bootable linux distro. > >I use it daily, and have no problems with this setup. > >Jarek >----- Original Message ----- >From: "Dan Aloni" <da...@co...> >To: "Sarah Tanembaum" <sar...@ya...> >Cc: <col...@li...> >Sent: Saturday, July 03, 2004 3:48 PM >Subject: Re: [coLinux-devel] wish list > > >> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >> > Perhaps you coLinux guru can help me out for the following: >> > >> > Suppose that I have dual boot machine, Windows(partition1) and >> > Linux(partition2). I know that I can convert the Linux >> > installation to >work >> > with coLinux within Windows, but with many things to alter such >> > as the >fstab >> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or /dev/cobd/? >and >> > disable loading modules of some devices such as USB, etc >> > ...(dunno how >yet). >> >> You don't actually need to disable module loading, but rather put >> the >right >> modules for the running coLinux kernel under the /lib/modules directory. >> >> > My question is that is it possible that coLinux do the automatic >> > reconfiguration for such environment e,g: >> >> The next snapshot version of coLinux will include device node aliasing, >> which means that you can configure any cobd to appear as a hd or >> sda partition, and even boot from it (e.g. root=/dev/hda4). >> Theoretically it >> would be possible to probe the Linux partitions in the Windows >> side and >> create a proper configuration file. This way you don't need to >> change /ect/fstab. >> >> -- >> Dan Aloni >> da...@co... >> >> >> ------------------------------------------------------- >> 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-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > >------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > - ------------------------------------------------------- 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-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQOwiZZOAWHT6jAf5EQLYhACgn4umdUIagl2W7YKVwP1At/noj9kAn0gA nCajeGyR+K0AeyvigcZkJonn =ie6L -----END PGP SIGNATURE----- *** END PGP VERIFIED MESSAGE *** ------------------------------------------------------- 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-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 |
From: <ch...@to...> - 2004-07-08 11:01:30
|
Adding CoW abilities to coLinux may be usefull as well. expecially for coLinux on Linux because where CoW is most usefull is for = a server that serves many virtual servers and It probably makes more sense to use a properly tuned linux system for that. chris > > Hello. > > I have not checked the whole thread, nor even previous posting, so may= be > same issue has been posted so far, but I think it is good that if we ca= n > share same diskimage between many VM technologies, VMware, Xen, qemu, > boches, Virtual PC, etc. (UML image is same as coLinux one, unless you > use CoW.) I mean, for example you can use VMWare's disk image to coLinu= x, > or vice versa. > you have two ways to do it. adding drivers to colinux is one way. the > drivers can mount other diskimages. other way is making conversion util= s. > this is easier to implement, but a little bit waste of your HDD. in thi= s > way, you would end up with storing two same diskimages with different > format. > > --- Okajima. > >>Dual booting is possible today using the LABEL feature that most distro= s >>supports (fedora being one of them): >> >>It works like this: >> >>1. Mount has a special syntax that lets you specify device labels > instead of >>real device names. Labels are parts of filesystems (ext2,ext3, probably >>others too). >> >>Assuming your /dev/hda1 has a label "XXX" you can mount it using either >> >>mount /dev/hda1 mountpoint >>mount LABEL=3DXXX mountpoint >> >>2. Same syntax can be used in /etc/fstab: >> >>----------------------- >>LABEL=3DXXX / ext2 defaults 0 0 >>----------------------- >>can be used instead of: >>----------------------- >>/dev/hda1 / ext2 defaults 0 0 >>----------------------- >> >>3. With the introduction of 2.6 kernel colinux supports > "/proc/partitions" >>which is required for LABELs to work. Previous version had a problem > where >>/proc/partitions didn't contain cobdX devices so "mount" didn't know > what to >>scan for labels. >> >>4. In theory it should be possible to even pass root=3DLABEL=3DXXX to k= ernel > at >>boot time (this requires initrd), but I was never able to do it. >> >>5. Labels can be assigned using "e2label" utility. For other FSs there >>should be appropriate utilities. >> >>So assuming you assign all your devices the appropriate labels (this > isn't >>possible for SWAP partitions, afaik) and modify the appropriate > /etc/fstab >>entries, you should have a clean dual-bootable linux distro. >> >>I use it daily, and have no problems with this setup. >> >>Jarek >>----- Original Message ----- >>From: "Dan Aloni" <da...@co...> >>To: "Sarah Tanembaum" <sar...@ya...> >>Cc: <col...@li...> >>Sent: Saturday, July 03, 2004 3:48 PM >>Subject: Re: [coLinux-devel] wish list >> >> >>> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >>> > Perhaps you coLinux guru can help me out for the following: >>> > >>> > Suppose that I have dual boot machine, Windows(partition1) and >>> > Linux(partition2). I know that I can convert the Linux installation > to >>work >>> > with coLinux within Windows, but with many things to alter such as > the >>fstab >>> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or > /dev/cobd/? >>and >>> > disable loading modules of some devices such as USB, etc ...(dunno > how >>yet). >>> >>> You don't actually need to disable module loading, but rather put the >>right >>> modules for the running coLinux kernel under the /lib/modules > directory. >>> >>> > My question is that is it possible that coLinux do the automatic >>> > reconfiguration for such environment e,g: >>> >>> The next snapshot version of coLinux will include device node > aliasing, >>> which means that you can configure any cobd to appear as a hd or sda >>> partition, and even boot from it (e.g. root=3D/dev/hda4). Theoretical= ly > it >>> would be possible to probe the Linux partitions in the Windows side > and >>> create a proper configuration file. This way you don't need to change >>> /ect/fstab. >>> >>> -- >>> Dan Aloni >>> da...@co... >>> >>> >>> ------------------------------------------------------- >>> 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-devel mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-devel >>> >> >> >> >>------------------------------------------------------- >>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-devel mailing list >>coL...@li... >>https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > ------------------------------------------------------- > 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-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Digital I. Inc. <ok...@di...> - 2004-07-10 01:18:20
|
Yes, I agree with you and adding CoW isn on my to-do list. I plan to do it by making generic COW function for Linux. I mean, UML's COW is an good invention, but specialized for UML. my COW can be used in all Linuxes, I hope. --- Okajima. >Adding CoW abilities to coLinux may be usefull as well. >expecially for coLinux on Linux because where CoW is most usefull is for a >server that serves many virtual servers and It probably makes more sense >to use a properly tuned linux system for that. > >chris > >> >> Hello. >> >> I have not checked the whole thread, nor even previous posting, so maybe >> same issue has been posted so far, but I think it is good that if we can >> share same diskimage between many VM technologies, VMware, Xen, qemu, >> boches, Virtual PC, etc. (UML image is same as coLinux one, unless you >> use CoW.) I mean, for example you can use VMWare's disk image to coLinux, >> or vice versa. >> you have two ways to do it. adding drivers to colinux is one way. the >> drivers can mount other diskimages. other way is making conversion utils. >> this is easier to implement, but a little bit waste of your HDD. in this >> way, you would end up with storing two same diskimages with different >> format. >> >> --- Okajima. >> >>>Dual booting is possible today using the LABEL feature that most distros >>>supports (fedora being one of them): >>> >>>It works like this: >>> >>>1. Mount has a special syntax that lets you specify device labels >> instead of >>>real device names. Labels are parts of filesystems (ext2,ext3, probably >>>others too). >>> >>>Assuming your /dev/hda1 has a label "XXX" you can mount it using either >>> >>>mount /dev/hda1 mountpoint >>>mount LABEL=XXX mountpoint >>> >>>2. Same syntax can be used in /etc/fstab: >>> >>>----------------------- >>>LABEL=XXX / ext2 defaults 0 0 >>>----------------------- >>>can be used instead of: >>>----------------------- >>>/dev/hda1 / ext2 defaults 0 0 >>>----------------------- >>> >>>3. With the introduction of 2.6 kernel colinux supports >> "/proc/partitions" >>>which is required for LABELs to work. Previous version had a problem >> where >>>/proc/partitions didn't contain cobdX devices so "mount" didn't know >> what to >>>scan for labels. >>> >>>4. In theory it should be possible to even pass root=LABEL=XXX to kernel >> at >>>boot time (this requires initrd), but I was never able to do it. >>> >>>5. Labels can be assigned using "e2label" utility. For other FSs there >>>should be appropriate utilities. >>> >>>So assuming you assign all your devices the appropriate labels (this >> isn't >>>possible for SWAP partitions, afaik) and modify the appropriate >> /etc/fstab >>>entries, you should have a clean dual-bootable linux distro. >>> >>>I use it daily, and have no problems with this setup. >>> >>>Jarek >>>----- Original Message ----- >>>From: "Dan Aloni" <da...@co...> >>>To: "Sarah Tanembaum" <sar...@ya...> >>>Cc: <col...@li...> >>>Sent: Saturday, July 03, 2004 3:48 PM >>>Subject: Re: [coLinux-devel] wish list >>> >>> >>>> On Thu, Jul 01, 2004 at 01:49:01PM -0400, Sarah Tanembaum wrote: >>>> > Perhaps you coLinux guru can help me out for the following: >>>> > >>>> > Suppose that I have dual boot machine, Windows(partition1) and >>>> > Linux(partition2). I know that I can convert the Linux installation >> to >>>work >>>> > with coLinux within Windows, but with many things to alter such as >> the >>>fstab >>>> > entry(change the /dev/hd??,/dev/sd??,etc to /dev/cobd? or >> /dev/cobd/? >>>and >>>> > disable loading modules of some devices such as USB, etc ...(dunno >> how >>>yet). >>>> >>>> You don't actually need to disable module loading, but rather put the >>>right >>>> modules for the running coLinux kernel under the /lib/modules >> directory. >>>> >>>> > My question is that is it possible that coLinux do the automatic >>>> > reconfiguration for such environment e,g: >>>> >>>> The next snapshot version of coLinux will include device node >> aliasing, >>>> which means that you can configure any cobd to appear as a hd or sda >>>> partition, and even boot from it (e.g. root=/dev/hda4). Theoretically >> it >>>> would be possible to probe the Linux partitions in the Windows side >> and >>>> create a proper configuration file. This way you don't need to change >>>> /ect/fstab. >>>> >>>> -- >>>> Dan Aloni >>>> da...@co... >>>> >>>> >>>> ------------------------------------------------------- >>>> 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-devel mailing list >>>> coL...@li... >>>> https://lists.sourceforge.net/lists/listinfo/colinux-devel >>>> >>> >>> >>> >>>------------------------------------------------------- >>>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-devel mailing list >>>coL...@li... >>>https://lists.sourceforge.net/lists/listinfo/colinux-devel >>> >> >> >> ------------------------------------------------------- >> 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-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > >------------------------------------------------------- >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-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: <ch...@to...> - 2004-07-06 15:02:31
|
> The next snapshot version of coLinux will include device node aliasing, > which means that you can configure any cobd to appear as a hd or sda > partition, and even boot from it (e.g. root=3D/dev/hda4). Theoretically= it > would be possible to probe the Linux partitions in the Windows side and > create a proper configuration file. This way you don't need to change > /ect/fstab. > > -- > Dan Aloni > da...@co... > So the aliasing will also support the loop? nodes right? for dual loopback root and coLinux e.g. root=3D/dev/loop7 chris |