Linode.com Forum

[CSpurrier]

How to setup your Linode with Debian Testing
by Craig Spurrier of Craigweb

There are three sets of Debian packages:
Stable:
This is the latest official release of the Debian GNU/Linux distribution. This is stable and well tested software, which changes only if major security or usability fixes are incorporated

Testing:
Testing contains packages that are intended to become part of the next stable distribution. There are strict criteria a package in unstable must obey before it can be added to testing.

Unstable:
This area contains the most recent packages in Debian. Once a package has met our criterion for stability and quality of packaging, it will be included in testing. Packages in unstable are the least tested and may contain problems severe enough to affect the stability of your system. Only experienced users should consider using this distribution. Avoid for servers.

This guide is for Testing to use Debian testing with your linode you must start with stable and upgrade to testing. (steps 3-5)

Step One
Create a directory to work in, then switch to it.

Code:
mkdir work
cd work


Step Two
Update the sources file
Run
Code:  apt-get update

Step Three
Install a text editor
Code:  apt-get install ee

Step Four
Edit the source file
Code:  ee /etc/apt/sources.list
Replace it with this:
Code:  
deb http://mirrors.kernel.org/debian/ testing main contrib non-free
deb-src http://mirrors.kernel.org/debian/ testing main contrib non-free

deb http://security.debian.org/ testing/updates main contrib non-free


Step Five
Update the sources file
Run
Code:  apt-get update

Step Six
Upgrade to testing.
Run
Code: apt-get dist-upgrade
Accept the defaults

Step Seven
Update your hostname

Code:  echo yourdomainnamehere >/etc/hostname 
Code:  /bin/hostname -F /etc/hostname

Step Eight
Install the Webmin Dependences
Code:
apt-get install libauthen-pam-perl libnet-ssleay-perl openssl perl perl-modules


Step Nine
Get Webmin
Code:
wget http://umn.dl.sourceforge.net/sourceforge/webadmin/webmin-1.180.tar.gz


Step Ten
Extract webmin to a folder and then switch to that folder
Code:
gunzip webmin-1.180.tar.gz
tar xf webmin-1.180.tar
cd webmin-1.180



Step Eleven
Install Webmin
Code:
./setup.sh /usr/local/webmin


Step Twelve
Install Apache and PHP

Code:
apt-get install apache2 php4


or

Code:
apt-get install apache php4


Step Thirteen
On your local computer point your web browser to https://yourdomain.com:10000 login as root.

Step Fourteen
Click Servers --> Apache and follow the prompts
Click Start Apache (at the top)

Step Fifteen
On your local computer point your web browser to http://yourdomain.com you should see a test page if you do your website is now working.

Step Sixteen
Set Apache to start on boot.
Click on System --> Bootup and Shutdown. Put a chek by httpd and click start select on boot.

Step Seventeen
Set up E-mail, Virtualmin, Ftp, Etc.
Enjoy your new server!

If any one needs help please reply.

[chapterthree]

This looks like a GREAT post. I'm gonna wipe out the node, and start from scratch using this tutorial probably early next week.

The only thing extra I need is MySQL. How would I go about setting that up in this tutorial? As in at what steps would I type what?

Thanks!

-Kevin

[CSpurrier]

Code: apt-get install mysql
To configure see the MySQL site.

Sorry, Mysql is not one of my strong subjects.

[Geary]

chapterthree wrote: The only thing extra I need is MySQL. How would I go about setting that up in this tutorial? As in at what steps would I type what?

Just do this, any time after upgrading:

Code: apt-get install mysql-server

In fact, I installed MySQL at the same time as Apache and PHP:

Code: apt-get install apache2 php4 mysql-server

-Mike

[Geary]

Oops, you probably want PHP4 and MySQL to actually work with Apache 2 and each other! You need a couple more modules to hook them all up.

Here's the whole thing:

Code: apt-get install apache2 mysql-server php4 libapache2-MOD-php4 php4-mysql

[sarge]

Fantastic tutorial! Thanks!

I think step 3 can be skipped entirely. There is no need to install ee editor because nano is already installed by default.

[CSpurrier]

You are right step three can be skipped, nano will work however I like EE better :)

[dotmil]

You may also consider changing 'testing' in sources.list to 'sarge'. That way when (some would say if) Sarge becomes stable, you can continue running it with no changes. This assumes that you want to continue running Sarge of course.