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.
Our posts have crossed each other (and I suspect this one will suffer the same fate), but I see I was right in suspecting additional drives.
In any case, I can tell you what has happened, in part, and most of it is what you wanted.
C has remained untouched. D has probably remained untouched, as to the best of my knowledge, Fedora Core 1 cannot resize NTFS drives/partitions, and I assume D was NTFS (since Fedora can't create NTFS partitions either).
The 16GB partition is probably used for root (as very few distros would fit on the 2 GB partition that you intended for /swap, and FC 1 is not one of them).
The 2 GB partition that you intended for /swap has been mounted as a regular partition, probably because it was not reformatted to the /swap filesystem-- did you use automatic partitioning, or tell the installer to use existing Linux partitions?
It's probably the /home folder, since that's the most common separate partition, and if it was used for /boot or something, it would be marked bootable or something (and would be quite small--50MB or less).
No idea where the FAT32 partition came from.
And whatever size /swap actually is, that space was taken from one of the other partitions-- couldn't guess which until you post the actual partition sizes-- but this should not be much of a problem as /swap usually maxes out at 512MB unless you really have more than 512MB of memory, in which case FC1 may act like RH 9 and take 2X your real RAM (no matter how much you have) for /swap. Very annoying habit, since -- let's face it, if you have 1 or 2GB of RAM, you really don't need 2 or 4GB of swap space. But that's RedHat and its ilk for you.
the / of your linux install will be either
/dev/hdb2 or /dev/hdb3
you'll have to mount one
and if it does not have the "etc"
directory, you'll have to unmount
it and mount the other. Don't worry,
it's actually quiet easy. Here's the steps:
1. boot using cd rescue
2. at prompt type "mkdir tmpdir". this
will create amount point for us.
3. type "mount /dev/hdb2 tmpdir". This
will actually mount the partition.
4. type "ll tmpdir" the 'll' is lowwer case 'LL'.
this will give you a directory listing.
If you see around 10 or 12 directories
including "etc" that is the correct one.
If "etc" is not there go to the next one by:
1. type "umount tmpdir" this is NOT a typeo
It is umount not unmount.
2. type "mount /dev/hdb3 tmpdir".
3. type "ll tmpdir" look for the directory "etc"
If you still dont see it let me know.
Assuming you have found the "etc" directory,
type "pico tmpdir/etc/sysconfig/firstboot". this will
open the file "firstboot" in the pico text editor.
now change YES to NO and save it and reboot and
see if that did it.
First thing...cfdisk didn't work but I may have typed it incorrectly. I *think* I forgot to put the space after cfdisk as in cfdisk /dev/hdb.
As for the partitioning, I used Partition Magic to create those new partitions on my old "D" drive as that seemed to be the consensus. If that wasn't the correct thing to do, could that be causing my problems?
Heading off to try this now. I do have one question for you though...you keep referring to /...is "/" another term for root?
there are two directories call "root"
'/' is the root directory but also "/root"
is called root directory. "/root" is the
root user's home directory. "/" is the
primary directory for all other directories.
ALL other directories or somewhere inside it
assuming, of course" that they are mounted.
Ex. "/root", "/etc", and "/home" are directories
The program ls lists first its non-directory file arguments, and then for each directory argument all listable files contained
within that directory. If no non-option arguments are present, a default argument `.' (the current directory) is assumed. The -d option causes directories to be treated as non-directory arguments. A file is listable when either its name does not start with `.', or the -a option is given.
Each of the lists of files (that of non-directory files, and for each directory the list of files inside) is sorted separately
according to the collating sequence in the current locale. When the -l option is given, each list is preceded by a summary line giving the total size of all files in the list, measured in semi-kilobytes (512 B).
The output is to stdout, one entry per line, unless multicolumn output is requested by the -C option. However, for output to a terminal, it is undefined whether the output will be single-column or multi-column. The options -1 and -C can be used to force single-column and multi-column output, respectively.
ll is actually a shell alias, as far as I know-- which we don't have to go into beyond saying that you can set a command that is long to type to an alias that is shorter for you. Meaning that for instance I have an alias that sets the command cd /usr/src/linux to the word "kernel" so that if I type the word kernel, the command will be executed and I don't have to type all that to get to my kernel-source directory.
On my system, which I believe to be standard in this respect, "ll" is an alias for "ls --color -l -h", which is to say, ls with the --color, -l, and -h switches, which are documented in the man page above.
In any case, there is no "ll" command, as far as I can see.
Did you mount /dev/hdb3 before trying to open a file from it?
Also, you seem to have missed a slash... once mounted, you'd want to type pico /tmpdir/etc/sysconfig/firstboot, unless you had cd-ed to that directory, in which case you could just type pico firstboot.
I'm now starting to think that there are problems with the installation.
Here's what I did:
mount /dev/hdb3 tmpdir
ls -l tmpdir
From here, I can see that there is a directory (is this what these are called?) in tmpdir that is /etc
from there I did:
and I got "new file" in Pico. Again, I presume that this means that "firstboot" doesn't exist and the OS is giving me the option to make "firstboot". Am I correct?
Is there a way to look inside /etc to see what's in there? I tried a couple of things, but all I got was "not a directory"
Also, just for fun...I tried "man ls" and got man command not found.
Now, before we go too much further with this, I've ordered SuSE 9.1 Personal Edition but it's apparently on backorder as it's been over a week and I've heard nothing from them nor have I received the order. Should I wait to see if that gets here...should I re-install Fedora Core 1...what should I do. I don't like to giv up on things but I fear that I'm taking up too much of everyone's time with this. I don't mind to keep trying but that will just lead to me posting more questions to you guys here
Hello, this is a help forum, you don't have a time limit on how much help you can get!
If you want to continue to try to get FC 1 installed while you wait for SuSE to show up, who am I to say don't do that? You can only learn more, and that's never bad.
As to the current issue, I can see why you might think the install was borked, but it might not be-- it's just not complete. In FC there's a wizard thingy, but every distro basically installs the base system (with extras, sometimes, but not always), and then reboots at least once and says things like "please configure your timezone, and make sure that the keyboard and printer settings are correct, and configure your bootloader and X-- oh and don't forget to set a root password and make a user." Where these things occur in Mandrake's boot process is slightly different than where they occur in SuSE's or FC's or Slackware's boot processes, but they are pretty much the last thing that will happen before the system is not only "installed", but the last thing that will happen before the system considers itself installed, which is really what's at issue here.
As far as the system is concerned, you're trying to use it before the install has completed, and there is no OS where that doesn't end in some tears of frustration.
In terms of how to see what's in /etc/, just cd to the directory and type ls, or ll (mind like a sieve, I see ) to list the contents of the directory.
But what I'm thinking is that you might really need to chroot this filetree-- you can look at man chroot whenever you like, I'll tell you now that the chroot command makes the root filetree ("/") rooted at whatever directory you like (although it's better for obvious reasons to chroot an actual / filetree and not /home, for example, as there's no /etc/ or /usr/bin or /sbin/ in /home, so nothing much would work if you did that.
But let's make this easy on you.... Can you download and burn a copy of Knoppix? It will run completely from CD, you'll have a full Linux desktop and it would be much easier and more pleasant for you and us to try to solve this issue if we could mount the HDD partitions from an attractive desktop and you could post the results in Mozilla from that same desktop instead of having to boot back and forth.