Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-31-2004, 11:55 PM
|
#1
|
|
Member
Registered: Jun 2004
Distribution: Gentoo
Posts: 102
Rep:
|
am able to run firefox off console as SU, but not as user...
Hi.
I had d/led firefox from slackwares website, and use installpkg to install it. Now if i type 'firefox' in console in SU mode it will run just fine, but if i'm in normal user mode it wount run... why?
|
|
|
|
08-01-2004, 01:00 AM
|
#2
|
|
Senior Member
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140
|
Because of permissions problem. Try to locate your firefox dir then look if it has permissions to read (and maybe execute too) for other user than root ( rwxr-xr-x ).
|
|
|
|
08-01-2004, 04:23 AM
|
#3
|
|
Member
Registered: Jun 2004
Distribution: Gentoo
Posts: 102
Original Poster
Rep:
|
i did chown [username] /usr/lib/firefox-0.9.2 however it didnt chnage the situation for the better
what is happeneing?
|
|
|
|
08-01-2004, 07:10 AM
|
#4
|
|
Senior Member
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140
|
what about chown your_user ~/.firefox if it exists and try to search more firefox files in your system, locate firefox
also what is the output for :
find /usr/lib/firefox-0.9.2 -uid 0 -perm 700
find /usr/lib/firefox-0.9.2 -uid 0 -perm 600
Last edited by Cedrik; 08-01-2004 at 07:12 AM.
|
|
|
|
08-01-2004, 07:55 AM
|
#5
|
|
Member
Registered: Jul 2003
Distribution: Slackware 10.0
Posts: 196
Rep:
|
little help on finding files:
touch /var/lib/slocate/slocate.db
updatedb&
slocate firefox
slocate has yet to fail me. If you already know about that well then I'm just useless huh? 
|
|
|
|
08-01-2004, 02:35 PM
|
#6
|
|
Member
Registered: Jul 2004
Distribution: Slackware 10.0
Posts: 57
Rep:
|
(post deleted)
|
|
|
|
08-01-2004, 02:57 PM
|
#7
|
|
Senior Member
Registered: Aug 2003
Location: Birkenhead/Britain
Distribution: Linux From Scratch
Posts: 2,073
Rep:
|
To just chown the firefox directory is not enough, you have to do it recursively,
chown -R username /path/to/firfox
that way it descends into the firefox folder and changes the permissions on every file. After you've run Firefox once and it's created your profile, chown it back to root, you don't want to be browsing with a browser you can write to.
chown -R root:root /path/to/firefox
|
|
|
|
08-01-2004, 03:19 PM
|
#8
|
|
Member
Registered: Jun 2004
Distribution: Gentoo
Posts: 102
Original Poster
Rep:
|
recursing chowning worked, thanks.
however creating a profile (i even had set the setting folder to me in user folder) and giving firefox back to root didnt' do much.
can i set it so user can read but not write? or that is the default?
|
|
|
|
08-01-2004, 03:25 PM
|
#9
|
|
Member
Registered: Nov 2003
Location: over there
Distribution: Debian Testing
Posts: 191
Rep:
|
Users should be able to read the directory by default. Try "chmod -R go+r /path/to/firefox"
That will give read permissions to pretty much everybody. It's good to keep directories under the ownership of root, so you don't accidentally nuke them one day. So keep it under root:root, and to make sure you can't write to it, "chmod -R go-w /path/to/firefox"
Last edited by Brane Ded; 08-01-2004 at 03:29 PM.
|
|
|
|
08-01-2004, 04:41 PM
|
#10
|
|
Senior Member
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140
|
Directories need to be executable as well (chmod +x)
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 08:30 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|