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 had the same problem when I first installed 8.1 and tried to install lilo to hda1. I reinstalled and just had lilo install to the MBR instead of hda1....I know that will work for you if all else fails. If thats not an option I dont know what to tell ya.
nah nah skip that paragraph on editting it by hand, I was just brainfarting, the installer is also on your / partition somewheres so you can just run "setup" again and skip all of the media install and arrow down to Configuration (redo all the steps in that though otherwise it'll remove the old settings) and I think the first or second thing it'll ask is whether to install lilo and where, make sure to tell it MBR.
Basically you're calling a "do-over" on that one little part of the install that didn't work right.
The base slack XF86config file should work for most machines, but you're going to want to run a probe to make your own anyway or build it with the xf86config utility you can find under /usr/X11/bin. To run the probe:
Then follow the instructions to test it. Putting it in /etc/X11 (and re-naming it XF86Config because its called XF86Config.new from the probe) is where X will read it when you next start X. That file will take a little monkeying around, adding more font paths, a few modules, and the settings at the end for the Modes and viewport.
will probably produce a better one.
Slack is very barebones, not user friendly, and there are a number of things that are this complicated, its also a lot more unix-like and really slim running, and the coolest thing since squirt cheese.
Originally posted by banelion i didnt quite catch what that other stuff u told me was for... is that to get me into x autmatically?
Nah, that goop is to get X at the right max-ed out resolutions for your gear, the config file for X that you start with is just an Uber-basic template that Patrick came up with that should work with any combination of the past four or so years worth of Graphics cards and the last near decade of monitors. Basically, if that pre-built works for you and you're hardly ever gonna use X, yeah man just leave it.
Offhand, going straight to X-windows is usually called runlevel 5, although because Slack is quirkie, for Slack its runlevel 4. The console you have now is runlevel 3, anothe version of the console, with only a single user mode is runlevel 1, usually used for debugging or for cleanup in the event of an intrusion. No networking, or any of the daemons like sendmail or sshd are on at runlevel 1 so that's handy. Runlevels 4 and 2 are (except in Slack's case), usually resevered as roll-your-own midways to create for whatever you need.
FYI: To use the /dev/hda1 partition, or any partition specified, after running Lilo to set it up. Boot an old MSDOS floppy disk or DOS bootable CD with fdisk on it. And run "fdisk /MBR" command and then reboot. Because lilo was directed to write to the hda1 partition a master boot record may still need to be written and/or updated.
There may be a way to instruct lilo to update the MBR but I don't know how. using DOS fdisk has always worked, so it is just the way I have done it.