colinux-users — coLinux users mailing list

Re: [coLinux-users] getting rid of old ethernet devices

[<Use...@zo...>]

and...@gm...(Andrew Roth)  19.02.08 22:24

>>
>> I'm also a bit confused by the workaround of adding a new mac
>> address per device.  I thought you would want to force each new tap
>> device to use the same mac address, to trick linux into thinking
>> they're new devices?
>>

>I figured this out now.  I was quite confused.  I see now you want
>each device to have a unique, but consistent mac address, to make
>linux recognize them on each boot.  When you don't specify a mac
>address in the colinux conf, it assigns one at random, and udev then
>thinks they're new devices and assigns them a new eth#.

Pay attention to which MAC Addresse you choose!
There ist one reserved bit with must be "0"!

Once Suggestion for a MAC Start value was given:

0A:C0:11:__:__:__
0A:C0:71:__:__:__

AC071 = "A COLI"nux in "hex modified l33t"(tm)

See thread 
"No network anmore?"
"colinux-Bugs-1861876 20071203-Snapshot -- ifconfig reports no networking"

for more.

[coLinux-users] 44% de la gente de su edad no est&#225; n satisfechas con su salario. &#191; C&#243; mo cambiar eso?

[coliny <co...@ln...>]

yhuijj

Re: [coLinux-users] getting rid of old ethernet devices

[Andrew R. <and...@gm...>]

>
> I'm also a bit confused by the workaround of adding a new mac address per
> device.  I thought you would want to force each new tap device to use the
> same mac address, to trick linux into thinking they're new devices?
>

I figured this out now.  I was quite confused.  I see now you want each
device to have a unique, but consistent mac address, to make linux recognize
them on each boot.  When you don't specify a mac address in the colinux
conf, it assigns one at random, and udev then thinks they're new devices and
assigns them a new eth#.

-Andrew


> On Feb 19, 2008 8:09 PM, Henry Nestler <Hen...@ar...> wrote:
>
> > Andrew Roth wrote:
> > > I've been playing around with different colinux versions and installed
> > > new virtual devices, and it seems with each one, linux added a new
> > eth#
> > > device.  So now I'm at eth14.  Needless to say it's a bit annoying for
> > > my config files.  It seems to be storing these device numbers in the
> > > linux distribution somewhere, but I can't find where.  Does anyone
> > know
> > > how I can clear out the old devices and start at eth0 again?
> >
> > Follow http://www.colinux.org/snapshots/devel-RUNNING:
> >
> >  -- Some dev distries increase eth1, eth2, eth3, ... on every boot.
> >    Typicaly have no network, but can see it with "cat /proc/net/dev".
> >    As workarrount set an unique MAC address for all network interfaces
> >    in config file. Or disable udev.
> >    Debian: Remove all entries from
> > /etc/udev/rules.d/z25_persistent-net.rules
> >
> > --
> > Henry N.
> >
>
>

Re: [coLinux-users] getting rid of old ethernet devices

[Andrew R. <and...@gm...>]

Ah, thanks!

A few questions as I try to understand this.  Isn't the purpose of udev to
keep the devices the *same*?  It seems pretty bizarre to increase devices on
every boot -- that's a lot of new devices.  Ubuntu (which I'm using) doesn't
seem to add devices on boot, only on actually new tap devices (maybe this is
what you mean?).

I'm also a bit confused by the workaround of adding a new mac address per
device.  I thought you would want to force each new tap device to use the
same mac address, to trick linux into thinking they're new devices?

-Andrew

On Feb 19, 2008 8:09 PM, Henry Nestler <Hen...@ar...> wrote:

> Andrew Roth wrote:
> > I've been playing around with different colinux versions and installed
> > new virtual devices, and it seems with each one, linux added a new eth#
> > device.  So now I'm at eth14.  Needless to say it's a bit annoying for
> > my config files.  It seems to be storing these device numbers in the
> > linux distribution somewhere, but I can't find where.  Does anyone know
> > how I can clear out the old devices and start at eth0 again?
>
> Follow http://www.colinux.org/snapshots/devel-RUNNING:
>
>  -- Some dev distries increase eth1, eth2, eth3, ... on every boot.
>    Typicaly have no network, but can see it with "cat /proc/net/dev".
>    As workarrount set an unique MAC address for all network interfaces
>    in config file. Or disable udev.
>    Debian: Remove all entries from
> /etc/udev/rules.d/z25_persistent-net.rules
>
> --
> Henry N.
>

