From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] process start time in future
Date: Fri, 28 Nov 2003 20:42:09 +0100 [thread overview]
Message-ID: <200311282042.09602.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <007501c3b535$79848d10$2000000a@schlepptopp>
Alle 23:26, giovedì 27 novembre 2003, roland ha scritto:
> btw: is jeff the only person doing development or patchmerging/bugfixing
> most of the time?
He is not the only one who develops UML: there is a whole bunch of patches
coming in, even if he is the only one with write access to the official
CVS/BitKeeper(I don't know which one) repository, as long as I know. Just as
the main kernel.
> is uml primarily a "one man" thing and uml dies, if jeff
> looses interest one day? i don`t hope so... but i really wonder anyway,
> that there is so few traffic on the mailinglists.
That's not true, provided you don't compare to the LKML...
> is uml still so "exotic"
> that so few people actually seem to be interested?
A few people? It's inside Debian(Matt Zimmerman is the maintainer), it's
bundled inside SuSE 9.0(we have often mail from SuSE labs)
1) it is very interesting: some things simply can't be done without it.
For instance, if you have a switched LAN, instead than one with a hub, to
install NIDS you normally need hardware support(i.e. a port on the switch,
connected to the NIDS, replicating what goes out from another port); and then
a devoted machine, only to run Snort...
2) it's widely used and will be more, since it has been included inside
official 2.6(even if you still need some patches :-( ); there are various
hosting providers providing virtual servers using it; in Italy, for instance,
one of these advertises on a lot of widely distributed informatic reviews...;
I've also read a lot of articles speaking about it.
> maybe everybody has
> vmware already... ;)
VMware is not free software and since it goes emulating hardware, it should
have more overhead; said that, I have no benchmark to show this. But if UML
were slower, it would only need tuning. Note that normally, UML memory is put
on a disk file, so it IS slower. But if you put /tmp on tmpfs(i.e. in RAM),
this goes away.
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-12-01 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 19:31 [uml-devel] process start time in future Johannes Formann
2003-11-27 22:26 ` roland
2003-11-28 19:42 ` BlaisorBlade [this message]
2003-12-01 22:57 ` Henrik Nordstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200311282042.09602.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox