Re: coLinux-users Digest, Vol 69, Issue 2

Hi Alexander Kriegisch (kriegaex),

I don't have any problem with it on Ubuntu 12.04 (speedlinux)
Did test with this example:
http://monkeypatch.me/blog/move-a-running-process-to-a-new-screen-shell.html
Best regards, Johann Pascher

2012/2/3  <colinux-users-request@...>:
> Send coLinux-users mailing list submissions to
>        colinux-users@...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/colinux-users
> or, via email, send a message with subject or body 'help' to
>        colinux-users-request@...
>
> You can reach the person managing the list at
>        colinux-users-owner@...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of coLinux-users digest..."
>
>
> Today's Topics:
>
>   1. Re: Problem with ptrace protection in Ubuntu (yin sun)
>   2. Re: Problem with ptrace protection in Ubuntu (yin sun)
>
>
> ----------------------------------------------------------------------

Problem with ptrace protection in Ubuntu

Hi.

I am running andLinux/coLinux:

$ uname -a
Linux andLinux 2.6.33.7-co-0.7.10-r1588 #1 PREEMPT Mon Aug 8 04:13:31 UTC 2011 i686 athlon i386 GNU/Linux

But...

$ cat /etc/motd | head -n 1
Welcome to Ubuntu 11.10 (GNU/Linux 2.6.33.7-co-0.7.10-r1588 i686)

Now the problem is so-called "ptrace protection", explained there:
https://wiki.edubuntu.org/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection

I tried to use tools like reptyr and injcode:
https://github.com/nelhage/reptyr#readme
https://github.com/ThomasHabets/injcode#readme

Both of them do not work as expected. My suspicion is that this is due to my combination of coLinux kernel
(without yama) and new Ubuntu (relying on yama). I tried to run the tools as root (sudo -i) because I
expected ptrace protection to be inactive according to the description at Ubuntu, but to no avail.

My questions are:
  1) Can you confirm that my suscpcion is correct?
    2a) If not, what else might be the reason for my problems?
    2b) If so, is there anything I can do about it like downloading a coLinux kernel with built-in yama support
from somewhere or asking you to build in yama protection in the future?

Disclaimer: Maybe I am not asking the right questions. Please note that I am a user, not a kernel hacker.

Your Ubuntu bluescreens !

Hello Bob,
Not sure about Henry, but I'm a bit annoyed by the tone of your
messages. Maybe you should try harder to figure out issue yourself ?
Maybe there's something wrong with your PC if no one else had similar
issues ? Does anyone care about this new Ubuntu release, you piss
everyone off ? Pardon my French ;) Nothing personal...

>These things that you have asked me to try seem like a waste of time so far.
It would be better if somebody that understands colinux well looked at the
patterns in memory where the corruption is detected to see if they recognize
anything related to what colinux is doing.

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

Re: Colinux Blue Screen Crashes

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

_______________________________________________
coLinux-users mailing list
coLinux-users@...
https://lists.sourceforge.net/lists/listinfo/colinux-users

kernel

now i have built my own colinux kernel
but after i have do
make modules
must i create a initrd.gz?
and if so
how?

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

lvm

anyone using physical partitions with lvm on colinux
if so
i try it and it try to mount but fail
no root fs to mount
what should i enter as root partion?
/dev/cobd0?
i have created cobd devices on the physical linux
but no luck

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2

Re: coLinux-users Digest, Vol 68, Issue 7

Hallo Martin,

sehr schön, dass du dich meldest.

Das ist halt so, dass sich keiner meldet ich bin da keine Ausnahme.
Ich hab wohl hin und wieder mal and dich gedacht aber zu einer Mail
hat es ohne egoistischen Grund auch nicht gereicht.
Bei mir ist es halt so dass ich auch nicht unnötig blöd irgendwas
schreiben will.
Bei anderen wird es ähnlich sein, man müsste die einzelne Personen
selber ansprechen.
Jeder ist zu sehr im System eingespannt, und wir passen da halt mit
Krankheit oder Ruhestand nicht wirklich mehr hinein.

