SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
(Solved) Slackware12 .. Fstab and Package Questions
I've just installed Slackware12 (very nice OS, thanks Pat), and have a couple of questions to improve my installation.
Question1: I don't seem to be able to view the contents of my slackware partition in KDE (/dev/hda1) as either user or root?
(permission denied ... as 'user')
(security policy prevents access ... as 'root')
My fstab file reads as follows: can anyone offer any suggestions on how I can have read/write permissions in KDE as root, and read permissions as user?
I have also noticed that some of my favorite packages are not installed ... Kaffeine, k9copy, iso-master .. etc ....
Question2: If I install these packages from the slackware11 repositories (using swaret), will i break my system in any way?
Or do I have to wait until the files appear in the slackware12 repositories and then swaret --install them?
Any advice would be appreciated
Thanks very much
Last edited by orbit; 07-15-2007 at 08:07 PM.
Reason: Topic was resolved
Forget about /dev/hda1. That is the device and not where the partition is mounted.
Not using slackware, I don't know about question 2. Most likely it the library versions of some packages will be different and you won't be able to install the packages. You might try installing these packages from source instead of an install version that installs binaries.
To answer your question; while in KDE, if i open either 'root' and/or 'user' console shells, i can list the / filesystem.
But if I try to access the / filesystem through KDE system:/media, the problem I mentioned above occurs.
All the other partitions have read/write permissions correct as per the fstab file I posted earlier, except for the slackware / partition.
Does this help at all, is there any other information I can give you to help resolve this problem?
Thanks very much, I'll look forward to your reply.
You can enter "/" in the file browser. I did notice that I can open my root partition via media:/. I don't know if that is because I am a member of the wheel group. Anyway, you can just enter "/" in the file browser so it isn't a biggie. What are the permissions on the / directory?
Hi again jschiwal, thanks again for your help on this topic
I can enter / in the konqueror file manager and slackware's root filesystem will show up, so that is a possible work around for the problem.
However I would still like to resolve this issue and use the /media icon, so that it is possible to access the partition normally like all the other partitions through KDE.
With regards to your permissions query of my / directory, I'm not sure how I can check that, as KDE shows the slackware partition as an 'Unmounted Hard Disk Volume' (even though I have booted slackware) and therefore does not give the usual [permissions] tab in the properties dialogue. I know how to check folder permissions in a midnight commander terminal, but I do not know how to use it to check an actual partition's permissions? Can you offer any suggestions as to how I can get that / permissions information to you?
Following on with your user group settings suggestion, I have checked the group settings for the system accounts;
The 'user' account is in these groups;
audio, cdrom, disk, floppy, ftp, games, haldaemon, messagebus, nobody, nogroup, plugdev, video and wheel.
The 'root' account is in these groups;
adm, bin, daemon, disk, floppy, sys and wheel groups.
Do you think any of these group settings need to be adjusted on either accounts to make KDE allow me to use the /media icon?
Once again thanks very much for your help, and again I'll look forward to your reply.
I think that the haldaemon and messagebus groups are system groups. Being a member of those might be dangerous.
nobody is a group with very little permissions. It is used by a root cron job to limit the permissions on a daemon. You don't need to be a member of nobody. I suspect you don't want to be a member of nogroup for the same reason.
I don't have a plugdev group. Check if this is a group that grants members access to some features or if it is a group used because the hotplugging system is jailed. For example, you don't want normal users to be members of the disk group because that would give access the the devices themselves.
The sidebar in konqueror also has a "system" icon that is a shortcut to open the root directory.
You can look at permissions in the console using the -l option of the ls command.
Ok thanks jschiwal,
I have now removed the groups; [haldaemon, messagebus, nobody and nogroup] from the 'user' account, and then restarted the pc.
(unfortunately, didn't make any difference when I attempted to mount the Slack12 partition, same 'permission denied' msg )
inputting ls -ld / in a root terminal returns;
drwxr-xr-x 22 root root 512 2007-07-10 11:03 //
Using the system sidebar in kde, if I highlight the slack12 (unmounted) partition, it shows:
From within my user account;
If I fast switch into my kde root account and do the same thing to the slack12 partition, it shows;
I don't have hotplug installed (I remember reading in one of the slack12 documentations, that Pat and the team had now dropped it in favor of the Hal daemon because of the upgrade to 2.6 kernel standard.
As a result of that change, I have read everywhere that users are just supposed to be added to the 'cdrom and plugdev' groups and then slack all works easily. This is why I haven't dropped the plugdev group from the user account.
Does this offer any leads to resolving this? Is there any other information I can give to help?
Again, thank you very much, I'll await your reply.
I would like to be able to access the slackware partition HDD icon in the /media directory using the mouse, (click=>Go) ... the same as I use all the other partitions; without getting a big 'Permission Denied' message.
If the icon is there, and the Slackware OS is running ... then I don't know why this icon shows up in /media as an 'Unmounted Hard Disk Volume' ?
(Which I am not at all allowed to access)
Having to manually input a / into the filemanager is a workaround for now, but it is messy and less than I would expect from this beautiful OS .. this is the (hopefully temporary) issue I am trying to resolve.
I can't reproduce this error at all. I don't normally use kde, but even so, media:/dev/sda3 (which is my root partition) displays fine in konqueror (as do all other devices). Does the icon show a lock on it when you just go to media:/ ?
Isn't the /media folder basically used by udev and/or hal to mount media in userspace? If so, then said media would be mounted with appropriate permissions for user. Mounting (an already mounted) root file system in userspace sounds like a bad idea.
Therefore, the proper way to access the root directory is with /
I overwhelmingly agree with mattydee about the "proper" way to access / - however, see my post in the other thread on this topic; I think you posted in it iirc, so you should get a mail notification about it.