System Permissions [Solved] and Autofs Errors [Unresolved]

[Tefrem34]

Hello to all the GenForumners.

I am stumped again.
I am trying to get my file system permission and sudo to work. Without making a directory in root, I can not make a new folder or even download anything off the internet. So I have been going through the forum and wiki trying to figure it out. I was fallowing the KDE setup guide and was trying to setup "Autofs" and I run the command

Code: Select all

/etc/init.d/autofs start

and it gives me

* Starting automounter ...
* No autofs support available in kernel [ !! ]
* ERROR: autofs failed to start

So I went into

/usr/src/linux

and ran

Code: Select all

make menuconfig

and made sure that I had

File systems --->
<*> Kernel automounter version 4 support (also supports v3)

enabeled. So I saved the ".config" and exited the kernel editor. I mounted my boot and ran

Code: Select all

grub2-mkconfig -o /boot/grub/grub.cfg

to make sure that it would update grub. However, I am missing a command some where, because after restarting my system I run

Code: Select all

/etc/init.d/autofs start

I get the same error. So, how would I update and save the changes to the kernel so it will work in my system?
My second issue is getting permissions enabled. I just can't figure out which line to edit with

Code: Select all

visudo

. I fallowed the hand boot in setting up my user account and adding it to the groups. I obviously did somthing wrong.
edit; I added my username under the root ALL=(ALL) ALL and sudo seems to be working, so, so far I figured that out.

Thanks again.

[ct85711]

the part that stands out to me, on a possible step you missed on the

...So I saved the ".config" and exited the kernel editor. I mounted my boot and ran...

Is the part of rebuilding the kernel (so the kernel knows of it). Just enabling it in the .config just tells the compiler to enable that option for the kernel when it is next built.

So, what you may need to do (if you didn't already do this, and didn't say that) is run

Code: Select all

make && make modules_install
make install

The first line will rebuild the kernel and any modules (with the new .config that you made doing the "make menuconfig"), and the second line will copy the kernel to your /boot directory. Do note, you still need to run

Code: Select all

grub2-mkconfig -o /boot/grub/grub.cfg

afterwards, so grub knows of the new kernel (it should pick the new kernel as default, and will give a fallback option to use the older version, so does not remove your old kernel, just copies the new kernel over)

[Tefrem34]

@ct85711, Thanks for the reply.

Code: Select all

make && make modules_install 
make install

That is what I missed! I wasn't sure if I could make changes without having to recompile the kernel so I didn't do this command.

Code: Select all

grub2-mkconfig -o /boot/grub/grub.cfg

I got an error on this when I first was trying to update the kernel, I think that I just have to mount my /boot partition and then do the grub update.
Thanks again for the clarification.
Cheers!

[ct85711]

