Page MenuHomeFreeBSD

[handbook]: Document how to mount NTFS disks
ClosedPublic

Authored by fernape on Jan 13 2021, 10:57 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, May 13, 3:28 PM
Unknown Object (File)
Fri, May 10, 2:35 PM
Unknown Object (File)
Wed, May 8, 9:32 AM
Unknown Object (File)
Apr 12 2024, 3:00 AM
Unknown Object (File)
Apr 12 2024, 12:50 AM
Unknown Object (File)
Apr 11 2024, 3:51 PM
Unknown Object (File)
Apr 7 2024, 3:55 PM
Unknown Object (File)
Mar 11 2024, 6:45 PM

Details

Summary

Comes from PR 251109

How to mount NTFS disks is a FAQ in our chats and forums.

Add a section in handbook/disks under 18. Storage with straightforward
information on how to mount NTFS disks.

Test Plan
  • igor clean
  • aspell happy
  • Handbook renders nicely

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

fernape created this revision.

Here's a few nits I noticed.
Otherwise, it looks good to me.

en_US.ISO8859-1/books/handbook/disks/chapter.xml
1575 ↗(On Diff #82201)
1585 ↗(On Diff #82201)
1590–1593 ↗(On Diff #82201)

Would it be better to recommend using kld_list in rc.conf?
Loading many modules (or a few big ones like nvidia and zfs) via loader on UEFI systems might cause fragmentation which can lead to the system not booting), and NTFS isn't really useful as a root filesystem on FreeBSD.

1611 ↗(On Diff #82201)

It's a bad idea to mount things in the user home directory, and /mnt already exists in hier(7).

1627 ↗(On Diff #82201)

If you change the mount-point above, remember to fix this one too. ;)

pauamma_gundo.com added inline comments.
en_US.ISO8859-1/books/handbook/disks/chapter.xml
1585 ↗(On Diff #82201)

Isn't "fuse" an acronym? In that case, shouldn't it be "FUSE" with appropriate markup? (Cf. 9.6.2 in https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/docbook-markup-inline-elements.html.)

1585 ↗(On Diff #82201)

I'd go one step further and just make it "Before using".

1635 ↗(On Diff #82201)

And this one too.

  • Address feedback from review.
fernape added inline comments.
en_US.ISO8859-1/books/handbook/disks/chapter.xml
1585 ↗(On Diff #82201)

Thanks, it reads betteer

1585 ↗(On Diff #82201)

Yes. Distinguish between FUSE and fusefs(5)

1590–1593 ↗(On Diff #82201)

Thanks a lot! I wasn't aware of that problems rc.conf(5) even says it is usually faster load modules with kld_list than in the loader.

  1. Shouldn't Microsoft be stylized as &microsoft;?
  2. We may consider adding a line suitable for fstab(5). I think that many people think that FUSE-based filesystems do not work well with fstab, which is not true. That could also be another commit.
  3. Great work!
en_US.ISO8859-1/books/handbook/disks/chapter.xml
1598 ↗(On Diff #82210)

Hmmm, I wonder if we should remove the ports installation instructions and just link to the ports chapter in the handbook. I'd advocate for this approach to reduce the duplication of documentation. Also, an inexperienced user may accidentally use ports instead of packages here which may cause some unnecessary complications.

What do you think?

1611 ↗(On Diff #82201)

I'm not opposed to the change, I'm just curious: why is mounting in /home a bad idea?

fernape marked 3 inline comments as done.

Address feedback by 0mp

  • Use &microsoft;
  • Add line for fstab(5)
  • Add references to pkg and ports sections and keep the pkg example.
fernape added inline comments.
en_US.ISO8859-1/books/handbook/disks/chapter.xml
1598 ↗(On Diff #82210)

I think referencing the pkg and ports section is pretty useful. I would keep the pkg example since it is pretty straightforward (it does not involve any curses screen asking to set options or anything). As a user I would not like to jump to a different section just to install a single package :-)

fernape marked an inline comment as done.

Asciidoc version of the same patch.

documentation/content/en/books/handbook/disks/_index.adoc
1036

Should we enourage users to use sysrc kld_list+=fusefs instead?

1091

Missing prompt character #.

  • Address changes suggested by 0mp:
fernape added inline comments.
documentation/content/en/books/handbook/disks/_index.adoc
1036

I like it, but truth to be told, I always forget about the existence of this utility :S

1091

Thanks!

Looks great!

I don't know much about the new style guide for the doc tree, I have to catch up a bit.

documentation/content/en/books/handbook/disks/_index.adoc
1062

Just to make sure, is it supposed to be not aligned like that?

This revision is now accepted and ready to land.Feb 7 2021, 12:09 AM
fernape added inline comments.
documentation/content/en/books/handbook/disks/_index.adoc
1062

This is what I see in git log -c when executed in my feature branch:

+[source,bash]
+....
+# gpart show da0
+=>       63  1953525105  da0 MBR   (932G)
+         63  1953525105    1 ntfs  (932G)
+....
+

However, as I type this in the text box in phabricator, the copy-pasted text looks unaligned.
vim shows everything aligned and the generated page has the data aligned too (63 below 63, etc).

Thanks for reviewing this!

Cheers! :)