On Mon Sep 08, 2014 at 07:13:14 +, Masti Ramya Jayaram wrote:
Yes, I explicitly made sure that there are no extra characters by
setting the entire page of 4096 bytes to zero before copying over the
new config. I am not sure what you mean by changed the target - I
simply replace the config
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Checking executables before running them in L4re/fiasco
Hi,
On Fri Sep 05, 2014 at 12:29:15 +, Masti Ramya Jayaram wrote:
Thanks for the information. I have two issues/questions:
a. I looked at the move_modules (which does not do much in my
Hi,
On Fri Sep 05, 2014 at 12:29:15 +, Masti Ramya Jayaram wrote:
Thanks for the information. I have two issues/questions:
a. I looked at the move_modules (which does not do much in my case) and I
tried to replace the linux.cfg from
Compiled in version:
Subject: Re: Checking executables before running them in L4re/fiasco
On Wed Sep 03, 2014 at 14:43:59 +, Masti Ramya Jayaram wrote:
You mean binaries that are started?
Yes but some modules have dependencies (like the Io server and
examples of target dependencies include libsigma). Is there a way to
find all of them?
Ok, you mean all the libraries that are
executables before running them in L4re/fiasco
On Tue Sep 02, 2014 at 14:08:03 +, Masti Ramya Jayaram wrote:
Also, could you elaborate a bit on how one could have smaller
components? I decided to do it at bootstrap at the moment because I
realized that using the IO server also means including
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Adam
Lackorzynski [a...@os.inf.tu-dresden.de]
Sent: 01 September 2014 23:57
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Checking executables before running them in L4re/fiasco
Hi,
On Mon Sep
@os.inf.tu-dresden.de
Subject: RE: Checking executables before running them in L4re/fiasco
Thanks for the suggestions. From what you say, I guess it is best to do
something between ned and say vmlinuz. It also makes better sense semantically
(the kernel has booted and checks if the application is ok
there.
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Masti
Ramya Jayaram [rma...@inf.ethz.ch]
Sent: 02 September 2014 09:57
To: Adam Lackorzynski; l4-hackers@os.inf.tu-dresden.de
Subject: RE: Checking executables before running them in L4re/fiasco
Thanks
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Adam
Lackorzynski [a...@os.inf.tu-dresden.de]
Sent: 01 September 2014 00:14
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Checking executables before running them in L4re/fiasco
On Sat Aug 30
Hi,
On Mon Sep 01, 2014 at 07:54:02 +, Masti Ramya Jayaram wrote:
Thanks for the suggestion. I have one other constraint: I would like
to keep trusted computing base (or the amount of security critical
code as small as possible).
From what I understand from
On Sat Aug 30, 2014 at 14:02:41 +, Masti Ramya Jayaram wrote:
I am using fiasco/l4re to run applications (say hello world) and
L4linux. The module list in the two cases looks like this:
entry hello-cfg
kernel fiasco -serial_esc -freq=533000
roottask moe rom/hello.cfg
module l4re
12 matches
Mail list logo
