I believe everyone has heard of Qemu. Qemu is the same named Bochs. Only performance and functions are better than Bochs. For example, support ISO installation and network-based DHCP gateways and compatible IMG pictures compatible with Bochs Why don't you run qemu? Oh, of course, there is also a shortcoming, just sometimes running unstable, and switching the shortcut key for the mouse is unreasonable, using Ctrl Shift two keys. First.
Well. Considering everyone is using Windows. I will write an example created under Windows. Let's see what tools you want to prepare: 1. QEMU-0.6.1 on window Downloads: http: // www. H6.Dion.ne.jp/~kazuw/qemu-win/qemu-0.6.1-windows.zip 2. Freebsd's ISO CD map. I recommend going FreeBSDChina.org Download (my download speed reaches 1m) 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 image, so you can use this tool Come to create a um. Download http://bochs.source .net/cgi-bin/topper.pl?name=see all releases&url=http://sourceforge.net/project/showFiles.phpqMRKGROUP_IDEQ12580 OK. Ready to work Bar.
First create an IMG with the BXImage tool comes with Bochs. Select the image of the HD, FAT format, size of 300-500m. The file name is C.IMG.
In addition, we look at the QEMU document, support ISO installation, one of which, -boot, after you choose A (Soft Drive), C (Hard Drive), D (CD-ROM), one of the parameters. Because we are the first Secondary installation, so we need to start from the disc, choose D, in addition, QEMU's time should be consistent with your host, so add a -LOCALTIME to see my startup parameters, you can also put this parameter Made a BAT file to start
FB53.BAT
Qemu.exe -l. -m 128 -hda c.img-cdrom f: /downloadload/5.3-RELEASE-I386-DISC1.ISO -BOOT D -LOCALTIME is saved, it can be used. The first use is nothing special The freebsd installation process, and 5.x are the same (specific reference other tutorial), but Xfree86 is replaced with xorg. Because I didn't plan to test XORG, so I won't do this first. Let's take a look at a system.
I said my installation method, I chose MINI installation, then install the SRC, and the MAN manual, there is basically no space. In addition, I remember to allocate a size of about 64m. This is the recommendation of FB. installation.
QEMU provides a virtual NE2000 network card, so when choosing the PPP / NET WORK configuration, select the model with DHCP, so that you get web support, relatively more convenient than Bochs. For DHCP gateway, please refer to QEMU English documentation, I have more detailed, I will not repeat.: P
After installation, the exit install menu turned off and changed the file of FB53.bat, change -boot d to -boot C, so you can start from the hard disk.
Simply install FB5.3 on QEMU, I think the QEMU is more convenient for Bochs. The resource consumption is less than VMware, and the speed is much faster than Bochs. So I recommend you to use this virtual machine. Back to our theme, freebsd The network performance is slightly better than Linux, at a slight point than Linux. After 5.3, I heard that I have been doing better, I have not tested us to see the Release Note's description: About PTHREAD:
Libkse is named libpthread for people, and becomes I386, AMD64, and the default thread library on the IA64 platform. The GCC's -pthread option is modified to utilize libpthread instead of the original libc_r. NOTE: Using earlier compiled programs (for example, Ports compiled before this modification) should use libmap.conf (5) to map libc_r and / or libkse to libpthread. Note: Users using the drives and libraries provided by NVIDIA to use libmap.conf (5) to map the reference to libpthread to libc_r, because these tools cannot operate correctly with libpthread. LibPThread now supports libpthread_system_scope environment variables to force 1: 1 mode (using system-visible thread). It should be noted that the use -dsystem_scope_only parameter can also force 1: 1 mode when compiling libpthread, which is also the default setting on the architecture of M: N mode. Alternatively, you can also use the libpthread_process_scope environment variable to force M: N mode (using process visible thread). For example:% libpthread_system_scope = yes threaded_app will force application threaded_app to use system-visible threads, and% libpthread_process_scope = yes threaded_APP can force it to use process visible threads. Ha ha. You can see http://cvs.freebsd.org.cn/~delphij/relnotes/relnotes/i386/Article.html#releng
Delphij is really big.
OK. Simple telling here. Originally intended to put this part of the firewall, but I am not very familiar with this. Do you still look at other people about this information. For everyone to refer to an article http: / /journal.cnfug.org/issue14/000082.htmlup. Getting God
