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.
I did a bare 9.0 install and then updated to slackware-current and all is working well except printer setup under the kde print wizard. I have cups 1.1.19 and the gimp-print drivers installed along with the foomatic filters.
Looking at dmesg I do not see that cups is starting.
I have tried to /etc/rc.d/rc.cups restart as root and get the error message that permission is denied.
Looking at permissions for rc.cups I have rw-r--r--. Shouldn't this be executable in order for rc.M to start the print spooling system?
Added info. From the current changelog
+--------------------------+
Mon Aug 25 19:56:00 PDT 2003
isolinux/initrd.img, rootdisks/install.*: Support more than one installation
disc. In expert or menu mode, run all the menus for each disc, and then
go on to install the packages from that disc. Various other bugfixes.
a/cups-1.1.19-i486-3.tgz: chmod 644 /etc/rc.d/rc.cups.new so that CUPS
will not run on a default installation until the admin changes the perms.
a/infozip-5.50-i486-2.tgz: Fixed a bug where a specially crafted archive
might try to write to ../ or ../../, etc, potentially overwriting system
You may have a point there. I'm not positive, but what you say makes sense. I did the chmod +x because if you look at some of the other scripts in /etc/rc.d that are executable by default, such as rc.inet1 and 2, you'll see that the permissions are -rwxr-xr-x. That's why I say chmod +x.
Not sure this is real secure but I looked at an 9.0 system and the permissions of rc.cups were -rwxr-xr-x (chmod 755) and that allowed the cups server to load and subsequently setup.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.