Automatic Drive Letter Selection in Windows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.16-20160622134333+f8bd1e6
Windows 7 64-bit, keybase client on installation chose a drive letter already assigned to another physical hard drive, rendering the KBFS mapping invisible and unusable. As the client is so new, my particular issue was difficult to pin down as an issue at all as I was unaware of how it was supposed to correctly function.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Windows client installation path that selects the drive letter for the KBFS mapping. Reproduce the reported conflict with a drive letter already assigned to a physical disk, then verify that installation selects an available letter and leaves the KBFS mapping usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100