SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I see in -current syslinux is at version 3.84. I would suggest upgrading it to latest, 4.03. Reasons being, as far I know, syslinux is the only bootloader that can boot directly into btrfs, without requiring a seperate /boot. Slack's -current version only allows for ext2/3, where as syslinux now supports ext2/3/4 and btrfs.
I am doing a manual upgrade of syslinux, so I don't need it in -current, but still a suggestion for people wanting a full btrfs only install. TIP: From what I've read, it does require /boot to be in the root of btrfs as a mkdir and not as a subvolume.
Really glad I stumbled onto this thread. I hadn't really thought about Syslinux being part of Slack. Having recently played around with it (well Extlinux), I think it might be my new favourite boot manager. It is simple to understand, easy to configure and has some features that lilo is missing like booting from a GPT partitioned disk.
Anyway, even though I was hardly aware of it just a couple of days ago I'm glad that the update made it into 14, since I'll probably switch to it for my next install.