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.
A proper /etc/fstab file is needed in order for Linux to boot, so it has to be edited during the install.
If you can install and use midnight commander during the install, you should have no problems. I don't know what tools are available in the Slackware install, however. If they only have vi for an editor, it can be murder for a stranger to the command line. See if you have either nano or pico as text editors during install, they are simple and easy.
The /etc/fstab file should reflect your actual partitioning scheme that you set up and filesystems that you formatted them as during your install. You should have a sample file somewhere to edit, otherwise I posted my scheme previously you can peruse.
Post the output of
and describe the filesystems you formatted them as for further help. Any skeleton /etc/fstab file you need to edit would help as well.
My Gentoo /etc/fstab file for another example:
# Duron 950 uilleann /etc/fstab file: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14 2003/10/13 20:03:38 azarah Exp $
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda3 /boot ext3 noauto,noatime 1 1
/dev/hda6 / reiserfs noatime 0 0
/dev/hda5 none swap sw 0 0
/dev/hda9 /home reiserfs noatime 0 0
/dev/hdb4 /pub ext3 noatime 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs defaults 0 0
Last edited by fancypiper; 03-07-2004 at 02:08 AM.
alright, well, in slackware, fstab is built automatically for you; your problem isn't with fstab
i am guessing you just didn't install lilo?
all you need to do is go into a konsole, and do
su (enter root password)
now go through the custom setup
start a new file
add linux (choose /dev/hda5)
install into the mbr of /dev/hda (hda will be your boot device)
*edit: here is what a slackware fstb should be (the same as what you have, except i think you turned off the proc fileystem; no biggie, but programs like gkrellm need proc as well as other system applications)
also, in order to get the "/boot" partition working, you will need to temporarily mount it without that entry line in fstab
so delete that line, reboot, and in konsole
mount /dev/hda1 /mnt/anything
dir (now keep all those files in mind, you will need to move them to /mnt/anything)
mv file_or_dir /mnt/anything
now put that entry back into fstab for /boot, reboot, and it should be well
Last edited by TheOneAndOnlySM; 03-07-2004 at 11:49 AM.
/mnt/anything is just a temporary mount point; currently, the folder /boot is located on your root partition; we just want to move all the contents of /boot on the root partition (/dev/hda5) to /dev/hda1
then in fstab, when your system boots up, it will notice that anything that refers to /boot will actually be pointing to /dev/hda1
so in short, no, you keep the name in fstab as /boot
also, you can make /mnt/anything any name you want; i actually have a folder called "anything" in /mnt that i use to do work like this (temporary things like mounting a dvd and such)
I use two mount points, /mnt/source and /mnt/destination for moving stuff around so I don't get mixed up as to which direction I am moving things. Mount what is to be moved/copied from at /mnt/source and where it is to be moved/copied to as /mnt/destination.
The kiss (keep it simple, stupid) principle at work.
Also, you might try commanding mc at the root command line and try out midnight commander. It's a really nice suite of apps in addition to a great file manager.
Last edited by fancypiper; 03-07-2004 at 12:36 PM.
I typed in liloconfig and it said "no command found" so I decided to do the /mnt/anything thing first and come back to lilo...
First I created the /mnt/anything
Then I did cd /boot
Then I did mv * /mnt/anything
It wouldnt let me copy 3 files (System.map@, vmlinuz@, and I forgot the other one)
Then I looked around and found Liloconfig in /sbin folder so I did
I didnt read SM's directions very carefully and chose the default options for setting up lilo. After selecting all of the default options, it gave me a message "setting up..." or something, I dont really remeber. Before it finished, the command prompt popped up and liloconfig quit.
I figured, "maybe im okay".
I rebooted w/o the CD with no success.
I put the cd back in, and booted with bare.i root=/dev/hda5 noinitrd ro
I looked in the /mnt/anything folder and it was empty, I looked in the /boot folder and it only had those 3 files in it with little locks by them. When I click them it says "Such and Such file doesnt seem to exist".
I opened up Konsole and typed in liloconfig. All it did was print out the command prompt.
are you sure you did "su" before you performed all those operations? if you did and you still couldn't get liloconfig working, you may need to do "su -"
just note; first try without setting up the /boot partition (as in, in fstab, don't put in a line about /boot) and make sure /boot still has all those files in it (/boot should still be a part of your root partition)
try setting up lilo First; remember to select /dev/hda5 (and follow the directions from my previous post); /dev/hda is the boot drive
restart and see if you can get lilo to boot; then we can work on creating a separate partition for /boot (though you may find it unnecessary once lilo is working and you don't intend to install any other distros)
*edit: Huge carefulnessness needed with wildcards! (*); do not use that because that will tell the mv command to move the entire root filesystem to /dev/hda1; just move the files one by one
Last edited by TheOneAndOnlySM; 03-07-2004 at 07:11 PM.