Hi friend! This is the way:

You need to run SysV-init Editor. The thing is really addictive. Feel the force of SysV!!
In kde do: System > Service configuration > SysV-init Editor.
The first screen that appears is self-explanatory. And it gives you complete control.
Post again and tell me what you think!

Hmm..
I can't find no service configuration in the KDE System menu..
Have to fire up Yast and see if I need to install the SysV-init Editor.
Or do I have to be logged into X as root?

I searched yast2, and it seems the package necessary is this:
sysvinit-2.85-20.i586.rpm

Ask rpm if you have it (rpm -q sysvinit), otherwise, install. Its so worth it!

Thanks friend,
I had the package installed already, but no System > Service configuration > SysV-init Editor.
Strange.

OK. Switched to root, same thing, no System > Service configuration > SysV-init Editor!
Can you find out what the command line entry is? (Sometimes SuSE forgets to update the menu when packages are post-installed).

what a hack! I don't know why the suse guys did it this way, but... We'll bring the system our way. Follow me:

sysvinit is located at /opt/kde3/bin/ksysv and it can be launched with "ksysv" command at the console. To be able to launch a root program when sued in the console you have, first, to disable access control by doing "xhost +" as a normal user.

1. Open console
2. As normal user do "xhost + "
3. Su to root
4. Do "opt/kde3/bin/ksysv"
5. Edit the script and save

To insert an item in the kde menu you can use the kde menu editor:

1. Launch Menu k
2. Choose Control Center > Regional and Accessibility > Keyboard shortcuts > The second dialog is "Command shortcuts", in the first line title there's a link "KDE menu editor": open it.
3. Create a new entry - which can be anywhere, btw - under System, call it System configuration (if you wanna comply with the suse standards. But its not mandatory).
4. Create a new item under the new entry. Call it sysV-init Editor. Under the field "command" you paste "ksysv -caption "%c" %i %m" (just like mine). If it doesn't work, issue the whole path /opt/kde3/bin/ksysv and don't forget to tick "Run as a different user" and the user is root, obviously.

Post again if it fails.

Well, you really got into the thick of things for me, didn't you? Thanks again for your efforts
Now I can finally contribute a little knowledge myself:
I decided to create the menu item before fiddling with the console commands, and suprise, surprise: there was now ksysv in /opt/kde3/bin! Searching Yast2 revealed that I needed to install the package kdeadmin3 which contains ksysv.
Done that, and lo, there is an entry System->Service Configuration containing KCron and SysV-Init Editor.
Now I can go play with it!

Btw, there is a little more direct way to get to the KDE menu editor: right-click on the (green) SuSE ball in the taskbar, and there it is..

Regards,

Mad_C

Well, you really got into the thick of things for me, didn't you? Thanks again for your efforts

You´re welcome, friend. Linux is one of the greatest collective efforts (if not the top one) of the history. It´s a joy to be a part of it.

I decided to create the menu item before fiddling with the console commands, and suprise, surprise: there was now ksysv in /opt/kde3/bin!

So, you mean, that rpm (sysvinit-2.85-20.i586.rpm) isn´t enough for one to run sysveditor?

Searching Yast2 revealed that I needed to install the package kdeadmin3 which contains ksysv.

Yast2 is a nice piece of software, indeed. People have made a big hype on whether its license is free software or not. Its not GPL, but its not restrictive as a prop. one. One thing is certain: yast2 accounts heavily for suse´s leading position.

Btw, there is a little more direct way to get to the KDE menu editor: right-click on the (green) SuSE ball in the taskbar, and there it is..

He he he... sorry for that! I knew that way was stupid. Sometimes I´m kinda lazy... There must be a direct way, also. And if you want to create a desktop icon, for example, its got to know where is the bin file. Do you know the command "whereis"? whereis finds files in your system, very useful. Do "whereis ksysv" to check it.

Bruno, that's what I meant:
>I decided to create the menu item before fiddling with the console commands, and suprise, >surprise: there was NO ksysv in /opt/kde3/bin!

> So, you mean, that rpm (sysvinit-2.85-20.i586.rpm) isn´t enough for one to run sysveditor?
No, you HAVE to install kdeadmin3 to get ksysv.

>Whereis: cool tool, I just keep forgetting about it.

Now if I can find somebody to help me with my DirectFB problems I will be a happy camper..

regards,

Chris

Hi,
I just wanted to report back in that I was able to fix my problem with DNS and host name resolving.
Everything is perfect. I got help from linuxant.com, since thats where I got my wireless drivers from.
I was missing some informtion in my ifcfg-wlan0. I added two lines and now it loads my linuxant drivers, then wpa encryption and then updates my DNS entries and my GAIM starts automatically at startup and connects pefectly.
I love this now. I feel myself getting addicted to Linux.

If only I can get some programs running on Wine.

Glad to know, crazi! What programs do you want to wine? You´d better start a new thread, as you will get more visibility.