gnome file manager missing on red hat 7.2

ronss · 03-21-2002, 02:53 AM

studying out of the redhat 7.1 manual, i have red hat 7.2 installed. i was going to practice with the gnome file manager which should be on my desktop. it,s not there and i cannot find it. need some help here . thanks ronss

Mara · 03-21-2002, 03:33 AM

Hmm, you're probably referring to Nautilus. Try running it from console.

ronss · 03-21-2002, 03:59 AM

red hat 7.2 has changes done to the file system. i am wondering if the gnome file manger is no longer available.i found the kde file manager and looks nothing like what is in the red hat 7.1 manual, its suppose to be similiar to the gnome file . i just did a little more research, red hat does have a different file system. the ext.3 journaling file system. i have just wasted $47 on this red hat 7.1 manual i bet:smash:

acid_kewpie · 03-21-2002, 05:18 AM

imho paying for a manual is usually a bad idea... the information is always around on line anywya, click my sig link...

the "gnome file namager" could either be nautilus or gmc, justrun them from console.

Nautilus is crap btw.

ronss · 03-21-2002, 08:10 AM

kind of agree. the two books that i have, red hat 7.1, and learning red hat linux , 2nd edition, about half the pages are on installing. i can do that without not a whole lot of problems. i just installed my first rpm , with the help of learning red hat 2nd editon, it was very helpful on that. someone was very critical about using rpm,s , read somewhere here, i really didn,t think it was that hard. more success coming , i hope, just got to do the reading. thanks ronss

acid_kewpie · 03-21-2002, 08:18 AM

well, the whole point of rpm's is that they are very easy to start off with, but once you start changing things around you will get a LOT of problems with dependencies. this package requires a certani version of another package, whilst a bunch of other ones want a different version, so to install a package you have to break a dependency, which frequently doesn't matter. most dependencies are too restrictive, meaning all teh rpms can get in a very nasty mess, that is near impossible to back out of. this contrasts to installing from source, where a ./configure script simply ensures certain programs and particular files exist and work, which means that you'll get much more compatabilty and upgradability.