colinux-users

[coLinux-users] coLinux 0.6.2-pre2

[Dan A. <da...@co...>]

Hello All,

Located at:

    http://www.colinux.org/snapshots/

The recently uploaded snapshot 20041002 (0.6.2-pre2), brings forth some
changes:

  * A fix for Windows XP SP2 with AMD64 (requires more testing)
    -----------------------------------------------------------
    
    An important fix that should allow coLinux to run on PAE setups, and
    prevent those BSODs that you were getting. 

    We noticed quickly after Windows XP SP2 was released. On AMD64 machines, 
    this version of XP enables PAE in order to implement the NX bit
    protection. The crashes that people experienced where not related to
    the NX bit but PAE and some bugs that plagued the driver's initialization
    routines.
    
    The coLinux low level code which is responsible for the context 
    switching did not handle PAE properly (PAE uses a different type of 
    paging).
    
    NOTE: I didn't test this snapshot on AMD64, so the NX bit might still
    cause trouble. If those of you with this hardware can test and report,
    that will be great.
  
  * Command line configuration
    --------------------------    
    
    It is now possible to configure coLinux from the command line, i.e,
    XML config is not needed. This mode and the XML mode are mutual 
    exclusive. 
    
    The reason for this feature is an ongoing effort to bring coLinux's
    interfaces to be closer to UML (User Mode Linux) *and* to make it 
    easier to operate for the novice users. 
    
    The kernel= option enables this mode. Order of parameters is not
    important when options don't depend on each other.
    
    For example:
    
        colinux-daemon kernel=vmlinux
	
      Boots a kernel without any block devices.


        colinux-daemon kernel=vmlinux mem=32
	
      Boots the kernel with 32 MB of RAM.


        colinux-daemon -d kernel=vmlinux mem=32
	
      The '-d' option still works.


        colinux-daemon kernel=vmlinux cobd0=c:\coLinux\root_fs
	
      It automatically adds \DosDevices\ where needed. Make sure
      you use double-slashes in the situations where shell escaping 
      forces you to.


        colinux-daemon kernel=vmlinux cobd0=c:\coLinux\root_fs root=/dev/cobd0 ro
	
      Of course we need to pass root= to the kernel. Note that every 
      parameter in that command line that is not handled by coLinux's 
      code is passed along as a kernel boot parameters.

      
        colinux-daemon kernel=vmlinux cobd0=root_fs root=/dev/cobd0 
	
      ... and resolve relative pathnames.
      
      
        colinux-daemon kernel=vmlinux cobd0=root_fs hda2=:cobd0 root=/dev/cobd0 
	
      Device node aliasing. The ':' tells the daemon that's cobd0
      is not a pathname - understand using the next example.
      

        colinux-daemon kernel=vmlinux hda1=root_fs root=/dev/hda1
	
      This makes life a lot easier. If you map an device node 
      directly - it would automatically allocate a cobd and
      make an alias for it!
      
      This syntax reminds a bit of QEMU's syntax (it also has 
      hda=).
      
      
        colinux-daemon kernel=vmlinux hda1=root_fs root=/dev/hda1 initrd=initrd.gz
	
      Upgrade your kernel modules for this snapshot.
      
      
    Options for networking:  
      
        eth0=tuntap

      Use the first TAP device.
      
            
        eth0=tuntap,"Local Area Network"

      You name it.

      
        eth0=tuntap,"Local Area Network",11:22:33:44:55:66

      Set an MAC address.
      

        eth0=pcap-bridge,"Local Area Network"

      Uses PCAP bridging. UML named this transport as 'pcap', I'm not sure 
      it's the same thing that used for the same purposes, so for the meanwhile 
      I'll name it 'pcap-bridge'.
      
      
    User Mode Linux has a bunch of networking features described in:
      
        http://user-mode-linux.sourceforge.net/networking.html
	  
    Which one would you like? Personally, I'd like to get it connected to 
    the UML switch along with a UML instance :).	    
    
    
  * Improved initrd image for modules upgrade
    -----------------------------------------
    
    Some tiny bug prevented this from working with aliasing enabled.
    
    For a kernel modules upgrade, use the initrd.gz image in the XML
    <initrd path="initrd.img" /> or pass initrd=initrd.gz in the
    command line.


Thanks,
      
