Installing Freebsd 11 via USB error 19

Today I tried to install FreeBSD 11.0
FreeBSD booted from the USB stick. When mounting the install image I received error:

Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19.

I couldn’t figure out why I constantly got this error.

After tweaking bios etc. Using an USB2 port I finally gave up an though my USB stick was broken..
But then creating the second stick I found the problem.

The first time I created my memory stick like this on Mac OS X

sudo dd if="FreeBSD-11.0-RELEASE-amd64-memstick.img" of="/dev/disk2s1" bs="10240"

Look at the wrong /dev/disk2s1 path.. (that’s wrong!! )

The second attempt I used the following command. (I needed tot unmount /dev/disk2s1 in DiskUtilty first
)

sudo dd if="FreeBSD-11.0-RELEASE-amd64-memstick.img" of=/dev/disk2 bs=1m conv=sync

Now it works :D

Simple acces to your HTTP(s) services via SSH and a SOCKS Proxy

I didn’t know this trick:
https://www.gypthecat.com/using-ssh-as-a-socks-vpn-on-mac-os

This blog entry describes how to use your normal SSH connection as a SOCKS proxy for web requests.
Just connect to the SSH server with the -D option on port 8080

ssh -D 8080 -p [port number] [username]@[IP address or hostname]

On Mac OS X just enable the socks proxy in the Advanced tab of your network/wifi card:
And enter as SOCKS proxy server 127.0.0.1, on port 8080

Screen Shot 2016-07-04 at 08.15.04

But for a full vpn attempt over SSH, maybe I should look at this:

https://github.com/apenwarr/sshuttle/

FreeBSD mysql-server failed precmd routine

Trying to start mysql-server tries start with the message failed precmd routine.

Debugging this can be done by altering /usr/local/etc/rc.d/mysql.server

Comment out the following parts : >/dev/null 2>/dev/null

mysql_create_auth_tables()
{
   ...
	eval $mysql_install_db $mysql_install_db_args # >/dev/null 2>/dev/null
   ...
}

mysql_prestart()
{
   ... 
	if checkyesno mysql_limits; then
		eval `/usr/bin/limits ${mysql_limits_args}` # 2>/dev/null
	else
		return 0
	fi
   ...
}

You will see the error message.
In my case the issue was an existing data-directory