I’ve encountered a really strange issue while mouting a SMB share on my Synology today. I started to mount the remote share using the following command: root@nas:/# mount -t cifs -o username=user,password=pass //ip/share/ /mnt and I was able to list the first directory level in the tree (inside /mnt), but I encountered this really weird error while trying to list anything deeper in the directory structure (/mnt/dir1). root@nas:/mnt/dir1# ls ls: reading directory .
Goal here is to install syncthing on an old armv5t Synlogoy DS212J, there’s probably other ways to achieve that but here’s the quickest method I ended up with: Get the binary corresponding to your architecture. Extract it and copy the binary under /usr/local/bin/syncthing and make it executable: $ tar zxvf syncthing-linux-arm-v0.14.46.tar.gz $ sudo mv syncthing-linux-arm-v0.14.46/syncthing /usr/local/bin/syncthing $ sudo chmod +x /usr/local/bin/syncthing Syncthing doesn’t need to run as root so I’d recommend to run the process from an unprivileged user, in my example user.
Issue I Made the upgrade from Ubuntu 16.10 to 17.04 (desktop) this week on my personal machine at home a Lenovo X201 and immediately saw some strange graphic behaviors like some windows not able to be displayed on top of others (Chromium + Terminator for example), or some screen flickering or worse the screen going completely black with a reboot as the only solution. I also had the following errors constantly popping inside syslog:
Really quick and dirty guide to get wireguard up and running between two machines. Wireguard (wireguard.io) is an amazing new VPN solution that is simple/secure/performant Goal is to have a roadwarrior setup, were we can connect from a moving laptop to a central server. All the traffic from the laptop will be routed through the wireguard tunnel and NATed on the central server, this way the client will be able to access its infrastructure remotely and also the Internet.
I was looking for a simple way to bind an application to a specific i3 workspace based on its window properties. A concrete example: I want to bind application chromium-browser with webpage Freeture.ch to Workspace 1 and the same application with webpage Bing.com to Workspace 2. Step 1 is to identify the different X properties offered by our window. Launch xprop and click on the chromium window, you shold get something like: