I've got a machine that dual boots Slackware and Windows 10 so I can show the steps on this machine.
First you need to identify which device and partition is used by Windows. You can use 'lsblk --fs' for this, e.g:
Code:
# lsblk --fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
|-sda1
`-sda2 ntfs Data 202662B626628D1A
sdb
|-sdb1 vfat FAT32 A109-5E2F 473.2M 5% /boot/efi
|-sdb2 swap 1 7ede5871-5e34-41ec-bcdc-d51102a89820 [SWAP]
`-sdb3 ext4 1.0 693d27b0-7c59-4291-a478-2a6f5d0c7a85 32.6G 79% /
sdc
`-sdc1 ext4 1.0 b7c779dc-f300-485d-8478-26d936a5a0cf 659.8G 23% /mnt/storage
nvme0n1
|-nvme0n1p1 vfat FAT32 SYSTEM A25D-26C4
|-nvme0n1p2
|-nvme0n1p3 ntfs Windows 9E6C5FE26C5FB42D
`-nvme0n1p4 ntfs WinRE_DRV 2AA4602FA45FFBA7
Note that I have 4 disks total. Two are for windows (sda is just data, nvme0n1 holds the windows 10 installation), the other two are my slackware disks. The windows partition is /dev/nvme0n1p3. You will have to do something similar and identify which disk and partition your windows installation resides on since your setup will be different.
Next we need a mount point. You can pick whatever point you want. I'm going to use '/mnt/windows', e.g:
Code:
# mkdir /mnt/windows
Now you need an fstab entry to mount this partition automatically at boot. This is what that install script sets up for you, but it's not hard to figure out if you read 'man fstab' and 'man mount'. I came up with the following line in my '/etc/fstab':
Code:
/dev/nvme0n1p3 /mnt/windows ntfs auto,umask=022 0 0
Read 'man fstab' for the details on what each field is used for above, but the gist of it is I'm mounting /dev/nvme0n1p3 at my /mnt/windows mount point. That partition has a filesystem type of ntfs, and I'm using 'auto' so it mounts automatically at boot time, and umask=022, which gives the root account full read/write access, and regular users read only access. I'm not planning on running fsck on this partition, so I left the last field at 0.
Note that in the setup script that Windu linked, the options are set as "fmask=133,dmask=022", etc. While this works as well from my testing, 'man mount' only talks about using umask for mounting ntfs types, and fmask/dmask for fat types. You can try those if you want, or just copy the value from dmask to set your umask.
Side note: It'll be better/more consistent to use a filesystem label or uuid for mounting, instead of the device node, since that can change if you alter the disk setup in the machine. I'm keeping this example simple and just used the device node.
Other note: This change takes effect at next reboot, or run 'mount -a' to mount all 'auto' flagged filesystems from fstab on an already running system (auto is the default, so its technically not necessary, but I use a mix of 'auto' and 'noauto' in my fstab anyways to keep track of things).
HTH
Edit:
The post as I have written above defaults to using the ntfs-3g fuse driver for mounting the ntfs partition from windows.
If you wanted to use the ntfs3 kernel driver instead (in kernels 5.15.x and up), then you can use a line like so in '/etc/fstab':
Code:
/dev/nvme0n1p3 /mnt/windows ntfs3 auto,force,umask=022 0 0
Note: I had to add 'force' as an option, else I got errors about "bad superblock" or "missing codepage". Apparently this is because that filesystem is marked dirty and the ntfs3 driver will not mount unless forced. I should fix it but I only load windows once in a blue moon and have been skipping fixing the disk for a while now...