You do need /boot mounted before you attempt to run the "make install", and the "grub2-mkconfig" commands. As while, you would still see a /boot directory even if you don't mount it, there wouldn't be anything in /boot (since it's stored in a different partition) till that partition is mounted.

[Tefrem34]

Thanks again for the tip!

You do need /boot mounted before you attempt to run the "make install"

I would have blundered that as well.

[Hu]

You may find it useful to change the permission on the underlying mountpoint to 0, so that if the filesystem is not mounted there, the permissions are obviously wrong. For example:

Code: Select all

umount /boot
chmod 0 /boot
ls -ld /boot
mount /boot
ls -ld /boot

[Tefrem34]

Code: Select all

/etc/init.d/autofs start
 * Starting automounter ...
/usr/sbin/automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required.
 * start-stop-daemon: failed to start `/usr/sbin/automount'                                                                           [ !! ]
 * ERROR: autofs failed to start

I didn't post this message after running

Code: Select all

make install

depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Ignoring.

I got this error now. So do I need to edit something else in that kernel selection?

@Hu, thanks for the info.
I am unsure what you are telling me. Should I run these commands before I try to update the kernel, or just in general for my system permitions?
I am going to run it just the same, I just would like to understand it.
I just ran it and I think I get what it did, but I still would like clarification.
Thanks.

[Hu]

On the root filesystem, you have a directory named boot. It should contain no files. When you mount your boot filesystem, it becomes accessible at /boot and the corresponding directory on the root filesystem becomes hidden. By setting the mode on the root filesystem's boot directory to 0, you make it obvious when the boot filesystem is not mounted.

[Tefrem34]

Thank you for the clarification.

[Tefrem34]

This is the version of autofs that I have installed

5.0.7-r4(05:34:35 PM 09/27/2014)(ldap -dmalloc -hesiod -libtirpc -mount-locking -sasl)

When I ran

Code: Select all

eix autofs

it is the lowest version.
So I take it that

test mount forbidden

is the culprate. But I still can not find out how to fix permitions for writing to my home directory.


I found this line from http://www.linuxquestions.org/questions ... -a-849965/ and the last comment was

One of the reason for this error can be, /tmp directory is not present or it's permission/ownership is wrong.

That's fine and all but I have not idea what I need to do in order to try this. Could someone give me a tip?

[Tefrem34]

I don't think that I mentioned that my /var and /home are on a different hard drive than my root. Could this be why I do not have permissions set for my home and user account, and why I can't write to my home folder or download anything?

Here is my /etc/fstab file

Code: Select all

# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda3               /boot           ext2            noauto,noatime           0 2
/dev/sda5               /               ext4            defaults,noatime,discard 0 1
/dev/sdc5               /var            ext4            defaults,noatime         0 0
/dev/sdc6               /home           ext4            defaults,noatime         0 0
#/dev/SWAP              none            swap            sw              0 0
/dev/sr0                /mnt/cdrom      auto            noauto,ro                0 0

would this affect mounting?

Something else that I found weird was some of my music folders on my storage HD are unaccessable. There is a strange character in the title and when I try to open it I get this error

The file or folder /run/media/rbear/Storage/Music/Rhapsody of Fire - Discograf�a does not exist.

[Hu]

This thread is getting confusing. From the OP, we now have an automounter problem (but no indication why an automounter is being used), some ambiguous write access problems, and a weirdly named CD rip.

OP: please pick one problem, explain in detail why it is a problem, what its symptoms are, and what you have tried to fix it. I suggest starting with the write access problems, since those seem to be the most serious. Tell us which directories you are unable to write, what user you used to try it, how the write fails, and why you think writing should work there.

[Tefrem34]

Well I figured out how to fix the permissions and download now.
I had to go

Code: Select all

kdesu dolphin

and change the permissions for the

Code: Select all

/usr/www

folder and did the same for my user home directory.

However,

Code: Select all

/etc/init.d/autofs start 

still gives me the same error. I even started x in root and tried it; same story.
So the search is still on.

[Tefrem34]

@Hu, sorry for the lack of cohesive dialog. I also didn't see your post until after I made the last one.

weirdly named CD rip

I don't know where this came from?

At first, there was a multitude of problems that effected each other which I thought was all one issue. For one, I couldn't write to any of my home directory, no downloading or creating folders with out being root (or starting x as root). I assumed that the drives were not mounting, thus not allowing me to write to any of my files. The reason I thought this, was because I could not properly setup Autofs, which I still cannot. Furthermore, I could not find an answer to why I couldn't download anything from the internet or create a new folder as a regular user. So I was going back and forth because I didn't know what was causing the problems.
Now that I was able to find a solution to the user file permissions, I am still stinted by the autofs and some files in media drive not being accessible (even as root). I have a dedicated storage drive that I use to hold my media and current projects that I need to be auto mounted so that I can work seamlessly with my applications and multiple OS's. The issue that I am having, besides having to put in my password to access it, is that certain files give me an error saying that there is no access, or no such folder,

The file or folder /run/media/rbear/Storage/Music/Rhapsody of Fire - Discograf�a does not exist.

when I know that it exists and has files in it. It is not all the folders but just a few. With all the distros that I have used, I have never experienced this issue before.
Ultimately, I did not know what all I needed to ask for in order to fix the issues of Autofs and strange file errors on a, ntfs formatted, media hard drive. I was just throwing stuff out there in hope that someone might have an idea what might be the culprit.
I hope that made sense.
Thanks again.

[Tefrem34]

Okay this officially sucks!

I have been trying to make a backup of my xorg configuration file and save it to my backup drives, external and internal, and I can not copy it to either. I even tried to do it as root. I have no permission to write to any other drive except my root and home folders. This is really frustrating.
I still can't find an article that offers a solution to this. So if someone can point me in the right direction, I would greatly appreciate it.

Thanks

[Tefrem34]

Finally, I found a solution to not having any read and write permissions for my Storage device.

First, I installed nftfs-3g along with fuse. I added fuse to my "rc-update default," I do not know whether or not it helped, and then proceeded to add this line to my /etc/fstab file

Code: Select all

# My Storage mount point
/dev/sde1               /media/Storage  ntfs-3g         defaults,noatime        0 0

I made sure that the device was unmounted and ran

Code: Select all

sudo mount -a

Then, I checked the files and all the folders in my Storage device, which now, no longer has the folder errors and I can write and save to those folders again. I haven't rebooted yet to make sure that it will mount on boot, but if it doesn't then I have some more reading/tweaking to do.
This video and articles were instrumental in solving the write permissions
use ntfs-3g and permissions http://askubuntu.com/questions/90339/ho ... ard-drives and http://www.linuxquestions.org/questions ... me-658388/
edit fstab for automounting https://www.youtube.com/watch?v=BhktLDhK5p8

I still get an error with the autofs, but since I have my device back it doesn't matter to me (until I run into another problem with mounting).

Thanks again for the help.