Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
first is your slave disk "fat" or "ntfs"???. If its fat, no problem. If it is NTFS, then you need to recompile the kernel to enable NTFS support because RH does not come default with the support enabled. More over, your ntfs will only have read support on it.
if your drive is ntfs: get it to a friends place, copy your stuff, and reformat it as fat and then put back all your files.
if your drive is fat: (GNU/Linux supports read and write on fat partitions)
kickstart RH9.0. as root create a dir say 'fat' under /mnt. assuming your slavedisk has only one parition run mount in this manner
mount -t vfat /dev/hdb1 /mnt/fat
this should do it. your files should now be visible under /mnt/fat. in case you can't figure out your drives mount point. run grep on the dmesg output to figure out OR alternativley try running fdisk against the possible drives like this
fdisk /dev/hdb
fdisk /dev/hdd
Hope this helps
DaVenom
---------------------------------
"Excellence is never an accident"
Here is what I get:
root@MiniServ:~# mount -t vfat /dev/hdb1 /mnt/fat
mount: mount point /mnt/fat does not exist
root@MiniServ:~#
root@MiniServ:~#
The bios does recognize the drive FYI all jumpered correctly.
Please advise ?
Thanks
Quote:
Originally posted by DaVenom shaun....
you have to be more specific.
first is your slave disk "fat" or "ntfs"???. If its fat, no problem. If it is NTFS, then you need to recompile the kernel to enable NTFS support because RH does not come default with the support enabled. More over, your ntfs will only have read support on it.
if your drive is ntfs: get it to a friends place, copy your stuff, and reformat it as fat and then put back all your files.
if your drive is fat: (GNU/Linux supports read and write on fat partitions)
kickstart RH9.0. as root create a dir say 'fat' under /mnt. assuming your slavedisk has only one parition run mount in this manner
mount -t vfat /dev/hdb1 /mnt/fat
this should do it. your files should now be visible under /mnt/fat. in case you can't figure out your drives mount point. run grep on the dmesg output to figure out OR alternativley try running fdisk against the possible drives like this
fdisk /dev/hdb
fdisk /dev/hdd
Hope this helps
DaVenom
---------------------------------
"Excellence is never an accident"
i recommend making a fat32 partition if you plan to send files back to linux from windows.
the ntfs thing is good if your only interested in copying from windows to linux, and not other way around which its not capable of.
o yea, if your ever in linux and choose the fat32 option and wanted to copy a file to it, and got some goofy message that its a readonly drive...then you have to restart your computer and copy a file to it in windows first, cause i think windows does something that prevents reading some times for no real reason.
also if windows doesnt let you write to the fat32 partition, then restart your computer...i encounted that recently and have no idea what causes it...just weird.
In KDE as root, I added a file called hd2 to my mnt directory
I then did this without the -t
mount /dev/hdb1 /mnt/hd2 and it worked great
I think I understand what I've done now.
I also figured out this same thing with the cdrom I now understand these mnt folders.
however I thought I would have to mount with fat, or vfat for something but it did not appears to be a problem
Also I noticed that I was able to use this thing called SLAX to read boot and read my ntfs drive, I'm sure I could have figured out how to mount this somehow and eventually compiled a kernel to get it working, however I'm newbie and thought I'd roll the dice on this SlaxLive thing, and it did work for that purpose
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.