Sponsored Content
Operating Systems Linux Running Windows "inside" a Linux-like OS? Post 302153614 by pflink on Tuesday 25th of December 2007 10:06:35 PM
Old 12-25-2007
Yes you can. Look into WINE Wine HQ. I personally haven't implemented it yet, but have heard decent things about it.

pflink
 

3 More Discussions You Might Find Interesting

1. HP-UX

script running with "ksh" dumping core but not with "sh"

Hi, I have small script written in korn shell. When it is called from different script, its dumping core, but no core dump when we run it standalone. And its not dumping core if we run the script using "/bin/sh" instead of "ksh" Can some body please help me how to resolve this issue. ... (9 Replies)
Discussion started by: simhe02
9 Replies

2. Shell Programming and Scripting

Passing username and password to a script running inside "expect" script

Hi I'm trying to run a script " abc.sh" which triggers "use.sh" . abc.sh is nothing but a "expect" script which provides username and password automatically to the use.sh script. Please find below the scripts: #abc.sh #!/usr/bin/expect -f exec /root/use.sh expect "*name*" send... (1 Reply)
Discussion started by: baddykam
1 Replies

3. Shell Programming and Scripting

Failure: if grep "$Var" "$line" inside while read line loop

Hi everybody, I am new at Unix/Bourne shell scripting and with my youngest experiences, I will not become very old with it :o My code: #!/bin/sh set -e set -u export IFS= optl="Optl" LOCSTORCLI="/opt/lsi/storcli/storcli" ($LOCSTORCLI /c0 /vall show | grep RAID | cut -d " "... (5 Replies)
Discussion started by: Subsonic66
5 Replies
WINESERVER(1)							  Windows on Unix						     WINESERVER(1)

NAME
wineserver - the Wine server SYNOPSIS
wineserver [options] DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows. wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can be useful to start wineserver explicitly with different options, as explained below. OPTIONS
-d[n], --debug[=n] Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start- ing wineserver if the +server option is set in the WINEDEBUG variable. -f, --foreground Make the server remain in the foreground for easier debugging, for instance when running it under a debugger. -h, --help Display a help message. -k[n], --kill[=n] Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable. -p[n], --persistent[=n] Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever. -v, --version Display version information and exit. -w, --wait Wait until the currently running wineserver terminates. ENVIRONMENT VARIABLES
WINEPREFIX If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is $HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly independent Wine sessions. WINESERVER Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load /usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely locations. FILES
~/.wine Directory containing user specific data managed by wine. /tmp/.wine-uid The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the WINEPREFIX directory device and inode numbers. AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the file Changelog in the Wine distribution for the complete details. BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org> AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at http://www.winehq.org/. <http://www.winehq.org/> SEE ALSO
wine(1). Wine 1.2-rc6 October 2005 WINESERVER(1)
All times are GMT -4. The time now is 09:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy