faum-node-pc(1) [debian man page]
FAUM-NODE-PC(1) Reference Information FAUM-NODE-PC(1) NAME
faum-node-pc - Start a virtual machine SYNOPSIS
faum-node-pc [-h] [-B dirname] [-D n] [-d] [-k keymap] [-g guitype] [-a audio_module] [--sparse] DESCRIPTION
faum-node-pc starts a virtual machine. OPTIONS
-h print short explanation -B dirname Use directory dirname to creating temporary files and disk image files. As a default node.def in the will get used. -D n set debug level to n -d turn on debugging (short for -D 1) -k keymap set the key translation map to keymap -g guitype Use guitype, where guitype is one of gtk or null. null disables the GUI entirely, useful for running automated experiments. gtk is the default. -a audio_module Use audio_module, where audio_module is one of alsa1x, esd, file, macosx, oss, pulse or null. Not all modules may be available for your system. By default, the best available audio module is chosen. --sparse Enable usage of sparse files for all generated media images, like hard disc images. Please use this option only, if you know that you've got sufficient disk space. EXAMPLES
To run faum-node-pc, you must have a precompiled system.ic that specifies the setup of the simulated PC as well as a simulation.setup that determines simulation specific parameters in your working directory. You can use fauhdlc to compile a structural VHDL setup into a system.ic file. FAUmachine comes with a number of example experiments in /usr/share/faumachine/experiments. To run such an experiment, you can use make -f /usr/share/faumachine/experiments/<experiment>/Makefile experiment. ENVIRONMENT
FAUM_AUDIO Specifies the desired audio module to use. Same as the -a option. FAUM_SPARSE Set to 1 to use sparse files for all media files. FAUM_GUI Specifies which gui to use. Same as the -g option. BUGS
Please report all bugs to info@faumachine.org[1]. SEE ALSO
fauhdlc(1) AUTHOR
This manual page was written by the FAUmachine Team[1]. CONTACT
Webpage[2] Project Team[1] AUTHOR
FAUmachine team COPYRIGHT
Copyright (C) 2000-2009 FAUmachine team. Developed at Friedrich Alexander University Erlangen-Nuremberg. FAUmachine comes with ABSOLUTELY NO WARRANTY. FAUmachine is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. See COPYING for details. NOTES
1. info@faumachine.org mailto:info@faumachine.org 2. Webpage http://www.faumachine.org/ FAUmachine 06/21/2012 FAUM-NODE-PC(1)
Check Out this Related Man Page
savecore(8) System Manager's Manual savecore(8) Name savecore - save a core dump of the operating system Syntax /etc/savecore [ options ] dirname [ system ] [ corename ] Description The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and writes a reboot message in the shutdown log. The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which increments each time is run in that directory. After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a form familiar to the program. Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out the core file (assuming that a core dump was taken). The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string in the shut down log. For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image files, you must use the command. The command has a conversion option to create sparse output files. Options -c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the option with caution, because once it clears the core dump, the core dump cannot be retrieved. -d dumpdev dumplo Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro- gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image that crashed, the option provides the correct dump device and dump device offset. -e Saves only the error logger buffer into a file. If used, core or namelist images are not saved. -f corename Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option is used only for diskless workstations. If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the running image is After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or failed. Files Shut down log Current running ULTRIX system See Also dd(1), uerf(8) savecore(8)