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.
I am trying to access my Windows files using;
mount -t vfat /dev/hda1/mnt/windows which returns an error. The first Partition is a FAT32 partition and the only other Partition is the Linux one.
using grep vfat /etc/fstab returns nothing.
I have tried mount -t FAT32 /dev/hda1/............
with identical result
It's not so simple as that, I find that I cannot mount any directory of any dev unless it is in the list of mountable devices in the user mount tool window in the System settings blind, hda1 is not in that list, only fd0 (floppy) & cdrom
I don't know what distro you're using, but it sounds as if you have to edit your /etc/fstab to allow normal users to access the partition. You can do this e. g. by using the parameter "users", maybe "rw" to have read and write access and "umask=0" to set the permissions of the files on your vfat partition.
If this doesn't work please look, if the directories /mnt/cdrom (or where your cdrom is mounted) and /mnt/windows have the same permissions.
Only the super user (su aka root) has the permissions to do this. You also need the relevant file system support to be turned on. These requirements are standard on all systems.
The random mount of a device does not require any editing of /etc/fstab as this would only be required if you want them permanently mounted on /mnt
OK sorry I forgot to use the word "not" in my previous post in the statement The random mount.... which I have now corrected. To be super user bring up a console and at the prompt enter su and you should be asked for the root password. You will notice that as a user at the prompt you will have $ but as super user you will have #.
If you have the # at the prompt you are the super user and you can use the mount command. if you get a response that it cannot mount the partition because it is an unknown file type then you will have to enable the vfat module in your kernel. This normal way to do this is, again as su, insmod vfat.
Hope this helps.
Sounds like you tried to start /etc/fstab. It's a text file you can edit with any texteditor. You could use any, depending on what you have installed. I prefer "pico" or "nano", but many folks use vi, vim or emacs. If you do this in a terminal window e. g. in KDE or Gnome, you could also use kedit or kwrite. Just type any of the commands and append the filename, like "pico /etc/fstab" as root. Then you should be able to modify the file.
my root prompt is # as you thought. I did 'insmod vfat' as you suggested and received the following:
needless to say I'm out of my depth!
I was still unable to use 'mount -t vfat.......
By the way my RedHat release is 9
The unresolved symbols means that you do not have your kernel source installed. You need to install the kernel source for your kernel which should be on the install disks. I was under the impression that RH installed the source automatically. The root cause appears to be that you don't have file system support for vfat. Once you have installed the kernel source try the insmod again.
re 'kernel source', the RH Linux came on 3 CDs. Can I boot from CD1 (as I did to install in the first place) and amend the installation? or do you suggest addressing the CD after normal booting?
I suspect that other bits are missing - I have a Sagem Broadband Modem and the driver came downloaded with a patch. I applied the patch but ./configure failed with error message " no C Compiler in path"
There must be a software installation method available. Sorry I know very little about the RH systems as I have worked almost exclusively with Debian based systems. I know with Mandrake they had a software manager that listed the packages available on the cd's. Suggest perhaps posing this question in the distro section. Sorry i am not much help on this.
I have found the source of my problems.
I believe that two of the three installation CDROMS are faulty.
I went to 'Add/Remove pgms and found loads of packages unistalled including a Windows file server called Samba.
When I tried to 'ADD' it asked for CDROM 2 & 3 neither of which could be addressed so the installations failed.
I looked at the two CDROMs using Windows & they could not be addressed (the CDROM Drive is behaving normally with other CDROMs).
As a 'NEWBIE' I naturally assume that when things go wrong the problem is my ignorance!
I will contact the supplier (linuxworld.co.uk) for replacement CDROMS.
Many thanks for you help and being prepared to 'stick with me'!
Yes, it does sound like your media is bad. RH9 has a built in disk test. If you put in the first disk it offers to do a 'media check'. Do this. Your installation seems to be missing several things, as my RH9 install can mount vfat just fine without having to insmod anything. Did you select 'minimal' at the package selection?