Posts

VNC Server Startup after System Reboot on Ubuntu 16.04

Image
There are dozen of guides how to install VNC server on Ubuntu System. But the main problem is that the VNC server doesn’t startup after reboot. And in this video we gonna try to fix that problem. In our case it’s a Ubuntu 16.04.3 Desktop.   First of all we need to install desktop environment packages the VNC will be using for the remote connections:     $ sudo apt-get install gnome-panel gnome-settings-daemon metacity nautilus gnome-terminal Then lets install TightVNC server:     $ sudo apt-get install tightvncserver To complete the initial setup of the VNC server after installation, we should use the vncserver command to set a secure password and create the initial configuration files: $ vncserver We will be prompted to enter and confirm a password for remote access to the system. After confirming the password, you can create a password for viewing only. Users logged in with a view-only password will not be able to control the VNC ser

Slackware Routing: configuring network interfaces, adding persistent routes, routing for multiple uplinks, policy based routing

Image
Adding persistent routes, routing with multiple gateways in Slackware is not a well described procedure that you can easily find in the internet. Even on official web page (http://www.slackware.com/config/network.php) there is no info about setting the routes up. This article represents the Slackware routing configuration, including network interfaces configuration, adding persistent routes and policy based routing for multiple uplinks. The topology below shows the realistic scenario when there are two uplinks from routers R1 and R2 and the goal is to provide the server availability from these uplinks. First, configure the network interfaces: exsentis@SlackFW:~$ sudo nano /etc/rc.d/rc.inet1.conf # Config information for eth0: IPADDR[0]="10.163.30.1" NETMASK[0]="255.255.255.0" USE_DHCP[0]="" DHCP_HOSTNAME[0]="" # Config information for eth1: IPADDR[1]="10.163.20.1" NETMASK[1]="255.255.255

SUSE OpenStack Cloud. Build SUSE Openstack Cloud

Image
1) Let's login to the Cloud Admin CLI and run the following script:    #crowbar batch --timeout 1800 build simple-cloud.yaml

SUSE OpenStack Cloud. Install SUSE Cloud Controller and Compute Nodes

Image

SUSE OpenStack Cloud. Install SUSE Cloud Admin

Image
1) Installation script:      # screen install-suse-cloud 2) After installation is comleted you should be able to login via web browser: Login: crawbar Password: crawbar

Install Devstack on OpenSuse Tumbleweed

Image