Document Details
Dual Protocol Permission Behaviors
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation demonstrates a subtle Windows bias by consistently mentioning Windows/SMB/NTFS concepts and tools before their UNIX/NFS equivalents, and by providing more detail and context for Windows-related behaviors. There is a lack of concrete Linux/NFS client command examples (e.g., no explicit Linux CLI commands for managing permissions), and Windows-specific tools and terminology (e.g., 'Windows security properties tab', 'Windows RPC calls', 'Active Directory') are referenced more frequently and in greater depth than their Linux counterparts.
Recommendations:
- Provide explicit Linux/NFS client command examples for managing permissions, such as using chmod, chown, and nfs4_setfacl, alongside or before Windows/SMB examples.
- Balance the explanation of permission management tools by including Linux GUI and CLI options (e.g., mention file managers or setfacl for NFSv4.x ACLs) where Windows tools (like the security properties tab) are referenced.
- When discussing name mapping and authentication, include more detail about how Linux/NFS clients interact with LDAP and other name services, not just Windows/Active Directory mechanisms.
- In tables and decision matrices, alternate the order of presentation (sometimes UNIX/NFS first, sometimes Windows/SMB) to avoid reinforcing a default Windows-first perspective.
- Add troubleshooting or usage scenarios from the perspective of Linux/NFS administrators, not just Windows/SMB admins.
Create pull request