[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 revision | ||
slackbook:booting [2012/09/03 21:29 (UTC)] – Install page has moved. alienbob | slackbook:booting [2012/09/12 20:42 (UTC)] (current) – [Sources] Bullet Points sycamorex | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== Booting ====== | ====== Booting ====== | ||
- | Ok, now that you've gotten Slackware installed on your system, you should learn exactly what controls the boot sequence of your machine, and how to fix it should you manage to break it somehow. If you use Linux long enough, sooner or later you will make a mistake that breaks your bootloader. Fortunately, | + | Ok, now that you've gotten Slackware installed on your system, you |
+ | should learn exactly what controls the boot sequence of your machine, | ||
+ | and how to fix it should you manage to break it somehow. | ||
+ | long enough, sooner or later you will make a mistake that breaks your | ||
+ | bootloader. | ||
+ | many other operating systems that hide the underlying details of how they | ||
+ | work, Linux (and in particular, Slackware) gives you full control over | ||
+ | the boot process. | ||
+ | re-running the bootloader installer, you can quickly and easily change | ||
+ | (or break) your system. | ||
+ | multiple operating systems, such as other Linux distributions or Microsoft | ||
+ | Windows. | ||
===== mkinitrd ===== | ===== mkinitrd ===== | ||
- | Before we go any further, a quick discussion on the Linux kernel is warranted. Slackware Linux includes at least two, but sometimes more, different kernels. While they are all compiled from the same source code, and hence are the " | + | Before we go any further, a quick discussion on the Linux kernel is |
+ | warranted. | ||
+ | different kernels. | ||
+ | code, and hence are the //" | ||
+ | your architecture and Slackware version, the installer may have loaded | ||
+ | your system with several kernels. | ||
+ | systems and kernels for multi-processor systems (on 32bit Slackware). | ||
+ | In the old days, there were lots of kernels for installing on many different | ||
+ | kinds of hard drive controllers. | ||
+ | there are //" | ||
- | If you look inside your /boot directory, you'll see the various kernels installed on your system. | ||
- | < | + | If you look inside your ''/ |
+ | see the various kernels installed on your system. | ||
+ | |||
+ | |||
+ | < | ||
darkstar:~# ls -1 / | darkstar:~# ls -1 / | ||
/ | / | ||
Line 16: | Line 39: | ||
</ | </ | ||
- | Here you can see that I have two kernels installed, vmlinuz-huge-2.6.29.4 and vmlinuz-generic-2.6.29.4. Each Slackware release includes different kernel versions and sometimes even slightly different names, so don't be alarmed if what you see doesn' | ||
- | Huge kernels are exactly what you might think; they' | + | Here you can see that I have two kernels installed, |
+ | '' | ||
+ | '' | ||
+ | includes different kernel versions and sometimes even slightly | ||
+ | different names, so don't be alarmed if what you see doesn' | ||
+ | match what I have listed here. | ||
+ | |||
+ | |||
+ | Huge kernels are exactly what you might think; they' | ||
+ | that does NOT mean that they have all of the possible drivers and such | ||
+ | compiled into them. Instead, these kernels are made to boot (and run) on | ||
+ | every conceivable computer on which Slackware is supported (there may very | ||
+ | well be a few out there that won't boot/work with them though). | ||
+ | certainly contain support for hardware your machine does not (and never | ||
+ | will) have, but that shouldn' | ||
+ | several reasons, but probably the most important is their use by Slackware' | ||
+ | installer - these are the kernels that the Slackware installation disks run. | ||
+ | If you chose to let the installer configure your bootloader for you, it | ||
+ | chooses to use these kernels due to the incredible variety of hardware they | ||
+ | support. | ||
+ | without the use of external modules. | ||
+ | kernels, you'll need to make use of something called an initrd, which is | ||
+ | created using the **//mkinitrd//**(8) utility. | ||
+ | |||
+ | |||
+ | So why should you use a generic kernel? | ||
+ | development team recommends use of a generic kernel for a variety of | ||
+ | reasons. | ||
+ | currently about twice the size of the generic kernels before they are | ||
+ | uncompressed and loaded into memory. | ||
+ | machine, or one with some small ammount of RAM, you will appreciate the | ||
+ | savings the generic kernels offer you. Other reasons are somewhat more | ||
+ | difficult to quantify. | ||
+ | kernels do appear from time to time, and generally speaking, the huge | ||
+ | kernels may not perform as well as the generic ones. Also, by using the | ||
+ | generic kernels, special arguments can be passed to hardware drivers | ||
+ | seperately, rather than requiring these options be passed on the kernel | ||
+ | command line. Some of the tools included with Slackware work better if | ||
+ | your kernel uses some drivers as modules rather than statically building | ||
+ | them into the kernel. | ||
+ | be alarmed: just think //" | ||
+ | |||
+ | |||
+ | Unfortunately, | ||
+ | using the huge kernels. | ||
+ | system, you must also include a few basic modules in an initird. | ||
+ | Modules are pieces of compiled kernel code that can be inserted or removed | ||
+ | from a running kernel (ideally using **// | ||
+ | This makes the system somewhat more flexible at the cost of a tiny bit of | ||
+ | added complexity. | ||
+ | drivers, at least for this section. | ||
+ | module for whatever filesystem you chose to use for your root partition | ||
+ | during the installer, and if your root partition is located on a SCSI disk | ||
+ | or RAID controller, you'll need to add those modules as well. Finally, if | ||
+ | you're using software RAID, disk encryption, or LVM, you'll also need to | ||
+ | create an initrd regardless of whether you're using the generic kernel or not. | ||
- | So why should you use a generic kernel? Currently the Slackware development team recommends use of a generic kernel for a variety of reasons. Perhaps the most obvious is size. The huge kernels are currently about twice the size of the generic kernels before they are uncompressed and loaded into memory. If you are running an older machine, or one with some small ammount of RAM, you will appreciate the savings the generic kernels offer you. Other reasons are somewhat more difficult to quantify. Conflicts between drivers included in the huge kernels do appear from time to time, and generally speaking, the huge kernels may not perform as well as the generic ones. Also, by using the generic kernels, special arguments can be passed to hardware drivers seperately, rather than requiring these options be passed on the kernel command line. Some of the tools included with Slackware work better if your kernel uses some drivers as modules rather than statically building them into the kernel. If you're having trouble understanding this, don't be alarmed: just think "huge kernel = good, generic kernel = better" | ||
- | Unfortunately, using the generic kernels | + | An initrd is a compressed **// |
+ | creating one isn' | ||
+ | includes | ||
+ | **// | ||
+ | **// | ||
+ | book, but we' | ||
+ | explanation, check the manpage | ||
+ | **// | ||
+ | argument. | ||
- | An initrd is a compressed cpio(1) archive, so creating one isn't very straightforward. Fortunately for you, Slackware includes a tool that makes this very easy: mkinitrd. A full discussion of mkinitrd is a bit beyond the scope of this book, but we'll show you all the highlights. For a more complete explanation, | ||
- | < | + | < |
darkstar:~# mkinitrd --help | darkstar:~# mkinitrd --help | ||
mkinitrd creates an initial ramdisk (actually an initramfs cpio+gzip | mkinitrd creates an initial ramdisk (actually an initramfs cpio+gzip | ||
Line 36: | Line 119: | ||
</ | </ | ||
- | When using mkinitrd, you'll need to know a few items of information: | ||
- | < | + | When using **// |
+ | few items of information: | ||
+ | any hard disk controllers you're using, and whether or not you're using | ||
+ | LVM, software RAID, or disk encryption. | ||
+ | of SCSI controller (and have your root partition located on the SCSI | ||
+ | controller), | ||
+ | partition type. Assuming you've booted into your Slackware installation | ||
+ | using the huge kernel, you can easily find this information with the | ||
+ | **// | ||
+ | ''/ | ||
+ | |||
+ | |||
+ | < | ||
darkstar:~# mount | darkstar:~# mount | ||
/dev/sda1 on / type ext4 (rw, | /dev/sda1 on / type ext4 (rw, | ||
Line 48: | Line 142: | ||
</ | </ | ||
- | In the example provided, you can see that the root partition is located on /dev/sda1 and is an ext4 type partition. If we want to create an initrd for this system, we simply need to tell this information to mkinitrd. | ||
- | < | + | In the example provided, you can see that the root partition is located |
+ | on ''/ | ||
+ | want to create an initrd for this system, we simply need to tell this | ||
+ | information to **// | ||
+ | |||
+ | |||
+ | < | ||
darkstar:~# mkinitrd -f ext4 -r /dev/sda1 | darkstar:~# mkinitrd -f ext4 -r /dev/sda1 | ||
</ | </ | ||
- | Note that in most cases, mkinitrd is smart enough to determine this information on its own, but it never hurts to specify it manually. Now that we've created our initrd, we simply need to tell LILO where to find it. We'll focus on that in the next section. | ||
- | Looking up all those different options for mkinitrd or worse, memorizing them, can be a real pain though, especially if you try out different kernels consistently. This became tedious for the Slackware development team, so they came up with a simple configuration file, mkinitrd.conf(5). You can find a sample file that can be easily customized for your system at / | + | Note that in most cases, **// |
+ | enough to determine this information on its own, but it never hurts to | ||
+ | specify it manually. Now that we've created our initrd, we simply need | ||
+ | to tell LILO where to find it. We'll focus on that in the next section. | ||
+ | |||
+ | |||
+ | Looking up all those different options for | ||
+ | **//mkinitrd//** or worse, memorizing them, can be a | ||
+ | real pain though, especially if you try out different kernels | ||
+ | consistently. This became tedious for the Slackware development team, | ||
+ | so they came up with a simple configuration file, | ||
+ | '' | ||
+ | can be easily customized for your system at | ||
+ | '' | ||
- | < | + | < |
darkstar:~# >/ | darkstar:~# >/ | ||
# See "man mkinitrd.conf" | # See "man mkinitrd.conf" | ||
Line 77: | Line 189: | ||
</ | </ | ||
- | For a complete description of each of these lines and what they do, you'll need to consult the man page for mkinitrd.conf. Copy the sample file to to / | ||
- | If you're unsure what options | + | For a complete description of each of these lines and what they do, |
+ | you'll need to consult | ||
+ | Copy the sample file to to '' | ||
+ | edit it as desired. Once it is setup properly, | ||
+ | **// | ||
+ | A proper initrd file will be constructed and installed | ||
+ | you having | ||
- | < | + | |
+ | If you're unsure what options to specify in the configuration file or | ||
+ | on the command-line, | ||
+ | nifty little utility that can tell what options are required for your | ||
+ | currently running kernel | ||
+ | **/// | ||
+ | When you run this script, it will generate a command line for | ||
+ | **// | ||
+ | for your computer, but you may wish to check everything anyway. | ||
+ | |||
+ | |||
+ | < | ||
darkstar:~# / | darkstar:~# / | ||
mkinitrd -c -k 2.6.33.4 -f ext3 -r /dev/sda3 -m \ | mkinitrd -c -k 2.6.33.4 -f ext3 -r /dev/sda3 -m \ | ||
Line 88: | Line 216: | ||
===== LILO ====== | ===== LILO ====== | ||
- | LILO is the Linux Loader and is currently the default boot loader installed with Slackware Linux. If you've used other Linux distributions before, you may be more familiar with GRUB. If you prefer to use GRUB instead, you can easily find it in the extra/ directory on one of your Slackware CDs. However, since LILO is the default Slackware bootloader, we'll focus exclusively on it. | + | LILO is the Linux Loader and is currently the default boot loader |
+ | installed with Slackware Linux. | ||
+ | distributions before, you may be more familiar with GRUB. If you prefer | ||
+ | to use GRUB instead, you can easily find it in the | ||
+ | '' | ||
+ | However, since LILO is the default Slackware bootloader, we'll focus | ||
+ | exclusively on it. | ||
- | Configuring LILO can be a little daunting for new users, so Slackware comes with a special setup tool called liloconfig. Normally, liloconfig is first run by the installer, but you can run it at any time from a terminal. | ||
- | {{ : | + | Configuring LILO can be a little daunting for new users, so Slackware |
+ | comes with a special setup tool called **// | ||
+ | Normally, **// | ||
+ | installer, but you can run it at any time from a terminal. | ||
- | liloconfig has two modes of operation: simple and expert. The " | + | {{ :slackbook: |
- | In order to use "expert" | + | **// |
+ | simple and expert. The //"simple"// | ||
+ | lilo for you. If Slackware is the only operating system | ||
+ | your computer, the //" | ||
+ | quickly | ||
+ | installations | ||
+ | so that you can choose which operating system to boot when you | ||
+ | turn your computer on. | ||
- | liloconfig is a great way to quickly setup your boot loader, but if you really need to know what's going on, you'll need to look at LILO's configuration file: lilo.conf(5) under the /etc directory. / | ||
- | <code> | + | In order to use //" |
+ | partition. | ||
+ | their root partitions, but this may not work as well as you expect. | ||
+ | **// | ||
+ | operating system with Slackware' | ||
+ | you want. Fortunately, | ||
+ | trivial. | ||
+ | install LILO to the Master Boot Record (MBR). | ||
+ | recommended to install the boot loader onto the root partition and set | ||
+ | that partition as bootable. | ||
+ | to install on the MBR. In fact, you will encounter fewer problems if | ||
+ | you do so. | ||
+ | |||
+ | |||
+ | **// | ||
+ | your boot loader, but if you really need to know what's going on, you' | ||
+ | need to look at LILO's configuration file: | ||
+ | '' | ||
+ | directory. | ||
+ | several sections. | ||
+ | specify things like where to install LILO (generally the MBR), any | ||
+ | special images or screens to show on boot, and the timeout after which | ||
+ | LILO will boot the default operating system. | ||
+ | section of my lilo.conf file looks like in part. | ||
+ | |||
+ | |||
+ | <file> | ||
# LILO configuration file | # LILO configuration file | ||
Line 116: | Line 284: | ||
vga = 773 | vga = 773 | ||
.... many more lines ommitted .... | .... many more lines ommitted .... | ||
- | </code> | + | </file> |
+ | |||
+ | |||
+ | For a complete listing of all the possible LILO options, you should | ||
+ | consult the man page for '' | ||
+ | briefly discuss the most common options in this document. | ||
+ | |||
+ | |||
+ | The first thing that should draw your attention is the //" | ||
+ | determines where the bootloader is installed. | ||
+ | the Master Boot Record (MBR) of your hard drive, you simply list the hard | ||
+ | drive' | ||
+ | that shows up as a SCSI device ''/ | ||
+ | to install to the boot block of a partition, you'll have to list the | ||
+ | partition' | ||
+ | partition on the only SATA hard drive in your computer, you would probably | ||
+ | use ''/ | ||
- | For a complete listing | + | The //" |
+ | operating system to boot. Operating systems are each listed in their | ||
+ | own section deeper in the file. We'll get to them in a minute. | ||
+ | timeout option tells LILO how long to wait (in tenths | ||
+ | before booting | ||
+ | systems seem to take a very long time to display the boot screen, so | ||
+ | you may need to use a larger timeout value than I have set. This is in | ||
+ | part why the simple LILO installation method utilizes a very long | ||
+ | timeout (somewhere around 2 whole minutes). | ||
+ | was set up by **// | ||
+ | probably should) see something similar when looking at your own | ||
+ | ''/ | ||
+ | this line is needed, so you're just going to have to trust me that things | ||
+ | work better if it is present. :^) | ||
- | The first thing that should draw your attention is the " | ||
- | The " | + | Now that we've looked into the global section, let' |
+ | operating systems section. Each linux operating system section begins | ||
+ | with an //" | ||
+ | with an //" | ||
+ | '' | ||
+ | Microsoft Windows. | ||
- | Now that we've looked into the global section, let's take a look at the operating systems section. Each linux operating system section begins with an " | ||
- | <code> | + | <file> |
# LILO configuration file | # LILO configuration file | ||
... global section ommitted .... | ... global section ommitted .... | ||
Line 141: | Line 342: | ||
table = /dev/sda | table = /dev/sda | ||
# Windows bootable partition config ends | # Windows bootable partition config ends | ||
- | </code> | + | </file> |
+ | |||
+ | |||
+ | For Linux operating systems like Slackware, the image line specifies | ||
+ | which kernel to boot. In this case, we're booting | ||
+ | ''/ | ||
+ | sections are pretty self-explanatory. | ||
+ | root filesystem, what initrd (if any) to use, and to initially mount | ||
+ | the root filesystem read-only. | ||
+ | anyone running a generic kernel or using LVM or software RAID. It | ||
+ | tells LILO (and the kernel) where to find the initrd you created using | ||
+ | **// | ||
- | For Linux operating systems like Slackware, the image line specifies which kernel | + | Once you've gotten ''/ |
+ | machine, simply run **// | ||
+ | Unlike GRUB and other bootloaders, LILO requires you re-run | ||
+ | **//lilo//** anytime you make changes | ||
+ | configuration file, or else the new (changed) bootloader image will | ||
+ | not be installed, and those changes will not be reflected. | ||
- | Once you've gotten / | ||
- | < | + | < |
darkstar:~# lilo | darkstar:~# lilo | ||
Warning: LBA32 addressing assumed | Warning: LBA32 addressing assumed | ||
Line 155: | Line 372: | ||
</ | </ | ||
- | Don't be too scared by many of the warnings you may see when running lilo. Unless you see a fatal error, things should be just fine. In particular, the LBA32 addressing warning is commonplace. | + | |
+ | Don't be too scared by many of the warnings you may see when running | ||
+ | **//lilo//**. Unless you see a fatal error, things | ||
+ | should be just fine. In particular, the LBA32 addressing warning is | ||
+ | commonplace. | ||
===== Dual Booting ====== | ===== Dual Booting ====== | ||
- | A bootloader (like LILO) is a very flexible thing, since it exists only to determine which hard drive, partition, or even a specific kernel on a partition to boot. This inherently suggests a choice when booting, so the idea of having more than one operating system on a computer comes very naturally to a LILO or GRUB user. | + | A bootloader (like LILO) is a very flexible thing, since it exists |
+ | only to determine which hard drive, partition, or even a specific | ||
+ | kernel on a partition to boot. This inherently suggests a choice | ||
+ | when booting, so the idea of having more than one operating system | ||
+ | on a computer comes very naturally to a LILO or GRUB user. | ||
- | People "dual boot" for a number of reasons; some people want to have a stable Slackware install on one partition or drive and a development sandbox on another, other people might want to have Slackware on one and another Linux or BSD distribution on another, and still other people may have Slackware on one partition and a proprietary operating system (for work or for that one application that Linux simply cannot offer) on the other. | ||
- | Dual booting should not be taken lightly, however, since it usually means that you'll now have two different operating systems attempting to manage the bootloader. If you dual boot, the likelihood | + | People //"dual boot"// for a number |
+ | to have a stable Slackware install on one partition | ||
+ | development sandbox on another, other people might want to have | ||
+ | Slackware on one and another Linux or BSD distribution on another, | ||
+ | and still other people may have Slackware on one partition and a | ||
+ | proprietary operating system (for work or for that one application | ||
+ | that Linux simply cannot offer) on the other. | ||
- | There are two ways to dual (or multi) boot; you can put each operating system on its own hard drive (common on a desktop, with their luxury of having more than one drive bay) or each operating system on its own partition (common on a laptop where only one physical drive is present). | ||
+ | Dual booting should not be taken lightly, however, since it usually | ||
+ | means that you'll now have two different operating systems | ||
+ | attempting to manage the bootloader. If you dual boot, the | ||
+ | likelihood of one OS over-writing or updating the bootloader entries | ||
+ | without your direct intervention is great; if this happens, you'll | ||
+ | have to modify GRUB or LILO manually so you can get into each OS. | ||
+ | |||
+ | There are two ways to dual (or multi) boot; you can put each | ||
+ | operating system on its own hard drive (common on a desktop, with | ||
+ | their luxury of having more than one drive bay) or each operating | ||
+ | system on its own partition (common on a laptop where only one | ||
+ | physical drive is present). | ||
==== Dual Booting with Partitions ==== | ==== Dual Booting with Partitions ==== | ||
- | In order to set up a dual-boot system with each operating system on its own partition, you must first create partitions. This is easiest if done prior to installing the first operating system, in which case it's a simple case of pre-planning and carving up your hard drive as you feel necessary. See the section called “[[slackbook: | + | In order to set up a dual-boot system with each operating system on |
+ | its own partition, you must first create partitions. This is easiest | ||
+ | if done prior to installing the first operating system, in which | ||
+ | case it's a simple case of pre-planning and carving up your hard | ||
+ | drive as you feel necessary. See [[slackbook: | ||
+ | information on using the **//fdisk//** or | ||
+ | **//cfdisk//** partitioning applications. | ||
<note important> | <note important> | ||
- | If you're dual booting two Linux distributions, | + | If you're dual booting two Linux distributions, |
- | </ | + | to attempt to share a /home directory between the |
+ | systems. While it is technically possible, doing so will increase | ||
+ | the chance of your personal configurations from becoming mauled by | ||
+ | competing desktop environments or versions. | ||
It is, however, safe to use a common swap partition. | It is, however, safe to use a common swap partition. | ||
+ | </ | ||
You should partition your drive into at least three parts: | You should partition your drive into at least three parts: | ||
Line 181: | Line 433: | ||
* One partition for swap | * One partition for swap | ||
- | First, install Slackware Linux onto the first partition of the hard drive as described in [[slackbook: | + | First, install Slackware Linux onto the first partition of the hard |
+ | drive as described in [[slackbook: | ||
- | After Slackware has been installed, booted, and you've confirmed that everything works as expected, then reboot to the installer for the second OS. This OS will invariably offer to utilize the entire drive; you obviously do not want to do that, so constrain it to only the second partition. Furthermore, | ||
- | You have a few possible courses of action with regards to the boot loader: | + | After Slackware has been installed, booted, and you've confirmed |
+ | that everything works as expected, then reboot to the installer for | ||
+ | the second OS. This OS will invariably offer to utilize the entire | ||
+ | drive; you obviously do **not** want to do that, so | ||
+ | constrain it to only the second partition. Furthermore, | ||
+ | attempt to install a boot loader to the beginning of the hard drive, | ||
+ | overwriting LILO. | ||
+ | |||
+ | |||
+ | You have a few possible courses of action with regards to the boot | ||
+ | loader: | ||
**Possible Boot Loader Scenarios** | **Possible Boot Loader Scenarios** | ||
- | **If the secondary OS is Linux, disallow it from installing a boot manager.** | + | **If the secondary OS is Linux, disallow it from installing a boot |
- | If you're dual booting to another Linux distribution, | + | manager.** |
+ | If you're dual booting to another Linux distribution, | ||
+ | installer of that distribution usually asks if you want a boot | ||
+ | loader installed. You're certainly free to not install a boot | ||
+ | manager for it at all, and manually manage both Slackware and | ||
+ | the other distribution with LILO. | ||
- | Depending on the distribution, | + | |
+ | Depending on the distribution, | ||
+ | frequently than you would if you were only running Slackware; | ||
+ | some distributions are notorious for frequent kernel updates, | ||
+ | meaning that you'll need to edit LILO to reflect the new | ||
+ | configuration after such an update. But if you didn't want to | ||
+ | edit configuration files every now and again, you probably | ||
+ | wouldn' | ||
**If the secondary OS is Linux, let it overwrite LILO with GRUB.** | **If the secondary OS is Linux, let it overwrite LILO with GRUB.** | ||
- | If you're dual booting to another Linux distribution, | + | If you're dual booting to another Linux distribution, |
+ | perfectly capable of just using GRUB rather than LILO, or | ||
+ | install Slackware last and use LILO for both. Both LILO and GRUB | ||
+ | have very good auto-detection features, so whichever one gets | ||
+ | installed last should pick up the other distribution' | ||
+ | and make an entry for it. | ||
- | Since other distributions often attempt to auto-update their GRUB menus, there is always the chance that during an update something will become maligned and you suddenly find you can't boot into Slackware. If this happens, don't panic; just boot into the other Linux partition and manually edit GRUB so that it points to the correct partition, kernel, and initrd (if applicable) for Slackware in its menu. | ||
- | **Allow the secondary OS to overwrite LILO and go back later to manually | + | Since other distributions often attempt |
+ | GRUB menus, there is always the chance that during an update | ||
+ | something will become maligned and you suddenly find you can' | ||
+ | boot into Slackware. If this happens, don't panic; just boot | ||
+ | into the other Linux partition | ||
+ | points to the correct partition, kernel, | ||
+ | applicable) for Slackware in its menu. | ||
- | This is not a bad choice, especially when Windows is the secondary OS, but potential pitfalls are that when Windows updates itself, it may attempt | + | **Allow |
+ | manually | ||
- | To re-establish LILO after another | + | This is not a bad choice, especially when Windows is the |
+ | secondary | ||
+ | updates itself, | ||
+ | again, and you'll have to re-install | ||
- | Even when using the " | + | |
+ | To re-establish LILO after another OS has erased it, you can | ||
+ | boot from your Slackware install media and enter the setup | ||
+ | stage. Do < | ||
+ | re-install Slackware; skip immediately to [[slackbook: | ||
+ | |||
+ | |||
+ | Even when using the //" | ||
+ | should detect both operating systems and automatically configure | ||
+ | a sensible menu for you. If it fails, then add the entries | ||
+ | yourself. | ||
==== Dual Booting from Hard Drives ==== | ==== Dual Booting from Hard Drives ==== | ||
- | Dual booting between different physical hard drives is often easier than with partitions since the computer' | + | Dual booting between different physical hard drives is often |
+ | easier than with partitions since the computer' | ||
+ | almost invariably has a boot device chooser that allows you to | ||
+ | interrupt the boot process immediately after POST and choose what | ||
+ | drive should get priority. | ||
+ | |||
+ | |||
+ | The snag key to enter the boot picker is different for each brand | ||
+ | of motherboard; | ||
+ | splash screen to find out what your computer requires. Typical | ||
+ | keys are < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | |||
+ | If you manage the boot priority via BIOS or EFI, then each boot | ||
+ | loader on each hard drive is only aware of its own drive and will | ||
+ | never interfere with one another. This is rather contrary to what | ||
+ | a boot loader is designed to do but can be a useful workaround | ||
+ | when dealing with proprietary operating systems which insist upon | ||
+ | being the only OS on the system, to the detriment of the user' | ||
+ | preference. | ||
- | The snag key to enter the boot picker is different for each brand of motherboard; | + | If you don't have the luxury |
+ | drives and don't feel comfortable juggling another partition and | ||
+ | OS on your computer, | ||
+ | virtual machine to give you access to another OS. Both of these | ||
+ | options | ||
+ | and might be the right choice for you, depending on your needs. | ||
- | If you manage the boot priority via BIOS or EFI, then each boot loader on each hard drive is only aware of its own drive and will never interfere with one another. This is rather contrary to what a boot loader is designed to do but can be a useful workaround when dealing with proprietary operating systems which insist upon being the only OS on the system, to the detriment of the user's preference. | ||
- | If you don't have the luxury of having multiple internal hard drives and don't feel comfortable juggling another partition and OS on your computer, you might also consider using a bootable USB thumbdrive or even a virtual machine to give you access to another OS. Both of these options is outside the scope of this book, but they' | + | ====== Chapter Navigation ====== |
+ | **Previous Chapter: [[slackbook: | ||
+ | **Next Chapter: [[slackbook: | ||
====== Sources ====== | ====== Sources ====== | ||
<!-- If you copy information from another source, then specify that source --> | <!-- If you copy information from another source, then specify that source --> | ||
- | * Original source: [[http:// | + | |
<!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
- | < | + | |
<!-- * Contrbutions by [[wiki: | <!-- * Contrbutions by [[wiki: | ||