Re: [coLinux-users] 0.7.2 release = kernel 2.6.22 + local root exploit

[El T. <ca...@gm...>]

Hi Henry,

Big thanks for your prompt update, you are the best!

I will get the patch when I get home tonight.

Cheers,

cameos

2008/2/19, Henry Nestler <Hen...@ar...>:
> El Topo wrote:
> > I just installed 0.7.2 release, and found that it uses 2.6.22,
> > unfortunately it has the big issue of local root exploit.
> >
> > for more info, see
> > http://it.slashdot.org/article.pl?sid=08/02/10/2011257
>
> Yes. That is true big. But only for untrusted users and opened ssh
> shells. No problems for localy working users, and if You are the only
> one user on your coLinux. ;-)
>
> Thanks for your watching.
>
> > I urge that a new patch release as soon as possible.
>
> Here is a kernel replacement:
> http://www.henrynestler.com/colinux/releases/0.7.2/hotfix/
>
> file: vmlinux-2.6.22-co-0.7.2-20080219.zip
> You can simply replace the installed file "vmlinux" with that binary.
>
> A full coLinux update with installer will follow.
>
> --
> Henry N.
>

[coLinux-users] Windows 2000 not working. Tried everything

[Luco <luc...@gm...>]

Hi,

I actually posted this on the dev list, but this may be a better
location. Although it is a tough one ;)

I have installed andLinux and enabled connection sharing on the physical
 ethernet. The tap adaptor is currently on DHCP. Applications try but
fail to connect to 192.168.11.150:81. The ethernet is currently static
at 180.*

I've tried every possible combination of adjustments to my network
settings for both adaptors, and disabled the firewall altogether but
still no luck.

Of course this is on 2000. On XP everything works immediately and perfectly.

After the first installation attempt, I received the following message
on subsequent attempts:

"Unable to execute file:
sc

ShellExecuteEx failed; code 2
The system cannot find the file specified"

Running a linux ap, such as Thunar produces the error:

"could not launch 'Thunar': could not connect to 192.168.11.150:81"

I've read most of the list archives, wiki, and website, and there isn't
much more I can think of to do.

Interestingly (in the bad way), if I set the Tap adapter to DHCP,
disable it, diable ICS on the ethernet, enable the tap, enable ICS on
the ethernet, the tap will be set a static IP. Is this the cause of the
problem?

Thanks

Re: [coLinux-users] getting rid of old ethernet devices

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

Andrew Roth wrote:
> I've been playing around with different colinux versions and installed
> new virtual devices, and it seems with each one, linux added a new eth#
> device.  So now I'm at eth14.  Needless to say it's a bit annoying for
> my config files.  It seems to be storing these device numbers in the
> linux distribution somewhere, but I can't find where.  Does anyone know
> how I can clear out the old devices and start at eth0 again?

Follow http://www.colinux.org/snapshots/devel-RUNNING:

 -- Some dev distries increase eth1, eth2, eth3, ... on every boot.
    Typicaly have no network, but can see it with "cat /proc/net/dev".
    As workarrount set an unique MAC address for all network interfaces
    in config file. Or disable udev.
    Debian: Remove all entries from
/etc/udev/rules.d/z25_persistent-net.rules

-- 
Henry N.

[coLinux-users] getting rid of old ethernet devices

[Andrew R. <and...@gm...>]

Hi all,

I've been playing around with different colinux versions and installed new
virtual devices, and it seems with each one, linux added a new eth# device.
So now I'm at eth14.  Needless to say it's a bit annoying for my config
files.  It seems to be storing these device numbers in the linux
distribution somewhere, but I can't find where.  Does anyone know how I can
clear out the old devices and start at eth0 again?

thanks
-Andrew Roth

Re: [coLinux-users] 0.7.2 release = kernel 2.6.22 + local root exploit

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

El Topo wrote:
> I just installed 0.7.2 release, and found that it uses 2.6.22,
> unfortunately it has the big issue of local root exploit.
> 
> for more info, see
> http://it.slashdot.org/article.pl?sid=08/02/10/2011257

Yes. That is true big. But only for untrusted users and opened ssh
shells. No problems for localy working users, and if You are the only
one user on your coLinux. ;-)

Thanks for your watching.

> I urge that a new patch release as soon as possible.

Here is a kernel replacement:
http://www.henrynestler.com/colinux/releases/0.7.2/hotfix/

file: vmlinux-2.6.22-co-0.7.2-20080219.zip
You can simply replace the installed file "vmlinux" with that binary.

A full coLinux update with installer will follow.

