> Too bad, that the vmware port isn't part of the ports tree and > doesn't have a version number in the file name. Otherwise it > would be more easily possible to communicate the exact software > release status. I think the idea just now is to avoid having people that complain quickly like you and crabby people like me colliding over the period in which rapid changes are being made. I'm sure there'd be more of these exchanges otherwise. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- can't get vmware to run ( on -current ) Andreas Klemm
- Re: can't get vmware to run ( on -current ) Mike Smith
- Re: can't get vmware to run ( on -current ) Andreas Klemm
- Re: can't get vmware to run ( on -current... Mike Smith
- Re: can't get vmware to run ( on -cur... Andreas Klemm
- Re: can't get vmware to run ( on... Mike Smith
- Re: can't get vmware to run ... Andreas Klemm
- Re: can't get vmware to run ( on -current... Julian Elischer
- Re: can't get vmware to run ( on -current ) Andreas Klemm
- Re: can't get vmware to run ( on -current... Mike Smith
- Re: can't get vmware to run ( on -current... Vladimir N. Silyaev
- Re: can't get vmware to run ( on -cur... Peter Wemm
- Re: can't get vmware to run ( on -current ) Julian Elischer
- Re: can't get vmware to run ( on -current ) Vladimir N. Silyaev