Specifically, is there a file that tells the init to load the interface so I can do some testing before/after it loads?

The GUI is started at run level 5. So, if you boot to run level 3 you will have a running system before the GUI starts. Typing telinit 5 as root will "finish" the job.

Is this what you meant?

Yes partially. I was just wonder if there was some kind of folder/file that listed in what order everything started.

I have a feeling the answer is the rc5.d folder where all the processes are listed as like S01, S02, etc. Is this a correct assumption?

I think so. On my system (10.2) I have the file(s)

and

(actually, they are symbolic links) which are responsible for starting the graphical login.

If I remember correctly, the "S" versions are for start-up and the "K" versions for shut-down and the number gives the order to run things.

Ok, so I made my script and what not what I wanted to run at bootup. I put it in runlevel 5 and changed the file to S99 and K99. Was I correct in assuming this would be the last process to start/stop during boot up?

I am absolutely bewildered why this won't work.

That would have been my assumption too. First, a silly question; you have made your script executable, right?

Assuming you have, a little more detail on what you are trying to do would be helpful.

Pretty sure I did, I followed some thing online (this is my first week with Linux in about 5-6 years) and did like chmod 775 something. Then I believe I typed another command to link it?

Does it sounds like I did the right part? (I dont have it in front of me)

All I am trying to do is setup a persistant route, so when the pc boots up the command 'route add 192.168.0.1 gw 30.38.72.50' and then 'echo Hello > diditwork.txt

Those are the only 2 lines I have it in the fine, along with #!/bin/bash

Hmm. When I saw this I noticed your related thread. I know it can be hard at times, but it is best to stick to a single thread.

Anyway, I don't know why the attempts you have made are not working, but here are some other suggestions.

It seems that in SuSE, configuration is best done via the tools in YaST.

I noted that you are on 10.1. In 10.2 the default for network configuration is NetworkManager. I believe this program was in 10.1 also. See if it is being used in your system. Start the Network Devices tool from YaST. The first screen (on 10.2 anyway) asks if you want to use NetworkManager or the traditional ifup to manage network connections. Choose ifup and then proceed with adding the desired route. I suggest this since I have noticed the occasional oddity with NetworkManager. With ifup you are 100% in control of the network settings.

Make sure you remove your custom script from the init.d area to test this.