I use ndiswrapper for installing windows driver for WiFi, but I do not know how to tell openSUSE that it should run ndiswrapper at boot.
I recognised /etc/rc.d/, rc?.d directories, but I do not know which kind of file I should create (K*, S*) - thats all.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you are ‘root’ and run something like ‘ndiswrapper -m’ I believe it
causes it to be loaded at boot. The issue is not loading ‘ndiswrapper’
the binary, but loading the ndiswrapper kernel module which is not ever
done via an init script.
Good luck.
Andrej novell wrote:
> I use ndiswrapper for installing windows driver for WiFi, but I do not
> know how to tell openSUSE that it should run ndiswrapper at boot.
>
> I recognised /etc/rc.d/, rc?.d directories, but I do not know which
> kind of file I should create (K*, S*) - thats all.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI/Opl3s42bA80+9kRAkPJAJ0fGfm+EU0E3AaHulmdD0e3XL+FsgCcCQSr
c/20KW3b6q8uUCUXYHTtw64=
=09F2
-----END PGP SIGNATURE-----
Thanks. This issue was partially solved in newbie problem - openSUSE Forums by JosipBroz.
But if I wish to run another process as service what I should done? The mechanism of rc.d is not very convenient (writing files into directories … -beside it I dont know programming languages).
P.S.:
usage: ndiswrapper OPTION
-i inffile install driver described by ‘inffile’
-a devid driver use installed ‘driver’ for ‘devid’ (dangerous)
-r driver remove ‘driver’
-l list installed drivers
-m write configuration for modprobe
-ma write module alias configuration for all devices
-mi write module install configuration for all devices
-v report version information
also maybe it is this but I dont tried it as I have solved the problem with ndiswrapper.
Thanks.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you want to run a process automatically on system bootup you need to
do it in /etc/init.d/ with a link in /etc/init.d/rc<runlevelNumber>.d
starting with S## where ## is a number, 00-99. Anyway, that’s how it
works. Creating a script to do this is trivial (really, really basic
programming) and there is a skeleton (/etc/init.d/skeleton) to help you
get going where all you basically do is paste in the start/stop comment
which you almost undoubtedly know already. If you don’t know the
command to start/stop your soon-to-be-a-service then you’ll need to
learn as this is just how computers work. Either you create a script
from a skeleton by adding a start/stop line or you modify the registry
(windows only) or you load it manually.
Good luck.
Andrej novell wrote:
> Thanks. This issue was partially solved in ‘newbie problem - openSUSE
> Forums’ (http://tinyurl.com/6k74qm) by JosipBroz.
>
> But if I wish to run another process as service what I should done? The
> mechanism of rc.d is not very convenient (writing files into directories
> … -beside it I dont know programming languages).
>
>
> P.S.:
> usage: ndiswrapper OPTION
> -i inffile install driver described by ‘inffile’
> -a devid driver use installed ‘driver’ for ‘devid’ (dangerous)
> -r driver remove ‘driver’
> -l list installed drivers
> -m write configuration for modprobe
> -ma write module alias configuration for all devices
> -mi write module install configuration for all devices
> -v report version information
>
> also maybe it is this but I dont tried it as I have solved the problem
> with ndiswrapper.
> Thanks.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI/PHX3s42bA80+9kRAuZkAJ9v3dOoS6JB+GjRG9zKJEt7njSxpwCdHjYS
evMLAA1mDAzJu4osT4EnaGk=
=11F5
-----END PGP SIGNATURE-----
There is a skeleton at /etc/init.d/skeleton. When you use this and fill in not only the start/stop part for your service (the stop part may be empty, but is should be there), but also the # comment lines iin the beginning, you can then go to YaST > System > System Services (Runlevel) and activate your service as all other services, so it will run at the appropriate runlevel(s).