It turns out that the below patch from 2007 has broken it. Now if
anybody knows where the mailing list archive has gone and how to
find the thread related to this patch ...
For the time being you can circumvent the problem by removing the whole
if (
FCheck
On Fri, Nov 18, 2016 at 10:33:20PM +, Jürgen Hartmann wrote:
> > A short update: Version 6.0.6 requires an old kernel, version
> > 12.5 is downloading now (which is a matter of several hours given
> > the local internet speed).
>
> Player 6 <-> Workstation 10 supp. kernel 3.1.0 to
> A short update: Version 6.0.6 requires an old kernel, version
> 12.5 is downloading now (which is a matter of several hours given
> the local internet speed).
Sorry, I should have mentioned that this might be an issue.
Each version of Vmware Workstation or Player supports only very few version
On 19/11/16 06:22, Dominik Vogt wrote:
> It war certainly fun to code. :-)
^
And a fight to debug? ;-)
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
signature.asc
Description: OpenPGP digital signature
A short update: Version 6.0.6 requires an old kernel, version
12.5 is downloading now (which is a matter of several hours given
the local internet speed). I'll have to find some 64-bit box to
run it.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
On Fri, Nov 18, 2016 at 12:18:15PM -0700, Jaimos Skriletz wrote:
> On Wed, Nov 16, 2016 at 4:43 PM, David Niklas wrote:
> > On Fri, 11 Nov 2016 23:13:49 +
> >
> > Not so much a question as a comment.
> > Many window managers and desktop environments have tried in vain to create
> > an automati
On Wed, Nov 16, 2016 at 4:43 PM, David Niklas wrote:
> On Fri, 11 Nov 2016 23:13:49 +
>
> Not so much a question as a comment.
> Many window managers and desktop environments have tried in vain to create
> an automatic menu generator without success, I recommend that fvwm does
> not attempt to
On Fri, 11 Nov 2016 23:13:49 +
Thomas Adam wrote:
> Hello all,
>
> For those of you who follow fvwm-workers@ may already know some of
> this, but for those of you who don't, it's worth mentioning what the
> state of fvwm development holds for the future.
>
> We have been discussing a lot ab
