Many "hardened" systems (eg. SSP/ProPolice) interfere with the way QEMU does dynamic code generation. The general solution is to disable these systems for QEMU. The QEMU design involves generating and running code on the fly, so it's unlikely these would provide any meaningful protection anyway. gcc-config -l (shows you a list of available cc) gcc-config i686-pc-linux-gnu-3.3.6-hardenednopiessp (use the correct version) source /etc/profile emerge qemu-cvs gcc-config i686-pc-linux-gnu-3.3.

On Windows XP/2K you can try to boot from the flash drive like so: qemu -hda //./PhysicalDriveN ... where N is the drive number found in the disk manager.

Why isn't full-screen mode "full screen"? The only thing I get is an original sized output with a full-screen border.

When using the db-2 library which comes with glibc is used in the Perl db modules the testsuite is not passed. This did not happen with db-1, gdbm, or ndbm. The pow() inline function I get when including <math.h> is broken. I get segmentation faults when I run the program.

Be sure that your build directory is mounted such that it has the same path either as a cygwin path ('/build/xemacs') or as a Windows path ('c:\build\xemacs'). Specify the target location of the extra libs on the command line to 'configure', e.g.for 21.4 or earlier './configure --site-prefixes=/build/libs i586-pc-mingw32' and for 21.5 or later './configure --with-site-prefixes=/build/libs i586-pc-mingw32'.

to be on a separate partition from your Mac OS X installation.</note>Gentoo Linux/PPC?</uri>

Currently, the same as -O2 (GCC 2.5) or -O3 (GCC 2.6, 2.7). Any number greater than that does the same thing. The Makefiles of newer kernels use -O2, and you should probably do the same.

I have set up /etc/nis.conf, and the Linux libc 5 with NYS works great. But the glibc NIS+ doesn't seem to work. Under Linux/Alpha, I always get "do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused" when using NIS.

Short answer: No. QEMU does not support creating a partition table/MBR on the fly. You need to use "/dev/hda" (e.g. the entire hard disk). Note: An experimental patch has been released that adds this functionality. You need to pass "-hda part:/dev/hda1" instead of "-hda /dev/hda". QEMU will then create an MBR and partition table on the fly for /dev/hda1. Changes to the MBR or partition table are lost when restarting QEMU.

This is an SDL bug. Specifically, SDL is using a 32-bit visual provided by Xgl, which causes pixels to be specified in RGBA format. SDL has a bug that makes it (wrongly) specify alpha blending for its windows. You can work around this by doing 'XLIB_SKIP_ARGB_VISUALS=1; export XLIB_SKIP_ARGB_VISUALS' before running QEMU.

The QEMU monitor can be redirected else where using the -monitor specifier. For example, you can have the monitor listen on a host port for remote connections via telnet/netcat/etc (example will be added later).

From: libes (Don Libes) To: wren@io.nosc.mil Subject: Compile fails with: Don't know how to make pty_.c > I'm trying to compile Expect on hpux 9.01, > downloaded from ftp.cme.nist.gov expect.tar > after running config > the make fails with "Don't know how to make pty_.c. (compile fails) > I see three versions pty_sgttyb.c, pty_termios.c and pty_unicos.c in > the load, but the configure picked none of them. > I tried forcing to pty_termios.

Currently, the same as -O2 (GCC 2.5) or -O3 (GCC 2.6, 2.7). Any number greater than that does the same thing. The Makefiles of newer kernels use -O2, and you should probably do the same.

This is answered below in the question "How do I know that Gridfinity is safe and won't harm my computer?".

You probably have not set up the ramdisk in /dev/shm. Add the following line to /etc/fstab: tmpfs /dev/shm tmpfs defaults 0 0

A workaround for those who must have 2 CD-ROMs visible at the same time is to use vvfat. Mount one of the CD-ROMs, and pass it as a hard disk via -hdd fat:/mnt-point. These will look like hard disks to the guest OS, and thus are not removable.

In the monitor, the "eject" command will remove the disk. The "change" command will insert a new one. If you are changing real disks (e.g. QEMU is using the host CD-ROM drive and you are changing physical CD-ROM disks) then it is recommended that you eject the CD-ROM from QEMU, and then change physical CD-ROM disks, and then use the "change" command in the monitor to reinsert the host CD-ROM disk.

Long answer: Once installed, Windows has only the minimal drivers required to boot the hardware on your computer - which happens to be completely different from what QEMU emulates. Windows 9x has enough problems with this, but Windows NT is especially fickle. You may be able to boot Windows 95 or 98 work from QEMU this way (there have been a few reports of success), but if you want to try we can not help you. You are better off installing Windows into a disk image.

It depends. Initial support for USB device proxy and emulation is now available in QEMU 0.8.0. From Fabrice Bellard's email to the QEMU developers list: I just committed an initial USB support for QEMU. This USB layer will ultimately enable QEMU to use some host USB devices and to simulate USB devices. WARNING: the current USB support is for USB hackers only - it is not meant to be fully usable yet. Flash drives have been reported to work.

Sort-of. Doing so will likely violate The Mac OS X End User License. QEMU does not emulate X86 Mac hardware, however some people have reported success hacking OS X to run on regular PC hardware (ie. qemu).

the time of this writing, it doesn't completely work yet. Darwin/PPC does work. Note that this has the same legal issues as X86 OS X.

Long answer: This generally requires cooperation from the guest OS/drivers (Like with Xen). Developers might be interested in the patch posted to the qemu-devel mailing list a while back which allowed for limited PCI proxy support on Linux hosts. You can find this here: more discussion here: http://lists.gnu.org/archive/html/qemu-devel/2005-03/msg00301.html and here: http://lists.gnu.org/archive/html/qemu-devel/2006-01/msg00082.html

Check out the Q project: http://www.kju-app.org/kju/. I have tested it briefly, and it works well so far. It is in Alpha officially but feels more advanced than alpha to me. Alternatively Parallels is the mainstream proprietary software. Also works well, although is a RAM hog, especially with two guests. You can try the PDtweaker module for Unsanity's Application Enhancer to make it work smoother. I couldn't make APE work on 10.4.7 though.

Since QEMU 0.9.0, the IDE emulation uses async transactions for DMA transfers. This employs the Linux AIO functionality that uses kernel threads. Making QEMU itself thread safe is an important goal for things such as allowing multiple cores (SMP). QEMU is not a cycle accurate emulator so some of this information is not going to be possible. Please use 'qemu -d ?' for a listing of items that can be logged. The QEMU build allows for it to be profiled via gprof.

A hardened server is a server in which the software has been modified to make it harder to attack. However, some servers are "harder" than others. There are a couple of ways to harden a server. The simplest way, and the least effective, is to run a set of scripts on a standard OS install. This confirms somewhat current patches and turns off services that could be exploited.

Hardening involves heating the part past a so-called "transition" temperature that varies slightly with the type of steel but usually lies around 1450?F (the metal becomes red hot at this temperature) and then dropping it into a bath of water or oil to quickly cool it, an operation called quenching. Quenching leaves the steel very hard but also quite brittle, somewhat like glass. Thus another heating operation is required to stabilize the steel and make the part more resistant to breakage.

Yes, they are hardened, tempered and ready to use after putting on your handle. You will probably have to clean and resharpen after assembly.