[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.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
slackware:install [2012/09/11 23:02 (UTC)] – [Post Installation] Add link to multilib article. alienbobslackware:install [2013/12/09 09:15 (UTC)] – [Post Installation] Formatting alienbob
Line 12: Line 12:
  
 Once your computer boots from the CD you'll be taken to a screen that allows you to enter any special kernel parameters. This is here primarily to allow you to use the installer as a sort of rescue disk. Some systems may need special kernel parameters in order to boot, but these are very rare exceptions to the norm. Most users can simply press enter to let the kernel boot. Once your computer boots from the CD you'll be taken to a screen that allows you to enter any special kernel parameters. This is here primarily to allow you to use the installer as a sort of rescue disk. Some systems may need special kernel parameters in order to boot, but these are very rare exceptions to the norm. Most users can simply press enter to let the kernel boot.
 +{{ :slackware:install:1-welcome.png?nolink |}}
  
-  Welcome to Slackware version 13.37 (Linux kernel 2.6.37.6)! + 
-   +
-  If you need to pass extra parameters to the kernel, enter them at the prompt +
-  below after the name of the kernel to boot (huge.s etc). +
-   +
-  In a pinch, you can boot your system from here with a command like: +
-   +
-  boot: huge.s root=/dev/sda1 rdinit= ro  +
-   +
-  In the example above, /dev/sda1 is the / Linux partition. +
-   +
-  This prompt is just for entering extra parameters.  If you don't need to enter +
-  any parameters, hit ENTER to boot the default kernel "huge.s" or press [F2]  +
-  for a listing of more kernel choices. +
 You should see a lot of text go flying across your screen. Don't be alarmed, this is all perfectly normal. The text you see is generated by the kernel during boot-up as it discovers your hardware and prepares to load the operating system (in this case, the installer). You can later read these messages with the ''dmesg(1)'' command if you're interested. Often these messages are very important for troubleshooting any hardware problems you may have. Once the kernel has completed its hardware discovery, the messages should stop and you'll be given an option to load support for non-us keyboards. You should see a lot of text go flying across your screen. Don't be alarmed, this is all perfectly normal. The text you see is generated by the kernel during boot-up as it discovers your hardware and prepares to load the operating system (in this case, the installer). You can later read these messages with the ''dmesg(1)'' command if you're interested. Often these messages are very important for troubleshooting any hardware problems you may have. Once the kernel has completed its hardware discovery, the messages should stop and you'll be given an option to load support for non-us keyboards.
  
Line 276: Line 263:
 One last thing - there will be mail in the root user's mailbox filled with useful information about package management, as well as system configuration and maintenance. You should check it with your favorite mail client. If you have not used any of the included mail clients, alpine is a good suggestion to get started quickly and easily. One last thing - there will be mail in the root user's mailbox filled with useful information about package management, as well as system configuration and maintenance. You should check it with your favorite mail client. If you have not used any of the included mail clients, alpine is a good suggestion to get started quickly and easily.
  
-=== Configuring Graphical Logins ===+==== 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.  You can first test that X auto-detects your video correctly by issuing the `startx` command.  If X11 starts and you end up at a desktop, you're probably good to go.  Open the /etc/inittab file, as root, in your editor of choice.  Change the following line: 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.  You can first test that X auto-detects your video correctly by issuing the `startx` command.  If X11 starts and you end up at a desktop, you're probably good to go.  Open the /etc/inittab file, as root, in your editor of choice.  Change the following line:
  
Line 293: Line 280:
 To select or switch between available [[slackware:desktop_environment|desktop environments]] run ''xwmconfig'' as root. To select or switch between available [[slackware:desktop_environment|desktop environments]] run ''xwmconfig'' as root.
  
-=== Adding multilib ===+==== Adding multilib ====
 If you just installed the 64-bit version of Slackware, you will soon discover that this is a "pure" 64-bit environment. In other words: out of the box, Slackware64 is not able to run or compile 32-bit program binaries. \\ Luckily, this is simple to fix. Adding the capability to run and/or compile 32-bit programs will turn your Slackware64 into a "multilib" system. Instructions can be found in the article "[[slackware:multilib|Adding Multilib Capability to Slackware on x86_64 Architecture]]" in our Wiki. If you just installed the 64-bit version of Slackware, you will soon discover that this is a "pure" 64-bit environment. In other words: out of the box, Slackware64 is not able to run or compile 32-bit program binaries. \\ Luckily, this is simple to fix. Adding the capability to run and/or compile 32-bit programs will turn your Slackware64 into a "multilib" system. Instructions can be found in the article "[[slackware:multilib|Adding Multilib Capability to Slackware on x86_64 Architecture]]" in our Wiki.
 ===== References ===== ===== References =====

Trace:

slackware:install ()