Differences

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

--- install [2015/05/09 09:05]
slackermedia
+++ install [2021/06/03 19:48] (current)
@@ Line 1: / Line 1: @@
 ====== The Installer ======
@@ Line 39: / Line 42: @@
 Slackware itself will take care of creating the filesystem, later.
-<WARN alert>
+<WRAP alert>
 Slackermedia assumes that you are using new drives, or at least drives that you
 have already backed up, because //everything// in this section will **destroy** any
 existing data on the drives. //That is the intent//. Do not follow this section
 verbatim if you have valuable data on your drive that you do not intend to erase.
-</WARN>
+</WRAP>
 The way Linux sees hard drives is by identifying what controller they are connected to on the motherboard, and then by assigning a letter to denote the order in which they were detected. The prefix for a hard drive is ''sd'' ([[http://tldp.org/HOWTO/Partition/devices.htm|for
 historical purposes]]). So the identifier for the first hard drive on a system would be ''sda'', and the second drive would be ''sdb''.
-You can verify what drives Linux finds by looking in the device, or ''/dev'', directory. You can see this by typing this:
+You can verify what drives Linux finds by looking in the device, or ''/dev'', directory. Do not type the ''#'' mark; that just represents the root prompt on your screen. However, the question mark is literal; type exactly ''sd?''
 <code>
@@ Line 55: / Line 58: @@
 </code>
-<WARN important>
+A friendlier view of devices attached to your computer, use ''lsblk'':
-Do not type the ''#'' mark; that just represents the root prompt on your screen.
-However, the question mark is literal; type exactly ''sd?''
+<code>
-</WARN>
+# lsblk
+</code>
 On a laptop, you probably only have one drive, so the result will likely be ''/dev/sda'' but a desktop can (and arguably should) have multiple drives, so results might be ''/dev/sda'' ''/dev/sdb'' ''/dev/sdc'', and so on to the last drive.
@@ Line 65: / Line 68: @@
 Whether you have one or three or more drives, each drive must have a partition in order for an OS to be installed.
-<WARN alert>
+<WRAP alert>
 Mistakes are easy to make. Disconnect any drive that you do not intend to erase while you create partitions, just in case you type in the wrong drive and erase something you did not mean to erase.
 In other words: only the drives you intend to erase should be attached to your computer, to prevent accidental data loss.
-</WARN>
+</WRAP>
 To create an MBR (for use with BIOS or UEFI-in-BIOS-mode) partition label (replace ''sdX'' with the appropriate drive identifier, and do not type the ''#'' mark, which is your Linux prompt):
@@ Line 100: / Line 103: @@
 </code>
-<WARN alert>
+<WRAP alert>
 If you are using multiple drives, then you should only make a swap partition on one non-SSD drive. You do not need swap space on each physical drive.
-</WARN>
+</WRAP>
 On old systems, swap space was a necessity in the event that you ran out of RAM. This is less of an issue now that RAM is relatively cheap, so if you have heaps of RAM then you probably do not need swap space. If you are using a desktop and do not require hibernation, or you just don't anticipate needing hibernation, then you can opt to forsake the swap partition and just create a single partition that spans the entire drive:
@@ Line 138: / Line 141: @@
 The installer will offer to format each drive for you. It is usually safe (and quickest) to perform a standard Format with no bad block checking. Use ''ext4'' or ''jfs'' for your filesystem type.
-<WARN info>
+<WRAP tip>
 Slackermedia recommends ''jfs'' solely based on experiential data. In some ways, it has fewer features than something like ''ext4'' but it is a good, stable open source filesystem that is useful on both SSD and standard drives, and it is backed by IBM and used by IBM on large amounts of data in very large data centers. It makes the most sense for Slackermedia, and has successfully powered
 Slackermedia machines that are in production for years (including one that is exclusively SSD).
 If you anticipate requiring re-sizing your filesystem at some point, then ''ext4'' is a superiour choice. If you know Linux well and have some other reason to prefer ''ext4'' or ''xfs'' or some other filesystem type, then use your better judgement to build your system.
-</WARN>
+</WRAP>
 Once your drives are formatted, select the source of the installation.
@@ Line 188: / Line 191: @@
 standard option.
-<WARN info>
+<WRAP important>
 This resolution does not affect the GUI; that will be auto-detected when you start the desktop. This resolution setting governs the initial text console.
-</WARN>
+</WRAP>
 The next few prompts are well documented onscreen, so read the info provided and continue with the install until you are prompted to configure ''GPM''. This defaults to **Yes** but it is safe to choose **No** if you do not anticipate using your mouse in a text-only console. If you are
@@ Line 225: / Line 228: @@
 To use ''wicd'', choose DHCP for now and install wicd later.
-<WARN important>
+<WRAP important>
 If you do not understand why any of those things are significant, or are confused about what to choose, then you should choose ''NetworkManager''.
-<WARN>
+</WRAP>
 Next, you are provided with a list of startup options. This is largely geared toward sys admins, or computer users who like to do sys admin tasks (like reading logs, playing on the network, start up various services, and so on).
@@ Line 258: / Line 261: @@
 Whether or not your job is done depends on whether or not you are using UEFI. If so, then you skipped the ''LILO'' boot loader install, so if you were to reboot now, you would have no way of getting into your OS without a rescue disc. If you did accidentally reboot before reading this paragraph, then reboot using your install media and follow
-the instructions in the appendix for recovering a lost password, and then return here.
+the instructions for [[recovery|recovering a lost password]], and then return here.
 Exit out of the installer, and use this command to enter your freshly installed system:
@@ Line 280: / Line 283: @@
 You can use one as a starting point, creating an entry that looks like this:
-insert lilo.conf here
+<code>
-foobar
+image=bzImage
+  label=Slackermedia
+  read-only
+  root=/dev/sda1
+</code>
+<WRAP alert>
+The location of your root partition may differ, depending on how you installed the system. Generally, it will be the partition into which you chroot'd.
+For more information on creating EFI and UEFI systems, see [[http://docs.slackware.com/howtos:slackware_admin:installing_on_uefi_hardware]]
+</WRAP>
-When you have finished editing, press control+o to "write Out" the file. In the
+When you have finished editing, press ''control+o'' to "write Out" the file. In the
 buffer that appears near the bottom of the screen, rename the file to
-lilo.conf.
+''lilo.conf''
-Press control+x to exit.
+Press ''control+x'' to exit.
-Now run LILO to instantiate the configuration.
+Now run ''lilo'' to instantiate the configuration.
+<code>
 # lilo
+</code>
+===== The Big Reboot =====
 It is now safe to reboot the computer. The best way to do that is to press
-control+alt+F2 to log back into your install media. Login as root again, and
+''control+alt+F2'' to log back into your install media. Login as root again, and
 then issue this command:
+<code>
   # reboot
+</code>
-This reboots your computer. Make sure that the install media is ejected so that
+This reboots your computer. Make sure that the install media is ejected so that your BIOS or UEFI does not boot back into the installer.
-your BIOS or UEFI does not boot back into the installer.
 Now that you have installed the OS, your next step is to set up your user
@@ Line 306: / Line 325: @@
+<WRAP centeralign>
+<wrap fa>[[pre|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[user|Q]]</wrap>
+</WRAP>
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;bottom:0;right:0;}pre|]]
-[[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;bottom:0;left:0;}user|]]