|(20 intermediate revisions by 8 users not shown)|
|−|Anyone else having problems accessing punkrockguy's repository? |+|
| || |
|−|== Default behaviour of mount == |+|
| || |
|−|The page used to claim that `mount` uses `ntfsmount` from the ntfsprogs package when ntfs-3g is not explicitly stated. This appears to be incorrect (probably outdated), as the ntfs-3g package includes a symlink, /sbin/mount.ntfs, which is used by `mount` on default and points to /bin/ntfs-3g. Correct me if i'm wrong. |+|
that to be to .
| || |
Nope, not gonna correct you, TaylanUB. Just tested an you're right. By default (in Arch) it uses ntfs-3g now. So this is good news. I think the install cd might still but for regular installs, we're good. Thanks for the updated information. Fixing. |+|
| || |
'Edit:'' Oop or not fixing. Thanks for doing TaylanUB. |+|
:'not . .
| || |
--[[User: Gen2ly| Gen2ly]] 18: 58, 9 April 2010 ( EDT) |+|
: [[User:|]]: , ()
| || |
|−|== Unmask option == |+|
:is on the for .
|−|umask: umask is a built-in shell command which automatically sets file permissions on newly created files. For Arch the default umask for root and user is 0022. With 0022 new folders have the directory permissions of 755 and new files have permissions of 644. You can read more about umask permissions here. | |
| || |
|−|unmask with 0022 is only for root, that means as user you can't create or delete something. The right option for user is 0002. |+|
| || |
|−|== /etc/fstab and the type parameter == |+|
| || |
|−|Using my home server and its ntfs partition I discovered an issue in the wiki, that you can confirm or not. |+|
I the , .
|−|If in /etc/fstab I identify the ntfs partition with the 'ntfs- 3g' parameter, like in the wiki, the partition is inaccessible and unmounted. The fstab isn't completely processed. |+|
|−|But if I identify that with the 'ntfs' parameter it works perfectly as expected. |+|
I with -in the , the and .
The 't .
I added instructions to add users to the
disk group when using ntfs-3g-fuseAUR. This was necessary to get access to usb sticks, in general acces to block devices
/dev/sd[a-z][1-9, as those are in the disk groups.
Is this good practice, or is there another way to achieve this?
I ask, because Users and groups#Pre-systemd groups lists
disk as a group that usually doesn't require users to be added to manually because
systemd takes care of it.
—This unsigned comment is by David the goliath (talk) 08:53, 28 May 2017. Please sign your posts with ~~~~!
- No, it's not a good practice (and never has been) to add normal users to the
disk group. If you do this, they have full access to anything stored on any of your disks, including files normally accessible only by root. If you want normal users to be able to mount removable devices, use udisks or some helper - these are safe tools that run with root privileges, either as daemons or with suid. -- Lahwaacz (talk) 12:12, 28 May 2017 (UTC)
- Lahwaacz: Could you please provide some reliable source of information about what are the best practices to allow normal user to be able to mount removable devices? I'm really interested on this, but I'm unable to understand Polkit/Udisks stuff. Excuse me for my lack of intelligence and use Archlinux instead something like Linux Mint or Ubuntu (I don't like them, I'm a difficult person) :( Timofonic (talk) 14:51, 21 July 2017 (UTC)
- Have you read the udisks article? udisks#Mount helpers looks like it will do what you want. What specific step is tripping you up? Try it out and post any issues you have on the forum, the wiki talk pages are mainly for discussing issues with wiki content. Silverhammermba (talk) 21:52, 21 July 2017 (UTC)
I had really bad experiences resizing partitions under gparted, it broke a Windows 10 system and had to reinstall it. I needed to resize partitions again and was finding desesperately a trustworthy tool.
After reading tons of reviews, I found Easeus Partition Master. Despite the process was quite slow, it got done perfectly.
I did read about Paragon utilities, but I don't trust them because what happened with PTS-DOS (Paragon was founded in Germany by former developers of the PhysTechSoft Russian company, they copied the source code without permission and developed their own fork) plus other bad stuff people say about their products.
Anyone had experienced with resizing partitions of Windows 10 or other versions can tell about the reliability og using GParted? I'm not sure, maybe parted/GParted got patched these days. Timofonic (talk) 14:51, 21 July 2017 (UTC)
NTFS full(?) permissions
The Linux compatible permissions section doesn't mention that the permissions are static;
chmod does not actually work on it.
According to JanC(/edited by pizzapants184) on askubuntu, the
permissions option can add more.. This might be needed to put (parts) of installations on the harddisk..(like systemd-nspawn stuff or are some of the directories in the linux tree data-heavy,access-infrequent?) That said "defaulty" any windows using that partition might be a security risk. (ugh my security sucks already, really) Jasper1984 (talk) 14:46, 20 January 2018 (UTC)