The Perfect Server - Ubuntu Intrepid Ibex (Ubuntu 8.10) - Page 3

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Submitted by falko (Contact Author) (Forums) on Fri, 2008-10-31 12:06. ::

4 Get root Privileges

After the reboot you can login with your previously created username (e.g. administrator). Because we must run all the steps from this tutorial with root privileges, we can either prepend all commands in this tutorial with the string sudo, or we become root right now by typing

sudo su

(You can as well enable the root login by running

sudo passwd root

and giving root a password. You can then directly log in as root, but this is frowned upon by the Ubuntu developers and community for various reasons. See http://ubuntuforums.org/showthread.php?t=765414.)

 

5 Install The SSH Server (Optional)

If you did not install the OpenSSH server during the system installation, you can do it now:

apt-get install ssh openssh-server

From now on you can use an SSH client such as PuTTY and connect from your workstation to your Ubuntu 8.10 server and follow the remaining steps from this tutorial.

 

6 Install vim-nox (Optional)

I'll use vi as my text editor in this tutorial. The default vi program has some strange behaviour on Ubuntu and Debian; to fix this, we install vim-nox:

apt-get install vim-nox

(You don't have to do this if you use a different text editor such as joe or nano.)

 

7 Configure The Network

Because the Ubuntu installer has configured our system to get its network settings via DHCP, we have to change that now because a server should have a static IP address. Edit /etc/network/interfaces and adjust it to your needs (in this example setup I will use the IP address 192.168.0.100):

vi /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 192.168.0.100
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.1

Then restart your network:

/etc/init.d/networking restart

Then edit /etc/hosts. Make it look like this:

vi /etc/hosts

127.0.0.1       localhost.localdomain   localhost
192.168.0.100   server1.example.com     server1

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Now run

echo server1.example.com > /etc/hostname
/etc/init.d/hostname.sh start

Afterwards, run

hostname
hostname -f

Both should show server1.example.com now.

 

8 Edit /etc/apt/sources.list And Update Your Linux Installation

Edit /etc/apt/sources.list. Comment out or remove the installation CD from the file and make sure that the universe and multiverse repositories are enabled. It should look like this:

vi /etc/apt/sources.list

#
# deb cdrom:[Ubuntu-Server 8.10 _Intrepid Ibex_ - Release i386 (20081028.1)]/ intrepid main restricted

#deb cdrom:[Ubuntu-Server 8.10 _Intrepid Ibex_ - Release i386 (20081028.1)]/ intrepid main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://de.archive.ubuntu.com/ubuntu/ intrepid main restricted
deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://de.archive.ubuntu.com/ubuntu/ intrepid-updates main restricted
deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://de.archive.ubuntu.com/ubuntu/ intrepid universe
deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid universe
deb http://de.archive.ubuntu.com/ubuntu/ intrepid-updates universe
deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://de.archive.ubuntu.com/ubuntu/ intrepid multiverse
deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid multiverse
deb http://de.archive.ubuntu.com/ubuntu/ intrepid-updates multiverse
deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://de.archive.ubuntu.com/ubuntu/ intrepid-backports main restricted universe multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ intrepid-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository. This software is not part of Ubuntu, but is
## offered by Canonical and the respective vendors as a service to Ubuntu
## users.
# deb http://archive.canonical.com/ubuntu intrepid partner
# deb-src http://archive.canonical.com/ubuntu intrepid partner

deb http://security.ubuntu.com/ubuntu intrepid-security main restricted
deb-src http://security.ubuntu.com/ubuntu intrepid-security main restricted
deb http://security.ubuntu.com/ubuntu intrepid-security universe
deb-src http://security.ubuntu.com/ubuntu intrepid-security universe
deb http://security.ubuntu.com/ubuntu intrepid-security multiverse
deb-src http://security.ubuntu.com/ubuntu intrepid-security multiverse

Then run

apt-get update

to update the apt package database and

apt-get upgrade

to install the latest updates (if there are any). If you see that a new kernel gets installed as part of the updates, you should reboot the system afterwards:

reboot

 

9 Change The Default Shell

/bin/sh is a symlink to /bin/dash, however we need /bin/bash, not /bin/dash. Therefore we do this:

ln -sf /bin/bash /bin/sh

If you don't do this, the ISPConfig installation will fail.

 

10 Disable AppArmor

AppArmor is a security extension (similar to SELinux) that should provide extended security. In my opinion you don't need it to configure a secure system, and it usually causes more problems than advantages (think of it after you have done a week of trouble-shooting because some service wasn't working as expected, and then you find out that everything was ok, only AppArmor was causing the problem). Therefore I disable it (this is a must if you want to install ISPConfig later on).

We can disable it like this:

/etc/init.d/apparmor stop
update-rc.d -f apparmor remove
apt-get remove apparmor apparmor-utils

up

Copyright © 2008 Falko Timme
All Rights Reserved.
add comment | view as pdf view as pdf | print: this | all page(s) |
Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
I had to set the DNS server
Submitted by Anonymous (not registered) on Sun, 2009-01-25 16:34.

I had to set the DNS server address in /etc/resolv.conf to get the dns to work.

(Running  Ubuntu 8.10 server in VirtualBox under Vista with two netw adapters, the VBox network on secondary host interface, and InternetConnectionSharing turned on in Vista)

reply | view as pdf view as pdf
Update Your Kernel Too, To Prevent Reboot Hangs
Submitted by AceFrahm (registered user) on Sat, 2008-12-13 05:12.

Use

apt-get dist-upgrade

 to upgrade your kernel too, in step 8 before you

reboot

 I was having trouble on my Dell 9200 with 7300LE Nvidia video card.  It would hang on reboot at the very end.  Processes shutdown, but it would not finally turn the power off for the restart.  Restart failed, so I had to physically hold the button down for 10 seconds to cycle the power off & on.  It would happen with another equivalent reboot command,

init 6

, too.

But this bug was fixed in an updated kernel.  To get that updated kernel, use this apt-get dist-upgrade command.

********************** EDIT  EDIT EDIT 2009-01-20 *****************

**********************     MORE INSTRUCTIONS     *******************

I noticed this grub file must be altered, to fix this reboot hang problem on a Dell 9200.

http://ubuntuforums.org/showthread.php?t=1001648&page=2

We’ll make a script to edit your /boot/grub/menu.lst file automatically. Make a folder, and add the path to this new folder to your $PATH environment variable, so that the bash shell of the command line will function on the script you will create inside that folder.

echo $PATH
export PATH=$PATH:/tempscript
echo $PATH
mkdir tempscript
cd /tempscript

Then make a script to edit the grub file. Start the vi text editor to create the file:

vi alter_menu

then press "i" to enter insert mode:

i

Cut & paste this script into the file (make sure you're not also pasting the HTML tags of this text too, because you are copying it from the browser):

#!/bin/bash
MENU='/boot/grub/menu.lst'
cat $MENU | while read LINE
do
   if [[ $LINE =~ ^$ ]]; then
     echo $LINE
   elif [[ $LINE =~ ^[^kernel] ]] || [[ $LINE =~ .*bin$ ]]; then
     echo $LINE
   elif [[ $LINE =~ ^kernel.* ]]; then
     echo $LINE reboot=b
   fi
done

Press [ESC] to exit insert mode of the vi editor, then press

ZZ

to save the script file and exit the editor. Now run the script and clean up:

chmod 777 alter_menu
alter_menu > /boot/grub/menu.lst.tmp
mv /boot/grub/menu.lst.tmp /boot/grub/menu.lst
cd ../../../../../../../../..
rm -r /tempscript

It is necessary to reboot manually one more time with the manual power button if your machine suffers from this problem, So that the server’s grub can boot with these new settings.
reply | view as pdf view as pdf
Putty fails login without warning if passwords contain CAPITALS
Submitted by AceFrahm (registered user) on Tue, 2008-12-09 06:12.

If you want to use Putty to complete the setup remotely as specified in step 5 on page 3,  you should use a password that has no capital letters. 

 For some stupid reason, putty will fail even though you are using the correct IP, correct username, and correct password, if the password has any capitals in it.

 If your password does, you can change it at the command prompt with the "passwd" command.

You should do that for both your user account AND the super user if you intend to use "sudo su" over Putty.

reply | view as pdf view as pdf
Re: Putty fails login without warning if passwords contain CAPIT
Submitted by drmeg (registered user) on Thu, 2008-12-18 00:44.
Actually, I have not had any difficulty with capitals in passwords using putty. Not sure why it does not seem to work for you.
reply | view as pdf view as pdf
Sponsored Links: Unified Communications: Thoughts, Strategies and Predictions
Join the discussion.
www.seamlessenterprise.com

IP Convergence
Integrate your wireless and wireline networks.
Learn how from the experts at Sprint.
www.seamlessenterprise.com

Wireless & Wireline Integration
Thoughts, strategies and solutions: join the discussion
www.seamlessenterprise.com

Unified Communications 2009
Join the Discussion. Now.
www.seamlessenterprise.com

Red Hat Virtual Experience - a free virtual event. Dec. 9th