[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| slackbook:install [2012/09/06 01:49 (UTC)] – [Target] loaded original text mfillpot | slackbook:install [2012/09/06 02:17 (UTC)] – [Slackware 13.37: a distribution to (re)discover (in French)] removed section, not in original text mfillpot | ||
|---|---|---|---|
| Line 424: | Line 424: | ||
| ==== Source ==== | ==== Source ==== | ||
| - | Here you'll tell the installer where to find the Slackware packages. The most common method is to use the Slackware install DVD or CDs, but there are various other options are available. If you have your packages installed to a partition that you setup in the previous step, you can install from that partition or a pre-mounted directory. (You may need to mount that partition with '' | + | Here you'll tell the installer where to find the Slackware packages. |
| - | + | The most common method is to use the Slackware install DVD or CDs, | |
| - | {{ : | + | but various other options are available. If you have your |
| + | packages installed to a partition that you setup in the previous | ||
| + | step, you can install from that partition or a pre-mounted directory. | ||
| + | (You may need to mount that partition with | ||
| + | **//mount//**(8) first. See chapter 11 for more | ||
| + | details.) Additionally, | ||
| + | options such as NFS shares, FTP, HTTP, and Samba. If you select a | ||
| + | network installation, | ||
| + | information first. We're only going to discuss installation from the | ||
| + | DVD, but other methods are similar and straightforward. | ||
| + | {{ : | ||
| ==== Select ==== | ==== Select ==== | ||
| - | One unique feature of Slackware is its manner of dividing packages into disksets. At the beginning of time, network access to FTP servers was available only through incredibly slow 300 baud modems, so Slackware was split into disk sets that would fit onto floppy disks so users could download and install only those packages they were interested in. Today that practice continues and the installer allows you to chose which sets to install. This allows you to easily skip packages you may not want, such as X and [[slackware: | + | One unique feature of Slackware is its manner of dividing packages |
| + | into disksets. At the beginning of time, network access to FTP | ||
| + | servers was available only through incredibly slow 300 baud modems, | ||
| + | so Slackware was split into disk sets that would fit onto floppy | ||
| + | disks so users could download and install only those packages they | ||
| + | were interested in. Today that practice continues and the installer | ||
| + | allows you to chose which sets to install. This allows you to | ||
| + | easily skip packages you may not want, such as X and KDE on headless | ||
| + | servers or Emacs on everything. Please note that the //" | ||
| + | always required. | ||
| - | {{ : | ||
| + | {{ : | ||
| ==== Install ==== | ==== Install ==== | ||
| - | Finally we get to the meat of the installer. At this stage, Slackware will ask you what method to use to choose | + | Finally we get to the meat of the installer. At this stage, Slackware |
| + | will ask you what method to use to chose packages. If this is your | ||
| + | first time installing Slackware, the //" | ||
| + | recommended. Even if this isn't your first time, you'll probably want | ||
| + | to use it anyway. | ||
| - | The " | ||
| - | The "newbie" | + | The //"menu"// and //" |
| + | individual packages | ||
| + | familiar with the OS. These methods allow such users to quickly prune | ||
| + | packages from the installer to build a very minimal system. If you | ||
| + | don't know what you're doing (sometimes even if you do) you're likely | ||
| + | to leave out crucial pieces of software and end up with a broken | ||
| + | system. | ||
| - | The " | ||
| - | {{ : | + | The //" |
| + | takes a very long time to install. This method will install all the | ||
| + | required packages, then prompt you individually for every other | ||
| + | package. The big advantage here is that is pauses and gives you a | ||
| + | brief overview of the package contents. For a new user, this | ||
| + | introduction into what is included with Slackware can be informative. | ||
| + | For most other users it is a long and tedious process. | ||
| + | |||
| + | The //" | ||
| + | the greatest skill and expertise with Slackware. These methods allow | ||
| + | the user to install packages from custom tagfiles. Tagfiles are | ||
| + | only rarely used. We won't discuss them in this book. | ||
| + | |||
| + | |||
| + | {{ : | ||
| ==== Configure ==== | ==== Configure ==== | ||
| - | Once all the packages are installed you're nearly finished. At this stage, Slackware will prompt you with a variety of configuration tasks for your new operating system. Many of these are optional, but most users will need to set something up here. Depending on the packages you've installed, you may be offered different configuration options than the ones shown here, but we've included all the really important ones. | + | Once all the packages are installed you're nearly finished. At this |
| + | stage, Slackware will prompt you with a variety of configuration | ||
| + | tasks for your new operating system. Many of these are optional, but | ||
| + | most users will need to set something up here. Depending on the | ||
| + | packages you've installed, you may be offered different configuration | ||
| + | options than the ones shown here, but we've included all the really | ||
| + | important ones. | ||
| - | The first thing you'll likely be prompted to do is setup a boot disk. In the past this was typically a 1.44MB floppy disk, but today' | ||
| - | {{ : | + | The first thing you'll likely be prompted to do is setup a boot disk. |
| + | In the past this was typically a 1.44MB floppy disk, but today' | ||
| + | Linux kernel is far too large to fit on a single floppy, so | ||
| + | Slackware offers to create a bootable USB flash memory stick. Of | ||
| + | course, your computer must support booting from USB in order to use | ||
| + | a USB boot stick (most modern computers do). If you do not intend to | ||
| + | use LILO or another traditional boot loader, you should consider | ||
| + | making a USB boot stick. Please note that doing so will erase the | ||
| + | contents of whatever memory stick you're using, so be careful. | ||
| - | Nearly everyone will need to setup the LInux LOader, LILO. LILO is in charge of booting the Linux kernel and connecting to an initrd or the root filesystem. Without it (or some other boot loader), your new Slackware operating system will not boot. Slackware offers a few options here. The " | ||
| - | LILO is a very important part of your Slackware system, so an entire section of the next chapter is devoted to it. If you're having difficulty configuring LILO at this stage, you may want to skip ahead and read Chapter 3 first, then return here. | + | {{ : |
| - | {{ : | + | Nearly everyone will need to setup the LInux LOader, LILO. LILO is |
| + | in charge of booting the Linux kernel and connecting to an initrd or | ||
| + | the root filesystem. Without it (or some other boot loader), your new | ||
| + | Slackware operating system will not boot. Slackware offers a few | ||
| + | options here. The //" | ||
| + | LILO for your computer, and works well with very simple systems. If | ||
| + | Slackware is the only operating system on your computer, it should | ||
| + | configure and install LILO for you without any hassels. If you don' | ||
| + | trust the simpler method to work, or if you want to take an in-depth | ||
| + | look at how to configure LILO, the //" | ||
| + | that complicated. This method will take you through each step and | ||
| + | offer to setup dual-boot for Windows and other Linux operating | ||
| + | systems. It also allows you to append kernel command parameters (most | ||
| + | users will not need to specify any though). | ||
| - | This simple step allows you to configure and activate a console mouse for use outside of the graphical desktops. By activating a console mouse, you'll be able to easily copy and paste from within the Slackware terminal. Most users will need to choose one of the first three options, but many are offered, and yes those ancient two-button serial mice do work. | ||
| - | The next stage in configuring your install | + | LILO is a very important part of your Slackware system, so an entire |
| + | section of the next chapter | ||
| + | difficulty configuring LILO at this stage, you may want to skip ahead | ||
| + | and read Chapter 3 first, then return here. | ||
| - | The following screen will prompt you for a domainname, such as example.org. The combination of the hostname and the domainname can be used to navigate between computers in your network if you use an internal DNS service or maintain your /etc/hosts file. | ||
| - | You have three options when setting your IP address; you may assign it a static IP, or you may use DHCP, or you may configure a loopback connection. The simplest option, and probably the most common for laptops or computers on a basic network, is to let a DHCP server assign IP addresses dynamically. In practice, this often results in a consistent address since both dhcpcd and dhclient initially request the same address previously assigned. If the address is unavailable then the machine gets a new one, but on small networks this may never happen. | + | {{ : |
| - | If the DHCP server on your network requires | + | This simple step allows you to configure and activate a console mouse |
| + | for use outside of the graphical desktops. By activating | ||
| + | mouse, | ||
| + | Slackware terminal. Most users will need to choose one of the first | ||
| + | three options, but many are offered, and yes those ancient two-button | ||
| + | serial mice do work. | ||
| - | To use a static IP address, you must provide: | ||
| - | **Static IP Address** | + | {{ : |
| - | * IP Address: the address of your computer, such as '' | + | The next stage in configuring |
| - | * Netmask: | + | configuration. If you don't wish to configure |
| - | * Gateway Address: the address of the gateway server providing internet access | + | stage, you may decline, but otherwise you'll be prompted to |
| - | * Nameserver: most likely, you' | + | provide a hostname for your computer. If you're unsure what to do |
| + | here, you might want to read through [[slackbook: | ||
| + | first. | ||
| - | The final screen during static IP address configuration is a confirmation screen, where you're permitted to accept your choices, edit them, or even restart the IP address configuration in case you decide to use DHCP instead. | ||
| - | Your network configuration is now complete. | + | The following screens will prompt |
| + | for a domainname, such as | ||
| + | example.org. The combination | ||
| + | can be used to navigate between computers | ||
| + | use an internal DNS service | ||
| + | ''/ | ||
| + | up your network, Slackware will name your computer //" | ||
| + | a song by the Grateful Dead. | ||
| - | As the startup services window warns, you should only turn on the startup services that you actually intend to use. This not only decreases boot time but makes for a more secure system. | ||
| - | Every computer needs to keep track of the current time, and with so many timezones how does Slackware | + | You have three options when setting your IP address; you may |
| + | assign it a static IP, use DHCP, or configure a | ||
| + | loopback connection. The simplest option, and probably | ||
| + | common for laptops or computers on a basic network, is to let a | ||
| + | DHCP server assign IP addresses dynamically. Unless you are | ||
| + | installing | ||
| + | do not need to setup a static IP address. If you're not sure which | ||
| + | of these options | ||
| - | If you installed the X disk set, you'll be prompted to select a default window manager or desktop environment. What you select here will apply to every user on your computer, unless that user decides to run '' | ||
| - | {{ : | + | Rarely DHCP servers requires you specify a DHCP |
| + | hostname before you're permitted to connect. You can enter this on | ||
| + | the Set DHCP Hostname screen. This is almost always be the same | ||
| + | hostname you entered earlier. | ||
| - | The last configuration step is setting a root password. The root user is the "super user" on Slackware and all other UNIX-like operating systems. Think of root as the Administrator user. root knows all, sees all, and can do all, so setting a strong root password is just common sense. | ||
| - | With this last step complete, | + | If you choose to set a static IP address, |
| - | ===== Post Installation ===== | + | enter it along with the netmask, gateway IP address, and what |
| + | nameserver to use. | ||
| - | When you have rebooted into your new Slackware installation, | ||
| - | The quickest and easiest way to create | + | The final screen during static IP address configuration is a |
| + | confirmation screen, where you're permitted | ||
| + | choices, edit them, or even restart | ||
| + | in case you decide to use DHCP instead. | ||
| - | Another important step is to make sure that your installation is up-to-date as new updates are being released that can include security fixes. To do that we can use the [[slackware: | ||
| - | One last thing - there will be mail in the root user's mailbox filled with useful information about package management, | + | Once your network configuration is completed Slackware |
| + | prompt you to configure | ||
| + | automatically upon boot. Helpful descriptions of each service appear | ||
| + | both to the right of the service name as well as at the bottom of the | ||
| + | screen. If you' | ||
| + | defaults in place. What services are started | ||
| + | easily | ||
| - | === Configuring Graphical Logins === | ||
| - | Once your system is up to date and you have created your first user, you may want to configure your system to boot into X by default, with a graphical login instead of a console login. | ||
| - | # Default runlevel. (Do not set to 0 or 6) | + | Every computer needs to keep track of the current time, and with so |
| - | | + | many timezones around the world you |
| - | + | have to tell Slackware which one to use. | |
| - | To be this: | + | If your computer' |
| + | Universal Time), you'll need to select that; most hardware clocks are | ||
| + | not set to UTC from the factory (though you could set it that way on | ||
| + | your own; Slackware doesn' | ||
| + | from the list provided and off you go. | ||
| - | # Default runlevel. (Do not set to 0 or 6) | ||
| - | id: | ||
| - | This sets your default run-level to 4, which is Slackware' | + | {{ : |
| - | You can manually enter run-level 4 by entering, as root, `init 4`. | + | If you installed the X disk set, you'll be prompted to select a |
| + | default window manager or desktop environment. What you select | ||
| + | here will apply to every user on your computer, unless that user | ||
| + | decides to run **// | ||
| + | a different one. Don't be alarmed if the options you see below do | ||
| + | not match the ones Slackware offers you. | ||
| + | **// | ||
| + | installed. So for example, if you elected to skip the //" | ||
| + | KDE will not be offered. | ||
| - | To select or switch between available [[slackware: | ||
| - | ===== References ===== | ||
| - | * Original source: http://slackbook.org/ | + | {{ :slackbook:setup-xwmconfig.png? |
| - | ===== External links ===== | + | The last configuration step is setting a root password. The root |
| + | user is the //" | ||
| + | operating systems. Think of root as the Administrator user. root | ||
| + | knows all, sees all, and can do all, so setting a strong root | ||
| + | password is just common sense. | ||
| - | * [[ftp:// | ||
| - | * [[http:// | ||
| - | ==== Slackware | + | With this last step complete, you can now exit the Slackware |
| + | installer and reboot with a good old < | ||
| + | < | ||
| + | Slackware installation disk, and if you performed all the steps | ||
| + | correctly, your computer will boot into your new Slackware | ||
| + | linux system. If something went wrong, you probably skipped the | ||
| + | LILO configuration step or made an error there somehow. Thankfully, | ||
| + | the next chapter should help you sort that out. | ||
| - | This is a series of four detailed articles about Slackware, written by Kiki Novak for the french magazine //Planète Linux// (issues 67, 68, 69 and 70, November 2011 - May 2012). | ||
| - | **Author' | + | When you have rebooted into your new Slackware installation, |
| + | very first step you should take is to create a user. By | ||
| + | default, the only user that exists after the install is the root | ||
| + | user, and it's dangerous | ||
| + | there are no restrictions as to what that user can do. | ||
| + | |||
| + | |||
| + | The quickest and easiest way to create a normal user for yourself | ||
| + | is to log in as root with the root password that you created at | ||
| + | the end of the intallation process, and then issue the | ||
| + | **// | ||
| + | you in creating a user; see [[slackbook:users|User and Group Management|the section called “Managing Users and Groups" | ||
| + | information. | ||
| + | |||
| + | ===== References ===== | ||
| + | |||
| + | * Original source: http:// | ||
| - | * [[http:// | ||
| - | * History of Slackware | ||
| - | * A few good reasons to choose Slackware | ||
| - | * A few good reasons not to choose Slackware | ||
| - | * It's not a bug, it's a feature! | ||
| - | * How to get Slackware | ||
| - | * Slackware-specific documentation | ||
| - | * [[http:// | ||
| - | * Choose your boot parameters | ||
| - | * Select your keyboard layout | ||
| - | * Partition your hard disk | ||
| - | * Format your partitions | ||
| - | * Decide what you want to install | ||
| - | * Configure and install the bootloader | ||
| - | * Your mouse in console mode | ||
| - | * Networking and services | ||
| - | * Which font for the console? | ||
| - | * System clock and timezone | ||
| - | * Which graphical environment? | ||
| - | * A password for root | ||
| - | * Finish the installation and reboot | ||
| - | * What now? | ||
| - | * [[http:// | ||
| - | * Create an initrd and use the generic kernel | ||
| - | * Fine-tune the LILO bootloader | ||
| - | * Configure the network | ||
| - | * Add one or more users | ||
| - | * Configure the sound | ||
| - | * [[http:// | ||
| - | * Traditional Slackware package management | ||
| - | * Manage official Slackware packages using slackpkg | ||
| - | * Help! I can't find a package I need! | ||
| - | * Building a package using a SlackBuild script from SlackBuilds.org | ||
| - | * Manage SlackBuilds comfortably using sbopkg | ||
| - | * Configure the graphical server X.org | ||
| - | * Select your graphical environment | ||
| - | * Slackware in French | ||
| - | Original files (ODT manuscript, screenshots, | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