-- 
Dan Aloni
da...@co...

[coLinux-users] RE: [coLinux-devel] coLinux 0.6.2-pre2

[peter g. <plu...@bi...>]

what exactly is PAE and how does it relate to the NX bit?

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Dan Aloni
> Sent: 03 October 2004 01:36
> To: Cooperative Linux Development
> Cc: Cooperative Linux Users
> Subject: [coLinux-devel] coLinux 0.6.2-pre2
>
>
> Hello All,
>
> Located at:
>
>     http://www.colinux.org/snapshots/
>
> The recently uploaded snapshot 20041002 (0.6.2-pre2), brings forth some
> changes:
>
>   * A fix for Windows XP SP2 with AMD64 (requires more testing)
>     -----------------------------------------------------------
>
>     An important fix that should allow coLinux to run on PAE setups, and
>     prevent those BSODs that you were getting.
>
>     We noticed quickly after Windows XP SP2 was released. On
> AMD64 machines,
>     this version of XP enables PAE in order to implement the NX bit
>     protection. The crashes that people experienced where not related to
>     the NX bit but PAE and some bugs that plagued the driver's
> initialization
>     routines.
>
>     The coLinux low level code which is responsible for the context
>     switching did not handle PAE properly (PAE uses a different type of
>     paging).
>
>     NOTE: I didn't test this snapshot on AMD64, so the NX bit might still
>     cause trouble. If those of you with this hardware can test and report,
>     that will be great.
>
>   * Command line configuration
>     --------------------------
>
>     It is now possible to configure coLinux from the command line, i.e,
>     XML config is not needed. This mode and the XML mode are mutual
>     exclusive.
>
>     The reason for this feature is an ongoing effort to bring coLinux's
>     interfaces to be closer to UML (User Mode Linux) *and* to make it
>     easier to operate for the novice users.
>
>     The kernel= option enables this mode. Order of parameters is not
>     important when options don't depend on each other.
>
>     For example:
>
>         colinux-daemon kernel=vmlinux
>
>       Boots a kernel without any block devices.
>
>
>         colinux-daemon kernel=vmlinux mem=32
>
>       Boots the kernel with 32 MB of RAM.
>
>
>         colinux-daemon -d kernel=vmlinux mem=32
>
>       The '-d' option still works.
>
>
>         colinux-daemon kernel=vmlinux cobd0=c:\coLinux\root_fs
>
>       It automatically adds \DosDevices\ where needed. Make sure
>       you use double-slashes in the situations where shell escaping
>       forces you to.
>
>
>         colinux-daemon kernel=vmlinux cobd0=c:\coLinux\root_fs
> root=/dev/cobd0 ro
>
>       Of course we need to pass root= to the kernel. Note that every
>       parameter in that command line that is not handled by coLinux's
>       code is passed along as a kernel boot parameters.
>
>
>         colinux-daemon kernel=vmlinux cobd0=root_fs root=/dev/cobd0
>
>       ... and resolve relative pathnames.
>
>
>         colinux-daemon kernel=vmlinux cobd0=root_fs hda2=:cobd0
> root=/dev/cobd0
>
>       Device node aliasing. The ':' tells the daemon that's cobd0
>       is not a pathname - understand using the next example.
>
>
>         colinux-daemon kernel=vmlinux hda1=root_fs root=/dev/hda1
>
>       This makes life a lot easier. If you map an device node
>       directly - it would automatically allocate a cobd and
>       make an alias for it!
>
>       This syntax reminds a bit of QEMU's syntax (it also has
>       hda=).
>
>
>         colinux-daemon kernel=vmlinux hda1=root_fs root=/dev/hda1
> initrd=initrd.gz
>
>       Upgrade your kernel modules for this snapshot.
>
>
>     Options for networking:
>
>         eth0=tuntap
>
>       Use the first TAP device.
>
>
>         eth0=tuntap,"Local Area Network"
>
>       You name it.
>
>
>         eth0=tuntap,"Local Area Network",11:22:33:44:55:66
>
>       Set an MAC address.
>
>
>         eth0=pcap-bridge,"Local Area Network"
>
>       Uses PCAP bridging. UML named this transport as 'pcap', I'm
> not sure
>       it's the same thing that used for the same purposes, so for
> the meanwhile
>       I'll name it 'pcap-bridge'.
>
>
>     User Mode Linux has a bunch of networking features described in:
>
>         http://user-mode-linux.sourceforge.net/networking.html
>
>     Which one would you like? Personally, I'd like to get it connected to
>     the UML switch along with a UML instance :).
>
>
>   * Improved initrd image for modules upgrade
>     -----------------------------------------
>
>     Some tiny bug prevented this from working with aliasing enabled.
>
>     For a kernel modules upgrade, use the initrd.gz image in the XML
>     <initrd path="initrd.img" /> or pass initrd=initrd.gz in the
>     command line.
>
>
> Thanks,
>
> --
> Dan Aloni
> da...@co...
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel

