Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

readlink(1) on UNC path reports raw WinNT device path instead of UNC path

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli, operating-systems

Research direction

Start by reproducing readlink.exe -f myfile_lnk with the UNC paths shown in the issue and trace the readlink path-resolution entry point. Compare the returned WinNT device path with the expected UNC path; done means the command preserves the share prefix and nfsdata component for the reported NFS and WebDAV cases.

Written by the indexing model from the issue text.

Description

C-bug

Current path (UNC path on OpenText NFS share, ms-nfs41-client or MS WebDAV share):
\\10.49.202.239@NFS@2049\nfsdata\wincoreutilstest

$ /cygdrive/c/Program\ Files/coreutils/bin/readlink.exe -f myfile_lnk
\\?\UNC\10.49.202.239@NFS@2049\wincoreutilstest\myfile

The expected output would be:
\\10.49.202.239@NFS@2049\nfsdata\wincoreutilstest\myfile

Dominant language
Rust
Stars
5.2k
Forks
107
Avg merge
2d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/coreutils

All issues in microsoft/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.