Hello,
I was told recently that you are currently in the process of dumping oskit in favor of uclibc or dietlibc. For my work, I need the log_net server which only compiles with oskit. So I cannot abandon it. Are they any problems or reasons why one shouldn't use oskit? Is it possilble to use a mixed configuration (e.g. compile log_net with oskit and own packages with dietlibc and use them together)?
Thanks, Arthur
Hi Arthur,
(explicitly cc:'d to Björn Döbel, the maintainer of l4ore)
On Wednesday 30 November 2005 12:49, Arthur Mielimonka wrote:
I was told recently that you are currently in the process of dumping oskit in favor of uclibc or dietlibc. For my work, I need the log_net server which only compiles with oskit. So I cannot abandon it. Are they any problems or reasons why one shouldn't use oskit? Is it possilble to use a mixed configuration (e.g. compile log_net with oskit and own packages with dietlibc and use them together)?
There are several reasons, some of them are: - oskit is quite fat and complex. The internal COM interface makes it - oskit is not maintained anymore difficult to understand what happens if a new library is added - oskit1.0 is GPL
It should be possible to compile the log_net server using the oskit and compile the other parts of L4env with dietlibc or uClibc. However, it would make much sense to port the log_net interface to the new ore server (l4/pkg/ore). Björn, could you give an estimation about the effort to port log_net to ore?
Frank
Hello,
On Wed, Nov 30, 2005 at 01:26:16PM +0100, Frank Mehnert wrote:
However, it would make much sense to port the log_net interface to the new ore server (l4/pkg/ore). Björn, could you give an estimation about the effort to port log_net to ore?
AFAIK the critical part of log_net is the TCP/IP implementation. I would skip the alternative Flips for its complexity. IMO a better solution is to use a small and simple network protocol implementation like
uIP http://www.sics.se/~adam/uip/
It comprises roughly 2000 LOC and is easy to understand and port.
What do you think?
Hi,
(explicitly cc:'d to Björn Döbel, the maintainer of l4ore)
I am also reading l4-hackers. :)
It should be possible to compile the log_net server using the oskit and compile the other parts of L4env with dietlibc or uClibc. However, it would make much sense to port the log_net interface to the new ore server (l4/pkg/ore). Björn, could you give an estimation about the effort to port log_net to ore?
After having talked to some people, the following steps seem to be necessary:
- log_net needs to be ported to use FLIPS instead of the oskit as its TCP-Stack - ORe does not provide TCP/IP. Christian assumes this should be easy. - we need to have an ORe driver for FLIPS.
I've put log_net on my todo list. The FLIPS driver was already on it.
Bjoern
Hello,
For my work, I need the log_net server which only compiles with oskit. So I cannot abandon it.
There now is a replacement for log_net, called log_ore in l4/pkg/lib/uip/log_ore. It builds with dietlibc. This log_net replacement uses the ORe network switch to communicate over the network and could be a solution for you.
log_ore's LOG handling is mainly copied from l4/pkg/dmon (a log client for DOpE). At the moment there is only support for standard LOG messages. I'll be working on binary channels asap, because this is what I need for my diploma thesis.
So far Bjoern
l4-hackers@os.inf.tu-dresden.de
-
Arthur Mielimonka -
Bjoern Doebel -
Bjoern Doebel -
Christian Helmuth -
Frank Mehnert -
Martin Pohlack