Hi folks.
I'm currently in the middle of rolling out a new bunch of Linux
workstations, and now the time has come to think about a virtual Windows
environment. I'd rather use Win4Lin for various reasons, and I'd like
some ideas as to how deal with one major problem - license file
locations.
VMWare licenses live in ~/.vmware, so I can go ahead and install the
software on every machine and buy a license for each user who requires
one. This makes my build process more generic, and I'm happy as a
result. We use NIS and NFS mounted home directories, so any one user can
access the resources they are licensed for on any workstation if the
software is always there.
Of course, with Win4Lin there's more of a "per-machine" type arrangement
with the license kept in /var/win4lin/install which is slightly less
than ideal. Would it be feasable to have a script that played with
symlinks to redirect the file location to the user home directory? Is it
actually possible to change the location that is searched for the
license file?
The current arrangement also requires the license.txt file to be
readable by all users who might want to run Win4Lin. Not good for
machines that have a lot of public access. We'd be allowing anyone who
wants to run Win4Lin at home a free shot at our license info. We could
restrict it to a group, but that adds another layer of administration
which is easily avoided if the software could search a home directory.
Also, it'd be nice to be able to change the default location of the
personal install directory away from the home directory. Each new
workstation has a 20 gig hard drive that we're currently using less than
2 gig of. Using the home directory puts quite a load on the network that
doesn't need to be there. Is this possible, to anyone's knowledge? I
know it can be moved manually and the settings tweaked, but unless this
can happen by default, no user is going to bother, no matter how micely
they're asked.
I've got about a month to make a decision here. Any comments would be
good, especially ones pointing out any manual pages I forgot to read, or
mentioning things dealt with in 3.0. :)
Thanks,
Mike.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
