Announcement

Collapse
No announcement yet.

Microsoft Releases A Big Update To Windows Subsystem For Linux, New Experimental Options

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Flaburgan
    replied
    WSL 2 is a joke, it cannot correctly access any NTFS drive. https://github.com/microsoft/WSL/issues/4197
    git status on a small repository hosted on the windows drive is taking seconds to answer. It is totally unusable, so I am stuck on WSL1.

    Leave a comment:


  • Vistaus
    replied
    Originally posted by sophisticles View Post
    I wonder how long before Microsoft releases a full, proper distro.

    I also wonder if they did, how long it would be before the Linux faithful would complain that it sucks.
    You mean like CBL-Mariner?

    Leave a comment:


  • elvis
    replied
    Originally posted by edxposed View Post


    [wsl2]
    networkingMode = bridged
    vmSwitch = Bridge

    Unrecorded, but is working. 22H2+ only
    You have to set up the bridge in advance though, and that doesn't work on a number of NICs (my Intel wireless card in my Dell laptop, for example).

    Same hardware supports bridging fine under VirtualBox on Windows, KVM/Qemu under Linux, etc. But bridging in Windows 11 itself (in general or for use with WSL2) fails.

    There are similar reports on TechNet and in GitHub issues. Microsoft's response is "Unsupported. Tough luck".
    Last edited by elvis; 19 September 2023, 09:40 AM.

    Leave a comment:


  • slalomsk8er
    replied
    Originally posted by RAINFIRE View Post

    Or you could just download the FIXED OpenSSH from GitHub linked in original post and not have to try all sorts of hacks to get the SSH Agent working in Windows 10, 11, Server, WSL or even by Windows Update. OS Version is borked. I'm not even sure a fixed OS SSH agent will even extend to the WSL? It's all just wrong on so many levels. Cygwin was better than this 15 to 20 years ago . . . again, just my opinion.
    Not sure, what's broken but the "hacks" are to get SSH inside of WSL talking to the agent running on Windows.

    Cygwin was nice at the time, installing Git is nicer but having a full Linux including the kernel makes a work windows notebook bearable.

    Leave a comment:


  • citral
    replied
    Originally posted by sophisticles View Post
    I wonder how long before Microsoft releases a full, proper distro.

    I also wonder if they did, how long it would be before the Linux faithful would complain that it sucks.
    Well it would obviously be closed source.
    And for having worked in the past with many closed-source unix variants (hp, aix, solaris) I can already tell you it will suck.

    Leave a comment:


  • RAINFIRE
    replied
    Originally posted by slalomsk8er View Post

    I use SSH keys in a password manager on windows (it's a managed work machine) and with socat and npiperelay, the SSH agent gets piped though to WSL2.

    from the my bashrc inside...
    Or you could just download the FIXED OpenSSH from GitHub linked in original post and not have to try all sorts of hacks to get the SSH Agent working in Windows 10, 11, Server, WSL or even by Windows Update. OS Version is borked. I'm not even sure a fixed OS SSH agent will even extend to the WSL? It's all just wrong on so many levels. Cygwin was better than this 15 to 20 years ago . . . again, just my opinion.

    Leave a comment:


  • slalomsk8er
    replied
    Originally posted by RAINFIRE View Post

    You don't understand having working public/private keys in SSH, even if it is a sub-system? It means WSL is not usable past the host system without typing passwords everywhere. This makes WSL non-usable on any serious system that has to talk to other computers.
    I use SSH keys in a password manager on windows (it's a managed work machine) and with socat and npiperelay, the SSH agent gets piped though to WSL2.

    from my bashrc inside of WLS:

    Code:
    export SSH_AUTH_SOCK=$HOME/.ssh/agent.sock
    
    ss -a | grep -q $SSH_AUTH_SOCK
    if [ $? -ne 0 ]; then
    rm -f $SSH_AUTH_SOCK
    (setsid socat UNIX-LISTEN:$SSH_AUTH_SOCK,fork EXEC:"$HOME/npiperelay/npiperelay.exe -ei -s //./pipe/openssh-ssh-agent",nofork &) >/dev/null 2>&1
    fi
    export SSH_AUTH_SOCK=$HOME/.ssh/agent.sock
    Looks a bit different but definitely a nicer write up then I could provide here: https://stuartleeks.com/posts/wsl-ssh-key-forward-to-windows/‚Äč
    Last edited by slalomsk8er; 20 September 2023, 03:11 AM.

    Leave a comment:


  • Karmux
    replied
    Some of my programmer colleagues were using WSL but soon started to realize that there is little point of Windows around WSL, all of extra hassle and overhead and started switching to Linux.

    Leave a comment:


  • mdedetrich
    replied
    Originally posted by jacob View Post

    They have had a full distro for quite a while now.
    Yup https://github.com/microsoft/CBL-Mariner

    Leave a comment:


  • jacob
    replied
    Originally posted by sophisticles View Post
    I wonder how long before Microsoft releases a full, proper distro.

    I also wonder if they did, how long it would be before the Linux faithful would complain that it sucks.
    They have had a full distro for quite a while now.

    Leave a comment:

Working...
X