[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [SLUG] Win4Lin vs VMWare
On Sun, 4 Jun 2000, Del wrote:
> The two programs also take a different approach to sharing files. VMware
> has a virtual disk for each VM, which appears as a single monolithic
> file on Linux, and is limited to 2GB. To share files between a VM
> running NT and the host Linux system, you need to set Linux up as a
> SAMBA server and share these files using the SMB (networking) protocol.
> Win4Lin uses a directory ($HOME/win) in each user's home directory to
> represent the Windows C: drive, and files in that area area are shared
> between Linux and Windows. The Win4Lin documentation does state, however,
> that these files should not be used by Linux while Win4Lin is running,
> because of the buffering algorithms used (and presumably, Win4Lin does
> no file locking).
You can however, map other drive letters to file systems, and have locking
happening fine.
> The Win95/98 directory tree used by Win4Lin is self contained. That means
> that, having built the tree and then shut Win4Lin down, the tree can be
> replicated across systems using tar/cpio or similar methods. One limitation
> is that the tree cannot be shared across NFS links (this is rather serious
> in an enterprise environment as it limits the ability for each user to have
> a "roving desktop" shared from a central NFS server). This allows the
> fast rollout of Win95/98 desktops and applications to a group of Linux
> systems.
This is true, however I have a better option...
Win4Lin does use the X-Protocol, and it does run quite well remotely.
(Not so great over modem) But quite usable over 10Meg Ethernet, and
VERY fast under 100).
Anyway.. Win4Lin server.. will do the same thing as Win4Lin client
edition, but allow you to run many on the same machine.
This means, you can effectively do what NT and Metaframe does, without NT.
Currently Win4Lin server is in beta, and pricing is currently being
negotiated. But, it's safe to say that it's going to be VERY competitive
compared to running NT+Terminal-Server+Metaframe.
Imagine.. a nice big grunty Linux box.. with Win4Lin server on it.. and
then a number of cheap thin client terminals.. (Say like the Echidna thin
clients).. All being delivered X and Windows applications to the desktop,
without all the admin nightmares of running PC's. Much lower TCO (Hate to
use TLA's.. but.. it means Total Cost of Ownership). These thin client
terminals are approx $550 ex tax in quantity.
One server to backup, all the clients are solid state.. (Plug and
play <grin>). One system to look after, centralised administration..
Gosh.. What a NEW concept that is...... NOT.
Once Citrix Server for Linux is out, the possibility of delivering these
"Win4Lin'ed" Applications and other X apps via low speed links like the
Internet or modem become a possibility, opening up huge new avenues of
interest from ASP companies.
If I can arrange enough portable equipment, I would like to demonstrate
all this stuff in action, perhaps at the next SLUG meeting?
I just need a beefy laptop, and some monitors/keyboard/mice for the thin
client terminals. (And a hub'n'stuff).
---
Anthony Rumble
LinuxHelp http://www.LinuxHelp.com.au Phone: 0500 500 368
Direct 02-9712-1799 Mobile 0412-955-042 Fax 02-9712-3977
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to slug-request@nospam.slug.org.au with
unsubscribe in the text