Install Samba Server on Ubuntu

If you want to share files between your Ubuntu and Windows computers, your best option is to use Samba file sharing.

To install, first open a terminal window and enter the following command:

sudo apt-get install samba smbfs

We’ve got samba installed, but now we’ll need to configure it to make it accessible. Run the following command to open the configuration file, substituting your editor of choice:

sudo gedit /etc/samba/smb.conf

Find this section in the file:

####### Authentication #######
# “security = user” is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba-HOWTO-Collection/ServerType.html
# in the samba-doc package for details.
;  security = user

Uncomment the security line, and add another line to make it look like this:

security = user
username map = /etc/samba/smbusers

This will set Samba to use the smbusers file for looking up the user list.

Create a Samba User

There are two steps to creating a user. First we’ll run the smbpasswd utility to create a samba password for the user.

sudo smbpasswd -a <username>

Next, we’ll add that username to the smbusers file. 

sudo gedit /etc/samba/smbusers

Add in the following line, substituting the username with the one you want to give access to. The format is <ubuntuusername> = “<samba username>”.  You can use a different samba user name to map to an ubuntu account, but that’s not really necessary right now.

<username> = “<username>”

Now you can create samba shares and give access to the users that you listed here.

Install Chrome in Ubuntu using PPA

Using Ubuntu PPA

First you need edit /etc/apt/sources.list file

gksudo gedit /etc/apt/sources.list

Add the following two lines for Ubuntu 9.04 (Jaunty) Users

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu jaunty main

For ubuntu 9.10 (Karmic) Users add the following two lines

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu karmic main
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu karmic main

For ubuntu 10.04 (Lucid) Users add the following two lines

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu lucid main
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu lucid main

The Ultimate Torrentflux Server based on Ubuntu / Debian

This is the all-inclusive guide on installing a safe torrentflux server. Tested on Ubuntu 8.04 Server and Debian Lenny. Using torrentflux-b4rt edition.

1. Basic Security

You should perform these basic steps to secure your server.

1.1 SSH access

Change your root password:

# passwd

Create “normal” user account:

# adduser steffen

Change SSH port and disable root login:

# nano /etc/ssh/sshd_config

"Port 2222"
"PermitRootLogin no"

Make shure you can login with the normal user account created in the step before. Otherwise you will be locked out of your system.

Restart SSH:

# /etc/init.d/ssh restart

Now you can connect to your system with:

# ssh -p 2222 -l steffen xx.xx.xx.xx

Run “su” to get admin rights:

# su

EOLUpgrades Ubuntu

Introduction

This page will explain how to upgrade an End of Life (EOL) release of Ubuntu to a supported system. This guide is not limited to Ubuntu (with the Gnome desktop). Any Ubuntu flavor (Kubuntu/Edubuntu and/or server installation and others) can use this guide. For upgrading supported releases please refer to this document. Mac users may have some difficulty upgrading to the most current release around versions 7.04/7.10.

If you want to know whether your release is EOL please have a look at the following resources:

• https://wiki.ubuntu.com/Releases
• http://en.wikipedia.org/wiki/List_of_Ubuntu_releases
• http://www.ubuntu.com/products/ubuntu/release-cycle

These guides assumes that the user knows his way on the terminal, as no graphical tools are used. This said, the steps for executing all the commands are actually copy/pasteable so everyone, from beginner to advanced user running EOL releases of Ubuntu can execute the upgrade(s).

Why upgrade

Why should you upgrade instead of performing a clean install of a supported version? Some don't like to perform new installations when there is a possibility to upgrade. The advantage of this is that you can keep your current configuration without having to change much. This is often the case in production environments where you don't want to lose a machine just because it needs a higher OS version.

The scientific approach. It is possible to do, so why wouldn't we give it a shot? This is how I started out writing this guide. I had to help someone else, who was in another timezone and I thought my sleep was precious so I wrote a guide telling him how to upgrade to 8.04. When I was finished I decided it was fun to see if I could upgrade from 4.10 to the most current version (I admit, I took a shortcut when I arrived at 6.06, I upgraded directly to 8.04).

Also, if your computer cannot start a live USB for whatever reason, and all you have is a Dapper Drake installation disc, then there's no other choice: you have to download the updates and install them from within Ubuntu.

The last reason is more a flame. Why would we do it the Microsoft way? If we don't know, just restart... Why don't we try to fix the issue, even if it takes a bit more time. The time it takes per upgrade is dependent on your installation.

There are reasons why one should not upgrade, but rather reinstall. From 9.04 (jaunty) ext4 becomes available. If you want to benefit from the new features ext4 has for you then you might just as well reinstall one of the supported releases (LTS and non-LTS).