And just changing the fstab file alone is no good. After doing any changes on any files in Red Hat, I think you have to (in your shell/konsole) type sysconfig. You should check if that is the file for RH. Mine is SuSEconfig. Same command, different name. All the appropriate file changes along the way will be made automatically by doing that command. Any time you make a direct file change, you MUST follow with that command, otherwise you're way ahead of me and probably cheating.
On Saturday January 4 2003 18:56, you wrote: > ls is list, dir is the directory listing. Doing --help behind either > command will help. > > First, type cd / to get to the top directory. Was going to say root > directory but the top directory will be fine. > > You will then see a list of possible places to change to. If your F: is > not mounted, you will have to first make sure it is mountable, this can be > done by examining the fstab file in /etc like going cd /etc and > finding the fstab file in either a file edit program or even the Konquerer. > > If the so called F: whatever you've called the FAT 32 partition can't be > seen in fstab, then you need to make the partition available for Linux. > > If it's there, you need to mount it. It may be a root only partition so to > speak so you may have to su then mount thenameofthepartion > > If the partition isn't seen in fstab, you will need to make the partition > available in the fstab file so Linux knows it can be mounted. > > I can hardly see the screen right now so that's enough for me, I'm not a RH > guy. Them is the basics though. :)) > > A RH user will now step in and help. > > On Saturday January 4 2003 18:36, you wrote: > > Hi all. > > > > At the risk of displaying my obvious newbiness, and incurring the quick > > "rtfm" solution, can someone point me in the right direction with the > > following directions? I've got lots of manuals and books and magazines, > > which I've been reading but sometimes it's nice to just be able to ask a > > direct question and get a direct answer. Here's the scoop ... > > > > 1. How do you do a "dir f:" command in linux ? > > > > It's only one simple little question, but I've not been able to find the > > equivalent in linux. > > > > I'm running RH 8.0 and I've been playing around with it. Actually > > thought I'd been doing quite well, but I've got a pretty decent box to > > run it on. Some of you might have seen it at the last instalfest at > > Nexus. It's got a p4-2.4gh-512mb- spec. I have a removeable C: with > > 20gb on it, a D: that is a 12X DVD drive, and an E: that is a 40x12x48 > > LitOn CD-RW. They all work great. > > > > What I've been trying to do is access an F: that is a fat32 formatted > > 6.4gb common "data disk", that I wish to be available to my RH > > configuration and to my WinXP-Pro configuration, when I pull the RH C: > > out and plug in my WinXP C: (80 gb Western Digital). > > > > With Windows, I can open up explorer and check out c: and d: and etc, or > > go to dos (a window, in XP) and type "dir x: /w" or whatever. I'm very > > comfortable in Dos or in Windows, but I don't know all the equivalent > > commands in linux. > > > > Maybe I need to do something with Samba to accomplish this ?? I don't > > know, but I'm sure lots of people in this group can point me in several > > different directions that will all help me. > > > > My New Years Resolution last year was to get into linux and here I am. > > I haven't given up, and I'm still enthused about learning it. One of > > the things that I did accomplish was setting up my C: as a removeable > > drive so that I could plug my OS of choice in and boot accordingly. > > With Windows on my C: I have long been able to do a "ghost" image which > > I do frequently for obvious reasons. With Linux on my C: I ran into a > > problem in that testing the backup seemed to indicate the backup was not > > a reliable image. I've been able to succeed with Ghost 2003, however, > > albeit with a minor tweak to get the image up after it was made. It > > seems it needed a boot disk to boot from on the first run after imaging > > in order to correct something in the mbr or the lilo config. I'm not > > sure which, but booting from a disk did succeed in fixing the boot > > process on the HD so that the next time booting off the HD was > > successful. So now I can make a backup of my Linux C: and then play > > with it to my hearts content, without fear of trashing something and not > > having a backup. > > > > Progress sometimes occurs in small steps. But I'm running off at the > > mouth, so I better quit while I'm ahead. See you all at the meeting on > > Wed. > > > > (I've got my browser (mozilla 1.1) set, as far as I can tell, to send > > this in text mode, so if it fails and sends it in html, please let me > > know). > > > > TIA.
