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.
Distribution: anything debian based, long live apt-get
Posts: 230
Rep:
if your using kde go to your user folder /home/username then type
cd .kde
the .kde folder is hidden, when your in there, cd into Autostart "/home/USERNAME/.kde/Autostart/", and write a shell script in there.....for instance..
if your using kde go to your user folder /home/username then type
cd .kde
the .kde folder is hidden, when your in there, cd into Autostart "/home/USERNAME/.kde/Autostart/", and write a shell script in there.....for instance..
For kernel modules ? (Modprobe will work, but there isn't an option to ensure that it will be reinstalled at next boot, AFAIK...)
Distribution: anything debian based, long live apt-get
Posts: 230
Rep:
i load a module at boot via a shell script in my kde autostart folder, and have never once had a problem with it since the day i wrote it a few months ago
I guess the only time that this approach could cause problems, would be if you needed the module to activate something important (display driver, network card etc.) before X was loaded.
My personal preference is for the first method, but modification and freedom of choice are what Linux is about, after all.
Originally posted by fatrandy13 i load a module at boot via a shell script in my kde autostart folder, and have never once had a problem with it since the day i wrote it a few months ago
You login in X as root? Why? Or you set a setuid bit for the script?
Anyway i don't think modules should be loaded only when KDE, GNOME or whatever starts ... There may be situations, but... hmmm....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.