Raspberry on Lantean

Raspbian + NFS

Thu, 20 Apr 2017 10:07:45 +0000

Install:

apt-get install nfs-kernel-server
nano /etc/exports

Once there, let's add:

/mnt/flash *(rw,sync)

Dont' forget to run exportfs!

Add New Services:

Here's the deal: rpcbind must run before nfs-server. But due to a bug... that's not the case. What happens if the sequence is not that?... simple! NFS is inaccessible.

In order to fix this, let's do the following:

cat >/etc/systemd/system/nfs-common.service <<\EOF 
[Unit]
Description=NFS Common daemons 
Wants=remote-fs-pre.target 
DefaultDependencies=no 

[Service] 
Type=oneshot 
RemainAfterExit=yes 
ExecStart=/etc/init.d/nfs-common start 
ExecStop=/etc/init.d/nfs-common stop 

[Install] 
WantedBy=sysinit.target 
EOF

cat >/etc/systemd/system/rpcbind.service <<\EOF 
[Unit] 
Description=RPC bind portmap service 
After=systemd-tmpfiles-setup.service 
Wants=remote-fs-pre.target 
Before=remote-fs-pre.target 
DefaultDependencies=no 

[Service]
ExecStart=/sbin/rpcbind -f -w 
KillMode=process 
Restart=on-failure 

[Install]
WantedBy=sysinit.target 
Alias=portmap 
EOF

Source Here!

Raspbian + Transmission: Fixing "Connection refused on port 9091"

Thu, 20 Apr 2017 10:02:30 +0000

I’ve just managed to solve a quite annoying glitch. After booting Raspbian, Transmission was immediately unable to connect to transmission-daemon on port 9091.

After much digging, i’ve found out that:

Restarting the service just makes things work
I was getting a bunch of error messages in /var/log/daemon.log (re: bind)
Several posts in few forums suggested that the service was being initialized before the network adapter was actually ready.

Long story short:

Raspbian + Flash Drive + fstab

Wed, 19 Apr 2017 18:53:27 +0000

First off, you need to figure out the path of your flash drive:

fdisk -l

Then... edit /etc/fstab as follows:

/dev/sda1 /mnt/flash vfat rw,user,umask=0002,uid=1001,gid=121 0 0

Note that umask is... the "inverted" regular file mask. This represents 665 (because we're evil). As per uid + gid, you can figure it out by means of this command:

id username

Update:

The best filesystem to use, if you need to maintain compatibility between the Flash Drive you'll use with your Raspberry, and macOS, is probably ExFat. Now, problem is: Linux doesn't really support ExFat by default.

Raspberry + Samba

Mon, 17 Apr 2017 09:00:32 +0000

Installing Samba:

apt-get install samba samba-common-bin

Once there, edit /etc/samba/smb.conf as follows:

workgroup = [your_workgroup_name]

[SHARE-NAME]
comment=Samba Share
path=/PATH/TO/YOUR/SHARE
browseable=Yes
writeable=Yes
only guest=no
create mask=0777
directory mask=0777
public=no

At last, setup the Samba password:

smbpasswd -a YOUR_USERNAME

Awesome Colored MOTD!

Sat, 15 Apr 2017 20:15:39 +0000

sudo su
apt-get update
apt-get install toilet figlet lolcat
toilet -F metal Lantean Box -w 200 -f shadow | lolcat

Raspberry + Transmission

Fri, 14 Apr 2017 15:49:41 +0000

Let's begin with the basics. We'll need to upgrade the system to the latest, and update the apt-get database. Once ready, we'll proceed with the transmission's daemon + cli binaries, as follows:

sudo
apt-get update
apt-get upgrade
apt-get install transmission-cli transmission-common transmission-daemon transmission-remote-cli

Authentication:
By default, transmission requires you to setup username / password. Since our goal is *not* to expose Transmission to the open internet (and we'll only use it via SSH), we'll simply neutralize any kind of authentication:

Raspbian: Disabling Graphic Mode

Fri, 14 Apr 2017 15:25:55 +0000

Why: because i'm setting up my Raspberry as a private server, and i really don't need the XWindow overhead!

How: As follows!

systemctl get-default

Verify that the output is: graphical.target.
Now... type the following!

sudo systemctl set-default multi-user.target

Ref. Here

Update:

Simpler way? just run raspi-config and change the setting right there!