You can always run emacs in console mode by installing the -nox11 port of emacs, editors/emacs-nox11, which is my chosen weapon when I need syntax highlighting and other items for source code editing(like git etc).
The error message says that you can't use 64 bit guest os on your host, because your host does not support intels 64-bit technology(the VT part). You can only run 32 bit guests.
This could be a limitation in VMWare or that you maybe are running a windows 32-bit OS that can't simulate a 64 bit...
More than what killasmurf86 has said, there is the added need for a static IP that can send and receive on port 25. Which in 99 times of a hundred rules out any type of domestic ISP, and the good domestic ISP's don't allow you to send mail other then through their relay server.
If your not to...
Many reasons, the main one I would say is the eases up binary upgrade. I would reverse that question. Is there a reason you actually need a custom kernel? You _need_ it is when features/drivers that can't be loaded dynamically(like ALTQ_*), otherwise I would say that it's never needed. You won't...
The "the point of no return" is when upgrading your pool from say 13 to 14, and if something doesn't work quite right you can "downgrade" the pool to 13 again(this is on OSOL/Solaris at least). If I remember it correctly when you move to version 16 something is permanently changed in the pools...
Nope. It will only be included in the release of FreeBSD 9.0(not scheduled yet, I think). There is a point of no return at version 16 if I remember it correctly.
Did you read the instructions in /usr/ports/UPDATING? If not, you should do that on a regular basis.
And searching the forum gives about 10 pages of information on PHP, and half of them deal with upgrading from 5.2 -> 5.3. The most relevant can be found here...
If it gives a blank page, then something has gone wrong and an error will have been written to an error log. Somewhere.
Once you have deleted php you need to reconfigure it so it picks up the changes from the makefile and not simply run with the old configuration. With portmaster this is...
There is no user called bluethundr@lbsd8-2.example.com. There are however a user called bluethundr that is allowed to connect from lbsd8-2.example.com. As you can't join that easy in a delete query, your SQL should look like this:
DELETE FROM user WHERE user="bluethundr" AND...
First of all, these are not "mine". This is taken from the /usr/ports/UPDATING file, which you should be reading at regular intervals. And as you don't seem to have updated in quite some time, I would start by going over it.
Now, for the config files. In general, any file that has been touched...
This is important for you, if you haven't already read it:
20100518:
AFFECTS: users of devel/apr0, devel/apr1, www/apache20, www/apache22
AUTHOR: pgollucci@FreeBSD.org
devel/apr port has been renamed to devel/apr1.
WITH_APR_FROM_PORTS=yes for www/apache22 has been dissolved and may be...
It does copy the two example files php.ini-development and php.ini-production to your /usr/local/etc, and from these you can either copy them directly as your php.ini file(remove the -dev|-prod part) or create your own. If you are just starting out with PHP I would suggest that you just copy the...
What ever version you did install, I'm pretty sure that it has nothing to do with FreeBSD and more likely a hardware failure either on the disks or the controller. While at the POST "screen" no information from the disks has been read yet.
Check all of these first.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.