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.
Originally, I had College Linux on one 6gb hd and windows xp on another 40gb drive. I downloaded Fedora because I wanted to try something else out. Red Hat is one of the most popular releases so I thought I would see what they had up their sleeves.
After Installing Linux I thought everything was running smooth. Until a few days later I tried to start Windows. Once selected, It freezes up like it thought it was running windows 95 or something (humor- not serious). Anyway, I restart into linux and try to access the drive but it just doesn't see it. College Linux was able to read the drive. Is that something specific to that release or is something screwed up? In the KDE Help center, the following is displayed under Partition Information:
This page displays information about partitions on your hard drives.
The exact information displayed is system-dependent. On some systems, partition information cannot be displayed yet.
On Linux, this information is read from /proc/partitions, which is only available if the /proc pseudo-filesystem is compiled into the (2.1.x or later) kernal.
The First two columns are the major and minor numbers respectively. The third column is the number of blocks (usually 1 block = 1024 bytes). The fourth column is a label for the device.
The user cannot modify any settings on this page.
No information is displayed.
Konqueror is showing
Hard Disc [/]
Hard Disc (hdb1) [/]
Hard Disc [var/lib/nfs/rpc_pipefs]
It looks like your /proc/ filesystem isn't mounted, which is very odd.
Try running "mount /proc/" or, failing that, "mount /proc/ -t procfs" (you will need to be root to do this), and look at the KDE Help Center again.
Running the "mount" command in a terminal should show you which filesystems are mounted, and which devices (if any) they reside on.
Another place to look is the /etc/fstab file; this lists all the filesystems that your computer will try to mount when it starts up. Run "dmesg | less" (that's a pipe, shift+backslash on most keyboards) in a terminal to see any error messages.
If the hda devices still won't mount, try running "less -f /dev/hda" in a terminal (as root). You should see a screenful of either ^@ or just gibberish. If you get a message like "No such device or address" then there's a problem accessing your hard disk. Check the ATA cable and power connector are both in the right way around, that it's set to be a master (not slave) drive and it's plugged into the same ATA cable as hdb. If it's set to "cable select", then make sure the cable is a cable select type (they have some of the wires twisted over I think).
Also, check your BIOS; if it's selected to boot into the slave hard disk, Windows doesn't stand much chance of booting up.
[root@localhost root]# mount /proc/
mount: proc already mounted
[root@localhost root]# mount /proc/ -t procfs
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
[root@localhost root]# mount
/dev/hdb1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
none on /dev/shm type tmpfs (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
when typing "less -f /dev/hda" I get the screen full of @'s and gibberish
When attempting to go to XP I get the following message:
This tells us that your hard-disk is working and the proc filesystem is mounted.
It looks like the problem lies with the Windows chain-loader, or with Windows itself. If you can boot from a Windows bootable floppy, you can run the command:
This will reinstall the Windows bootloader onto C:. You can then boot the Linux system from a rescue disk, and reinstall the Linux boot loader to get Linux back; hopefully that will fix the problem.
…It's been a while since I've used Windows properly, and this is strictly a Windows (well, DOS) question.
But I think you're missing the sys.com (or sys.exe or whatever it is) executable from your Windows setup. Possibly it's been replaced with something else; you'd be better off asking in a Windows forum how you reinstall just your bootloader. Mention “sys c:” too so that more people know what you're talking about.