-- 
Henry N.

[coLinux-users] Running Colinux on 32 Vista

[Jim M. <jm...@te...>]

Hello: Does anyone out there know how to actually configure and start up linux using Colinux on 32 bit Vista Home Premium? I installed the Debian 4.0 option!

Jim McRitchie
Edmonton, Canada

[coLinux-users] 0.7.2 release = kernel 2.6.22 + local root exploit

[El T. <ca...@gm...>]

Hi,

I just installed 0.7.2 release, and found that it uses 2.6.22,
unfortunately it has the big issue of local root exploit.

for more info, see
http://it.slashdot.org/article.pl?sid=08/02/10/2011257

I urge that a new patch release as soon as possible.

Cheers,

cameos

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.2 released

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

Cooperative Linux version 0.7.2 is released now.

There are no changes between rc5 and release version, we released the
binary from builddate 18-Jan-2008. Users of this snapshot don't need update.

This is an upgrade with new kernel and lots of fixed bugs.

Download:  http://sourceforge.net/projects/colinux/files
Notes:
http://sourceforge.net/project/shownotes.php?group_id=98788&release_id=577168
Changelog: http://www.colinux.org/snapshots/stable-ChangeLog
Wiki:      http://colinux.wikia.com/

NEWS of Version 0.7.2
Bugfixes:
  * #1324092: cofs rename replace existing file.
  * #1791993: Ship modules with root as owner and group.
  * #1853578: memory usage limit: 0 MB on machines with 4 GB RAM.
  * Fix cofs chdir with wildcards on existing upper/lower directory.
  * Don't drop last char from config, if last line no ends with CRLF.

Console and daemons:
  * New menu entries in FLTK console
    Power off: Fast power down coLinux kernel. Without file sync!
    Reboot:    Sends ctrl-alt-del, init process goes into runlevel 6
    Shutdown:  Calls "/sbin/shutdown -h now" with fallback to "/sbin/halt"
               Shutdown will automatic call from stopping as service,
               or if user clicks close on the colinux-daemon.
  * New: "colinux-daemon -p pidFile" stores ID of coLinux in file pidFile.
    "colinux-console-fltk|nt -p pidFile" attach the monitor from stored
    ID.  With this mechanism can open a /named/ console without knowing
    the current ID (Process ID).  pidFile will removed on normal shutdown.
  * Network daemons TAP, Bridged and Slirp runs with process priority high.
  * Added a nice colinux 3D logo image to the "About" box (Nlucas)
  * Stop with error, if double defined device (cobd,cofs,eth,exec)
  * Optimized workaround for DEP/noexecute problems (flush tlb).

Kernel:
  * Kernel has been updated to 2.6.22
    (Thanks to Anders Eriksson for 2.6.13, 2.6.14, 2.6.15)
  * Holds multiple kernel versions in patch series files
    (2.6.12, 2.6.13, 2.6.14, 2.6.15, 2.6.17, 2.6.22)
  * cloop updated to 2.06 (compressed loop blockdevice from Knoppix)
  * Hotplug enabled, udev usable

