NTFSUSERMAP(8)

✨ NAME ✨

Okay bestie, this is the NTFSUSERMAP(8) page, and it's all about ntfsusermap 💖. It's the NTFS building a user mapping file tool. Basically, it's how Windows accounts get matched up with Linux logins 🫶.

🎀 SYNOPSIS 🎀

ntfsusermap windows-system-device [other-ntfs-device...]

windows-system-device is the device holding the Windows system whose users you want to map over to your current Linux system 💻.

other-ntfs-device is any other device with files that both that Windows install and your current Linux system need to access 📂.

Some ground rules, no cap 🚨: you have to run ntfsusermap as root 👑, and the devices you pass in must not be mounted 🙅‍♀️.

Type ntfsusermap with no args and it'll show you a quick summary of the command arguments 🧚.

🦋 DESCRIPTION 🦋

ntfsusermap creates the file that maps Windows accounts to Linux logins, for the users who own files that should be visible from both Windows and Linux 🌸.

It's lowkey detective work 🕵️‍♀️. It digs through existing files that were made on Windows, tries to find the important ones, and then asks which Linux user or group should own them. When it asks for a Linux owner or group, your reply can be:

• the uid or gid (numeric or symbolic) of the Linux owner or group of the file.
  • Once you say that, it won't pick any more files with that same Windows owner. Slay, one and done ✨.
• or no answer, if you can't work out the owner or group 🤷‍♀️.
  • Then another file owned by that same Windows user or group might get picked later, so a mapping can still happen 🔄.

Standard Windows users like "Administrator" or "All Users" get their mappings defined implicitly, so you never have to do those yourself 💅. Also, a user mapping should never be defined as Linux root. Do not do this, it's a whole vibe disaster 💀.

When there are no more important files left, ntfsusermap writes the mapping file into UserMapping in the current directory 📝. Next, that file has to be moved into the hidden .NTFS-3G directory at the root of every NTFS file system you want to share between Windows and Linux 🗂️. Moving it needs the file system to be mounted. Heads up though: the new file won't be used if it isn't there at mount time 😭. So the file system has to be unmounted and then mounted again for the new mapping to take effect 🔁.

🌈 OPTIONS 🌈

No option is defined for ntfsusermap. Just the arguments, bestie 🫠.

💜 EXAMPLES 💜

Want to map the users from the Windows system on /dev/sda1? Easy peasy 🍓:

ntfsusermap /dev/sda1

🍑 EXIT CODES 🍑

ntfsusermap exits with 0 when no error is detected ✅. If it does detect an error, it exits with 1 ❌.

⚠️ KNOWN ISSUES ⚠️

For common questions and known issues, check out the FAQ at:

https://github.com/tuxera/ntfs-3g/wiki/NTFS-3G-FAQ/

If you find a brand new issue in the latest release, please email the development team with a detailed description 📧. Their address is ntfs-3g-devel@lists.sf.net 💌.

👩‍💻 AUTHORS 👩‍💻

ntfs-3g.secaudit has been developed by Jean-Pierre André 🫡.

🙌 THANKS 🙌

Several people put in heroic effort, often over five or more years, to make the ntfs-3g driver happen 😭🫶. The biggest shout-outs go to Anton Altaparmakov, Richard Russon, Szabolcs Szakacsits, Yura Pakhuchiy, Yuval Fledel, and Miklos Szeredi, the author of the groundbreaking FUSE filesystem development framework 👑.

🧚 SEE ALSO 🧚

ntfsprogs(8), attr(5), getfattr(1) 💫

Bestie, that's the whole tea 🫖💖. This page was ntfsusermap 1.2.0, dated February 2016, from the NTFSUSERMAP(8) crew 🌸✨.