[coLinux-users] Re: [coLinux-devel] coLinux 0.6.2-pre2

[Nuno L. <lu...@nl...>]

peter green, escreveu :
> what exactly is PAE and how does it relate to the NX bit?
> 

PAE - Physical Address Extensions - is a way Intel made for 32 bits
processors to address more than 4 GB of memory. It was introduced in
the Intel Pentium Pro, so every CPU made in the last years also
implements it (not sure, but I think Pentium M doesn't have it).

This is done by extending the paging mechanism and, when enabled,
extends the page frame tables structures from 32 to 64 bits and
adds another table to the virtual memory scheme.

I don't want to go too deep on this. With PAE enabled, every process is
still limited to 4 GB of directly addressed memory, but it can now use
more by requesting pages from the OS (the same as overlays in DOS days).
Also, the total memory that can be addressable is usually limited by the
OS, not the PAE limit (52 bits, if I remember correctly).

NX needs that PAE be enabled because the 32 bits page structures didn't
had more space to hold more protection bits in it. With PAE enabled, 
there is now space for the NX bit and more.

Regards,
~Nuno Lucas

[coLinux-users] Re: [coLinux-devel] coLinux 0.6.2-pre2

[Paradise <par...@gm...>]

HI, I just install the new version and and turn on NX bit protection,
however run I run the coLinux give me same result with old version,
the Windows XP just crash with blue screen..


On Sun, 3 Oct 2004 02:35:53 +0200, Dan Aloni <da...@co...> wrote:
> Hello All,
> 
> Located at:
> 
>    http://www.colinux.org/snapshots/
> 
> The recently uploaded snapshot 20041002 (0.6.2-pre2), brings forth some
> changes:
> 
>  * A fix for Windows XP SP2 with AMD64 (requires more testing)
>    -----------------------------------------------------------
> 
>    An important fix that should allow coLinux to run on PAE setups, and
>    prevent those BSODs that you were getting.
> 
>    We noticed quickly after Windows XP SP2 was released. On AMD64 machines,
>    this version of XP enables PAE in order to implement the NX bit
>    protection. The crashes that people experienced where not related to
>    the NX bit but PAE and some bugs that plagued the driver's initialization
>    routines.
> 
>    The coLinux low level code which is responsible for the context
>    switching did not handle PAE properly (PAE uses a different type of
>    paging).
> 
>    NOTE: I didn't test this snapshot on AMD64, so the NX bit might still
>    cause trouble. If those of you with this hardware can test and report,
>    that will be great.
> 
>  * Command line configuration
>    --------------------------
> 
>    It is now possible to configure coLinux from the command line, i.e,
>    XML config is not needed. This mode and the XML mode are mutual
>    exclusive.
> 
>    The reason for this feature is an ongoing effort to bring coLinux's
>    interfaces to be closer to UML (User Mode Linux) *and* to make it
>    easier to operate for the novice users.
> 
>    The kernel= option enables this mode. Order of parameters is not
>    important when options don't depend on each other.
> 
>    For example:
> 
>        colinux-daemon kernel=vmlinux
> 
>      Boots a kernel without any block devices.
> 
>        colinux-daemon kernel=vmlinux mem=32
> 
>      Boots the kernel with 32 MB of RAM.
> 
>        colinux-daemon -d kernel=vmlinux mem=32
> 
>      The '-d' option still works.
> 
>        colinux-daemon kernel=vmlinux cobd0=c:\coLinux\root_fs
> 
>      It automatically adds \DosDevices\ where needed. Make sure
>      you use double-slashes in the situations where shell escaping
>      forces you to.
> 
>        colinux-daemon kernel=vmlinux cobd0=c:\coLinux\root_fs root=/dev/cobd0 ro
> 
>      Of course we need to pass root= to the kernel. Note that every
>      parameter in that command line that is not handled by coLinux's
>      code is passed along as a kernel boot parameters.
> 
>        colinux-daemon kernel=vmlinux cobd0=root_fs root=/dev/cobd0
> 
>      ... and resolve relative pathnames.
> 
>        colinux-daemon kernel=vmlinux cobd0=root_fs hda2=:cobd0 root=/dev/cobd0
> 
>      Device node aliasing. The ':' tells the daemon that's cobd0
>      is not a pathname - understand using the next example.
> 
>        colinux-daemon kernel=vmlinux hda1=root_fs root=/dev/hda1
> 
>      This makes life a lot easier. If you map an device node
>      directly - it would automatically allocate a cobd and
>      make an alias for it!
> 
>      This syntax reminds a bit of QEMU's syntax (it also has
>      hda=).
> 
>        colinux-daemon kernel=vmlinux hda1=root_fs root=/dev/hda1 initrd=initrd.gz
> 
>      Upgrade your kernel modules for this snapshot.
> 
>    Options for networking:
> 
>        eth0=tuntap
> 
>      Use the first TAP device.
> 
>        eth0=tuntap,"Local Area Network"
> 
>      You name it.
> 
>        eth0=tuntap,"Local Area Network",11:22:33:44:55:66
> 
>      Set an MAC address.
> 
>        eth0=pcap-bridge,"Local Area Network"
> 
>      Uses PCAP bridging. UML named this transport as 'pcap', I'm not sure
>      it's the same thing that used for the same purposes, so for the meanwhile
>      I'll name it 'pcap-bridge'.
> 
>    User Mode Linux has a bunch of networking features described in:
> 
>        http://user-mode-linux.sourceforge.net/networking.html
> 
>    Which one would you like? Personally, I'd like to get it connected to
>    the UML switch along with a UML instance :).
> 
>  * Improved initrd image for modules upgrade
>    -----------------------------------------
> 
>    Some tiny bug prevented this from working with aliasing enabled.
> 
>    For a kernel modules upgrade, use the initrd.gz image in the XML
>    <initrd path="initrd.img" /> or pass initrd=initrd.gz in the
>    command line.
> 
> Thanks,
> 
> --
> Dan Aloni
> da...@co...
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 



