Chris Ball wrote:
>> I think we could run prelink on the OLPC images from within
>> pilgrim, just before converting it to jffs2.
>
>> It will result in a slight speedup in startup time, but nothing
>> compared to importing modules that dominates startup time of the
>> Python a
On Oct 5, 2007, at 23:36 , Bernardo Innocenti wrote:
>
> The base address of processes are randomized for
> security on several Linux distributions, including
> Fedora.
>
> You can disable it globally by doing this:
>
> echo 0 >/proc/sys/kernel/randomize_va_space
>
>
> But this, of course, it not a
Hi,
> I think we could run prelink on the OLPC images from within
> pilgrim, just before converting it to jffs2.
> It will result in a slight speedup in startup time, but nothing
> compared to importing modules that dominates startup time of the
> Python activities.
Actually, I di
On 10/05/2007 03:28 AM, Bert Freudenberg wrote:
> Would that be possible with the virtualization containers?
I don't think vservers messes around with the virtual
address space of processes.
> Btw, if I'm not mistaken, the Linux loader does something similar, so
> if the relocating step could
Hi folks,
once security containers are enabled, each activity basically "owns"
the box, right? It will basically feel alone in both the file system
as in memory, appearing as a single task. This might make some
optimizations possible that otherwise aren't in a generic multi-
tasking OS.
On
