Search

Tags

Anti-Malware Anti-Spyware Apache2 Apple Beeps Blog Debian Debian 3.0 (sarge) Debian 4.0 (etch) Debian 5.0 (lenny) Dell Free Adware Protection Free Malware Protection Free Software Free Spyware Protection Free Utilities GNU/Linux GUI IE8 Intel Internet Explorer KDE Keyboard Laptop Linux Mac Macintosh Microsoft MySQL OpenSSH OpenSSL PHP POST Power Mac G4 Power Macintosh G3 Power On Self Test Rackable Systems Scams Shortcuts Smoothwall Express Spybot Spybot Search and Destroy web server Windows Vista Windows XP

Log In

Installing ProFTPd FTP Server on a Debian System

30th April - Submitted by bamajr

INSTALLING PROFTPD FTP SERVER. (FTP Servers allow easy remote file transfers, especially when uploading files for web sites. Please be aware that ProFTPd transmits username and password data in an unsecure/plain text format. You need to be careful to make sure you secure this by only allowing access by specific users, only using it when it is absolutely necessary, and changing that user’s password often.)

  1. At the Debian GNU/Linux w/ KDE Welcome Screen, chose the “Menu” option in the lower left part of the screen.
  2. In the Menu chose the “Console Login” option. (You Can also simply click ALT+N from the Debian GNU/Linux w/ KDE Welcome Screen, in place of the first two steps in this section. This is a shortcut to the Console or “CONSOLE MODE”.)
  3. At the Login prompt type: “root” and hit the [enter] key.
  4. Type in the Password of the “root” user and hit the [enter] key.
  5. Then you will type the following code:
    Code:

    test:~# apt-get update

    then press the [enter] key. This will download the latest, most up to date installation packages. Do not try to continue until it has completed the package header downloads.

  6. Once all the package headers have been downloaded, type:
    Code:

    test:~# apt-get install proftpd

    then press the [enter] key. This will start the install process for the ProFTPd server.

  7. You will get a ProFTPd configuration screen asking if you want the ftp server to run as a standalone server or a inetd service. (I use the inetd option, so this document will include that option.)
  8. Use your arrow keys to select inetd and hit the [enter] key.
  9. The installation will continue and the configuration option you just chose will be applied. Once the installation is complete the screen will tell you that the ProFTPd is started, and return you to the # Command Prompt.
  10. CREATE USERS – I have not developed a set of instructions for creating ProFTPd Users yet, but will update this guide when I have.
  11. TESTING SECTION – I have not developed a set of instructions for testing this installation yet, but will update this guide when I have.
  12. Portions of these steps were taken from an article found here.
  13. Congratulations, you now have a fully working FTP Server for your Debian System!
CONFIGURING SECURITY OPTIONS FOR YOUR PROFTPD FTP SERVER. There are several security options you can enable on your ProFTPd Server. (The configuration of your ProFTPd server is handled by the ProFTPd configuration file found at “/etc/proftpd.conf”)

