[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/05 05:18 (UTC)] – [Dual Booting with Partitions] copied original text and correct formatting mfillpot | slackbook:booting [2012/09/12 20:42 (UTC)] (current) – [Sources] Bullet Points sycamorex | ||
---|---|---|---|
Line 33: | Line 33: | ||
- | < | + | < |
darkstar:~# ls -1 / | darkstar:~# ls -1 / | ||
/ | / | ||
Line 109: | Line 109: | ||
- | < | + | < |
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 132: | Line 132: | ||
- | < | + | < |
darkstar:~# mount | darkstar:~# mount | ||
/dev/sda1 on / type ext4 (rw, | /dev/sda1 on / type ext4 (rw, | ||
Line 149: | Line 149: | ||
- | < | + | < |
darkstar:~# mkinitrd -f ext4 -r /dev/sda1 | darkstar:~# mkinitrd -f ext4 -r /dev/sda1 | ||
</ | </ | ||
Line 170: | Line 170: | ||
- | < | + | < |
darkstar:~# >/ | darkstar:~# >/ | ||
# See "man mkinitrd.conf" | # See "man mkinitrd.conf" | ||
Line 209: | Line 209: | ||
- | < | + | < |
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 230: | Line 230: | ||
installer, but you can run it at any time from a terminal. | installer, but you can run it at any time from a terminal. | ||
- | {{ :slackware:setup_lilo_cl.png?550 |}} | + | {{ :slackbook:setup-lilo.png?550 |}} |
**// | **// | ||
Line 268: | Line 268: | ||
- | <code> | + | <file> |
# LILO configuration file | # LILO configuration file | ||
Line 284: | Line 284: | ||
vga = 773 | vga = 773 | ||
.... many more lines ommitted .... | .... many more lines ommitted .... | ||
- | </code> | + | </file> |
Line 327: | Line 327: | ||
- | <code> | + | <file> |
# LILO configuration file | # LILO configuration file | ||
... global section ommitted .... | ... global section ommitted .... | ||
Line 342: | Line 342: | ||
table = /dev/sda | table = /dev/sda | ||
# Windows bootable partition config ends | # Windows bootable partition config ends | ||
- | </code> | + | </file> |
Line 364: | Line 364: | ||
- | < | + | < |
darkstar:~# lilo | darkstar:~# lilo | ||
Warning: LBA32 addressing assumed | Warning: LBA32 addressing assumed | ||
Line 507: | Line 507: | ||
==== 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: | ||