From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C2abN-0007FN-PD for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:17:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C2abL-0007D3-6q for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:17:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C2abJ-0007Cx-BE for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:16:59 -0400 Received: from [159.178.60.122] (helo=trend1.shands.ufl.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C2aWL-0006Se-Dr for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:11:49 -0400 Message-Id: Date: Wed, 01 Sep 2004 15:11:30 -0400 From: "Thomas Munn" Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__PartF3D389F2.0__=" Subject: [Qemu-devel] Attitute and Predisposition of the List & newbie documets Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=__PartF3D389F2.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit While I am not among those who are enlightened enought to talk about opcodes and their proper optimization, I do have a few observations to make, having watched this list for 2 months. 1. People really don't like newcomers on this list. 2. QEMU-USERS would be great, if it actually worked. I have asked on the list TWICE now, with absolutely no comment (or way to get qemu-users) working. The interface fails, and messages never get anywhere. Unless this is a tricky INTENT, in that users will just go to /dev/null. Which is fine, if the project just wants to be for gear heads. 3. QEMU is rather DIFFICULT to use. I have been a UNIX admin for 10 years, am fairly conversant in iptables etc. Yet my firewalling questions were ignored THREE times. Firewalling a host is a cool concept, I can have "trusted boxes" and make sure they only talk to whom they are supposed to. I figured out MYSELF that you have to filter on the FORWARD chain. No one was even kind enough to respond "RTFM" or "You need to filter on the forward chain." Its Not in the docs etc. Most people wouldn't be able to do this( e.g figure out how to firewall guest os). Again, if you want gearheads only, then fine. 4. I am compiling a list of my difficulties, and will be writing documentation to help people setting qemu for the first time. The existing documentation simply does not cover in high detail how to get qemu working. For example, I found it very confusing on what qemu-fast is for. A simple "QEMU-FAST ONLY works with linux at this time. You must install a working GUEST image, apply the appropriate patch to the GUEST kernel, and then run qemu-fast. DO NOT TRY to use QEMU-FAST otherwise. It will simply segfault! I will be posting the document to this list. If anyone else has any suggestions, I will incorporate them into a professional, and complete document designed for the newcomer. My perspective of this document, will, alas, only be from the linux corner, as I do not use QEMU in windows......(as a host os) Something akin to the GENTOO install handbook would be the caliber I would be shooting for. Sincerely, Thomas J. Munn --=__PartF3D389F2.0__= Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML
While I am not among those who are enlightened enought to talk about = opcodes and their proper optimization, I do have a few observations to = make, having watched this list for 2 months.
 
1.  People really don't like newcomers on this list.  =
2.  QEMU-USERS would be great, if it actually worked.  I = have asked on the list TWICE now, with absolutely no comment (or way to = get qemu-users) working.  The interface fails, and messages never get = anywhere.  Unless this is a tricky INTENT, in that users will just go = to /dev/null.  Which is fine, if the project just wants to be for = gear heads.
3.  QEMU is rather DIFFICULT to use.  I have been a UNIX = admin for 10 years, am fairly conversant in iptables etc.  Yet my = firewalling questions were ignored THREE times.  Firewalling a host = is a cool concept, I can have "trusted boxes" and make sure they only talk = to whom they are supposed to.  I figured out MYSELF that you have to = filter on the FORWARD chain.  No one was even kind enough to respond = "RTFM" or "You need to filter on the forward chain."  Its Not in the = docs etc. Most people wouldn't be able to do this( e.g figure out how to = firewall guest os).  Again, if you want gearheads only, then = fine. 
4.  I am compiling a list of my difficulties, and will be = writing documentation to help people setting qemu for the first time. = The existing documentation simply does not cover in high detail how to = get qemu working.  For example, I found it very confusing on what = qemu-fast is for.  A simple "QEMU-FAST ONLY works with linux at this = time.  You must install a working GUEST image, apply the appropriate = patch to the GUEST kernel, and then run qemu-fast.  DO NOT TRY to use = QEMU-FAST otherwise.  It will simply segfault! 
 
I will be posting the document to this list.  If anyone else has = any suggestions, I will incorporate them into a professional, and complete = document designed for the newcomer.
 
My perspective of this document, will, alas, only be from the linux = corner, as I do not use QEMU in windows......(as a host os)
 
Something akin to the GENTOO install handbook would be the caliber I = would be shooting for.
 
Sincerely,
 
Thomas J. Munn
--=__PartF3D389F2.0__=--