| 22 Mar 2024 |
 K900 | (which is basically a network share that's run by the VM) | 17:33:00 |
 greg | My WSL2 filesystems are accessible alongside my normal filesystem roots | 17:33:13 |
| K900 | In reply to @greg:thehellings.com
My WSL2 filesystems are accessible alongside my normal filesystem roots The "Linux" icon in Explorer goes to the same path | 17:33:37 |
| K900 | It's just not there in older Windows versions | 17:33:46 |
| K900 | So the UNC path is more consistent | 17:33:49 |
 Peeps | No I used WSL2 with Ubuntu. Sorry im not sure if I explained myself correctly. Like when I run my Ubuntu, i see "peepo@mypc:~$", but when i run the NixOs, it changes a bit but it shows my windows filesystem and the files of the folder where I entered NixOs. | 17:35:28 |
| K900 | Oh, that's just the current directory | 17:35:43 |
| K900 | I think Ubuntu might reset it by default? | 17:35:51 |
| K900 | We don't | 17:35:53 |
| K900 | You can cd ~ to get to your home directory | 17:35:59 |
| K900 | Or cd / to get to the Linux filesytem root | 17:36:07 |
| K900 | * Or cd / to get to the Linux filesystem root | 17:36:09 |
| K900 | Your Windows drives are accessible under /mnt/<drive letter> by default | 17:36:22 |
| Peeps | Oh there we go. Thats what I needed. Didnt even think to try that. Thats interesting. So is it all under one umbrella? To be fair I never tried to access windows from ubuntu. | 17:37:22 |
| Peeps | In reply to @k900:0upti.me
Your Windows drives are accessible under /mnt/<drive letter> by default Actually thats similar to where I was landing, its starting to make sense now lol | 17:37:47 |
| K900 | It's a bit complicated | 17:37:42 |
| K900 | The Linux side sees the Windows drives as network filesystems that are automounted to /mnt | 17:38:08 |
| Peeps | I see. Well thanks for the help :) | 17:38:35 |
| K900 | The Windows side sees the Linux side as a network filesystem that's not mounted anywhere but can be seen through a UNC path | 17:38:32 |
| K900 | So they both see each other | 17:38:46 |
| K900 | But in different ways and in different parts of the hierarchy | 17:39:07 |
| 23 Mar 2024 |
| Peeps | Im trying to get pulseaudio working but: W: [pulseaudio] pid.c: Failed to open PID file '/run/user/1000/pulse/pid': Too many levels of symbolic links
Its making me sad. | 00:02:03 |
| Peeps | Not sure if this formatting will work but here we go:
[nix-shell:~]$ ls -l /run/user/1000/pulse | grep pid
lrwxrwxrwx 1 root root 31 Mar 22 22:27 pid -> /mnt/wslg/runtime-dir/pulse/pid
Based on my research, this thing is pointing to itself, which is a nono. I can remove it with rm pid, i suppose, but wouldnt that just lead to another issue?
| 00:16:37 |
| Peeps | Redacted or Malformed Event | 00:26:29 |
|  @federicodschonborn:matrix.org joined the room. | 00:36:59 |
| Peeps | * Not sure if this formatting will work but here we go:
[nix-shell:~]$ ls -l /run/user/1000/pulse | grep pid
lrwxrwxrwx 1 root root 31 Mar 22 22:27 pid -> /mnt/wslg/runtime-dir/pulse/pid
| 02:02:15 |
| Peeps | Okay this is awkward but i got audio working, lol. I wish I knew why its working now. | 02:08:15 |
|  SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (hash-versioned python modules when) to SomeoneSerge (migrating synapse). | 02:11:37 |
| K900 | In reply to @peepojuice:matrix.org
Im trying to get pulseaudio working but: W: [pulseaudio] pid.c: Failed to open PID file '/run/user/1000/pulse/pid': Too many levels of symbolic links
Its making me sad. You should not need Pulseaudio on WSL | 04:59:55 |
| K900 | WSLg provides its own sound server | 05:00:01 |
