This is one thing that has me wondering about SMF. It is apparently a known issue but in the latest version and new install nothing looked right because it was using http://127.0.0.1 to find everything! How on earth would it ever do this or think it is normal?
Excerpt of crazy html code it produces that causes the issue:
........
For themes and custom CMS setups, the typical HTML theme is not ready to go at all but here are some common sed commands (search and replace that will get most of them working without breaking as you'd expect).
The problem is that often the theme directory will be separate from the content and this will break the relative paths that these themes use.
sed -i s/'href="'/'href="/themes/yourtheme/'/g index.html
sed -i s/'src="'/'src="/themes/y........
It is a permissions issue that is hard to fix.
All but one USB device is greyed out.
I am already a member of "vboxusers"
I have already enabled and disabled USB support for the guest.
I have already reinstalled the latest VBOx guest editions
If running as root it all works fine
Changing........
There is a weird quirk with how this works, but there is a variable called "src" that defaults to 0 or disabled if not specified as 1.
The default 0 means not to recur billing on a subscription. It's too bad it's not more obvious anywhere nor is there an explanation or warning during payment or after to both the seller and buyer.
Here's a proper subscription code example that does recur and does not cancel........
CPanel says you can access 98% of the functions through CLI which experienced Unix/Linux admins prefer for simplicity and for scripting. I've never found CPanel easy to use from the admin panel, it seems everything is hard to find and a simple task becomes a series of hunts.
So for people like me here's the list: http://cpanel.net/system-administrators/command-line-scrip........
OpenVZ has made vzctl version 4.7 default to using ploop which is a big annoyance. No one wants it otherwise we'd use Xen or KVM.
Make sure to manually specify vzctl 4.6.1 or you will have issues with old scripts breaking since it defaults to using ploop (a single image like Xen/KVM).
Here's a list to old versions of vzctl.........
On the same OS with the same kernels basically I cannot boot FreeBSD installer, I believe the issue is the host CPU.
One host runs an Intel and works, while an Opteron 2373 does not work despite suggestions from this thread: http://149.20.54.209/showthread.php?t=36761
I've tried cpu options like "kvm64" "Opteron_G3" and none........