One way to set a user’s locale and charset is to:
- create a new login class,
- set the login class’s locale and
- set the user’s login class as the newly created class.
Example: Setting petur‘s locale and charset to en_GB.UTF-8 and UTF-8, respectivly.
Append the following to /etc/login.conf
danishKeyboard|Users with a Danish Keyboard:\
Update the capability database by executing cap_mkdb /etc/login.conf.
Set danishKeyboard as petur‘s login class by executing pw user mod petur -L danishKeyboard.
Finally, log in as petur and confirm that the locale has been correctly set as well as that the console correctly displays UTF8 characters.
Goal: Click a dock icon to open a remotely tmux’ed irssi session. The dock icon shows irssi’s logo.
Prerequisites: irssi running in a named tmux session on a remote machine.
- Open Script Editor.app
- Paste in the following script:tell application “Terminal”
do script “/usr/bin/ssh -t YOURSERVER ‘tmux attach -t SESSION'”
In which you replace YOURSERVER with ip/host of the machine running tmux/irssi and SESSSION with the tmux session name in which irssi is running.
- Save the script as an app (File -> Save, select Application as the file format.) to /Applications/
- Drag irssi.app from /Applications to the Dock
- irssi.app has a default icon. Lets change that.
Find an icon for irssi. This should be a .png file which is atleast 256×256 with a transparent background. It is important that the background is transparent otherwise the icon will appear in a ugly white frame. Here is one:
Execute the following to create an .icns file for the above icon.
mkdir -p ~/tmp/irssi
mv ~/Downloads/2000px-Irssi_logo.svg.png ~/tmp/irssi/
mv 2000px-Irssi_logo.svg.png icon.png
sips -z 256 256 icon.png –out irssi.iconset/icon_256x256.png
sips -z 128 128 icon.png –out irssi.iconset/icon_128x128.png
sips -z 32 32 icon.png –out irssi.iconset/icon_32x32.png
sips -z 16 16 icon.png –out irssi.iconset/icon_16x16.png
iconutil -c icns irssi.iconset
- The output of step 6 is an .icns file.
- Head back to /Applications, select irssi.app and open it’s Info.
- Drag the irssi.icns file you just created and release it on top of the icon shows in irssi.app Info.
- Repeat step 4 to update the icon shown in the dock.
This is the final result; Clicking on the irssi logo launches a terminal, performs an ssh to the remote machine and resumes a tmux session in which irssi is running.
I prefer the Caps Lock key over ESC because the travel to that key is shorter.
To map Caps Lock to ESC add the following to a script and ensure it executes shortly after logging into X.
/usr/local/bin/xmodmap -e "clear Lock"
/usr/local/bin/xmodmap -e "keysym Caps_Lock = Escape"
In my case, I use XFCE so I auto start it by adding /home/<user>/bin/capsToEsc.sh under Settings -> Session and Startup -> Application Autostart -> Add -> Command.
Step by step instructions on installing BitBucket on FreeBSD 11.1.
pkg install openjdk8
Mount filesystems on boot
Add the two following lines to /etc/fstab:
fdesc /dev/fd fdescfs rw 0 0
proc /proc procfs rw 0 0
Mount the two filesystems so you don’t have to reboot.
mount -t fdescfs fdesc /dev/fd
mount -t procfs proc /proc
pkg install perl5
pkg install git
pkg install bash
ln -s /usr/local/bin/bash
pkg install postgresql96-server
echo 'postgresql_enable="YES"' >> /etc/rc.conf
su - postgres
createuser -sdrP dba
CREATEROLE bitbucketuser WITHLOGIN PASSWORD'foobar'VALID UNTIL 'infinity';
CREATEDATABASEbitbucket WITHENCODING='UTF8'OWNER=bitbucketuser CONNECTIONLIMIT=-1;
Create a user for BitBucket
adduser #default values for all but Shell; set bash as the shell.
Download bitbucket from Atlassian’s website. Thoose the “TAR.GZ Archive” version.
tar xzf atlassian-bitbucket-5.8.1.tar.gz -C /usr/local
mv atlassian-bitbucket-5.8.1/ bitbucket
chown -R bitbucket:bitbucket bitbucket
chown -R bitbucket:bitbucket bitbucket
su - bitbucket
Edit bitbucket’s .profile file:
- Add and export JAVA_HOME.
- Append JAVA_HOME/bin to PATH (uncomment PATH if commented out)
- Add BITBUCKET_HOME=/usr/local/etc/bitbucket; export BITBUCKET_HOME
cron parses crontab every minute. In order to check crontab for syntax errors, check the logs output:
sleep 60; grep crontab /var/log/syslog | tail
A bhyve guest is unable to connect to the network after it’s host was configured to use NIC aggregation.
The guest’s vm switch was configured to use one of the NIC aggregation’s ports instead of the interface itself.
This was evident by:
[root@T20][~]# vm switch list
NAME TYPE IDENT VLAN NAT PORTS
public auto bridge0 - - em0
In the above listing, public should be using lagg0.
Remove the em0 port from public and add lagg0 to it:
vm switch remove public em0
vm switch add public lagg0
At this step I choose to simply restart the guest after which it was back on the network.