Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Looking back at my posts I can see how vague I was. Sorry, I was frustrated hehe. I just formatted a 10 gig HD and make a 2 gig non bootable swap partition and an 8 gig bootable linux partition, installed phlak, and Lilo. But now when I try to boot it gets about halfway, but then I get the error
Kernal Panic - Cannot mount root fs on 341 (03:41)
Please append a useable "Root+" Boot option
And then it just hangs there until I reboot.
I can get in and edit lilo.conf thanks to my PHLAK bootdisk (which is also the installed distro.)
How might I go about fixing this problem?
I have tried Root = hda1, hda1, hda2 and hdb, as well as Boot = hda, hda1, hda2, hdb and combonations of the two. How might I fix this?
I have searched everywhere and cannot find the answer to this problem, thanks in advance...
All I can think of is you want /dev/hda1 not /dev/hda1/ - it's not a directory. I believe that is your problem unless it was a typo in your post, not your lilo.conf.
Oh, and boot = is where you want the bootloader to be installed on. You probably want this on /dev/hda (note the lack of a number, meaning the master boot record (MBR) of the hard drive, on the first harddrive on IDE cable 1). If you were to write boot = /dev/hda1 however, you will be installing it onto (correct my term if I'm wrong) the superblock of that partition, which by default your system will not load the bootloader from.
Note that you need to run /sbin/lilo after everytime you change the config file otherwise the bootloader will not be updated with your changes.
Good luck. Everyone else feel free to correct me if I'm wrong!
for each (linux) entry lilo need at least 4 entries to work correctly heres what mine looks like:
image = /boot/kernel-2.4.28 ( the path of the kernel you want to boot, look in boot for vmlinuz or such)
root = /dev/hda2 (where the root partition is (e.g. /))
label = Slackware
read-only (initially mount the root filesystem read-only for check before remounting read-write)
EDIT: the boot option (usually towards the very top of the file) is where you want to install lilo to for example:
boot = /dev/hda (this will install it to the master boot record)
boot = /dev/fd0 (this will install lilo to a floppy)
since this is your first linux install i would recommend installing lilo to a floppy instead of the master boot record (if you decide linux isn't your thing, this will make it easier to uninstall off of your system).
Umm, are you running it from a root console? However it would say "Permission denied" if you weren't. Maybe lilo is installed somewhere else, just try plain old 'lilo' as root.
If it still isn't working give 'locate lilo' a go and see what it finds out. If there's a file called lilo run it with an option of --version or something just incase it's not actually lilo. If it is run it normally as root.
Ok, NOW im getting a "permission denied" message even though im in root. The distro is phlak, and heres my lilo.conf file...
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# Support LBA for large hard disks.
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
# Specifies the device that should be mounted as root. (`/')
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
# Specifies the location of the map file
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi noapic acpi=off apm=power-off"
# Boot up Linux by default.
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.