Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: mbertrand on March 30, 2016, 02:33:41 PM
-
I have CUPS 1.6.2 extension running but it keep complaining about permissions. For example "foomatic-rip has insecure permissions".
You can't change permissions because it is mounted read only. What to do?
/tmp/tcloop/foomatic-rip/usr/local/lib/cups/filter/foomatic-rip
-
the foomatic-rip filter is in the cups-filters extension - you could try using that instead of the foomatic-rip extension?
-
Ok I will try thanks.
Did you set the ownership to root?
-
The ownership is set to whatever "sudo make install" sets it to :)
-
Ok I got my printer to work but if I use the cups-filter like you suggested because you say that foomatic-rip is part of but it I have error saying that it can't find foomatic-rip and I don't see it in the list of files. I can use the foomatic-rip package instead but I have to un squash it and chown the filters to root:root and then re sqash or else I get error that permissions are not good enough.
Is there a reason why the filters in foomatic-rip are user tc and group staff because I think they should be user root and group root?
-
I don't know why the permissions in the foomatic-rip extension are as they are.
I see /usr/local/lib/cups/filter/foomatic-rip is a symlink to /usr/local/bin/foomatic-rip in the foomatic-rip extension - in the cups-filters extension /usr/local/lib/cups/filter/foomatic-rip exists, but not /usr/local/bin/foomatic-rip.
Maybe you could try adding a symlink from /usr/local/bin to /usr/local/lib/cups/filter/foomatic-rip with the cups-filters extension and see if that works?
-
Sorry but I'm using cups-filter and I don't see foomatic-rip anywhere? Am I blind!
-
Assuming that you're using v7.0 x86, the file is /usr/local/lib/cups/filter/foomatic-rip
My suggestion is to try: $ sudo ln -s /usr/local/lib/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip
..and see if that works.
-
No! Looks like we are still using 5.
-
Ah - well you could unsquash the extension, copy it somewhere, fix the permissions, squash it up again and keep it as a local extension?