-- 
Regards,
Paradise

[coLinux-users] Re: [coLinux-devel] coLinux 0.6.2-pre2

[Dan A. <da...@co...>]

On Sun, Oct 03, 2004 at 11:18:32PM +0800, Paradise wrote:
> HI, I just install the new version and and turn on NX bit protection,
> however run I run the coLinux give me same result with old version,
> the Windows XP just crash with blue screen..

Could you please send the numbers you see in that blue screen? It 
might tell whether it crashes directly because of the NX bit.

-- 
Dan Aloni
da...@co...

[coLinux-users] Re: [coLinux-devel] coLinux 0.6.2-pre2

[Nuno L. <lu...@nl...>]

Dan Aloni, dando pulos de alegria, escreveu :
> On Sun, Oct 03, 2004 at 11:18:32PM +0800, Paradise wrote:
> 
>>HI, I just install the new version and and turn on NX bit protection,
>>however run I run the coLinux give me same result with old version,
>>the Windows XP just crash with blue screen..
> 
> 
> Could you please send the numbers you see in that blue screen? It 
> might tell whether it crashes directly because of the NX bit.
> 

Also one thing that may be the cause, be sure to remove old driver
by doing "colinux-daemon --remove-driver" and installing it again
with "colinux-daemon --install-driver".

This is just speculation, but it could be your case, so it would
not make any harm doing it.

Regards,
~Nuno Lucas

[coLinux-users] Re: [coLinux-devel] coLinux 0.6.2-pre2

[Paradise <par...@gm...>]

Yes, I did remove old driver by "colinux-daemon --remove-driver" and
installing it again
with "colinux-daemon --install-driver". 

The crashed blue screen code as below:

0x000000FC (0xEC0C201C, 0x006A817B, 0xF3BF7A74, 0x00000001)
NAVENG.SYS - Address F3BF7A74 base at F3BF7A74 Datestamp 00000000

