DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to 'optimize' my boot process. I'm running Debian GNU/Linux sarge-sid, installed from a Knoppix 3.3 CD, which I think is the guilty for this problem.
I read a lot about boot process and all that stuff. I know that scripts that shall be killed or executed in each runlevel shall be in /etc/init.d directory and are called by a symlink in /etc/rn.d where N is the runlevel number.
The problem is that I have symlinks to the same script in several runlevels, thing that seems kind of silly to me, because, i.e., kdm can't be started in runlevel 2...
For example:
In runlevel 1, init must kill: gdm, speedtouch and xsession. When did those things started? God, it's runlevel 1...
In runlevel 2 it insists to start gdm, kdm, speedtouch, iptables and samba. How?
In runlevel 3 it's still insisting in start gdm, kdm, speedtouch and samba...
It seems to me that it's ok that 'speedtouch' and 'iptables' start running in runlevel 4 and in runlevel 5 'kdm' starts.
My question is, can I just remove the symlinks from /etc/rc1.d, 2.d, 3.d and 4.d? That way it wouldn't keep trying to start annoying things in annoying runlevels.
One last question, my 'speedtouch' script is failing because kernel module speedtch interferes with it's execution. I have to type: rmmod speedtch and then /etc/init.d/speedtouch start in order to connect.
How can I avoid kernel from loading module speedtch?
I'm trying to 'optimize' my boot process. I'm running Debian GNU/Linux sarge-sid, installed from a Knoppix 3.3 CD, which I think is the guilty for this problem.
I read a lot about boot process and all that stuff. I know that scripts that shall be killed or executed in each runlevel shall be in /etc/init.d directory and are called by a symlink in /etc/rn.d where N is the runlevel number.
The problem is that I have symlinks to the same script in several runlevels, thing that seems kind of silly to me, because, i.e., kdm can't be started in runlevel 2...
You have done some reading good. The levels 2 through 5 are all the same in Debian unless you do as you seem to want to and configure it differently.
Quote:
For example:
In runlevel 1, init must kill: gdm, speedtouch and xsession. When did those things started? God, it's runlevel 1...
They are not getting started those should be links to killing off the processes if they look like these they I have here in a spare machine where I mounted the Knoppix partition.
The one start link (S20single) is for the single user mode start.
Quote:
In runlevel 2 it insists to start gdm, kdm, speedtouch, iptables and samba. How?
I think you mean "Why?" for the same reason I gave above the 2-5 levels are all the same.
Quote:
In runlevel 3 it's still insisting in start gdm, kdm, speedtouch and samba...
Same as above.
Quote:
It seems to me that it's ok that 'speedtouch' and 'iptables' start running in runlevel 4 and in runlevel 5 'kdm' starts.
Networking gets started in the 2-5 so you would definitely want iptables in all of them.
Quote:
My question is, can I just remove the symlinks from /etc/rc1.d, 2.d, 3.d and 4.d? That way it wouldn't keep trying to start annoying things in annoying runlevels.
Certainly you can configure your scripts any way you want just make sure you do not destroy the functioning of the system in the process. For instance if you do not wish to start kdm in 2, 3 and 4 I believe the correct syntax for the command as root would be update-rc.d kdm remove 2 3 4 . you may want to consult the man page this is from memory.
Quote:
One last question, my 'speedtouch' script is failing because kernel module speedtch interferes with it's execution. I have to type: rmmod speedtch and then /etc/init.d/speedtouch start in order to connect.
How can I avoid kernel from loading module speedtch?
Thank you very much in advance
Well the simple but complicated solution is to compile and install a new kernel and leave the module out then you never have to worry about it being loaded. A good work around is to have the second line of your script have "rmmod speedtch" then carry on with its normal function eg.
Problem solved. I won't touch those scripts in 2-5 runlevels...
I also added 'rmmod speedtch' to the speedtouch script second line. Should be good now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.