{
    "content": [
        {
            "type": "text",
            "text": "# ntfsusermap(8) (man)\n\n**Summary:** ntfsusermap - NTFS Building a User Mapping File\n\n**Synopsis:** ntfsusermap windows-system-device [other-ntfs-device...]\nWhere windows-system-device is the device containing the Windows system whose users are to be\nmapped to current Linux system.\nAnd other-ntfs-device is another device containing files which are to be accessed both by the\nWindows mentioned above and current Linux system.\nthe  ntfsusermap  command  must  be  started  as root, and the designated devices must not be\nmounted.\nTyping ntfsusermap with no args will display a summary of command arguments.\n\n## Examples\n\n- `Map the users defined on the Windows system present on /dev/sda1 :`\n- `ntfsusermap /dev/sda1`\n\n## See Also\n\n- ntfsprogs(8)\n- attr(5)\n- getfattr(1)\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (13 lines)\n- **DESCRIPTION** (23 lines)\n- **OPTIONS** (2 lines)\n- **EXAMPLES** (5 lines)\n- **EXIT CODES** (3 lines)\n- **KNOWN ISSUES** (8 lines)\n- **AUTHORS** (2 lines)\n- **THANKS** (5 lines)\n- **SEE ALSO** (5 lines)\n\n## Full Content\n\n### NAME\n\nntfsusermap - NTFS Building a User Mapping File\n\n### SYNOPSIS\n\nntfsusermap windows-system-device [other-ntfs-device...]\n\nWhere windows-system-device is the device containing the Windows system whose users are to be\nmapped to current Linux system.\n\nAnd other-ntfs-device is another device containing files which are to be accessed both by the\nWindows mentioned above and current Linux system.\n\nthe  ntfsusermap  command  must  be  started  as root, and the designated devices must not be\nmounted.\n\nTyping ntfsusermap with no args will display a summary of command arguments.\n\n### DESCRIPTION\n\nntfsusermap creates the file defining the mapping of Windows accounts  to  Linux  logins  for\nusers who owns files which should be visible from both Windows and Linux.\n\nIt relies on existing files which were created on Windows, trying to locate significant files\nand asking which Linux user or group should own them. When a Linux  owner  or  group  is  re‐\nquested, the reply may be :\n\n- the uid or gid (numeric or symbolic) of Linux owner or group of the file.\nIn that situation, no more file with the same Windows owner will be selected.\n- or no answer, when not able to define the owner or group.\nIn that situation another file owned by the same Windows user or group may be selected\nlater so that a mapping can be defined.\n\nThe mappings for standard Windows users, such as \"Administrator\" or \"All Users\"  are  defined\nimplicitly. As a consequence a user mapping should never be defined as Linux root.\n\nWhen  there  are no more significant files, ntfsusermap create the mapping file into the file\nUserMapping in the current directory. This file has to  be  moved  to  the  hidden  directory\n.NTFS-3G  in  the  root  of all the NTFS file systems to be shared between Windows and Linux.\nThis requires the file system to be mounted, but the created file will not be taken into  ac‐\ncount  if  not  present  at  mount  time, which means the file system has to be unmounted and\nmounted again for the new mapping file to be taken into account.\n\n### OPTIONS\n\nNo option is defined for ntfsusermap.\n\n### EXAMPLES\n\nMap the users defined on the Windows system present on /dev/sda1 :\n\nntfsusermap /dev/sda1\n\n### EXIT CODES\n\nntfsusermap exits with a value of 0 when no error was detected, and with a value of 1 when an\nerror was detected.\n\n### KNOWN ISSUES\n\nPlease see\n\nhttps://github.com/tuxera/ntfs-3g/wiki/NTFS-3G-FAQ/\n\nfor  common questions and known issues.  If you would find a new one in the latest release of\nthe software then please send an email describing it in detail. You can contact the  develop‐\nment team on the ntfs-3g-devel@lists.sf.net address.\n\n### AUTHORS\n\nntfs-3g.secaudit has been developed by Jean-Pierre André.\n\n### THANKS\n\nSeveral  people made heroic efforts, often over five or more years which resulted the ntfs-3g\ndriver. Most importantly they are Anton Altaparmakov, Richard  Russon,  Szabolcs  Szakacsits,\nYura  Pakhuchiy,  Yuval Fledel, and the author of the groundbreaking FUSE filesystem develop‐\nment framework, Miklos Szeredi.\n\n### SEE ALSO\n\nntfsprogs(8), attr(5), getfattr(1)\n\n\n\nntfsusermap 1.2.0                           February 2016                             NTFSUSERMAP(8)\n\n"
        }
    ],
    "structuredContent": {
        "command": "ntfsusermap",
        "section": "8",
        "mode": "man",
        "summary": "ntfsusermap - NTFS Building a User Mapping File",
        "synopsis": "ntfsusermap windows-system-device [other-ntfs-device...]\nWhere windows-system-device is the device containing the Windows system whose users are to be\nmapped to current Linux system.\nAnd other-ntfs-device is another device containing files which are to be accessed both by the\nWindows mentioned above and current Linux system.\nthe  ntfsusermap  command  must  be  started  as root, and the designated devices must not be\nmounted.\nTyping ntfsusermap with no args will display a summary of command arguments.",
        "flags": [],
        "examples": [
            "Map the users defined on the Windows system present on /dev/sda1 :",
            "ntfsusermap /dev/sda1"
        ],
        "see_also": [
            {
                "name": "ntfsprogs",
                "section": "8",
                "url": "https://www.chedong.com/phpMan.php/man/ntfsprogs/8/json"
            },
            {
                "name": "attr",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/attr/5/json"
            },
            {
                "name": "getfattr",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/getfattr/1/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 13,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 23,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "EXAMPLES",
                "lines": 5,
                "subsections": []
            },
            {
                "name": "EXIT CODES",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "KNOWN ISSUES",
                "lines": 8,
                "subsections": []
            },
            {
                "name": "AUTHORS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "THANKS",
                "lines": 5,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 5,
                "subsections": []
            }
        ]
    }
}