28-mar-2016: Welcome to our new server! Faster and less prone to crashing.
Add this page to your book
Remove this page from your book
All of the information contained here is taken from http://www.slackbook.org/beta/#ch_install.
Thanks, some of topics referred to as chapters can be linked to appropriate wiki articles. — Harishankar 2012/08/20 03:47
Perhaps, the parts showing Slackware installation output should be wrapped in the code tags (or something similar). It doesn't read well. Especially the Booting the installer section. For a new user it might not be clear whether it's the author's comment or the installer output. — sycamorex 21/08/2012 21:59
Please pay attention to create all pages copied from the Slackware Book in the slackbook: namespace… not in the “slackware:” namespace
— — Eric Hameleers 2012/08/21 14:18
Would it not be better to create a fdisk example with sectors? — Whiz 25/08/2012 00:02
Wouldn't it be a good idea to use real screenshots instead of B&W images? Maybe with VirtualBox? — Harishankar 2012/08/25 22:57
Image sizes better now, thanks to mfillpot — Brian Lawrence 2012/08/26 04:36
Created screenshots in media manager Slackware:images would like comments. — Whiz 26/08/2012 15:09
Good work! I see only one colour screenshot currently but it's bright and crisp. — Harishankar 2012/08/26 08:13
Will you be replacing all of the screenshot with full color images on the page as they are created or just dumping them into the media manager until all images are ready? — mfillpot 2012/08/26 12:04
I first create all the images then dump them in the into the media manager and as I understand it can they be referenced from there.— Whiz 26/08/2012 18:18
Images look great. — Harishankar 2012/08/26 19:35
I re-encoded the images so they are smaller, further they are the same.— Whiz 30/08/2012 18:55
Namespace and Translation
Per Eric's comment above, should translations of this page be included in the slackbook: namespace or in the slackware: namespace this page was put under? — Gerardo Zamudio 2012/08/26 14:17
Pages that are taken from the Slack Book should go in the slackbook namespace, not in the slackware namespace. Translations of the Slack Book should go into the associated language namespace - for instance “slackbook:install” should be translated in Spanish as “es:slackbook:install” or else our Wiki's language system will not be able to work out if a page is available in more than one language.
This page, slackware:install , seems to have large parts copied verbatim from the Slack Book. Or was the Slack Book page on installation using kikinovak's text? I think we need kikinovak to tell us. If this Wiki page actually was derived from the Slack Book then it needs to be moved to the slackbook: namespace.
— Eric Hameleers 2012/08/26 14:22
Restored the document to the slackware namspace to allow community input. — Matthew Fillpot 2012/09/05 16:38
It is still confusing that typing the word “install” as a search argument leads to two different docs in different namespaces.
It would help the user to know the differences, maybe a short introductory paragraph stating the specific purpose of this one?
Also, we miss a presentation of the specifics of GPT and UEFI in the context of the installer. For instance it is not obvious for some users to understand why the first screen they see can differ (Grub vs Syslinux) depending on their firmware's abilities or settings. — Didier Spaier 2015/06/25 12:23
Partitioning with fdisk is a little different from the past, since fdisk now supports different partitioning schemes. If you run 'fdisk /dev/sda' and press 'm' for help, then you can see this at the bottom:
Create a new label
g create a new empty GPT partition table G create a new empty SGI (IRIX) partition table o create a new empty DOS partition table s create a new empty Sun partition table
Slackware uses LILO which writes to the MBR, so you need to configure the disk as DOS with MBR and then create at least two partitions for swap (type 82) and linux system (type 83) and set the bootable flag on it, just like in the good old, bad old days.
So if you have a 20 GB disk for example, run 'fdisk /dev/sda', type 'o' to create a DOS partition, type 'n' to make a new partition for +18 GB and again, for 2 GB, type 't' to change the 2 GB partition to 82 (Linux Swap), type 'a' to make the 2nd partition bootable and type 'w' to write it to disk.
Deviate from the above, and LILO won't install. – Herman 2016/06/19