> > The Hurd can run in parallel to itself. If it can run in parallel to other
> > OSs depends if those OSs can run on Mach, and if you have a bootloader for them
> > that runs in the Hurd.
>
> If I understood Farid correctly, he ran the Hurd beside Lites.
Yes, that's correct.
-Farid.
--
Fari
> What about it? The Hurds don't know about each other. There are no ports
> from the one Hurd accessible to the others (well, I should say almost no
> ports, but it's the user starting the sub-Hurd who eventually will be able
> to decide). In particular, no privileges are leaked.
Well, boot i
On Wed, Nov 07, 2001 at 07:19:23PM +, Patrick Strasser wrote:
> I think a sub-Hurd is the Hurd's way of doing this at the moment. What
> can it do for us in this direction,
It can already do everything. It runs its own filesystems, its own proc
server, its own pfinet server, and has its own
Hi,
I followed a link to our beloved Slashdot [1] and found a discussion
about a kernel patch using the new Linux capabilities system (since 2.2)
and introducing a
new kernel call. It is called vserver [2] and was anounced on the linux
kernel mailing list on 11 Oct. 2001.
>From what I read in t
