HOW TO INSTALL GSB: GNOME SlackBuild 3.0 (for Slackware/Slackware64 13.37) ======================================= Contents 1. Introduction 2. Reporting Bugs 3. Quick-Start Installation using Slapt-get 4. Other Installation methods 4.1 Before installation 4.2 Default Automated net installation 4.3 Full Manual Slapt-get installation method 5. After installation 6. Uninstalling GNOME SlackBuild 7. Questions, Comments and Support 1. Introduction --------------- This document provides information on installing our pre-built GSB packages on Slackware and Slackware64. GSB encompasses all needed packages for a fully configurable, customisable and usable GNOME desktop environment. If you haven't yet, you should read about the GSB project before installing: This version of GSB is built and only supported on: Slackware 13.37 Slackware64 13.37 If you are trying to use GSB on systems other than the above you will encounter problems. If you are running a previous version of Slackware or Slackware64, you must upgrade. Do not attempt to install this version of GSB on previous versions of Slackware and Slackware64. 2. Reporting Bugs ------------------ Any questions or bug reports, please email gsb-dev@googlegroups.com or drop by the #gsb channel on freenode. 3. Quick-Start Installation using Slapt-get ------------------------------------------- If you have not used slapt-get before then you should skip below to the section marked "Slapt-get Installation Method" and give it a quick read before proceeding. It is recommended that you upgrade to the latest slapt-get before installing or upgrading GSB. You can find the slapt-get package at: For Slackware: http://www.slackware.org.uk/gsb/gsb-3.0_slackware-13.37/gsb/ad/ For Slackware64: http://www.slackware.org.uk/gsb/gsb64-3.0_slackware-13.37/gsb/ad/ For a list of available mirrors, please see MIRRORS.TXT. Update your /etc/slapt-get/slapt-getrc file to point to Slackware 13.37 and GNOMESlackBuild repositories. Make sure to add the :OFFICIAL tag to the end of your SOURCE= which points to the Slackware repository, and the tag :CUSTOM to the SOURCE= line which points to your GNOMESlackBuild repository. Without the :CUSTOM tag, the official Slackware packages will outweigh GSB packages, and not all required packages will be upgraded. It it recommended that your drop to single user mode (with networking) before upgrading your machine or doing a full installation. It is also wise to reboot afterward. For more details, see below "Before Installation" ** UPGRADING FROM A PREVIOUS INSTALLATION ** For more details, please consult the UPGRADE.TXT. If you are upgrading your GSB from an earlier version, make sure to point your /etc/slapt-get/slapt-getrc SOURCE= to a gsb-current repository. 1. Upgrade slapt-get package and update repository: $ slapt-get --update && slapt-get --install slapt-get 2. Add gpg keys: $ slapt-get --add-keys 3. Upgrade your packages: $ slapt-get --upgrade ** INSTALLING NEW ** If you are installing on a fresh Slackware 13.37 system, then you will need to grab a copy of slapt-get from the repository (above), and then update your /etc/slapt-get/slapt-getrc file. Afterwards: 1. Update slapt-get: $ slapt-get --update 2. Update gpg keys: $ slapt-get --add-keys 3. Upgrade your packages and delete obsolete or old packages which have been removed from the repository: $ slapt-get --upgrade --remove-obsolete 4. Install the GSB desktop via the metapackage: $ slapt-get --install gsb-desktop All relevant packages will installed or upgraded through this metapackage. You can then add additional packages if you wish via slapt-get or gslapt from your new GNOME desktop. 4. Other Installation methods ----------------------------- GSB currently supports two other installation methos; a fully automated net based installer and installation from a local repository mirror. The automated net installer, obviously, requires an active internet connection to perform the installation - packages are downloaded from one of the GSB mirror sites (randomly selected from our mirrors list) and installed onto the system automatically. However, with the net installer there is no facility to select what packages will be installed - the net installer will install all packages listed in the 'gsb-complete' meta package (see below). This is by far the best option for users who want a fully functional, fully featured GNOME desktop. If net installation is not possible or there are many installations to be performed, GSB can be installed from a local mirror/repository. This procedure requires a full local copy of the whole GSB binary tree - either on hard disk, a CDROM or some other portable media, and follows the same general process as the manual slapt-get net installation, except that slapt-get is configured to use a local GSB repository rather than a online one. Each of the procedures for installation is detailed below. Once you have decided which option is best for you, please refer to the appropriate section for full instructions. 4.1 Before installation ------------------------ The installation is best done at runlevel 3 without X11 running. It is not advisable to do the installation from within an XTerm or Terminal Emulator. If you have any X11 sessions open which were started with the 'startx' command (or similar) after you logged into the console in text mode, you must exit those sessions to insure the installation goes smoothly. Once those are closed you will probably be returned to your normal (unprivileged) user account shell prompt, you should now logout using: $ logout You should now be back at the text based 'login:' prompt. Skip the next 2 paragraphs nad continue with the procedure. If your system boots (or has been put) into runlevel 4 (the graphical login runlevel), you must put the system back into runlevel 3. Firstly, if you are in X11, you need to get to a text login console - hold down the Ctl and Alt keys and press F6. This will take you to a text based 'login:' prompt, where you should log in as 'root' using your root password. Once logged in, use this command to bring the system back to runlevel 3: $ init 3 Wait for the process to finish (it might help to hit Enter a couple of times after 20-30 seconds). During the process, your active terminal may be changed, so you may not be returned to the shell prompt. If the active terminal has changed, it will probably now show another 'login:' prompt. If you are returned to the shell prompt after hitting Enter a couple of times, you do not need to log out (and can skip the rest of this section) - you are logged in as 'root' and can begin installation. In either of the two cases above, if you have a text based 'login:' prompt on screen, you must login as 'root' using your own root password. You should now be logged into your system as the 'root' user, your system should be at runlevel 3, and there should be no active X11 sessions. 4.2 Default Automated net installation --------------------------------------- This is the simplest method of installation and requires very little detailed explanation - you simply run one command and a full installation of GSB, plus any of the required Slackware/Slackware64 package dependancies, will be installed. Depending on whether you have 'wget', 'curl' or 'lynx' available on your system, you can use one of the following commands to begin installation. Be sure to use the correct URI for your architecture - GSB supports both IA32 (32 bit Slackware) and x86_64 (64 bit Slackware64). Using wget: For x86: $ wget -q -O- http://gnomeslackbuild.org/net-install | bash For x86_64: $ wget -q -O- http://gnomeslackbuild.org/net-install/64 | bash Using curl: For x86: $ curl http://gnomeslackbuild.org/net-install | bash For x86_64: $ curl http://gnomeslackbuild.org/net-install/64 | bash Using lynx: For x86: $ lynx --source http://gnomeslackbuild.org/net-install | bash For x86_64: $ lynx --source http://gnomeslackbuild.org/net-install/64 | bash 4.3 Full Manual Slapt-get installation method ----------------------------------------- You will need to update your /etc/slapt-get/slapt-getrc file according to the instructions above in "3. Quick-Start Installation using Slapt-get". Then you will need to update the slapt-get cache files: $ slapt-get --update To install all GSB packages, run the following command: $ slapt-get --available | awk {'print $1'} | grep "gsb$" | grep -v l10n | \ xargs slapt-get --install -y With any luck, the installation process will finish without any errors or problems and GSB will now be fully installed on your system. Please read the section 'After installation' (and the sections which follow it) below. 4.5 Installing from a local copy -------------------------------- Installing from a local copy of GSB and/or Slackware/Slackware64 is a very similar process to the manual slapt-get net installation detailed above. It is recommended that you read that section in addition to this one, in order to understand the slapt-get installtion process. Only brief instructions are given here. For the following instructions, referrs to the local filesystem location for the GSB mirror, and referrs to the local filesystem location to the Slackware/Slackware64 mirror. Both of these should, obviously, be replaced with the full correct paths to each mirror. These paths can also be on a CDROM or USB device if the mirrors are located on such media. Add the two SOURCE entries to point to a local mount and directory: SOURCE=file:// SOURCE=file:// Save the file and exit the text editor. Use these commands to update the slapt-get cache files: $ slapt-get --update You can then install packages as described above. 5. After installation --------------------- IMPORTANT! Fix your config files. Some of the config files in /etc are going to need your attention. You'll find the new incoming config files on your system with the ".new" extension. You may need to fill these in with information from your old config files and then move them over. It is highly recommended that you reboot your system after installation in order to insure that all services/daemons required by GNOME have been started. You can start the daemons manually and avoid the need to reboot, but there are a number of services that need to be started. It may be easier to reboot; otherwise, to must reload udev and message bus. $ /etc/rc.d/rc.udev reload $ /etc/rc.d/rc.messagebus reload Depending on your packages installed, you may also want to enable new services at boot time. $ chmod +x /etc/rc.d/rc.avahidaemon $ chmod +x /etc/rc.d/rc.networkmanager $ /etc/rc.d/rc.avahidaemon start $ /etc/rc.d/rc.networkmanager start If your system is configured to start at run level 4 (the X11 graphical login), your usual display manager should now have been replaced with GDM - the GNOME Display Manager. You should be able to log in with your usual username and password in the same way as you did before - but be sure to check that GNOME (or Compiz GNOME if you want fancy 3D stuffs) is selected in the Sessions list. If you usually log into your system at run level 3 (text based login) and then use 'startx' or similar you should log in as your usual (not root!) user and run: $ xwmconfig Select the GNOME option from the menu. You can then use 'startx' to start GSB as usual. If you have any problems starting GSB or logging in, please see below for support links and mailing lists. 6. Uninstalling GNOME SlackBuild -------------------------------- You will need to remove all GNOME SlackBuild packages, and then re-install any Slackware/Slackware64 provided packages that may have been replaced by GSB. To remove all the GSB packages, run (as root): $ removepkg $(ls /var/log/packages/*gsb | grep -v slapt-get) | tee /tmp/gsb-uninstall.log This will remove all GNOMESlackBuild packages and leave slapt-get still installed to help reinstalling any required Slackware packages again. You should probably check the uninstall log at /tmp/gsb-uninstall.log to see if any files installed by GSB packages got left behind - it's up to you how much housekeeping you want to do on those files. :-) Once all the GSB packages are removed and you've done any housekeeping, you will need to re-install any Slackware/Slackware64 packages which were replaced by the GSB provided ones. A complete list of standard Slackware/Slackware64 packages GSB replaced during installation can be found in our SLACKWARE_REPLACED_PACKAGES.TXT. If you are using slapt-get to re-install the packages, you will need to comment out any SOURCE= line(s) for GSB in your /etc/slapt-get/slapt-getrc file (if any were added during installation). Then be sure to run: $ slapt-get --update Once that is finished, you can re-install the standard Slackware packages by running: $ slapt-get --install where the is those obtained from the replaced packages list. If you don't use slapt-get to maintain your Slackware/Slackware64 packages, you can use 'installpkg' (or whatever your preferred package management front-end is) to simply re-install any required packages. It would also be a good idea to select an alternative window manager (as detailed in the 'After installation' section), and reboot your system to insure all GSB daemon/services have been stopped. 7. Questions, Comments and Support ---------------------------------- Do one of the following (in this order): * Read the FAQ.TXT and CHANGES_AND_HINTS.TXT for extra hints. * For bug reports and feature requests, please check our issue tracker for previous reports of the same problem and possible solutions. If your bug or feature is not solved or listed, add it: * Join the GSB User Discussion Mailing List: Firstly, check the archive to see if anyone else has had a similar problem which has already been solved. You will not get any points for requesting help with a problem that has already been addressed. The mailing list is the easiest and preferred method of contact for support type issues - it allows us to keep an archive of questions and answers. Note: You must be subscribed to the mailing list in order to post messages. * Join the #gsb IRC channel on irc.freenode.net and ask questions. On IRC, we may appear to be always online, but we are frequently away from the console and you may not receive an answer for a while. But stick around since we'll try to give a reply, eventually :-) --- The GNOME Slackbuild Team