On Tue, 5 Dec 2000, Peter Samuelson wrote:
> [Tigran Aivazian]
> > I think 'flags' is what it used to be called ages ago but that is
> > irrelevant -- everyone presumably already changed all their software
> > to use 'features' (I did, for example) and forgot about the old
> > 'flags' forever
> > presumably already changed all their software to use 'features' (I did,
> > for example) and forgot about the old 'flags' forever
>
> Blessed vmware-config.pl contains
>
> \(flags\|features\).*
>
> so it should run...
vmware-config as used by the other 99.% of people does not
-
To
[Tigran Aivazian]
> I think 'flags' is what it used to be called ages ago but that is
> irrelevant -- everyone presumably already changed all their software
> to use 'features' (I did, for example) and forgot about the old
> 'flags' forever
Ages ago? s/flags/features/ happened in test11pre5.
On 5 Dec 00 at 12:25, Tigran Aivazian wrote:
> In case you haven't noticed yet -- the 'features' field of /proc/cpuinfo
> has been changed again so vmware won't run anymore. The fix is just as
> obvious as the previous one -- to change /usr/bin/vmware-config.pl script
> from grepping for 'featur
Hi Petr,
In case you haven't noticed yet -- the 'features' field of /proc/cpuinfo
has been changed again so vmware won't run anymore. The fix is just as
obvious as the previous one -- to change /usr/bin/vmware-config.pl script
from grepping for 'features' to grep for 'flags'. I think 'flags' is w
5 matches
Mail list logo
