Hi. You use it so that you don't have to reboot when you have changed configurations, installed new programs etc. etc. Very handy :) Steve. On Sat, 06 May 2000, you wrote:

My question is why you would do init anything? what are you trying to accomplish?

Steve Sheriff wrote:

...

Hi everyone.

Small problem after 6.4 upgrade.

Switching to init S and then back to init 2 will not allow me to do a start x. One of the fonts is missing:

Cannot connect fatal server error could not open default font 'fixed'

and I have to do a normal reboot to get the X serbver up again.

Question: This does not happen if I do init 1 instead of init S. Does init 1 serve the same purpose as init S? If so, then this is the workaround.

Thanks, Steve.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

-- Michael H. Collins http://www.linuxlink.com The Ultimate WM http://www.xfce.org Fun with the Austin Linux group http://www.austinlug.org Need a Real Texas Radio Fix? http://www.texasrebelradio.com

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Hi Nadeem Yes, I am using xfstt. It is loaded in boot.local. Maybe I should put it somewhere else? Steve. On Sat, 06 May 2000, you wrote:

Hi, Are you using xfsft (or xfstt) by any chance? Its quite possible that switching to "S" causes it to shutdown but switching back to "2" does not bring it up again. Check your rc scripts. With "1", its possible that switching to it does not kill the font server, so switching back to 2 is not a problem.

Thanks, Nadeem

...

Hi everyone.

Small problem after 6.4 upgrade.

Switching to init S and then back to init 2 will not allow me to do a start x. One of the fonts is missing:

Cannot connect fatal server error could not open default font 'fixed'

and I have to do a normal reboot to get the X serbver up again.

Question: This does not happen if I do init 1 instead of init S. Does init 1 serve the same purpose as init S? If so, then this is the workaround.

Thanks, Steve.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Hello, go to my www.firstnethou.com/gz/xfsft_HOW-TO.html for step by step instructions for what Chris describes below. George Sat, 06 May 2000, ÷Ù ÎÁÐÉÓÁÌÉ:

Steve Sheriff wrote:

...

Yes, I am using xfstt. It is loaded in boot.local. Maybe I should put it somewhere else?

You'ld probably be best creating a proper startup script for it.

Go to /sbin/init.d and copy the skeleton script to a new file, for example xfstt. Now edit xfstt to point to the correct places for starting xfstt.

Finally, make links in /sbin/init.d/rc1.d, rc2.d and rc3.d to the script you've just created. The links should begin with an S (for start) or K (for kill, used when exiting that runlevel) and be followed by a number relating to the order in which the scripts are executed, and finally the name of the script in the above directory, for example: ln -s ../cron S21cron ln -s ../cron K19cron

The following is an exerpt from /etc/inittab: # runlevel 0 is halt # runlevel S is single-user # runlevel 1 is multi-user without network # runlevel 2 is multi-user with network # runlevel 3 is multi-user with network and xdm # runlevel 6 is reboot

As you can see, runlevel S and runlevel 1 are significantly different. The boot.local script only gets read on initial bootup. So when you enter runlevel S, just about everything is killed and upon moving back to runlevel 2 or 3, the font server isn't restarted. On the other hand, runlevel 1 doesn't just kill everything it can get its hands on and the font server survives.

...

On Sat, 06 May 2000, you wrote:

...

Are you using xfsft (or xfstt) by any chance? Its quite possible that switching to "S" causes it to shutdown but switching back to "2" does not bring it up again. Check your rc scripts. With "1", its possible that switching to it does not kill the font server, so switching back to 2 is not a problem.

...

Small problem after 6.4 upgrade.

Switching to init S and then back to init 2 will not allow me to do a start x. One of the fonts is missing:

Cannot connect fatal server error could not open default font 'fixed'

and I have to do a normal reboot to get the X serbver up again.

Question: This does not happen if I do init 1 instead of init S. Does init 1 serve the same purpose as init S? If so, then this is the workaround.

Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

-- My personal website http://www.firstnethou.com/gz/welcome.htm -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/