SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I keep a notebook at my Slackware computer and jot down everything I do so I can refer back to it. This has been especially helpful in keeping track of packages I install and what dependencies were required, notes on kernel compiling, editing config files, etc. I can't tell you how many times I've already flipped back through my little Slackware diary thinking 'now how did I do that again'? Sometimes they're just random little notes like 'remember to run /sbin/lilo after editing lilo.conf'. It's growing into quite the useful resource for me.
My favorite entry in my little "logbook":
Code:
Turn on computer after installing new memory.
It's the blue button on the front.
I know I only used it once if 4 1/2 months. But it does help to turn the box on.
still waiting on that antenna order, once I get it I'll hook it up to my wireless PCI card and then get the drivers and then SLACKWARE YES!
I think you'll really like Slackware. I'm a relative newcomer to Slack; I've been Slacking since 10.0. Upgrading to 12.1 was very smooth:-) I love all of the new software packages:-)
If you encounter difficulties we'll be glad to help you:-)
I think you'll really like Slackware. I'm a relative newcomer to Slack; I've been Slacking since 10.0. Upgrading to 12.1 was very smooth:-) I love all of the new software packages:-)
If you encounter difficulties we'll be glad to help you:-)
I've used Slack 11, 12, and just installed 12.1 last night. So far I like it. Especially the new Lilo screen
I don't know about that. GRUB is more complex and doesn't require that you run anything after editing menu.lst (therefore you can edit it from ANY OS/LiveCD without having to do additional chroot or advanced LILO commands etc.). On the other hand, LILO is very simple, straightforward and little can go wrong if you know what you're doing.
They're both good (I prefer LILO's simplicity and since I only run one distro/OS on my machine I don't really need GRUB [ie I'm not editing lilo.conf that much], but GRUB is great as well).
I don't know about that. GRUB is more complex and doesn't require that you run anything after editing menu.lst (therefore you can edit it from ANY OS/LiveCD without having to do additional chroot or advanced LILO commands etc.). On the other hand, LILO is very simple, straightforward and little can go wrong if you know what you're doing.
They're both good (I prefer LILO's simplicity and since I only run one distro/OS on my machine I don't really need GRUB [ie I'm not editing lilo.conf that much], but GRUB is great as well).
They're both good (I prefer LILO's simplicity and since I only run one distro/OS on my machine I don't really need GRUB [ie I'm not editing lilo.conf that much], but GRUB is great as well).
You can multi-boot with lilo. I ran a dual boot with Slackware/FreeBSD for a time. But, I'm now back to exclusively running Slackware 12.1:-)
Quote:
Here's my old liloconf:
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Linux
read-only
# Linux bootable partition config ends
# FreeBSD
other = /dev/hda3
table = /dev/hda
label = FreeBSD
They're both good (I prefer LILO's simplicity and since I only run one distro/OS on my machine I don't really need GRUB [ie I'm not editing lilo.conf that much], but GRUB is great as well).
I'm have multiple Slackware installations (testing/development, SBo devel, everyday use, etcetera) and OpenBSD here, and I've periodically had other distributions installed for various reasons (usually testing to see if a bug is present in them too), and lilo has always worked just fine.
I think the important bit is "if you know what you're doing..." ;-)
I'm going to embark on an epic journey where I use nothing but Slackware for thirty days and report in on my findings.
One recommendation. When you'll log into your system first time as root, check your mail, and read letters (especially the one with subject "to root").
I found that Slackware 11 is the most stable version ever; still put it on a server working for almost 3 years now. 12 and 12.1 has some minor issues with X windows system. What i am looking for is the lightweight and highly stable Linux that Slackware delivers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.