It runs if I turn OFF NX, However It crashes when I turn on NX. About
"naveng.sys"
 it's something relate to Norton AntiVirus? I am running Norton System
Work 2004 on my system.

On Mon, 04 Oct 2004 00:49:28 +0100, Nuno Lucas <lu...@nl...> wrote:
> Dan Aloni, dando pulos de alegria, escreveu :
> 
> 
> > On Sun, Oct 03, 2004 at 11:18:32PM +0800, Paradise wrote:
> >
> >>HI, I just install the new version and and turn on NX bit protection,
> >>however run I run the coLinux give me same result with old version,
> >>the Windows XP just crash with blue screen..
> >
> >
> > Could you please send the numbers you see in that blue screen? It
> > might tell whether it crashes directly because of the NX bit.
> >
> 
> Also one thing that may be the cause, be sure to remove old driver
> by doing "colinux-daemon --remove-driver" and installing it again
> with "colinux-daemon --install-driver".
> 
> This is just speculation, but it could be your case, so it would
> not make any harm doing it.
> 
> Regards,
> ~Nuno Lucas
> 
> 



-- 
Regards,
Paradise

[coLinux-users] easy install on colinux

[Pierre C. <pit...@gm...>]

Hi everybody
I am new to colinux but I think this is even a better linux virus than Live CDs.
I have not succedded yet in the installation of a debian on it by a
lack of time.
I just asked myself a question.
Why can't we make a one clik installation of colinux with a debian for
exemple without having to configure the xml file (quite buggy) ?
I will work on it in my free time, but what do you think about that?
A nice big 25 MB bittorent link would be nice I think.

Maybe, colinux can find the place to store many preconfigured, one clik, distro.
I would be very pleased to test many distros on windaube in the single
click way.
cheers
pi2

http://pit2PEER.org
--
a free CD burner is a happy CD burner.
                                                  a wise chinese gourooo.

[coLinux-users] RE: [coLinux-devel] coLinux 0.6.2-pre2

[peter g. <plu...@bi...>]

sounds like it
have you tried it with norton antivirus disabled?
and if that fails to work have you tried it on a clean windows install?

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Paradise
> Sent: 04 October 2004 11:12
> To: Nuno Lucas; Digital Infra Inc.; Dan Aloni
> Cc: Cooperative Linux Development; Cooperative Linux Users
> Subject: Re: [coLinux-devel] coLinux 0.6.2-pre2
> 
> 
> Yes, I did remove old driver by "colinux-daemon --remove-driver" and
> installing it again
> with "colinux-daemon --install-driver". 
> 
> The crashed blue screen code as below:
> 
> 0x000000FC (0xEC0C201C, 0x006A817B, 0xF3BF7A74, 0x00000001)
> NAVENG.SYS - Address F3BF7A74 base at F3BF7A74 Datestamp 00000000
> 
> It runs if I turn OFF NX, However It crashes when I turn on NX. About
> "naveng.sys"
>  it's something relate to Norton AntiVirus? I am running Norton System
> Work 2004 on my system.
> 
> On Mon, 04 Oct 2004 00:49:28 +0100, Nuno Lucas 
> <lu...@nl...> wrote:
> > Dan Aloni, dando pulos de alegria, escreveu :
> > 
> > 
> > > On Sun, Oct 03, 2004 at 11:18:32PM +0800, Paradise wrote:
> > >
> > >>HI, I just install the new version and and turn on NX bit protection,
> > >>however run I run the coLinux give me same result with old version,
> > >>the Windows XP just crash with blue screen..
> > >
> > >
> > > Could you please send the numbers you see in that blue screen? It
> > > might tell whether it crashes directly because of the NX bit.
> > >
> > 
> > Also one thing that may be the cause, be sure to remove old driver
> > by doing "colinux-daemon --remove-driver" and installing it again
> > with "colinux-daemon --install-driver".
> > 
> > This is just speculation, but it could be your case, so it would
> > not make any harm doing it.
> > 
> > Regards,
> > ~Nuno Lucas
> > 
> > 
> 
> 
> 
> -- 
> Regards,
> Paradise
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to 
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel

[coLinux-users] Re: [coLinux-devel] coLinux 0.6.2-pre2

[Nuno L. <lu...@nl...>]

