LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-07-2007, 12:03 PM   #1
alienux
Member
 
Registered: Sep 2006
Location: Dayton, Ohio
Distribution: Slackware 12, Fedora Core, PCLinuxOS
Posts: 194

Rep: Reputation: 30
Permissions changed after changing to init 4


Couldn't find any info on this with LQ or Google searches.....

Ever since I've used Slackware, I've always left the default inittab setting to boot into init 3, then started x manually. I recently decided that I wanted to use a custom login screen, so I installed the moodin plugin and changed my inittab file so that I would boot into init 4.

After doing this, as a regular user, I could no longer access my CD-RW device through k3b, and I could no longer get sounds with flash content. I had to add my user to both the cdrom and audio groups to get those items to work. I know adding the mooding plugin shouldn't have affected permissions, but I didn't think changing the default bootup runlevel would.

Those are the only changes I made to the computer. What caused the permissions changes, and since those were somehow changed, what other permissions may have changed that I may not have noticed yet? (Everything else appears to be ok).
 
Old 03-07-2007, 01:02 PM   #2
ille.pugil42
Member
 
Registered: Dec 2005
Distribution: Slackware
Posts: 151

Rep: Reputation: 30
I've been running Slackware for a long time, and I've never seen a problem with permissions changing when going from init 3 to 4. The only thing that's changing there is what services are loading, unloading. To prove this point, change the init back to 3 and see what happens with audio.
 
Old 03-07-2007, 01:10 PM   #3
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 543Reputation: 543Reputation: 543Reputation: 543Reputation: 543Reputation: 543
Here's a tip I just figured out which you might want to check on: Make sure the etc/fstab file is readable by everyone, or at very least readable/accessibly to you the 'user'.
A while back I went on a security binge and chmodded and un-SUIDed a lot of stuff, among them was that file.
I didn't realize that this was why I couldn't seem to mount anything anywhere except as root, despite allowing user/users in fstab.
Also make sure that mount and umount are executable by user/group as well.

PS - My DVD player software and music player weren't allowed accessing the CD-drives either until this change.

Last edited by GrapefruiTgirl; 03-07-2007 at 01:14 PM.
 
Old 03-07-2007, 01:47 PM   #4
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,964
Blog Entries: 11

Rep: Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865Reputation: 865
Quote:
Originally Posted by alienux
After doing this, as a regular user, I could no longer access my CD-RW device through k3b, and I could no longer get sounds with flash content. I had to add my user to both the cdrom and audio groups to get those items to work. I know adding the mooding plugin shouldn't have affected permissions, but I didn't think changing the default bootup runlevel would.
That would actually be Slackwares defaults; Slack is quite tight by
default, and users don't have access to audio or cdrom devices until
explicitly granted.

I can't see how that would relate to the default runlevel, though.

And as for permissions: you can check all files against MAINFEST.bz2
on your Slackware CD - it holds all relevant info.



Cheers,
Tink
 
Old 03-07-2007, 01:54 PM   #5
alienux
Member
 
Registered: Sep 2006
Location: Dayton, Ohio
Distribution: Slackware 12, Fedora Core, PCLinuxOS
Posts: 194

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by Tinkster
That would actually be Slackwares defaults; Slack is quite tight by
default, and users don't have access to audio or cdrom devices until
explicitly granted.
That makes sense with other posts I've seen where users couldn't access audio or cdrom in Slackware, but on both 10.2 and 11, my default install let normal users access those things without me having to modify anything, that's what's confusing to me. I really didn't think changing runlevel could do anything, but that was the only system related change I actually made. I think I'm just going to chalk this one up to random weirdness.
 
Old 03-07-2007, 02:09 PM   #6
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 543Reputation: 543Reputation: 543Reputation: 543Reputation: 543Reputation: 543
I don't think changing the runlevel actually did it.
I can't accurately comment on how the default config was set up on my system, as I'm 2 months new to linux, and have made a lot of tune-ups and changes since I installed Slackware. That said, I had been having mount problems or 'issues' ever since day one, which are now 100% solved and working great, now that I know what I'm doing a little better
 
Old 04-09-2007, 03:57 PM   #7
alienux
Member
 
Registered: Sep 2006
Location: Dayton, Ohio
Distribution: Slackware 12, Fedora Core, PCLinuxOS
Posts: 194

Original Poster
Rep: Reputation: 30
I had occasion to try this again with a fresh Slackware installation, and was able to reproduce the same behavior. The initial user that I created was able to access cdrom, video, and several other groups with no additional configuration after install (although when I did the "groups" command, it showed no groups). When I changed the system to init 4, I could no longer access the cdrom, anything requiring 3D acceleration, etc., until I manually added the user to those groups.

Not really a problem, but now I at least know when it happened.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
permissions are changed when mounting joadoor Linux - Security 3 04-03-2006 06:59 AM
changed permissions, ls does not work blizunt7 Linux - General 3 09-26-2005 07:12 AM
changed permissions shosh Linux - General 3 11-02-2004 05:07 AM
Something Changed File Permissions anthony114 Linux - Security 2 08-12-2003 08:53 PM
Permissions changed crashmeister Linux - Security 3 11-13-2002 07:57 AM


All times are GMT -5. The time now is 08:57 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration