SlackwareThis Forum is for the discussion of Slackware 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.
Just so you don't mistrust so much, Piter Punk is one of the foremost and longest standing contributors to Slackware. Search nearly any Slack Changelog for his name and you'll see what I mean.
So is editting this file the right thing to do? It seems like I'm hacking up a system file, and I shuold maybe be approaching it differtnyl, whats the usualy course of action for adding you own slackware services?
You can also take it one step further. I do many such "tweaks" to stock slackware scripts. It's a pain in the but every time I install slackware to change all those files again. So, I'll explode package on the original package, make my modifications, package it back up, make a new ISO with the new package included and then burn a new disk.
That way, once I'm done installing, I have no tweaks to perform. It's already setup just the way I like it.
As for the post before your last, if I were to put a script in rc.d, and chmod it -x, it would automaically start on bootup (even if I didnt edit the setup file?)
Look at the for loop again in /var/log/setup/setup.services... That's all that script does. The for loop at the bottom is the meat of the script and the rest is just dialog fluff. IMO, it's actually quicker to open a terminal and use chmod than it is to do it thru pkgtool....
On a side note, the only way this exectable/non-exectable rc system works is if you enclose your startup command in an if then statement. So, if your using /etc/rc.d/rc.local to fire your script up, then use this in rc.local:
Code:
if [ -x /etc/rc.d/rc.ut2004ded ]; then
/etc/rc.d/rc.ut2004ded start
fi
or put that towards the end of rc.M... Doesn't matter what script you use. They are both appropriate places to start your UT server.
I dont know, I dont trust a guy named Piter Punk, this is slackware compatible?
Making comments about "forum nazis" and snide remarks about PiterPunk are not good ways of endearing yourself to the people most qualified to help you here.
So your saying people shouldn't be allowed to make jokes in the Subject line, IN THE SLACKWARE SECTION? Are you crazy? Fuck em if they can't take a joke.
You need to chill out man. Comments about nazi's are uncalled for whether joking or not. People don't appreciate it, especially if they're jewish. Use your head. Swearing is best left out of the forums as well. This is a public place, some common sense and tact is called for.
I ignored it and continued to help but I think you'll find any future help around here hard to come by unless you make some adjustments.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.