Root users can not escape a chroot with/... The very meaning of ".." has been irrevocably changed in a chrooted process, and that new root is inherited by all descendants.
Here is an example:
~ $ mkdir tmp ~ $ sudo ~ # touch tmp/CHROOT-LAND ~ # dir tmp total 12 4 drwxrwxr-x 2 augart augart 4096 feb 28 13:34./ 8 drwxr-xr-x 105 augart augart 8192 feb 28 13:34../ 0 -rw-r--r-- 1 root root 0 feb 28 13:34 CHROOT-LAND ~ # chroot tmp chroot:/bin/bash: No such file or directory ~ # mkdir tmp/bin ~ # mkdir tmp/lib ~ # mkdir tmp/sbin ~ # cp/sbin/sash tmp/sbin ~ # chroot tmp/sbin/sash Stand-alone shell (version 3.4) > -ls . .. CHROOT-LAND bin lib sbin > cd/.. > -ls -l drwxrwxr-x 5 167108 4475 4096 Feb 28 18:37. drwxrwxr-x 5 167108 4475 4096 Feb 28 18:37.. -rw-r--r-- 1 0 0 0 Feb 28 18:34 CHROOT-LAND drwxr-xr-x 2 0 0 4096 Feb 28 18:35 bin drwxr-xr-x 2 0 0 4096 Feb 28 18:37 lib drwxr-xr-x 2 0 0 4096 Feb 28 18:37 sbin
They have it, why not create a sourceforge like site for their own projects
IBM has done that for several years, and is trying to turn this over to professionals like SourceForge who have this as their core competency. My project, Jikes RVM, is one of the thirty that's been transferred. For the past three years, we'd been hosted on IBM's developerWorks.
or do they plan to donate some money to it to help it all as a whole??
They don't just "plan to". They made a donation (I don't know how big) to SourceForge and paid them to assist with the transfer of the projects.
I'm pleased about the move; being there with other Free Java projects will make it easier for folks looking for a free runtime environment for Java to find us.
I'm at IBM Watson, down the hall from one of the Performance Explorer (PE) guys, and I just went up to ask about it.
PE did indeed go over, and it's licensed under the IBM CPL, which is very similar to the Apache Public License (APL). The CPL isn't just "generally an open-source license," it's been certified as one by the OSDI.
One of the authors of PE is a graduate student, and he's been pretty busy with his own life right now. It probably won't make it out at the end of this month. We're nudging the authors, anyway. They just want to get the code into better shape for release.
PE is a sub-project of Jikes RVM, a free VM for Java project I develop on, and it's at http://jikesrvm.sourceforge.net . I'm sorry to say that, right now, the PE directory in our CVS repository is just a placeholder.
> > Now if they can just get x86 binaries to run on my P4, we'll be set!
> Hmm, you must be using Windows:
I assume by P4 the author meant "Power 4", the name Apple uses to describe a generation of PowerPC processors.
Even better than just having a modified reference counting scheme, it has a choice of memory managers you can plug in. You can write your own, too. The API for it is JMTk (the Java Memory management Toolkit).
Slashdot Mirror
I apologize for the rotten formatting in the ancestor to this post. As you can see, I am now using the <P> tag.
I'm at IBM Watson, down the hall from one of the Performance Explorer (PE) guys, and I just went up to ask about it. PE did indeed go over, and it's licensed under the IBM CPL, which is very similar to the Apache Public License (APL). The CPL isn't just "generally an open-source license," it's been certified as one by the OSDI. One of the authors of PE is a graduate student, and he's been pretty busy with his own life right now. It probably won't make it out at the end of this month. We're nudging the authors, anyway. They just want to get the code into better shape for release. PE is a sub-project of Jikes RVM, a free VM for Java project I develop on, and it's at http://jikesrvm.sourceforge.net . I'm sorry to say that, right now, the PE directory in our CVS repository is just a placeholder.
> > Now if they can just get x86 binaries to run on my P4, we'll be set! > Hmm, you must be using Windows: I assume by P4 the author meant "Power 4", the name Apple uses to describe a generation of PowerPC processors.
There's more info on the memory management system in the Jikes RVM user's guide.
The memory managers supported include: