This is probably the same problem that I posted under http://www.linuxquestions.org/questi...&threadid=5647 but I have a little more info and still need help.

My system appears to be trying to start ppp during boot. Where is the command that makes this happen?

What's in your startup scritps (dir listing of /etc/init.d) and the rc2.d and rc3.d runlevels.

Most likely you're starting up routed. (shot in the dark)

I am getting really frustrated with this problem. I tried to download and install the latest version of Mozilla, only to have make install run for about 1/2 hour and then fail with a code 2 failure, whatever that is.
Then I tried to download and install the latest version of RP3 with same friggin results.

You juggested: "look at what's in your startup scritps (dir listing of /etc/init.d) and the rc2.d and rc3.d runlevels".

I do not understand what to look at, since these are directories with files therein that I am unfamiliar with.

Anyway, my system was just fouled up, and I lacked technical expertise to fix it. So I reloaded. Whatever was wrong has been fixed.

Incidentally, after I finished reloading, I set up my networking parameters and then invoked Mozilla. Once again, it appeared that Mozilla was not connecting with my ISP. So, I tried Netscape Navigator and, guess what...a connection was established!

I don't know what is wrong with Mozilla, but I shall not be using it again.

Damn. Sorry 'bout your luck.

In the init.d/ folder are a bunch of scripts (usually - symbolic liks or shortcuts may be used for compatibility) that are needed to call different system services upon each runlevel change. The scripts conatin commands to gracefully start/stop/reload/restart different services (ie: network, apache, route, upsd, ad infinitum...). By using shortcuts to the actual scripts, it means that whenever I make a modification to script "foo", it will apply to all runlevels and I won't have to edit the same script in each runlevel directory (rc1.d/ rc2.d/....)

The "init" service handles this process. Each subdir of "init.d/" (rc1.d/, rc2.d/, etc...) contains shortcuts to the above mentioned scripts. The naming of the directories is based upon the run-level. So "rc1.d" contains shortcuts to the scripts needed to go to run-level 1, or 'single-user' mode. So there would be no symlink (shortcut) for anything to do with networking (rc2.d/). We want networking in runlevel 2, so there would be shortcuts to your scripts related to networking. We want to make sure that things start and stop in the correct order. In other words, we want to load the module for our network card before we try to assert an IP address and routing information. We control this as below:

The shortcuts are prefixed with either an "Snn" or "Knn" where "nn" represents a number. "Snn" is seen by the 'init' service as "start this" and "Knn" is "kill this". The numbers represent the order of the Start/Kill sequence. So "S01foo" will run before "S25bar". So when you boot you load the keyboard and I/O and and the basic stuff to get us running. If you're only booting to single-user mode, you would only load those services linked from "rc1d". When you leave (init runlevel "0" - halt for eg.) you only shut down ("Knn") those services in "rc1.d".

I would imagine that someone else here could have given you a much better description in a lot fewer bytes, but that's the best I can offer.

Very helpful info...thanks