* Ben Paley [EMAIL PROTECTED] [0729 22:29]:
Hello everybody,
If no-one responds this time I'll get the hint, please excuse me for
reposting, I'm just going out of my mind!
I'm getting a total crash every time I try to run vmware. This is my system:
bash-2.05b$ uname -a
FreeBSD
On Wednesday 21 July 2004 12:06, Dick Davies wrote:
etc, etc...
sod portupgrade - manually pkg_delete all the vmware crap, then pkg_add it.
On boot, I get this message:
kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file
or directory
-bash-2.05b# locate
On 7/20/2004 3:45 PM Thompson, Jimi wrote:
FreeBSD has 3 types of distros - CURRENT, STABLE, and
RELEASE. In order of increasing stability, they are:
CURRENT = currently in development (Alpha) and by far the least stable
of the 3
RELEASE = released to the populous at large (Beta) and fairly
On Wednesday 21 July 2004 10:20 am, Drew Tomlinson [EMAIL PROTECTED]
wrote:
On 7/20/2004 3:45 PM Thompson, Jimi wrote:
FreeBSD has 3 types of distros - CURRENT, STABLE, and
RELEASE. In order of increasing stability, they are:
CURRENT = currently in development (Alpha) and by far the least
On Jul 21, 2004, at 2:34 PM, Joshua Tinnin wrote:
Then why do I hear that 5.2.1-RELEASE is not ready to be called STABLE?
FreeBSD's -CURRENT tree has generally been reasonably stable, but there
have been periods (including quite recently with threading/#define
PREEMPTION) where -CURRENT has not
On Wednesday 21 July 2004 12:31 pm, Charles Swiger [EMAIL PROTECTED] wrote:
On Jul 21, 2004, at 2:34 PM, Joshua Tinnin wrote:
Then why do I hear that 5.2.1-RELEASE is not ready to be called STABLE?
FreeBSD's -CURRENT tree has generally been reasonably stable, but there
have been periods
On Jul 21, 2004, at 3:51 PM, Joshua Tinnin wrote:
[ ... ]
OK, as I understand, the branches are -CURRENT and -STABLE. But I
often see
4.10-STABLE recommended for production use. This is probably due to
what you
describe above.
That's right, 4.10 is the latest -STABLE release.
What does RELEASE
On Wednesday 21 July 2004 01:14 pm, Charles Swiger [EMAIL PROTECTED] wrote:
On Jul 21, 2004, at 3:51 PM, Joshua Tinnin wrote:
[ ... ]
OK, as I understand, the branches are -CURRENT and -STABLE. But I
often see
4.10-STABLE recommended for production use. This is probably due to
what you
On 7/21/2004 11:34 AM Joshua Tinnin wrote:
On Wednesday 21 July 2004 10:20 am, Drew Tomlinson [EMAIL PROTECTED]
wrote:
On 7/20/2004 3:45 PM Thompson, Jimi wrote:
FreeBSD has 3 types of distros - CURRENT, STABLE, and
RELEASE. In order of increasing stability, they are:
CURRENT = currently
Hello everybody,
If no-one responds this time I'll get the hint, please excuse me for
reposting, I'm just going out of my mind!
I'm getting a total crash every time I try to run vmware. This is my system:
bash-2.05b$ uname -a
FreeBSD potato.hogsedge.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue
Ben Paley wrote:
Hello everybody,
If no-one responds this time I'll get the hint, please excuse me for
reposting, I'm just going out of my mind!
I'm getting a total crash every time I try to run vmware. This is my system:
bash-2.05b$ uname -a
FreeBSD potato.hogsedge.net 5.2-CURRENT FreeBSD
SNIP
bash-2.05b$ uname -a
FreeBSD potato.hogsedge.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Jun
22
07:07:08 BST 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/POTATO
i386
bash-2.05b$ pkg_info | grep vmware
vmware3-3.2.1.2242_7,1 A virtual machine emulator - a full PC in a
window
/SNIP
Ben,
On Tuesday 20 July 2004 22:32, Chris wrote:
Why are you using CURRENT? Don't you know that you can expect things to
break, not work, and overall see the end of the world as you know it?
Well - maybe not the latter. Perhaps you might be better served running
a STABLE branch instead of an
On Tuesday 20 July 2004 23:45, Thompson, Jimi wrote:
If you have a machine that you actually _use_, my advice is that you
should definitely not run current. While you will get the same kinds
of responses that you typically get from the M$ OS, it's probably not
what you want a production box,
14 matches
Mail list logo