Ich müsste mal bei dir wieder vorbeischauen dann könnte man darüber
sicher einiges ausführlicher besprechen.
Komischerweise bin auch ich wieder ziemlich eingespannt, zumindest aus
meiner Sicht, auch wenn mir direkt keiner was anschafft.
Ich unterbreche hier mal ... mein Anliegen kommt später das rennt nicht davon.

Mal sehen was Heute anliegt, hab erst gefrühstückt.

bis später Hannes

2012/1/9  <colinux-users-request@...>:
> Send coLinux-users mailing list submissions to
>        colinux-users@...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/colinux-users
> or, via email, send a message with subject or body 'help' to
>        colinux-users-request@...
>
> You can reach the person managing the list at
>        colinux-users-owner@...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of coLinux-users digest..."
>
>
> Today's Topics:
>
>   1. Re: Colinux Blue Screen Crashes (Bob Wheater)
>   2. Re: Colinux Blue Screen Crashes (Miller, Shao)
>   3. Re: Colinux Blue Screen Crashes (Bob Wheater)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 9 Jan 2012 15:04:08 -0500
> From: "Bob Wheater" <bwheater@...>
> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes
> To: <colinux-users@...>
> Message-ID: <003401cccf09$d9d87a40$8d896ec0$@net>
> Content-Type: text/plain; charset="iso-8859-1"
>
>> Vincent Rivi?re wrote:
>
>>My complete boot.ini line is:
>
>>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP
> Professionnel" /fastdetect >/noexecute=alwaysoff /nopae
>
>
>
>>To check if PAE is actually on or off, look at the >system properties
> (Win+Pause), on the General tab (the >default one). Look at the bottom,
> after the line with >frequency and amount of RAM. If "Physical Address
>>Extension"
>
>>is written, then PAE is on. If there is no such text, >PAE is off.
>
>
>
>>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check
> it is actually disabled and see if >coLinux works better.
>
>
>
> My general tab on the system properties does NOT have ?Physical Address
> Extension?.
>
>
>
> You seem to be confusing PAE with DEP (Data Execution Prevention). See
> http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx
>
> The /noexecute switch controls DEP.
>
>
>
> However DEP may only apply to windows server 2003 and not XP.
>
>
>
> ? The PAE mode kernel requires an Intel Architecture processor, Pentium Pro
> or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows
> Server 2003.?
>
> From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503
>
> According to this PAE does NOT apply to a 1gb system. It only applies to 4gb
> and greater systems.
>
>
>
> Regards,
>
> Bob
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Mon, 9 Jan 2012 15:13:55 -0500
> From: "Miller, Shao" <shao.miller@...>
> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes
> To: "Bob Wheater" <bwheater@...>
> Cc: colinux-users@...
> Message-ID:
>        <F0E5F8699DE1364584CDB894E99713552A71D508@...SB.NET>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Did you get my last message regarding possibly useful info you could share?  If not, I'd appreciate it if
you could review it.
>
>
>
> There are several kernels:
>
> *       Uniprocessor, no-PAE (the default ntoskrnl.exe)
> *       Uniprocessor, PAE (ntkrnlpa.exe)
> *       Multiprocessor, no-PAE (ntkrnlmp.exe)
> *       Multiprocessor, PAE (ntkrpamp.exe)
>
>
>
> Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), highlight the System process,
then choose View -> Lower Pane View -> DLLs and make sure that View -> Show Lower Pane has a check-mark.
 Then scroll through the list of DLLs and observe which one matches the pattern ntXXX.exe.