Installer:
  * Text was to big for description box in installer. [Bugs item #1819219]
  * Add Ubuntu 6.06.1 to images page. Update image Fedore 7. Add web link
    to Notes for each image. Link to 'other images on SF' clickable now.
  * Un-/Installer checks a running coLinux before overwrite or remove old
    files.  [Bugs item #1396459, #1549148]
  * Uninstall old colinux with old exefile, path from registry uninstaller
    [Support Requests-1553923]
  * Update tapinstall.exe (alias devcon) from DDK 3790.1830 (Mar 24 2005)
  * Block installing on 64 bit systems.

Buildsystem:
  * Linux as host: Restructed build of colinux.ko, use kbuild system
    from host. Host with regparm=3 is usable (tested host 2.6.22).
  * Linux Kernel and daemons can build with differ gcc versions now.
    ABI is runtime checked.
    Usable gcc for kernel: 3.4.x, 4.0.x, 4.1.x, 4.2.x up to 4.3.0
  * Warnings from gcc 4.x fixed.

Debugging:
  * New: Debugging.txt with hints for debugging colinux start problems.
  * Option "-v level" enable verbose messages and debug prints on console.
  * colinux-debug-daemon: Only connect to driver, if args -s settings.
  * Leveled debug output to Dbgview.exe (www.sysinternals.com).
    Needs to enable facility/level with colinux-debug-daemon before.

Updated libraries and tools:
  * gcc 4.1.2 (unpatched now, not from mingw)
  * binutils 2.17.50
  * mingw 3.11
  * w32api 3.9
  * WinPcap 4.0.1

-- 
Henry Nestler

Re: [coLinux-users] Xming keeps losing fullscreen mode

[James H. <Jam...@ro...>]

On Saturday 09 February 2008 21:12, James Hirschorn wrote:
> I haven't been using colinux for awhile, and just started again.
>
> I upgraded from 0.6.4 to colinux stable (0.7.1). Now I am having a problem
> I have never seen before. I use Xming in fullscreen mode. Every 5 minutes
> or so, I end up back in Windows XP with the Xming window minimized. 

I found the culprit: EMC Retrospect.

James

> It does 
> not seem to be related to any user actions.
>
> If anyone else has observed this please let me know.
>
> Thanks,
> James
>
> -------------------------------------------------------------------------
> 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

[coLinux-users] Xming keeps losing fullscreen mode

[James H. <Jam...@ro...>]

I haven't been using colinux for awhile, and just started again.

I upgraded from 0.6.4 to colinux stable (0.7.1). Now I am having a problem I 
have never seen before. I use Xming in fullscreen mode. Every 5 minutes or 
so, I end up back in Windows XP with the Xming window minimized. It does not 
seem to be related to any user actions. 

If anyone else has observed this please let me know.

Thanks,
James

[coLinux-users] Seamlessly integrate XP into Linux with SeamlessRDP

[Jun O. <ok...@di...>]

Seamlessly integrate XP into Linux with SeamlessRDP
http://www.linux.com/feature/124908

           --- Okajima, Jun. Tokyo, Japan.

Re: [coLinux-users] Address space layout

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

Jitesh Shah wrote:
> Hi,
> I was going through the address space layout of guest. (all the #defines
> for SELF_MAP, PASSAGE_PAGE, etc....)
> I don't understand how the guest kernel knows that these virtual
> addresses are reserved??... What if I #define, say, another page below
> the SELF_MAP??

You means Address space layout in include/asm-i386/cooperative.h in
coLinux kernel source?
(http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/patch/base-2.6.22.diff)

/*
 * Address space layout:
 */

#define CO_VPTR_BASE                         (0xffc00000)
#define CO_VPTR_PHYSICAL_TO_PSEUDO_PFN_MAP   (CO_VPTR_BASE - 0x1000000)
#define CO_VPTR_PSEUDO_RAM_PAGE_TABLES       (CO_VPTR_BASE - 0x1100000)
#define CO_VPTR_PASSAGE_PAGE                 (CO_VPTR_BASE - 0x1101000)
#define CO_VPTR_IO_AREA_SIZE                 (0x10000)
#define CO_VPTR_IO_AREA_START                (CO_VPTR_BASE - 0x1200000)
#define CO_VPTR_SELF_MAP                     (CO_VPTR_BASE - 0x1400000)

These addresses are reserved, because they are not defined as free
virtual address pool for memory mapping. The addresses are fixed virtual
addresses. It is no coLinux specific. In the Linux kernel exist some
more fixed addresses, for example the kernel code starts at 0xc0000000.

Internal details about working coLinux exist under "Publications" on
http://www.colinux.org/, the text "2004 paper" and page 10 in "2004
slides" are well good for understanding.

-- 
Henry N.

[coLinux-users] Address space layout

[Jitesh S. <jit...@gm...>]

Hi,
I was going through the address space layout of guest. (all the #defines for
SELF_MAP, PASSAGE_PAGE, etc....)
I don't understand how the guest kernel knows that these virtual addresses
are reserved??... What if I #define, say, another page below the SELF_MAP??

[coLinux-users] (no subject)

[colipa <co...@co...>]

bupaacn."|"qysnlxr

Re: [coLinux-users] swap partition not working (device or resource busy)

[Andrew R. <and...@gm...>]

Thanks for the ideas.  I used dd to verify that the device was mapped to
what I expected in windows.  I also tried the direct hard drive access
format you suggested, unfortunately with the same results.

The problem occurred actually when I upgraded from ubuntu edgy 6.10 to gutsy
7.10.  I noticed when I boot up in gutsy, instead of /dev/hda devices I have
/dev/sda.  Sometimes when I try to mount an external usb drive (when booted
natively, not through colinux) I get /dev/..: Device or resource busy, same
as I get with the swap.  Unplugging and replugging the usb drive fixes it,
obviously can't do that with an internal swap device.  Anyways I'm not sure
why it's suddenly doing that, but it might be related.

In any case, I use a file swap 'device' and that's enabled me to use the
more memory intensive programs again.

-Andrew

On Jan 26, 2008 5:25 AM, Henry Nestler <Hen...@ar...> wrote:

> Andrew Roth wrote:
> > Hi all,
> >
> > I used to be able to mount my swap partition in colinux, but it seems to
> > be failing silently now.
> >
> > [...]
> > --(23:47)-- $ sudo mkswap /dev/hda5
> > /dev/hda5: Device or resource busy
> > --(/home/andrewr)-----------------------------------(
> andrewr@andrewr-laptop:1)--
> > --(23:47)-- $
> >
> > My config is pretty simple:
> > [...]
> > # File systems
> > hda5=\Device\HarddiskVolume4 # swap
> > hda6=\Device\HarddiskVolume5 # ubuntu
>
> Doubble check, that you used the right Volume number 4.
> From http://www.chrysocome.net/dd run
>  dd --list
> and check that the name HarddiskVolume4 is linked to your Partition.
>
> I'm preffer more the style in form
>  hda5=\Device\Harddisk0\Partition4 # swap
>  hda6=\Device\Harddisk0\Partition5 # ubuntu
> There the names are coded by hardware, and not from windows internal
> counts of "HarddiskVolume*".
>
> Other idea is to use a swapfile in the mounted hda6 filesystem.
>
> --
> Henry N.
>

Re: [coLinux-users] Serial/USB ports

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

Harald Weidner wrote:
> Hello,
> 
> Is it possible to access a serial or USB port from a colinux guest?

Yes it is. USB, buildin serial port or "Winmodems" are usable.

> I would like to set up a colinux guest as a "firewall" for a Windows XP
> machine. An analog modem, which is connected to the serial port (directly or
> through serial-USB adapter), should be managed by pppd within the colinux
> guest. The Windows host should be able to access the Internet only through a
> HTTP proxy, SMTP gateway, and DNS forwarder running in colinux.
> 
> Can this scenario be realized?

The serial port has only data transfer, no metadata. That means, you
have a fixed baudrate and no control signals (DTR,RTS,DCD). I don't know
how hard would be the setup with such limitations.

-- 
Henry N.

[coLinux-users] Serial/USB ports

[Harald W. <hwe...@gm...>]

Hello,

Is it possible to access a serial or USB port from a colinux guest?

I would like to set up a colinux guest as a "firewall" for a Windows XP
machine. An analog modem, which is connected to the serial port (directly or
through serial-USB adapter), should be managed by pppd within the colinux
guest. The Windows host should be able to access the Internet only through a
HTTP proxy, SMTP gateway, and DNS forwarder running in colinux.

Can this scenario be realized?

Regards,
Harald

Re: [coLinux-users] need help on understanding coLinux

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

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.

Re: [coLinux-users] need help on understanding coLinux

[Nambi J U <ju...@gm...>]

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...> 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...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>

[coLinux-users] need help on understanding coLinux

[Prakash S. <pra...@gm...>]

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

[coLinux-users] colinux failed : cobd0=debian.iso with readonly attribute

[Wufu C. <cc...@gm...>]

Hi
   I try to build the cd with colinux (with guest : live debian[1]).
I get the ideal while I read article[2].
  step#1:  now , I can auto-run colinux with guest live debian.
all in one folder(codebian) in windows

codebian
  colinux-daemon.exe
  linux.sys
  ...
  xming
  netdrivers
  autolaunch.bat

 live-debian.iso
  ...

   step#2 :and , I copy all the file of codebian directory into usb driver
also it works.


   step#3 :  but while I try to build the ISO with the files in codebian
directory
the coliux runs OK, and the initrd also run , but failed while try to mount
the cobd0 (live-debian.iso)
after some investigation, I find the live-debian.iso readonly attribute
cause it failed.

I have verified this with step1a :
I set the live-debian.iso readonly in the codebian directory in windows.
the colinux/initrd failed while mount the cobd0(live-debian.iso)

    I'not sure where is the problem :
a)problem in live-debian 's initrd image
I try to mount the cobd0 with readonly option while the colinux failback to
mini shell with busybox
mount -r /dev/cobd0 /mnt
but the mount is OK after I set the live-debian.iso to read-write in
codebian directory in step#1a

b)problem  in colinux / windows access right conflict.

Best Regards

Wufu Chen


[1]
provide Colinux on the live cd to run Ubuntu directly inside Windows
http://ubuntuforums.org/showthread.php?t=221273

[2]
live debian
http://live.debian.net/