Talk:Gentoo in WSL

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

On changing the default user

Talk status
This discussion is still ongoing.

I edited the page yesterday to reflect that due to the way Gentoo is installed in WSL (imported through PowerShell instead of installed from the Windows Store, or whatever they're calling it today), /etc/wsl.conf doesn't work to set the default user when opening a WSL window. I added the instructions for editing the registry to do this. This morning, someone's added the old instructions back in, even though they don't work. I just got around to installing Gentoo under WSL on Win11 yesterday on the Framework Laptop I bought a couple of months ago; instructions nearly everywhere said to create /etc/wsl.conf. I did, and it made not a bit of difference: new windows still brought up a root prompt. I recalled having to tweak the registry on my other Windows installs and eventually found those instructions and brought them over here.

--Salfter (talk) 17:48, 24 February 2022 (UTC)

Don't worry, that's probably just the wiki way working in it's abrupt fashion (Gentoo_Wiki:Contributor's_guide). Perhaps the other user thinks that both methods work ?
I'm sorry I don't have the knowledge to say, or the installations to test this out. I wonder what TylerSzabo thinks ? (ping). Are their certain conditions that can have both ways work, like old versions or something ?
All the best -- Ris (talk) 18:04, 24 February 2022 (UTC)
Thanks, for pinging me, P.Fox (Ris) . Firstly, Salfter , I'm sorry if my edit came across as overly abrupt - I liked the method you documented, especially when used with generic exported tarballs. My goal was to include both options including the information lost from the previous edit. My expectation for deliberately removed information is to first annotate with {{Warning|This may not work for some users, see [[Talk:Gentoo_in_WSL]]}} template (or something similar) followed by a discussion of the issue you're hitting in the talk pages so it can be debugged and clarified without potential loss of useful information.
Setting the user in /etc/wsl.conf is described in the Microsoft Documentation for WSL Configuration which is why those directions are so common elsewhere. The changes in /etc/wsl.conf require the instance to be terminated with wsl -t <Distro> and may require a slight wait (this is also noted in the MS documentation). I just tested it on a Windows 11 (build 22000.493) system and Windows 10 (build 19044.1526) system with success. I use the /etc/wsl.conf method to set default user on multiple Distros on multiple machines reliably.
My current hypothesis is that the documentation is insufficient and a note to restart with wsl -t <Distro> should be added. I do think that the information should remain up for the benefit of users that aren't having that issue (with appropriate warnings until it's better understood after further debugging). I'm going to hold off on making such an edit to the main page just yet as I'd like to be on the same page in Talk, first; and I especially don't want anyone to feel like they're being railroaded in edits.
:) -- TylerSzabo (talk) 18:52, 24 February 2022 (UTC)
FWIW, /etc/wsl.conf works just fine for my attempt on my Windows 10 install with WSL installed from "Turn Windows features on or off" and Gentoo imported from the stage3 as listed. The registry was not changed. --Grknight (talk) 18:07, 24 February 2022 (UTC)
Editing /etc/wsl.conf and adding the default user seems to work just fine (without editing the registry). I think the Windows registry instructions should be edited to have "optional" or "users may need to" clauses, or removed completely. Majamin (talk) 17:44, 28 May 2023 (UTC)

Troubleshooting mount errors

Talk status
This discussion is still ongoing.

I find the solution to mount errors to use nomultilib a bit suspect as this should not change anything. I would like some evidence to back this claim up. I do not have access to a Windows 11 machine to test or I'd do it myself. --Grknight (talk) 19:07, 23 August 2022 (UTC)