Running Windows "inside" a Linux-like OS?


 
Thread Tools Search this Thread
Operating Systems Linux Running Windows "inside" a Linux-like OS?
Prev   Next
# 1  
Old 12-25-2007
Running Windows "inside" a Linux-like OS?

I'd like to know if it's possible to run Windows "inside" a Linux-like OS similar to how you can run Linux in Windows, rather than dual-booting them both. As I mentioned in an earlier post, I want to do some serious parallel computing which Windows isn't even capable of at the moment... But I'd also like to do *everything* Windows can do, not that I'm in love with Windows or anything. I hope one of you guys know the answer to this. Thanks.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. 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

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. 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
Login or Register to Ask a Question
lx(5)							Standards, Environments, and Macros						     lx(5)

NAME
lx - Linux branded zone DESCRIPTION
The lx brand uses the branded zones framework described in brands(5) to enable Linux binary applications to run unmodified on a machine with a Solaris Operating System kernel. The lx brand includes the tools necessary to install a CentOS 3.x or Red Hat Enterprise Linux 3.x distribution inside a non-global zone. The brand supports the execution of 32-bit Linux applications on x86/x64 machines running the Solaris system in either 32-bit or 64-bit mode. Supported Linux Distributions The lx brand emulates the system call interfaces provided by the Linux 2.4.21 kernel, as modified by Red Hat in the RHEL 3.x distributions. This kernel provides the system call interfaces consumed by the glibc version 2.3.2 released by Red Hat. In addition, the lx brand partially emulates the Linux /dev and /proc interfaces. Configuration and Administration The lx brand supports the whole root non-global zone model. All of the required linux packages are installed into the private file systems of the zone. The zonecfg(1M) utility is used to configure an lx branded zone. Once a branded zone has been installed, that zone's brand cannot be changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used to log in to the zone. Application Support The lx zone only supports user-level Linux applications. You cannot use Linux device drivers, Linux kernel modules, or Linux file systems from inside an lx zone. You cannot add any non-standard Solaris devices to a Linux zone. Any attempt to do so will result in a zone that zonecfg(1M) will refuse to verify. You cannot run Solaris applications inside an lx zone. Solaris debugging tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be applied to Linux processes executing inside the zone, but the tools themselves must be running in the global zone. Any core files generated are produced in the Solaris format, and such files can only be debugged with Solaris tools. ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWlxr, SUNWlxu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M), brands(5), zones(5), lx_systrace(7D) SunOS 5.11 19 Sep 2006 lx(5)