ArchLinux Boot Mount partition

The whim of the installation of the ArchLinux. Found a lot of content and Ubuntu are very different.

At least for the time being, I have no good impression of it except for the speed. It's too much of a dad. There are traps everywhere.

On the other hand, when it comes to archlinux loading, it is a history of blood and tears. A whole two genius. Get a line of code.

First of all, tell me about my scene:

My three systems share two NTFS partitions. Windows does not have to say it. Ubuntu I wrote the Mount command into rc.local (sudo mount-o gid=1000,uid=1000/dev/sda5/media/alai/work). Can be perfect to have read and write permissions, and the owner is my normal user, not root.

But now the problem is, ArchLinux is not the way to start booting. I did not find such an exact script. I tried to write the Mount script myself and put it in the/etc/xdg/autostart directory. But the script doesn't write well, There is a problem loading. I want to go. decided to return to the system file and finally selected the/etc/fstab.

About Fstab file formats I'm not going to say much. I don't know much about it. There are a lot of blogs on the internet. I just said that someone else missed it.

Many people may not have noticed that the owner of the attached directory is rooted in the web-based tutorials or manual. Of course, some people say that you can add RW to make all users read and write. This is not impossible. I met a not very optimistic scene, downloaded a total of files later executed, But even root prompts insufficient permissions. It's really embarrassing.

Read the online about the Fstab file in the fourth field of the description, vaguely think he is mount-o behind the parameters. Take this point as a starting point. Try again.

/dev/sda1/media/alai/system ntfs-3guser,rw,suid,exec,gid=alai,uid=alai0 2/dev/sda5/media/alai/work NTFS-3GUSER,RW , Suid,exec,gid=alai,uid=alai0 2/dev/sda6/media/alai/others ntfs-3guser,rw,suid,exec,gid=alai,uid=alai0 2

The above piece of code perfectly solves my problem.

Now let's verify the hypothesis above. Put the parameters of the fourth paragraph above into the back of a mount command to use:

At the very beginning I looked at the man fstab. There are few explanations. When I had the assumptions above, I looked at the man mount.

Can see, the first sentence said. My conclusions are biased. Mount options and Fstab are interoperable, but some options can only be used in fstab.

Another question to explain is that it may be noted that my mount's file format is ntfs-3g. This problem has also been found on the internet for a long time. If you are using mount in a archlinux system, if you want to mount the partition in this format with writable permissions, There will be problems. Because this format does not support writing. The error is as follows:

LogFile is isn't clean, mounting read-only, mount in Windows.

It's strange that I don't have this problem under Ubuntu. Whatever he is.

This problem is also good to solve, with ntfs-3g instead of NTFS format. You just need to install one tool.

[[email protected] alai]# sudo pacman-ss ntfs-3gextra/ntfs-3g 2015.3.14-1 [installed]    NTFS filesystem driver and Util Ities[[email protected] alai]# sudo pacman-s ntfs-3g   # Execute this command on the line, above the-SS is to see if there is a package.

OK, the problem is solved.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

ArchLinux Boot Mount partition