Try qemu and install FreeBSD 5.3

I believe you have heard of qemu. qemu is a well-known virtual machine like bochs. however, the performance and functions are relatively better than bochs. for example, why not run qemu when it supports ISO installation, DHCP gateway, and IMG images compatible with bochs? Haha, of course, there are also some shortcomings, but sometimes the operation is unstable, and the keyboard shortcut for switching the mouse is not properly designed, the two keys Ctrl + shift will be used first.

Well, considering that everyone uses Windows, I will write an example created in windows.
Let's take a look at the tools you want to prepare:
1. QEMU-0.6.1 on window
: Http://www.h6.dion.ne.jp /~ Kazuw/qemu-Win/qemu-0.6.1-windows.zip
2. FreeBSD's ISO disc ing. I recommend you download freebsdchina.org (my download speed reaches 1 MB)
Ftp://ftp.freebsdchina.org/pub/FreeBSD/ISO-IMAGES-i386/5.3/5.3-RELEASE-i386-disc1.iso
3. bochs IMG creation tool. Because qemu is compatible with bochs IMG images, this tool can be used to create
Well. Download The http://bochs.sourceforge.net/cgi-bin/topper.pl? Name = see + all + releases & url = http://sourceforge.net/project/showfiles.phpqmrkgroup_ideq12580

OK. Prepare for work.

First, use the bximage tool provided by bochs to create an IMG. Select HD, fat format, and the image size is-MB. The file name is C. IMG.

In addition, let's take a look at the qemu documentation, which supports ISO installation. One of the items is-boot. Then, select a (soft drive), C (hard drive), and D (optical drive) based on your needs) one parameter.
Because it is the first installation, we need to start from the CD and select D. In addition, the qemu time should be consistent with the time of your host, So we add a-localtime parameter.
Check out my startup parameters. You can also make this parameter into a bat file to start

Fb53.bat

Qemu.exe-L.-M 128-hda C. IMG-cdrom f:/download/5.3-RELEASE-i386-disc1.iso-boot D-localtime

Save and you can use it. the first use of FreeBSD is nothing special, that is, the installation process of FreeBSD, and 5. X is the same (For details, refer to other tutorials), but xfree86 is replaced with Xorg. because I didn't plan to test Xorg, I don't need to worry about it. Let's install a system first.

Let me talk about my installation method. I chose mini installation and installed SRC and man manual. Basically, there is no space. in addition, remember to allocate a swap partition with a size of about 64 MB during installation. this is the recommended installation for FB.

Qemu provides a virtual ne2000 Nic. Therefore, when you select the PPP/net work configuration, select the DHCP mode to obtain network support, which is more convenient than bochs.

For more information about the qemu DHCP gateway, see the qemu English document.

After installation, exit the Install Menu and disable qemu. Change the fb53.bat file and change-boot d to-boot C, so that the disk can be started.

By simply installing fb5.3 on qemu, I think qemu is much more convenient than bochs, with fewer resource consumption than VMware and a much faster speed than bochs. So I recommend you use this virtual machine.
Back to our topic, FreeBSD's network performance is slightly better than Linux, and the thread is slightly worse than Linux. After 5.3, I heard that it is doing well and I have never tested it.
Let's take a look at the pthread description in release note:

The well-known libkse is named libpthread and becomes the default thread library on the i386, amd64, and IA64 platforms. The-pthread option of GCC is modified to use libpthread instead of the original libc_r. Note: use an earlier compiled program (for example, ports compiled before this modification) to map libc_r and/or libkse to libpthread using libmap. conf (5. Note: drivers and libraries provided by NVIDIA must use libmap. conf (5) to map libpthread references to libc_r, because these tools cannot run correctly together with libpthread.   Libpthread currently supports libpthread_system_scope environment variables in forced mode (using a visible system thread ). It should be noted that the-dsystem_scope_only parameter can also be used to force the mode when compiling libpthread, which is also the default setting for architectures that do not currently support the M: N mode. In addition, you can also use the libpthread_process_scope environment variable to force the M: N mode (using the thread visible to the process ). For example: % Libpthread_system_scope = Yes threaded_app The application threaded_app will be forced to use a thread visible to the system, while % Libpthread_process_scope = Yes threaded_app Then it is forced to use a thread visible to the process.

Haha. You can check it out.
Http://cvs.freebsd.org.cn /~ Delphij/relnotes/i386/article.html # releng

Delphij is really the boss.

Okay. Let's talk about it briefly. I was planning to add this part of the firewall, but I am not very familiar with this aspect. Let's take a look at other people's information on this aspect.
For everyone to refer to an article http://journal.cnfug.org/issue14/000082.html
Up. daze God