>
>
>
> You can be using a PAE kernel without knowing it and without the /PAE switch in BOOT.INI.
>
>
>
> - Shao Miller
>
> ________________________________
>
> From: Bob Wheater [mailto:bwheater@...]
> Sent: Monday, January 09, 2012 15:04
> To: colinux-users@...
> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes
>
>
>
>> Vincent Rivi?re wrote:
>
>>My complete boot.ini line is:
>
>>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP Professionnel"
/fastdetect >/noexecute=alwaysoff /nopae
>
>
>
>>To check if PAE is actually on or off, look at the >system properties (Win+Pause), on the General tab (the
>default one). Look at the bottom, after the line with >frequency and amount of RAM. If "Physical Address >Extension"
>
>>is written, then PAE is on. If there is no such text, >PAE is off.
>
>
>
>>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check it is actually disabled and
see if >coLinux works better.
>
>
>
> My general tab on the system properties does NOT have "Physical Address Extension".
>
>
>
> You seem to be confusing PAE with DEP (Data Execution Prevention). See http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx
>
> The /noexecute switch controls DEP.
>
>
>
> However DEP may only apply to windows server 2003 and not XP.
>
>
>
> " The PAE mode kernel requires an Intel Architecture processor, Pentium Pro or later, more than 4 GB of RAM,
and Windows 2000, Windows XP, or Windows Server 2003."
>
> From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503
>
> According to this PAE does NOT apply to a 1gb system. It only applies to 4gb and greater systems.
>
>
>
> Regards,
>
> Bob
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Mon, 9 Jan 2012 16:11:22 -0500
> From: "Bob Wheater" <bwheater@...>
> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes
> To: <colinux-users@...>
> Message-ID: <004201cccf13$3e4661f0$bad325d0$@net>
> Content-Type: text/plain; charset="us-ascii"
>
> Its using the default uniprocess kernel (nopae):
>
> ntoskrnl.exe NT Kernel & System           Microsoft Corporation
> 5.1.2600.6165
>
> according to process explorer.
>
>
>
> What last message? I though everything was posted to the list. I checked my
> files and the only message from you concerns posting the top part of windbg
> output which I did post when I reported the problem to the bug tracker.
>
> -Bob
>
>
>
> From: Miller, Shao [mailto:shao.miller@...]
> Sent: Monday, January 09, 2012 3:14 PM
> To: Bob Wheater
> Cc: colinux-users@...
> Subject: RE: [coLinux-users] Colinux Blue Screen Crashes
>
>
>
> Did you get my last message regarding possibly useful info you could share?
> If not, I'd appreciate it if you could review it.
>
>
>
> There are several kernels:
>
> *       Uniprocessor, no-PAE (the default ntoskrnl.exe)
> *       Uniprocessor, PAE (ntkrnlpa.exe)
> *       Multiprocessor, no-PAE (ntkrnlmp.exe)
> *       Multiprocessor, PAE (ntkrpamp.exe)
>
>
>
> Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe),
> highlight the System process, then choose View -> Lower Pane View -> DLLs
> and make sure that View -> Show Lower Pane has a check-mark.  Then scroll
> through the list of DLLs and observe which one matches the pattern
> ntXXX.exe.
>
>
>
> You can be using a PAE kernel without knowing it and without the /PAE switch
> in BOOT.INI.
>
>
>
> - Shao Miller
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>
> ------------------------------
>
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
> End of coLinux-users Digest, Vol 68, Issue 7
> ********************************************

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev

ram memory

  if i will let my colinux vm have 512 ram
how should the line in my config look like

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox

Colinux blue screen crashes

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox

_______________________________________________
coLinux-users mailing list
coLinux-users@...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: Contents of coLinux-users digest...

Hi, is it possible that you did not exclude this cofs images from windos index?
http://www.win-tipps-tweaks.de/cms/windows-7-tipps/tricks/windows-7-schneller-machen.html

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev

Is there any way to improve cofs performance?

Hi, I'm a new user, using coLinux 0.7.9 with the 2.6.33.7 kernel.   I'm using cofs for a certain
application, and it seems to be the bottleneck with throughput.   In 
researching this, it seems that cofs is just slow, and that's how it is, but I was wondering if there's any way
at all to speed it up.  I think I read that cofs already writes asynchronously, and that in tests -noatime
didn't seem to make a difference.  Is there anything else to try?   Any little performance gain
would really help out a lot.

Thanks!

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev