[protonsix]

Hi friends of Tux,

Please skip my post if digressions give you indigestion.

My buddy and I are dabbling somewhat unsuccessfully with Mandrake 8.2. Got a few questions, maybe you have a hint or two.

He has temporarily lost internet service. So I have been ferrying files on CD-ROMs to his PC.

A Great McMurdo mist lifted when we found out about the fstab secrets of mnt/cdrom and mnt/cdrom2. I am just barely getting OK with the [/hda1,...skip ahead if not used... primaries] ---- [/hda5 (swap),/hda6... the extended partition's logical parts]

My buddy's installation seems to be missing a Conquistador file manager. (Eurospeak) I just about lost it when I could neither guess the Unix for delete on the console OR lay hands on the GUI file manager. I could not spot the answer on the console page filler. Then I foolishly attempted to use the generic pdf reader on long Mandrake docs! I gave up--wisely.

Where is this KDE Konqueror lurking? I would try to search with a command, but I am 99% sure it would not work as I would not know what directory to check. The Parameter Cafeteria (on MAN Street) for some Linux commands leaves me bewildered...

To finish with one more bail out of my floundering dinghy, I am stymied trying to install Adobe Acrobat 5 reader on his PC. There's a report of input/output error for the Adobe file named "install", say in doing a copy from CD to hard drive. Does this purported error have something to do with Linux naming one of its own internal routines the same name? The Adobe file install appears to be a script file, but does not end in sh as DOS batch files end in bat.

This is probably not relevant, but I extracted/de-archived the Adobe download using a Windows utility.

I am fond of the penguin, but I just about feel like checking with coldwire to see what a one-way advance purchase fare would be back to McMurdoville. He is showing signs of homesickness.

Roland

[protonsix]

Hi friends of Tux,

I found something called Appendix B. A Comparison of Common DOS and Linux Commands (Red Hat Linux Getting Started Guide). Just what I was seeking.

I am only feeling in the Antarctic night, but I am going to try out the command find / -name konqu* [unable to find an rpm with konqueror name on installation CD's]

The desktop on my friend's KDE desktop is icon-free. The offerings on the menuing jump-ups leave me just this side of hyperthermia.

I just then found out penguins don't live at McMurdo! It figures.

Roland

[protonsix]

From konq_main.cc

37 static KCmdLineOptions options[] =
38 {
39 { "silent", I18N_NOOP("Start without a default window."), 0 },
40 { "profile <profile>", I18N_NOOP("Profile to open."), 0 },
41 { "mimetype <mimetype>", I18N_NOOP("Mimetype to use for this URL, (e.g. text/html or inode/directory)."), 0 },
42 { "+[url]", I18N_NOOP("Location to open."), 0 },
43 { 0, 0, 0}
44 };

Maybe the Konqueror's hidden entry point is konq_main at the command line!

I am still clueless about installing Acrobat reader. Your help is sought earnestly.

Roland

[codejockey]

A very good thought -- but I think not likely correct. More important: on my system, konqueror is located in /opt/kde/bin. If you can locate other KDE apps on your system, konquerer is likely to be in the same location. Did you try the find command that was suggested (note that Unix/Linux is case-sensitive, so Konqueror is different from konqueror; note also that you should run the command as root, in order to have access to every directory on your system)? You might also try the following command: env | egrep KD and look for an environment variable such as KDEDIR, which will point you to the root of the KDE application.

On the Acrobat Reader: more later.

Hope this helps.

[codejockey]

Addendum: you will need quotes in the find command: find / -name "konq*". Without them, the shell will expand the asterisk ('*'), not what you intended.

Hope this helps.

[protonsix]

Hi codejockey,

Yeah, I bet the entry point in the source code may not show up in a binary file with the same name. Sure seems plausible though. Probably should have looked in some sort of command file that describes the relocatable output desired from the compiler.

Thanks too for warning me of the syntax I need to be aware of to do what I was trying to do.

I am eager to play with the find command. I can't express my frustration at not being able to find anything I unless I knew where it was---Catch 22.

The boxes of environment settings conveyor-belted to egrep the picker of KD stuff is Penguin cool. Will try for sure.

Going to give Tux another chance to install happily on my PC tomorrow on /dev/hda3.

Roland

[codejockey]

A few additional thoughts on finding things:

The type command (a bash/Bourne shell built-in) will report the full pathname of the file that would be executed if the supplied argument were to be executed as a command. For example, type ls would show you which binary or script named ls would be executed by typing the ls command at the command prompt. Handy, as it considers aliases as well as filenames.

The which command searches your PATH for the first instance of a command matching the supplied argument. For example, which ls would show you the location of the ls command (/bin/ls on my system). Note that the which command does NOT consider aliases. Here's the difference:

ROOT: 85 /etc/X11/xinit-> which ls
/bin/ls
ROOT: 86 /etc/X11/xinit-> type ls
ls is aliased to `/bin/ls $LS_OPTIONS'

Note that the type command shows that ls would actually be executed with $LS_OPTIONS as an argument (and that ls is aliased). The which command simply reports the location of the ls command without any further info.

You might try which konqueror or type konqueror and see what your results are (you may get a message that no konqueror is found in some long string of directories (your PATH), but even if you do, at least you know that it's time to use the find command to locate the executable once and for all).

Hope this helps.

[protonsix]

Hi codejockey,

I am excited about trying the commands on my PC. I only get over to my friend's machine with the vanishing konqueror a few times a week.

Thanks too for suggesting an order of trying these tools.

First, I gotta get my Tux safely onto the third rock from the MBR.

Roland