Paradise, dando pulos de alegria, escreveu :
> The crashed blue screen code as below:
> 
> 0x000000FC (0xEC0C201C, 0x006A817B, 0xF3BF7A74, 0x00000001)
> NAVENG.SYS - Address F3BF7A74 base at F3BF7A74 Datestamp 00000000
> 
> It runs if I turn OFF NX, However It crashes when I turn on NX. About
> "naveng.sys"
>  it's something relate to Norton AntiVirus? I am running Norton System
> Work 2004 on my system.

There are two KB articles I found that may be relevant here:

0x000000FC (ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY):

* http://support.microsoft.com/default.aspx?kbid=878474

and how to really disable antivirus software:

* http://support.microsoft.com/default.aspx?scid=kb;en-us;240309

In my opinion, there are four possible causes here (at least):

1) It's a Norton Antivirus problem.

Be sure to update your Antivirus software to a recent version.
A possible way to comprove this would be to remove the colinux driver
and see if this error is still triggered.

2) Norton Antivirus doesn't cope well with colinux driver.

It may be that Norton AV doesn't work well with colinux, resulting
in the stop error mentioned.
It can be comproved by completely uninstalling Norton AV and checking if
colinux runs OK (and don't forget to follow the link to make sure NAV is
really uninstalled).

3) It's colinux.sys fault. It's still not ready for DEP/NX.

I don't believe this, as if it was, it should be pointing into the
colinux.sys driver, not naveng.sys (Norton AV driver).
With this I mean it can still have problems with NX, but I don't
believe the cause of the current problem is colinux, but maybe 2).

4) Other problems, like a real virus in your PC.

You could have a real virus in your PC, trying to disable the Norton AV
program, resulting in that exception with DEP/NX enabled.
As NAV is very used program, there are many viruses that try to disable
it first, and can be failing now with DEP/NX enabled.
A way to confirm this is using some other antivirus, like AVG, Avast,
etc (they have a free edition for home use).


Regards,
~Nuno Lucas

[coLinux-users] coLinux 0.6.2-pre3

[Dan A. <da...@co...>]

On Mon, Oct 04, 2004 at 06:12:00PM +0800, Paradise wrote:
> Yes, I did remove old driver by "colinux-daemon --remove-driver" and
> installing it again
> with "colinux-daemon --install-driver". 
> 
> The crashed blue screen code as below:
> 
> 0x000000FC (0xEC0C201C, 0x006A817B, 0xF3BF7A74, 0x00000001)
> NAVENG.SYS - Address F3BF7A74 base at F3BF7A74 Datestamp 00000000
> 
> It runs if I turn OFF NX, However It crashes when I turn on NX. About
> "naveng.sys"
>  it's something relate to Norton AntiVirus? I am running Norton System
> Work 2004 on my system.

I've uploaded a new snapshot (20041006) that specifically addresses the 
NX bit problem, by directly turning it off in the page tables. Can you 
please retry with this?

-- 
Dan Aloni
da...@co...

Re: [coLinux-users] coLinux 0.6.2-pre2

[<ch...@to...>]

>
>     Which one would you like? Personally, I'd like to get it connected =
to
>     the UML switch along with a UML instance :).
>

>
> Thanks,
>
> --
> Dan Aloni
> da...@co...
>

The switch is cool. Also not networking but COW is also very usefull.
Great for the budding admin -- screw up the system just start a new cow
file ;) instant system restore. Also great for education use colinux to
teach linux students can each have thier own cow file. And save space on =
a
multi user machine. And as you probably know virtual server farmers can
use cow with the switch to let clients have root. But this would be more
for coLinux on Linux ;)

chris

RE: [coLinux-users] coLinux 0.6.2-pre2

[peter g. <plu...@bi...>]

> The switch is cool. Also not networking but COW is also very usefull.
> Great for the budding admin -- screw up the system just start a new cow
> file ;) instant system restore. Also great for education use colinux to
> teach linux students can each have thier own cow file. And save space on a
> multi user machine. And as you probably know virtual server farmers can
> use cow with the switch to let clients have root. But this would be more
> for coLinux on Linux ;)
>
> chris
colinux was never really built to be a jail
if you can load code into the kernel (through modules for example but there
may be other ways) you have kernel mode access to the host system