(The next set of instructions assume you are still at the the # Command Prompt. from the instructions above.)

  1. To stop the server prior to more configuration type:
    Code:

    test:~# /etc/init.d/proftpd stop

    then press the [enter] key. This will stop the ProFTPd Server processes for modification.

  2. To use TLS security you will need to generate a key, and update your server’s configuration file to use it.
    Generating a key is simple enough with the openssl command, which is contained in the openssl package:

    Code:

    test:~# mkdir /etc/proftpd

    then press the [enter] key to create the directory. Next type:

    Code:

    test:~# cd /etc/proftpd

    then press the [enter] key to change to that directory. Now enter the command:

    Code:


    test:~# openssl req -new -x509 -days 365 -nodes -out ftpd-rsa.pem \
    -keyout ftpd-rsa-key.pem

    then press the [enter] key.

  3. With the files generated you can add the following to your proftpd.conf file:
    Code:

    <ifmodule mod_tls.c>
    TLSEngine on
    TLSLog /var/log/proftpd-tls.log
    TLSProtocol TLSv1
    # Are clients required to use FTP over TLS when talking to this server?
    TLSRequired off
    TLSRSACertificateFile /etc/proftpd/ftpd-rsa.pem
    TLSRSACertificateKeyFile /etc/proftpd/ftpd-rsa-key.pem
    # Authenticate clients that want to use FTP over TLS?
    TLSVerifyClient off
    </ifmodule>

    You can also limit users to specific directories. To limit the user “bamajr” to the starting directory “/tmp” you can use:

    Code:

    DefaultRoot /tmp bamajr

    Another approach is to generally restrict all users to their own home directory. This can be accomplished with:

    Code:

    DefaultRoot ~

    This causes all users to be presented with the contents of their home directory (as specified by /etc/passwd) when they log in.

  4. When you are done with the configuration, you can start the ProFTPd server back up by typing:
    Code:

    test:~# /etc/init.d/proftpd start

    then press the [enter] key. This will start the ProFTPd Server processes for use. You could also reboot the system by typing:

    Code:

    test:~# shutdown now -r

    then press the [enter] key. This will shut your Debian System off and reboot it.

Filed under: Computers, Linux-Unix, Software | No Comments »

Installing Subversion on a Debian System running Apache2

29th April - Submitted by bamajr

INSTALLING SUBVERSION (Again, this is a multi-package installation to provide version control for each web page you choose to monitor.)

  1. At the Debian GNU/Linux w/ KDE Welcome Screen, chose the “Menu” option in the lower left part of the screen.
  2. In the Menu chose the “Console Login” option. (You Can also simply click ALT+N from the Debian GNU/Linux w/ KDE Welcome Screen, in place of the first two steps in this section. This is a shortcut to the Console or “CONSOLE MODE”.)
  3. At the Login prompt type: “root” and hit the [enter] key.
  4. Type in the Password of the “root” user and hit the [enter] key.
  5. Then you will type the following code:
    Code:

    test:~# apt-get update

    then press the [enter] key. This will download the latest, most up to date installation packages. Do not try to continue until it has completed the package header downloads.

  6. Once all the package headers have been downloaded, type:
    Code:

    test:~# apt-get install libapache2-svn subversion subversion-tools

    then press the [enter] key. You will be asked if you want to continue. Press “y” and then press the [enter] key to continue. This will install the necessary Subversion files. Let this process complete and it will take you back to the # Command Prompt.

    Code:

    test:~# cd /home/

    then press the [enter] key.

    Code:

    test:~# mkdir svn

    then press the [enter] key. This will create the “svn” directory in the “home” directory and take you back to the # Command Prompt.

    Code:

    test:~# chown www-data svn

    then press the [enter] key. This sets the system user www-data as the owner of the /svn/ directory.

    Code:

    test:~# su www-data –c “svnadmin create svn/src”

    then press the [enter] key. Your repository will live in /home/svn/src. (Please Note! If you let your users run things as www-data (eg. they can install CGI applications) they will be able to write to your repository!)

    Code:

    test:~# cd

    then press the [enter] key.

    Code:

    test:~# pico /etc/apache2/sites-available/ssl

    then press the [enter] key. This will launch the PICO NANO editor, to add information to the file.

  7. The very bottom of the file should now read:
    Code:

    <location /svn/src>
    DAV svn
    SVNPath /home/svn/src
    AuthType Basic
    AuthName "My Subversion Repository"
    AuthUserFile /home/svn/.dav_svn.passwd
    Require valid-user
    #<limitexcept GET PROPFIND OPTIONS REPORT>
    # Require valid-user
    #</limitexcept>
    </location>
    SSLEngine On
    SSLCertificateFile /etc/apache2/ssl/apache.pem

  8. Once you have made the necessary edits to the ssl file, hold down the CTRL key and press the “X” key. This will ask you if you want to save the file. Press the “Y” key.
  9. You will then be prompted to enter a path to save the file. Leave the default path and file in place and hit the [enter] key. You will be returned to the # Command Prompt.
    Code:

    test:~# /etc/init.d/apache2 restart

    then hit the [enter] key. This will restart the Apache2 server, and enforce the new modifications you just made.

  10. CREATE USERS – I have not developed a set of instructions for creating Subversion Users yet, but will update this guide when I have.
  11. TESTING SECTION – I have not developed a set of instructions for testing this installation yet, but will update this guide when I have.
  12. Portions of this guide was taken from an article available online here.
  13. Congratulations, you now have Subversion running on your Debian web server! (However, in order to get Subversion to correctly monitor and display version information about your Webpage, you will have to finish the Subversion configuration. You may want to refer to the article listed above for that information.

Filed under: Computers, Linux-Unix, Software | No Comments »

Installing Apache2 and OpenSSL on a Debian System

28th April - Submitted by bamajr

INSTALL APACHE2 & OPENSSL. (This multi-package configuration for web hosting is complete with the ability to provide HTTP and HTTPS based web pages.)

  1. At the Debian GNU/Linux w/ KDE Welcome Screen, chose the “Menu” option in the lower left part of the screen.
  2. In the Menu chose the “Console Login” option. (You Can also simply click ALT+N from the Debian GNU/Linux w/ KDE Welcome Screen, in place of the first two steps in this section. This is a shortcut to the Console or “CONSOLE MODE”.)
  3. At the Login prompt type: “root” and hit the [enter] key.
  4. Type in the Password of the “root” user and hit the [enter] key.
  5. Then you will type the following code:
    Code:

    test:~# apt-get update

    then press the [enter] key. This will download the latest, most up to date installation packages. Do not try to continue until it has completed the package header downloads.

  6. Once all the package headers have been downloaded, type:
    Code:

    test:~# apt-get install apache2 openssl

    then press the [enter] key to install the latest version of the Apache2 Web Server (HTTP://)and the OpenSSL (HTTPS://) Server Packages. Once this process completes it will take you back to the # Command Prompt. Next type:

    Code:

    test:~# mkdir /etc/apache2/ssl

    then press the [enter] key to create a folder called “ssl” in the /etc/apache2 directory. This will also return you to the # Command Prompt. Now type:

    Code:

    test:~# RANDFILE=/dev/random openssl req $@ -new -x509 -days 365 -nodes

    then press the [enter] key. You will be advanced to the next line to add additional information.

    Code:

    > out /etc/apache2/ssl/apache.pem \”

    then press the [enter] key. You will be advanced to the next line to add additional information.

    Code:

    > -keyout /etc/apache2/ssl/apache.pem

    then press the [enter] key. This will walk you through a series of steps to build a “Self Signed” SSL Certificate. Read each step carefully, and answer each question with Short, Direct answers. When it finishes you will be returned to the # Command Prompt.

    Code:

    test:~# chmod 600 /etc/apache2/ssl/apache.pem

    then press the [enter] key. This sets the file permissions for the apache.pem file and returns you to the # Command Prompt.

    Code:

    test:~# cp /etc/apache2/sites-available/default /etc/apache2/sites-available/ssl

    then press the [enter] key. This creates a copy of the “default” file named “ssl” for use with our OpenSSL Server.

  7. Now we need to add the site to the sites-enabled directory. This is done by making a symbolic-link to the configuration from /etc/apache2/sites-enabled/. You can see that this has already done for the “default” file by looking in /etc/apache2/sites-enabled/ directory for a “000-default” file. Apache has a command to do this automatically for the ssl file, from the # Command Prompt.
    Code:

    test:~# cd /etc/apache2/sites-available/

    then press the [enter] key.

    Code:

    test:~# dir

    then press the [enter] key. You should see both a “default” and a “ssl” file.

  8. Now to enable the SSL Site we have a special “Enable Site” command.
    Code:

    test:~# a2ensite ssl

    then press the [enter] key.

  9. Next to enable the SSL Mod in Apache2 we have a special “Enable Mod” command.
    Code:

    test:~# a2enmod ssl

    then press the [enter] key.

    Code:

    test:~# cd /etc/apache2/sites-enabled/

    then press the [enter] key.

    Code:

    test:~# dir

    then press the [enter] key. You should see the “000-default” and the “ssl” file in that “sites-enabled” directory.

    Code:

    test:~# cd ..

    then press the [enter] key. Check to make sure you are in the /etc/apache2 directory now.

    Code:

    test:~# pico ports.conf

    then press the [enter] key. This will open the “ports.conf” in the PICO NANO file editor. Use your down arrow to get to the line below “Listen 80” and type: “Listen 443”, but DO NOT hit the key this time.

  10. This time, hold down the CTRL key and press the “X” key. This will ask you if you want to save the file. Press the “Y” key.
  11. You will then be prompted to enter a path to save the file. Leave the default path and file in place and hit the key. You will be returned to the # Command Prompt.
    Code:

    test:~# pico /sites-avaiable/ssl

    then press the [enter] key. This will open the “ssl” file in the PICO NANO file editor. Use your down arrow to get to navigate the document.

  12. Starting with the “NameVirtualHost *” line, edit the file to read as follows:
    Code:

    NameVirtualHost *:443

    ServerAdmin $USERNAME@YOURSERVERNAME.com

  13. Then scroll to the bottom of the screen and find the “” line. Add a lines above it that reads as follows:
    Code:

    SSLEngine On
    SSLCertificateFile /etc/apache2/ssl/apache.pem

  14. Now hold down the CTRL key and press the “X” key. This will ask you if you want to save the file. Press the “Y” key. You will then be prompted to enter a path to save the file. Leave the default path and file in place and hit the key. You will be returned to the # Command Prompt.
    Code:

    test:~# cd

    then press the [enter] key. This will take you back to the “root” directory.

    Code:

    test:~# /etc/init.d/apache2 restart

    then press the [enter] key. This will restart the Apache2 server, and enforce the new modifications you just made.

  15. Bring up a web browser and go to the IP Address of the machine you are working on: (“http://localhost/” if you or working locally or “http://0.0.0.0” if you are working remote.) Hit the [enter] key. You should get a screen that says “It Works!” on it.
  16. In the same web browser change the address to “https://localhost/” or “https://0.0.0.0” in the address bar and hit the [enter] key. You should get a popup asking about the “Self Signed” Security Key.
  17. Accept the Certificate.
  18. Then you will probably get a screen that asks if you want to display the non-secure content.
  19. Accept it as well.
  20. Now you will get a screen that says “It Works!” on it.
  21. Portions of this guide was taken from an article available online here.
  22. Congratulations, you have a fully functional HTTP & HTTPS web server!

Filed under: Computers, Linux-Unix, Software | No Comments »

Installing an OpenSSH Server and Client on a Debian System

27th April - Submitted by bamajr

INSTALLING AN OPENSSH SERVER & CLIENT. OpenSSH is a remote management utility that gives you access to your new server’s console/command line from anywhere you can get an internet connection. (This tool is useful in remote management or remote problem solving.)

  1. At the Debian GNU/Linux w/ KDE Welcome Screen, chose the “Menu” option in the lower left part of the screen.
  2. In the Menu chose the “Console Login” option. (You Can also simply click ALT+N from the Debian GNU/Linux w/ KDE Welcome Screen, in place of the first two steps in this section. This is a shortcut to the Console or “CONSOLE MODE”.)
  3. At the Login prompt type: “root” and hit the [enter] key.
  4. Type in the Password of the “root” user and hit the [enter] key.
  5. Then you will type the following code:
    Code:

    test:~# apt-get update

    then press the [enter] key. This will download the latest, most up to date installation packages. Do not try to continue until it has completed the package header downloads.

  6. Once all the package headers have been downloaded, type:
    Code:

    test:~# apt-get install openssh-server

    then press the [enter] key to install the OpenSSH Server packages. You will be get a prompt about being sure. Hit the “Y” key and press the [enter] key to continue. When the installation has completed you will be returned to the # command prompt.

  7. Now type:
    Code:

    test:~# apt-get install openssh-client

    then press the [enter] key to install the OpenSSH Client packages. You will be get a prompt about being sure. Hit the “Y” key and press the [enter] key to continue. When the installation has completed you will be returned to the # command prompt.

  8. To ensure the OpenSSH Server is running type:
    Code:

    test:~# shutdown now –r

    to reboot your system. Once you are back to the Debian GNU/Linux w/ KDE Welcome Screen, you should be able to create an SSH connection from a SSH Client on another computer. (You will need to follow the Client’s installation, configuration and user instructions in order to make the connection. I use Quest PuTTY as the SSH Client on my Windows XP Pro Laptop. PuTTY is available as a free download from here.

  9. Portions of these steps were taken from an published article available here.
  10. Verify that you can create an SSH Connection. Once you have verified you can make a connection via SSH, you can close the connection by typing:
    Code:

    test:~# exit

    at the # command prompt. and then hitting the [enter] key. This will close the SSH connection and quit/exit the client program.

  11. Congratulations, you have successfully installed OpenSSH Server & Client on your Debian System!

Filed under: Computers, Linux-Unix, Software | No Comments »

Installing vnc4server on a Debian system running KDE 3

24th April - Submitted by bamajr

INSTALLING A VNC4SERVER. (vnc4server is a remote desktop management utility allowing remote access to the KDE GUI on your Debian System. This connection can be established from any machine running a supported client, from anywhere you can get an internet connection. This tool is useful in solving problems with your server after it has been setup.)

  1. At the Debian/GNU w/ KDE Welcome Screen, chose the “Menu” option in the lower left part of the screen.
  2. In the Menu chose the “Console Login” option. (You Can also simply click ALT+N from the Debian GNU/Linux w/ KDE Welcome Screen, in place of the first two steps in this section. This is a shortcut to the Console or “CONSOLE MODE”.)
  3. At the Login prompt type: “root” and hit the [enter] key.
  4. Type in the Password of the “root” user and hit the [enter] key.
  5. Then you will type the following code:
    Code:

    test:~# apt-get update

    then press the [enter] key. This will download the latest, most up to date installation packages. Do not try to continue until it has completed the package header downloads.

  6. Once all the package headers have been downloaded, type:
    Code:

    test:~# apt-get install vnc4server

    then press the [enter] key. This will install the vnc4server packages. You will be get a prompt about being sure. Hit the “Y” key and press the [enter] key to continue. When the installation has completed you will be returned to the # command prompt.

  7. Next, type:
    Code:

    test:~# vnc4server –geometry 1024x768 –depth 24 –name test

    then hit the [enter] key. You will be prompted to enter and confirm a password. (This password will be used to access the desktop of this machine remotely.) Once the password has been entered and verified you will have successfully launched the vnc4server on your system, and will be returned to the # command prompt.

  8. We will now kill the vnc4server process by typing:
    Code:

    test:~# vnc4server –kill :1

    then hit the [enter] key. This will terminate the vnc session you just started, leaving you at the # command prompt. Now type:

    Code:

    test:~# cp /root/.vnc/xstartup /root/.vnc/xstartup_old

    then hit the [enter] key. This will create a backup “_old” of the xstartup file in case you need it later. (The “xstartup” file may be located in the /$USER/.vnc/xstartup directory or in the /root/.vnc/xstartup directory. The location of this will depend on whether the installation is done from within the KDE GUI and which user is logged in at the time of the installation, or if the installation is performed from the command console, as the “root” user.

    To verify that the backup was created successfully, type:

    Code:

    test:~# dir /root/.vnc/

    and make sure you have both a “xstartup” and “xstartup_old” file displayed. (If you do not have both files, check the prior steps and try it again.

  9. Next, we will edit the “xstartup” file by typing:
    Code:

    test:~# pico /root/.vnc/xstartup

    then hit the [enter] key. This will launch the NANO editor in order to edit the xstartup file. Delete everything in this file using the delete button on your keyboard. Once the page is blank, type in the following lines exactly as I have them listed below:

    Code:


    #!/bin/sh
    #Uncomment the following two lines for normal desktop:
    #unset SESSION_MANAGER
    # exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic -nowin &
    #x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
    #x-window-manager & startkde &

  10. Hold down the CTRL key and press the “X” key. This will ask you if you want to save the file. If you have finished these edits press the “Y” key.
  11. You will then be prompted to enter a path to save the file. Leave the default path and file in place and hit the [enter] key. You will then be returned to the # command prompt.
  12. Congratulations, Your Debian System is now Running vnc4server!
  13. If you know how to create scripts and you want to make your vnc4server run as a service that starts with the system when it is turned on, you can complete the next “OPTIONAL” identified step. Otherwise skip past the “OPTIONAL” step to continue.
  14. BEGINNING OF OPTIONAL STEP: You may want to make your vnc4server start up with you server automatically, each time you have to reboot it. You can do this by creating a script “/etc/init.d/vnc4server” as shown below:
    Code:

    test:~# update-rc.d vnc4server defaults 20

    to add to the startup commands.

    Code:

    test:~# shutdown now –r

    then hit the [enter] key, telling your system to reboot. Once the system reboots the Debian/GNU w/ KDE Welcome Screen. You need to switch back to the console mode and log in as the “root” user. ENDING OF OPTIONAL STEP

  15. At the console # command prompt…
    Code:

    test:~# vnc4server –geometry 1024x768 –depth 24 –name test

    then hit the [enter] key. This will re-launch a VNC session called “test”.

  16. Once the new vnc4server session has been launched you will be sent back to the # command prompt. Type:
    Code:

    test:~# exit

    then hit the [enter] key to log out of the console.

  17. Additional information, codes and commands can be found at [url]http://www.vnc.com/products/free/4.1/[/url]
  18. You may want to read the article found here for more information related to configuring vnc4server to start automatically.
  19. You may also want to read related articles found here on Google

Filed under: Computers, Linux-Unix, Software | No Comments »

Setting the Time and Date in KDE

23rd April - Submitted by bamajr

SETTING THE DATE & TIME IN KDE. (This section will walk you through setting the correct date and time for your system. It is important that your Linux system have the correct date and time for event logging, updating and other functions.)

  1. Assuming you are already logged into the KDE GUI, Find the Time display (usually in the lower Right-Hand Corner of the screen with a default configuration, though it could be at the top or either side of the screen as well.) and drag your cursor over it. This will display a bubble showing the current date and time.
  2. With your mouse, single Right-Click to bring up the “Clock” menu. Select the “Adjust Date & Time” Option by a single Left-Click of your mouse. (If you are logged in as a general user, you will be prompted for the password of a user on the system who is authorized to make these changes. If you are logged into the KDE GUI with “root” or “su” access, you will not be prompted for a password.)
  3. Set the correct Date in the calendar section.
  4. Set the correct Time (24 Hour/Military format) in the Clock section. Select the City/Region/Time Zone that is closest to your own.
  5. Click the “Apply” button at the bottom of the screen. (FYI: When you click apply your screen may go black or blank. DO NOT WORRY! Simply wait 30 seconds. If what was displaying on the screen does not return automatically in that time, hit the [enter] key on your key board, to restore the display on screen.)
  6. Your Time and Date should now be accurate!

Filed under: Computers, Linux-Unix, Software | No Comments »

Configure “ROOT” Access to KDE GUI in Debian GNU/Linux

22nd April - Submitted by bamajr

CONFIGURE ROOT ACCESS TO GUI. The following steps allow the “root” the ability to log into the KDE GUI from the KDE Welcome Screen (“root” access to any GUI is an extremely high security risk!)

Experienced Linux users avidly oppose making this modification to the KDE GUI. Linux was designed to be much more stable and secure than Windoz. Denying the “root” user the ability to log into the KDE GUI directly helps ensure stability and security. Allowing the “root” user to log into the KDE GUI directly, requires a specific bypass of security features.

Think of a Windoz System. When you log in as an “Administrator” you can do anything to the system, without question. However, if you log into a Windoz System as a “Limited User” and want to make changes effecting the overall operation of the machine, you are prompted with a message stating you don’t have rights/permissions to make such changes. One of the biggest security threats to a Windoz System is how many processes run with “Administrative” privileges even if you are not logged in as an Administrator. This leaves gaping holes for potential Virus Infection, System Hi-Jacking, Mal-ware, Spy-ware and other issues.

So, if you realize all the possible ways a Windoz machine can be exploited, why would you want to allow a similar ability on your Linux machine? Well, I suggest that when a system is used in a testing environment, developers can save valuable time if they are not forced to verify changes buy providing a “root” or “su” password.

I do not recommend inexperienced Linux users make the changes discussed in this guide. I also highly recommend that these steps not be performed on a “mission critical” machines such as live workstations or servers. KDE developers specifically recognized the security implications and disabled “root” access to the KDE GUI starting with KDE version 3.4 and newer. So, if you are going to make the change we show you in the steps below, you are doing so at your own risk!

  1. Click on the “MENU” option in the GUI login interface. Select “CONSOLE LOGIN” from this menu.
  2. At the login prompt, enter “root” for the user.
  3. At the password prompt, enter your root password which you setup in the INSTALLING DEBIAN GNU/LINUX.Section of this guide. Once you are logged in, you will be left at the # command prompt.
    Code:

    test:~# cp /etc/kde3/kdm/kdmrc /etc/kde3/kdm/kdmrc_old

    then hit the [enter] key. This will create a duplicate kdmrc file named “kdmrc_old” for a backup and take you back to the # command prompt.

    Code:

    test:~# dir /etc/kde3/kdm/

    to display the files in the kdm directory. Verify that you have both the “kdmrc” file and the backup “kdmrc_old” file. If you have both files, continue to the next step. If you do not have both files, you need to repeat the last two steps again.

    Code:

    test:~# pico /etc/kde3/kdm/kdmrc

    then hit the [enter] key. This will open the kdmrc file in the NANO editor.

  4. Use the Page Down/Up buttons to locate:
    Code:

    AllowRootLogin=false

    and change the file to read:

    Code:

    AllowRootLogin=true

  5. Next, Use the Page Down/Up buttons to locate “[X-*-Greeter]” section. In this section you will be looking for an entry:
    Code:

    HiddenUsers=root

    or you may find it to read as:

    Code:

    #HiddenUsers=root

    Either way you find it, you need to change it so that it reads:

    Code:

    HiddenUsers=

  6. Hold down the CTRL key and press the “X” key. This will ask you if you want to save the file. If you have finished these edits press the “Y” key.
  7. You will then be prompted to enter a path to save the file. Leave the default path and file in place and hit the key.
  8. You will be returned to the # command prompt.
    Code:

    test:~# shutdown now –r

    Then hit the [enter] key. This tells your system to reboot. Do not proceed until the system has come back up and displays the Debian KDE Welcome screen. (Welcome to ??)

  9. Although some modifications have been made, some of this information was obtained from a published article available online at http://www.mepis.org/node/7775

LOG IN AS ROOT (for the first time!)

  1. At the Debian/GNU w/ KDE Welcome Screen, log in to the GUI.
  2. Type in the Username of “root”.
  3. Type in the Password of the “root” user and hit the [enter] key.
  4. At this point the KPersonalizer will launch. The default settings are ok, so just hit the enter key to advance. (You will hit this key 5 times. Wait on the next screen before you hit the key each additional time.)
  5. Once the KPersonalizer has closed you will see the Useful Tips – KTip Screen. (This is a great tool for newbies. It will give tips on how to better use your new system. However, it can be very annoying for many who don’t think they need it.) For the time being just hit the CLOSE button.
  6. Hit the “K” menu button in the lower left-hand corner. (Similar to the Windows START Menu, but with a lot of items you will most likely not recognize.)
  7. Select the “Run Command” option from the “K” menu. This will launch a command screen, with a box for you to type a Command to be run.
  8. In that box type: “konsole” and hit the [enter] key. This will launch a Debian/GNU w/ KDE “Shell – Konsole” session. You should see a curser on command line/text interface waiting at the command prompt (HOSTNAME:~# ) for your input. (Notice the difference in the display of the Prompt. When logged in as an authorized user on the system you will see “$USER@HOSTNAME:~$ ” but when you are logged in as the “root” user, you will see only “HOSTNAME:~# ” instead. This is how you know if you are using the shell as “root” or just an authorized user!)
  9. With your mouse, left click once inside that program, to activate that window.
  10. Then type: “exit” and hit the [enter] key. This will close the “Shell – Konsole” session.
  11. Next, Hit the “K” menu button in the lower left-hand corner. (Similar to the Windows START Menu, but with a lot of items you will most likely not recognize.)
  12. Select the “Run Command” option from the “K” menu. This will launch a command screen, with a box for you to type a Command to be run.
  13. In that box type: “kuser” and hit the [enter] key. This will launch a Debian/GNU w/ KDE “KDE User Manager – KUser” session. DO NOT MAKE ANY CHANGES! This is just to check and make sure you are not prompted for a password, when you launch this program. If you receive a message asking for a password when you launch this program, something was not completed correctly in the CONFIGURE ROOT ACCESS TO GUI section. If this is the case, you will have to log out and start back at the beginning of the CONFIGURE ROOT ACCESS TO GUI Section. If you did not see a message asking for a password, proceed to next step.
  14. With your mouse, single left click on the “File” menu, and then single left click on the “Quit” option. This will close the “KDE User Manager – KUser” session.

ROOT Access to GUI – GRANTED!

Filed under: Computers, Linux-Unix, Software | No Comments »

Installing Debian 4.0 (etch) on a PC

21st April - Submitted by bamajr

Debian GNU/Linux Logo Image 1Debian GNU/Linux Logo Image 2

“Installing Debian 4.0 (etch) on a PC” is an online user’s guide to providing assistance with the basic Installation, Configuration and Setup of a Debian GNU/Linux 4.0 (etch) on a PC.

Before you begin, please understand this guide has to assume you have a fundamental skill set in Computer Use, Linux/Unix Operating Systems, Command Line/Shell Utilities and a basic understanding of the differences between operating systems (I.E. Windows, Apple/Macintosh, DOS, Unix/Linux and others!) and some hardware understanding.

Even if you are well educated in the areas from above, we highly recommended you read this ENTIRE guide before performing any of the steps on your system. As you read through the first time, create a list of questions or concerns you will need to be addressed, before starting work on your own system. Do not start installation or setup on your own system until you have addressed all the questions and/or concerns you have on your list.

Next, you will need to verify the computer you are going to use has hardware which is compatible with Debian GNU/Linux. You can get a better idea of hardware compatibility by reading the “Linux Hardware Compatibility HOW-TO” by Steven Pritchard. The HOW-TO is found at http://www.tldp.org/HOWTO/Hardware-HOWTO/.

There are a couple of things you will want to have available to you during the steps you are about to follow. Your Debian GNU/Linux machine may need an available internet connection. It is best to make sure an “ALWAYS ON” and/or “HIGH-SPEED” internet connection is available and capable of working with the system you are about to modify, before starting. You may also want a second machine with an active internet connection so that you can reference this article or other websites as you got through these steps.

At the time this guide was put together, the steps in our guide were verified multiple times on the “STABLE” release of Debian GNU/Linux 4.0 (etch) w/ KDE 3.5.5 GUI. Current Document Version: 1.0.0.alpha (Document Version) Now, to the grindstone!

  1. Download the KDE ISO package to your desktop from http://www.debian.org/distrib/ (This will take some time, so start this when you have other things you can be doing.) I use the KDE image found at http://cdimage.debian.org/debian-cd/5.0.1/i386/iso-cd/debian-501-i386-kde-CD-1.iso for all my Debian GNU/Linux installations with KDE.
  2. Burn the Debian KDE ISO to a CD/DVD. (I’m not going to cover the steps to burn an .ISO to a CD/DVD at this time. Realistically, if you don’t know how to do this already, you may want to re-evaluate your computer abilities as it relates to using linux.)
  3. Insert the new BOOTABLE Debian KDE installation disk into the system you are going to be converting to a Debian Server.
  4. Configure your BIOS to boot from CD (Some newer PCs will give you the option to hit F12 for a boot menu. From here you can choose to boot to IDE/SCSI/USB CD/DVD-ROM.) Once you have successfully booted to the Debian installation Disk, you will start to see onscreen prompts which you will need to follow. The first one says “Press [enter] to boot into Debian Setup” so you will need to start there!
  5. Once the Debian Setup has loaded, you will simply select the configuration options as you are asked for them. Select the answers that apply to you. You will be prompted in the following order…
    Configuration:

    Language: English

    Configuration:

    Territory: United States

    Configuration:

    Keymap to use: American English

    Configuration:

    Primary Network Interface: Eth1:BroadcomCorp...

    Make sure you select a Network Interface card which is able to be used on the network. Many times a WiFi card may be selected by default, but can’t be used without some additional configuration. I do not recommend selecting a WiFi card for the initial installation!

    Configuration:

    Hostname: MyDebianPC

    This is what Micro$oft Windoz users would call the computer name.

    Configuration:

    Domain Name: YourOwnDomain.com

    If you are using your system on a domain, you will need to enter the domain name here. If you don’t have a domain, enter a fake one followed by .com/.net/.org or etc.

    Configuration:

    Partitioning Method: Guided-use entire disk

    6. Configuration:

    Select Disk to Partition: IDE master (hda) - 80.0 GB hitachi...

    Make sure you select the drive you want Debian installed on. The disk you choose will be wiped clean and the data on that disk will be lost.

    Configuration:

    Partitioning Scheme: All files in one partition

    Configuration:

    Write Changes to Partition: yes

    Configuration:

    Finish partitioning and write changes to disk:

    Configuration:

    Write the changes to disk: yes

    Configuration:

    Select your timezone: Central

    Configuration:

    Root Password:

    Enter a password for the su (super user) account.

    Configuration:

    Confirm Root Password:

    Re-enter the same password you entered for the su (super user) account.

    Configuration:

    Full name for new user: Full Name

    Enter the name you wish to use on your system.

    Configuration:

    Username for new user: Username

    Enter the username you wish to use on your system.

    Configuration:

    password for user account:

    Enter a password for the new user.

    Configuration:

    Confirm user password:

    Re-enter the same password you entered for the new user.

    Configuration:

    Use network mirror: yes

    Using a network mirror will download all the latest and most up to date software packages. You must have a correctly configured Network Interface for this to work. (You can skip this if it doesn’t work, and do it later!)

    Configuration:

    Debian archive mirror country: US

    It is a good practice to select the country your system will be used in.

    Configuration:

    Debian archive mirror:

    It is a good practice to select a mirror as close to you as possible, although this doesn’t always ensure the fastest connection or download speed.

    Configuration:

    Proxy:

    Most people will leave this blank. Only you will know if you need to use a proxy. If you do, you will enter the proxy settings here.

    Configuration:

    Participate in package usage survey: yes

    I always recommend that you participate in the Debian package usage survey. This survey only sends information related to your computer’s hardware and the packages you download, to the Debian Developer Base, to aid in future development. This helps make Debian better. The survey does not send identifiable personal information to Debian.

    After this selection, all the selections you have made to this point will be applied and the software packages will be installed. This may take some time, so don’t be alarmed.

    Configuration:

    Install the Grub boot loader: yes

    If Debian is the only OS (Operating System) you will be using on this machine, at one time, you will select to Install the Grub boot loader. If you are running multiple Operating Systems on this machine, you will have to do some additional configuration here, not supported by this particular user guide.

    The installation will now complete. This can take a little while as well. When it is finished you will be prompted to…

    Configuration:

    un-mount/eject cd

    At this time your CD/DVD Drive should open, allowing you to remove the CD. Then you will select the option to reboot your machine.

Congratulations, you have completed the Debian Installation/Setup Process. You can now begin using Debian. Are you ready to use it for the first time?

FIRST TIME LOGGING INTO DEBIAN. At this point, we just need to verify that your system is usable and works correctly. This section will walk you through logging in as the “$USER” you created when installing Debian GNU/Linux to your system.

  1. At the Debian/GNU w/ KDE Welcome Screen, (this point forward identified as the “Welcome Screen”) log in to the GUI. To identify the “Welcome” Screen, you should see a screen displayed in shades of blue. In the middle of the screen you should see a box which states “Welcome to $HOSTNAME” with a place to type in the Username and Password. This is what you will be using to access the GUI [Graphical User Interface], similar to logging into Windows with a Username and Password. (You should also see the date displayed in the lower right-hand corner of this screen, along with “Session Type” and a “Menu” in the lower left-hand corner of the screen.)
  2. Type in the Username of the personal user you created when setting up your Debian system “$USER”.
  3. Type in the Password of the “$USER” and hit the [enter] key.
  4. At this point the KPersonalizer will launch. The default settings are ok, so just hit the enter key to advance. (You will hit this key 5 times. Wait on the next screen before you hit the key each additional time.)
  5. Once the KPersonalizer has closed you will see the Useful Tips – KTip Screen. Again, just hit the CLOSE button.
  6. Hit the “K” menu button in the lower left-hand corner. (Similar to the Windows START Menu, but with a lot of items you will most likely not recognize.)
  7. Select the “Run Command” option from the “K” menu. This will launch a command screen, with a box for you to type a Command to be run.
  8. In that box type: “konsole” and hit the [enter] key. This will launch a Debian/GNU w/ KDE “Shell – Konsole” session. You should see a curser on command line/text interface waiting at the command prompt ($USER@HOSTNAME:~$ ) for your input.
  9. With your mouse, left click once inside that program, to activate that window.
  10. Then type: “exit” and hit the [enter] key. This will close the “Shell – Konsole” session.
  11. Next, Hit the “K” menu button in the lower left-hand corner.
  12. Select the “Log Out” option. You will get a screen titled; End Session for “$USER” and you will select the “End Current Session” option. This will take you back to the Debian/GNU w/ KDE Welcome Screen.
  13. THIS STEP IS NOW COMPLETE!

The steps in this guide have been verified to work by many different people, on many different systems and with various hardware. However, neither this document, our websites, Sapphire Solutions, Ltd., I or any other person associated with Sapphire Solutions, assume any responsibility for any misprints, possible omissions, your own mistakes, your inability to follow directions, variations in code/text, variations in newer/older versions of the Operating System/Packages/Software, or accuracy of the document.

This is a “BEST EFFORT” document in that those involved in writing it have done the very best to update and maintain this document for accuracy and ease of use. However, because of all the variations and flavors of Linux/Unix we do not guarantee these steps for anyone or on any system.

Filed under: Computers, Linux-Unix, Software | No Comments »

Dell Inspiron 700m

20th April - Submitted by bamajr

If you’ve been to our blog before, you may have read about Dell’s latest, Premier Business Laptop, the Latitude E6500. It came with my choice of Micro$oft’s latest flop – Windoz Vista, or probably the best OS Micro$oft has ever developed – Windoz XP Pro (SP3). Though I preferred the new laptop utilize a professionally installed version of Debian/GNU Linux, I settled for XP Pro instead. Although you can now buy servers from Dell pre-loaded with RedHat, Micro$oft has made it very difficult for users and OEMs to cut the umbilical cord between the PC and Windoz.

I want very badly, to run my favorite distribution, Debian GNU/Linux on this new system. However, the extraordinary hardware feature set found on the E6500 is not widely supported yet in Debian. Even though I figure it won’t be long before the newer hardware is supported, I should probably try Debian/GNU Linux on older Dell laptop first. I have had great success with this distribution on the IBM ThinkPad T40-Series Laptops, but had never tried it on a Dell, until now.

There happens to be a nice Inspiron 700m available, making it possible for me to attempt running Debian on a Dell.

Dell Inspiron 700m Laptop

Dell Inspiron 700m Laptop

I’ve stated before, any good laptop needs to be portable, have good battery life, have external expansion ports, and operate at a reasonable temperature. So, how does the Inspiron 700m stack up?

As you would expect, this much smaller laptop is somewhat limited. You can see the configuration of the system I started with below:

  • PROCESSOR: Intel® Pentium M Dothan 1.8 GHz w/ 2 MB L2 Cache & 400Mhz FSB (Centrino Configuration)
  • OPERATING SYSTEM: Genuine Windows Windows XP Professional
  • LCD PANEL: 12.1 inch Wide Scree (1280×800)
  • WARRANTY & SERVICE: 2 Year Support for End Users
  • VIDEO CARD: Intel® Extreme Graphics 855 GM w/ VGA & S-Video Out
  • MEMORY: 1 GB, DDR SDRAM, (2 x 512 MB DIMMS)
  • INTERNAL KEYBOARD: Internal English Keyboard
  • PRIMARY STORAGE: 40GB, 5400RPM Hitachi/IBM IDE Hardrive
  • OPTICAL DRIVE: 8X DVD+/-RW by NEC Corporation
  • WI-FI WIRELESS CARD: Intel® Wireless™ 2915 802.11a/b/g Mini-PCI Card
  • MODEM: Conexant Internal 56K Modem
  • PC/PCMCIA Card Slot
  • SD Card Reader
  • TOUCH PAD
  • 2 x USB 2.0 PORTS
  • Broadcom 440x 10/100 NIC
  • Sigmatel Audio w/ Headphone and Microphone Jack
  • 1 x 1394 Mini-Firewire PORT
  • 14.8V, 4 Cell Battery
  • 19.5V, 65W, AC Adapter w/ flat cord

I got all the basics in, but it is entirely possible that I missed a few items! So, if you want more information on this system, click here!

The 700m is very portable in that it only weights 4.5 lbs, has a small 12.1 inch screen and is just less than an inch thick. It is the perfect size for carrying in a briefcase or shoulder bag. With some simple search engine research, you can see the Inspiron 700m was moving toward the new Mini Laptops now available from Dell.

This portability didn’t come without sacrifice. There wasn’t an option for a DB9 or DB25 Serial Port, it only had 2 USB Ports and only 1 PCMCIA slot. The smaller size and lighter weight also means a smaller battery. The 4 cell battery which came with this machine didn’t offer enough run time away from an AC outlet. The 700m could easily be taken with you, but if you required more than 2 hours use, you had to make sure you also had the AC adapter packed as well.

Thinking ahead about how this system will be used and what it will be used for, I did some research. Knowing I want to run Debian/GNU Linux on this machine, I read up on whether or not the individual hardware components were compatible with Debian. I also took into consideration, the tasks I most often perform while working in the field. These tasks include installing, testing and turning-up data circuits, POTS Lines, and VoIP Systems. I may also have to configure or test any hardware found on the Local Network. I’m always needing to connect to network equipment through it’s legacy DB9 console port.

This pre-planning and research allows me to identify several deficiencies of the Dell Inspiron 700m. I will need a DB9 Serial Port to connect to network equipment. This is especially true when working with 3Com and Cisco hardware. My research also tells me to replace the Intel WiFi card with one utilizing the Atheros Chipset. I can see the need for additional battery life. The system has 1 GB of RAM which is fine for Linux, but I want more (you know, just in case!). The 5400 RPM hardrive lacks the performance I’m looking for. This means I need to make changes.

The first thing on my mind for this laptop was the Atheros Chipset, WiFi card. I knew I had several in the spare parts I had acquired over several years of working on IBM T40 Series ThinkPads. There may not be a suitable “Windoz” driver for this card in the Dell Machine, but what I will be using it for in Debian, only requires that it has the Atheros Chipset.

Next, I found a SIIG “Single Serial PC Card” (P/N: JJ-PCM012). This card isn’t the best option for a Serial interface though. The DB9 connection is at the end of a foot long dongle, which connects to the Card via RJ45 plug and jack. However, I found it cheap, so it will do for now.

Dell still sells parts for the Inspiron 700m so I purchase a new 6 Cell replacement battery for this machine. I could have gotten any number of batteries from eBay for quite a bit less, but I’m very skeptical of non-OEM batteries.

To finish my system I wanted better performance. I could easily get that extra performance by boosting the RAM from 1Gb to 2 and by replacing the 5400 RPM Hardrive with one running at 7200 RPMs. I found it all new, unopened and with full manufacturer’s warranty on eBay.

Once I had all the new hardware available, installation was a simple task.

In the end, due to the research I did ahead of time, this older Dell Inspiron 700m is now a newer, much more capable machine. It runs Debian GNU/Linux quite well!

Filed under: Computers, Laptops, Linux-Unix | No Comments »

Changing the “root” password on a Debian System

17th April - Submitted by bamajr

Changing the “root” password on a Debian System

It is nearly impossible to recover your existing password, however it may be possible to re-set the “root” password to a new password which you can use going forward.

The process here is possible only if:

  • You are using the “GRUB” boot loader &
  • Your root partition is not encrypted!

This process wont be as difficult as it may seem. If you will simply follow the steps I give you very carefully, I’m sure you will be pleasantly surprised. It is important that you read this entire page of directions completely, before actually performing any of the steps. This way if you have any questions or concerns, you can address them before starting the process.

  1. To get started, your will either need to reboot your system, or turn it on from the “Powered Off” state.
  2. When Grub loads, select the kernel that you want to edit using the up/down arrows. (If you’ve only installed one Linux Operating System, the kernel that is selected and is at the top is the default kernel you use. Also, unless you have configured your system not to automatically load the default kernel, you have to be quick in doing this, or it will proceed to boot into the default kernel in just a few seconds.)
  3. You will then press the “e” key on your keyboard to edit the selected kernel.
  4. Using your up/down arrows, scroll to the line with the kernel on it and press the “e” key again.
  5. At the end of the line, add…
    Code:

    init=/bin/sh

    …then hit the <enter> key. This tells the system that after loading the kernel, go directly to a bash shell, and then takes you back to the kernal screen.

  6. Then press the “b” key to boot.The system will load and take you to the command/bash prompt (i.e. sh-3.1#).
  7. At this point, your root partition is mounted as a “read only” partition, so you won’t be able to change the password on it until you mount it as a “readable/writeable” partition. So, at the command/bash prompt (i.e. sh-3.1#) type…
    Code:

    sh-3.1# mount -orw,remount /

    …then hit the <enter> key. This tells the system to remount the partition with the new option “rw” (readable/writeable).

  8. Now, you will change the password. At the command/bash prompt (i.e. sh-3.1#) type…
    Code:

    sh-3.1# passwd

    …then hit the <enter> key. You will be prompted to enter a new unix password and then confirm it. Each time you type your new password in you will need to hit the <enter> key.

  9. After selecting & confirming your new password you will get a message:[code]passwd: password updated successfully[/code] This confirms that your new password was entered and confirmed and has now been saved. You will notice that you have also been returned to the command/bash prompt (i.e. sh-3.1#).
  10. You will now need to remount the file system as read-only. At the command/bash prompt (i.e. sh-3.1#) type…
    Code:

    sh-3.1# mount -oro,remount /

    …then hit the <enter> key. This tells the system to remount the partition with the default option (read only).

  11. The process will complete and you will be returned to the command/bash prompt (i.e. sh-3.1#), with you partitions intact as they were before we performed the password change. At the command/bash prompt (i.e. sh-3.1#) type…
    Code:

    sh-3.1# exec init

    …then hit the <enter> key. This tells the system to replace the current process with “init” and start the system. (Which is what the kernel would have done by default before we editied it with init=/bin/sh to take us to the command/bash prompt.) Your system will now boot normally.

These steps have been tested on a Debian GNU/Linux system running the “SARGE” release, and work just fine. However, I have not tested these steps in the “ETCH” or “LENNY” releases.

Filed under: Computers, Linux-Unix, Software | No Comments »