Add additional hard link notice to FirstRunImportFromStable #36029
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's been confusion on whether lazer duplicates files and uses up double the disk space when importing files from stable to lazer.
While a notice does already exist serving this purpose, this only shows up once a path to a stable installation is selected AND validated. This clearly isn't enough as there's still people from today, 10 days ago, and much later asking if lazer duplicates disk space when importing from stable.
This PR adds an extra sentence to the description of the import page on the first run overlay, letting users know that hard links are used to effectively share files between stable and lazer when possible. This should give the user two notices that hard links can be utilized, hopefully putting more minds at ease.
Feel free to close if this is deemed unnecessary.