When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line. I'm curious why SLED is the only one available directly. Political? Tumbleweed is available via the store. Here's where it gets interesting: on a company managed Windows PC, they can control what you can get from the Store. In my company at least, Tumbleweed is not on the list. I bet this is the case for many corporate users. So they select a distro from those that are immediately available. For SUSE I guess it is good if an SLED is selected. I get that. But from a openSUSE perspective, the situation is less good. -- Roger Oberholtzer
On Fri, 2023-01-13 at 08:32 +0100, Roger Oberholtzer wrote:
When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line.
I'm curious why SLED is the only one available directly. Political?
Tumbleweed is available via the store. Here's where it gets interesting: on a company managed Windows PC, they can control what you can get from the Store. In my company at least, Tumbleweed is not on the list. I bet this is the case for many corporate users. So they select a distro from those that are immediately available. For SUSE I guess it is good if an SLED is selected. I get that. But from a openSUSE perspective, the situation is less good.
tl;dr - The Store and the `--web-download` (and/or what you see with `--online`) methods are controlled by 2 different entities [the Microsoft partner portal vs. DistributionInfo.json from github.com/microsoft/wsl) but have slight overlap depending on the configuration of the .json file for any given github WSL release. Things on the Microsoft side w/ WSL delivery are a bit in flux, but should even out in the next few months. The transition from <1.0.0 to >=1.0.0 has had growing pains, but should end up a win overall. I can get into it more if you'd like (or maybe this[1] will shed more light), but there's only so much we can control at the moment and we're working on it :) I'm not sure what you're referring to w/ the SLED part of your comments or how that relates to what you'd see here[2]. If you care to elaborate, maybe we can clear that up. SLED _is_ an option when registering as part of firstboot for SLE WSL distro(s), that's recently new - but there's no "You're getting SLED" item in the Store. Also, if you share more info around output from `wsl --list --online` and/or `wsl --status` and/or `wsl --version`, that would be useful too. [1]: https://github.com/microsoft/WSL/pull/9286 [2]: https://apps.microsoft.com/store/search/SUSE?filteredCategories=Developer%20... -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On Fri, Jan 13, 2023 at 6:41 PM Scott Bradnick <scott.bradnick@suse.com> wrote:
On Fri, 2023-01-13 at 08:32 +0100, Roger Oberholtzer wrote:
When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line.
I'm curious why SLED is the only one available directly. Political?
Tumbleweed is available via the store. Here's where it gets interesting: on a company managed Windows PC, they can control what you can get from the Store. In my company at least, Tumbleweed is not on the list. I bet this is the case for many corporate users. So they select a distro from those that are immediately available. For SUSE I guess it is good if an SLED is selected. I get that. But from a openSUSE perspective, the situation is less good.
tl;dr - The Store and the `--web-download` (and/or what you see with `--online`) methods are controlled by 2 different entities [the Microsoft partner portal vs. DistributionInfo.json from github.com/microsoft/wsl) but have slight overlap depending on the configuration of the .json file for any given github WSL release. Things on the Microsoft side w/ WSL delivery are a bit in flux, but should even out in the next few months. The transition from <1.0.0 to >=1.0.0 has had growing pains, but should end up a win overall.
I can get into it more if you'd like (or maybe this[1] will shed more light), but there's only so much we can control at the moment and we're working on it :)
I'm not sure what you're referring to w/ the SLED part of your comments or how that relates to what you'd see here[2]. If you care to elaborate, maybe we can clear that up. SLED _is_ an option when registering as part of firstboot for SLE WSL distro(s), that's recently new - but there's no "You're getting SLED" item in the Store.
Also, if you share more info around output from `wsl --list --online` and/or `wsl --status` and/or `wsl --version`, that would be useful too.
wsl --list --online 2004.622.0:<2023/1/16, 8:57:18>: 0x80070005 (WIN32: 5 ERROR_ACCESS_DENIED) The following is a list of valid distributions that can be installed. Install using 'wsl --install -d <Distro>'. NAME FRIENDLY NAME Ubuntu Ubuntu Debian Debian GNU/Linux kali-linux Kali Linux Rolling SLES-12 SUSE Linux Enterprise Server v12 SLES-15 SUSE Linux Enterprise Server v15 Ubuntu-18.04 Ubuntu 18.04 LTS Ubuntu-20.04 Ubuntu 20.04 LTS OracleLinux_8_5 Oracle Linux 8.5 OracleLinux_7_9 Oracle Linux 7.9 wsl --status Default Distribution: Debian Default Version: 2 Windows Subsystem for Linux was last updated on 1/4/2023 The Windows Subsystem for Linux kernel can be manually updated with 'wsl --update', but automatic updates cannot occur due to your system settings. To receive automatic kernel updates, please enable the Windows Update setting: 'Receive updates for other Microsoft products when you update Windows'. For more information please visit https://aka.ms/wsl2kernel. Kernel version: 5.10.102.1 -- Roger Oberholtzer
On 2023-01-16 02:18:34 Roger Oberholtzer wrote:
|To receive automatic kernel updates, please enable the Windows Update |setting: 'Receive updates for other Microsoft products when you update |Windows'.
So now Linux has become a 'Microsoft product.' :-) I suppose it was inevitable... Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 x86_64
On Tue, Jan 17, 2023 at 8:12 AM J Leslie Turriff <jlturriff@mail.com> wrote:
On 2023-01-16 02:18:34 Roger Oberholtzer wrote:
|To receive automatic kernel updates, please enable the Windows Update |setting: 'Receive updates for other Microsoft products when you update |Windows'.
So now Linux has become a 'Microsoft product.' :-) I suppose it was inevitable...
They are also a big contributor to the kernel. In the recent WSL, one can run GUI programs. Funny to run Windows but use KDE's Dolphin as the file system browser... I haven't really played with WSL. It's on my list of things to do. I am a Linux developer. But the users are a decidedly Windows lot. And the corporate IT as well. -- Roger Oberholtzer
On 2023-01-17 09:14, Roger Oberholtzer wrote:
On Tue, Jan 17, 2023 at 8:12 AM J Leslie Turriff <jlturriff@mail.com> wrote:
On 2023-01-16 02:18:34 Roger Oberholtzer wrote:
|To receive automatic kernel updates, please enable the Windows Update |setting: 'Receive updates for other Microsoft products when you update |Windows'.
So now Linux has become a 'Microsoft product.' :-) I suppose it was inevitable...
They are also a big contributor to the kernel.
In the recent WSL, one can run GUI programs. Funny to run Windows but use KDE's Dolphin as the file system browser...
I am curious. What do you see as directory symbol, "/" or "\"?
I haven't really played with WSL. It's on my list of things to do. I am a Linux developer. But the users are a decidedly Windows lot. And the corporate IT as well.
I wish the reverse existed and worked that well. Ok, it is wine. Tried to run a program yesterday and it failed. The program worked, but failed to do its job because it did not find the hardware. Easy Smart Configuration Utility v1.3.10.0 from TP-link. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Tue, Jan 17, 2023 at 11:11 AM Carlos E. R. <robin.listas@telefonica.net> wrote:
I am curious. What do you see as directory symbol, "/" or "\"?
It would most likely be the forward slash. Just like it is for a CIFS volume mounted from a Windows server. When I get things installed as I would like, I can report more. The main reason I am even looking at this is because we use Subversion to manage our source code. We do lots of symbolic links. The go-to subversion client for Windows (Tortoise SVN) does not make symbolic links. Even though the Windows file system has supported them at the file system level for years. This is all a test to see if we can check out the source tree in WSL/Tumbleweed and see the files as expected in Windows. Strange but true. -- Roger Oberholtzer
On Tue, Jan 17, 2023 at 1:23 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
The main reason I am even looking at this is because we use Subversion to manage our source code. We do lots of symbolic links. The go-to subversion client for Windows (Tortoise SVN) does not make symbolic links. Even though the Windows file system has supported them at the file system level for years.
Windows requires administrative privileges to create native symbolic links.
On Tue, Jan 17, 2023 at 11:38 AM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Tue, Jan 17, 2023 at 1:23 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
The main reason I am even looking at this is because we use Subversion to manage our source code. We do lots of symbolic links. The go-to subversion client for Windows (Tortoise SVN) does not make symbolic links. Even though the Windows file system has supported them at the file system level for years.
Windows requires administrative privileges to create native symbolic links.
This I have read. But the issue with Tortoise SVN is that it does not even try. Maybe I should check to see that this is still the case. -- Roger Oberholtzer
Carlos E. R. wrote:
In the recent WSL, one can run GUI programs. Funny to run Windows but use KDE's Dolphin as the file system browser...
I am curious. What do you see as directory symbol, "/" or "\"?
We ran openSUSE on WSL on my son's laptop a couple of years ago, afair, it was '/', but the shell was quite accepting. -- Per Jessen, Zürich (3.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
We use WSL for linux development in our windows only company network. It works great. You even can execute Windows Exe-Binaries. But tmux does not run - it's not a substitute for a real operating system. Am 17.01.2023 11:28 schrieb Per Jessen:
Carlos E. R. wrote:
In the recent WSL, one can run GUI programs. Funny to run Windows but use KDE's Dolphin as the file system browser...
I am curious. What do you see as directory symbol, "/" or "\"?
We ran openSUSE on WSL on my son's laptop a couple of years ago, afair, it was '/', but the shell was quite accepting.
On Wed, 2023-01-18 at 08:09 +0000, Bernd Ritter wrote:
We use WSL for linux development in our windows only company network. It works great. You even can execute Windows Exe-Binaries.
But tmux does not run - it's not a substitute for a real operating system.
Am 17.01.2023 11:28 schrieb Per Jessen:
Carlos E. R. wrote:
In the recent WSL, one can run GUI programs. Funny to run Windows but use KDE's Dolphin as the file system browser...
I am curious. What do you see as directory symbol, "/" or "\"?
We ran openSUSE on WSL on my son's laptop a couple of years ago, afair, it was '/', but the shell was quite accepting.
tmux runs fine in WSL. Maybe every.single.use.case isn't 1:1 when compared w/ Linux on bare metal, but it definitely works in general. There is an issue w/ systemd-tmpfiles-setup.service (and the LoadCredential directive(s) in the .service file) but running the contents of `ExecStart` manually allow it to work. Could also add that to a `command=` stanza in /etc/wsl.conf so it works when the distro "boots". -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On Mon, 2023-01-16 at 09:18 +0100, Roger Oberholtzer wrote:
On Fri, Jan 13, 2023 at 6:41 PM Scott Bradnick <scott.bradnick@suse.com> wrote:
On Fri, 2023-01-13 at 08:32 +0100, Roger Oberholtzer wrote:
When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line.
I'm curious why SLED is the only one available directly. Political?
Tumbleweed is available via the store. Here's where it gets interesting: on a company managed Windows PC, they can control what you can get from the Store. In my company at least, Tumbleweed is not on the list. I bet this is the case for many corporate users. So they select a distro from those that are immediately available. For SUSE I guess it is good if an SLED is selected. I get that. But from a openSUSE perspective, the situation is less good.
tl;dr - The Store and the `--web-download` (and/or what you see with `-- online`) methods are controlled by 2 different entities [the Microsoft partner portal vs. DistributionInfo.json from github.com/microsoft/wsl) but have slight overlap depending on the configuration of the .json file for any given github WSL release. Things on the Microsoft side w/ WSL delivery are a bit in flux, but should even out in the next few months. The transition from <1.0.0 to
=1.0.0 has had growing pains, but should end up a win overall.
I can get into it more if you'd like (or maybe this[1] will shed more light), but there's only so much we can control at the moment and we're working on it :)
I'm not sure what you're referring to w/ the SLED part of your comments or how that relates to what you'd see here[2]. If you care to elaborate, maybe we can clear that up. SLED _is_ an option when registering as part of firstboot for SLE WSL distro(s), that's recently new - but there's no "You're getting SLED" item in the Store.
Also, if you share more info around output from `wsl --list --online` and/or `wsl --status` and/or `wsl --version`, that would be useful too.
wsl --list --online
2004.622.0:<2023/1/16, 8:57:18>: 0x80070005 (WIN32: 5 ERROR_ACCESS_DENIED) The following is a list of valid distributions that can be installed. Install using 'wsl --install -d <Distro>'.
NAME FRIENDLY NAME Ubuntu Ubuntu Debian Debian GNU/Linux kali-linux Kali Linux Rolling SLES-12 SUSE Linux Enterprise Server v12 SLES-15 SUSE Linux Enterprise Server v15 Ubuntu-18.04 Ubuntu 18.04 LTS Ubuntu-20.04 Ubuntu 20.04 LTS OracleLinux_8_5 Oracle Linux 8.5 OracleLinux_7_9 Oracle Linux 7.9
wsl --status
Default Distribution: Debian Default Version: 2
Windows Subsystem for Linux was last updated on 1/4/2023 The Windows Subsystem for Linux kernel can be manually updated with 'wsl --update', but automatic updates cannot occur due to your system settings. To receive automatic kernel updates, please enable the Windows Update setting: 'Receive updates for other Microsoft products when you update Windows'. For more information please visit https://aka.ms/wsl2kernel.
Kernel version: 5.10.102.1
I'm a bit concerned by that "0x80070005" error, seems like you've been locked out of WSL updates (as it mentions later; is this not a machine under your control?). Are you running these commands as an Administrator or non-admin user? It's always better to _use_ WSL as a non-admin user (or maybe better to say 'without any privilege escalation'). You're seemingly running an old WSL kernel, did `wsl --version` error out [or basically run --help]? I get this: PS C:\Users\scott> wsl --version WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22621.1105 since I'm running the latest release from github.com/microsoft/wsl/releases -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
Am Freitag, 13. Januar 2023, 08:32:00 CET schrieb Roger Oberholtzer:
When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line.
I'm curious why SLED is the only one available directly. Political?
I have Leap 15.4 in WSL, from the store. Before that I had 15.3 and 15.2. Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :) Cheers, MH -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech Matrix: @mathias:eregion.de IRC: [Lemmy] on freenode and ircnet (bouncer active) keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Am 17.01.2023 um 11:02 schrieb Andrei Borzenkov:
On Tue, Jan 17, 2023 at 12:52 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :)
Care to elaborate howto for dummies?
1. take any linux that supports docker 2. run a base container based on the linux distribution you want, apply customizations if required 3. once the container has terminated, export the container as a tar file 4. import that tarfile in WSL like so: |wsl --import <DistroName> <InstallLocation> <InstallTarFile>| That's all folks. In greater detail: https://learn.microsoft.com/en-us/windows/wsl/use-custom-distro That is how I got RHEL8 into WSL on my computer - Exported a container based on the freely available/usable UBI8 image :) Cheerz MH -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On Tue, Jan 17, 2023 at 11:26 AM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Am 17.01.2023 um 11:02 schrieb Andrei Borzenkov:
On Tue, Jan 17, 2023 at 12:52 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :)
Care to elaborate howto for dummies?
1. take any linux that supports docker
2. run a base container based on the linux distribution you want, apply customizations if required
3. once the container has terminated, export the container as a tar file
4. import that tarfile in WSL like so: |wsl --import <DistroName> <InstallLocation> <InstallTarFile>|
That's all folks.
In greater detail:
https://learn.microsoft.com/en-us/windows/wsl/use-custom-distro
That is how I got RHEL8 into WSL on my computer - Exported a container based on the freely available/usable UBI8 image :)
We have a Leap OEM installer that we build with KIWI. It is a disk image (including the partition table). It is 'installed' by dd to the disk. KIWI makes a nice boot wrapper that lets you select the disk and does the dd. Or just dd the image yourself. When it is first booted, the usual locale questions are asked. Like a new laptop would usually do. Maybe I can tar the OS partition and try this. I'm mainly curious how the /etc/fstab is managed so all is found as expected. Maybe the OS's fstab is not used to start the OS? Aren't the images in the Microsoft store available somewhere? In OBS? -- Roger Oberholtzer
On Tue, 2023-01-17 at 11:42 +0100, Roger Oberholtzer wrote:
On Tue, Jan 17, 2023 at 11:26 AM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Am 17.01.2023 um 11:02 schrieb Andrei Borzenkov:
On Tue, Jan 17, 2023 at 12:52 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :)
Care to elaborate howto for dummies?
1. take any linux that supports docker
2. run a base container based on the linux distribution you want, apply customizations if required
3. once the container has terminated, export the container as a tar file
4. import that tarfile in WSL like so:
wsl --import <DistroName> <InstallLocation> <InstallTarFile>|
That's all folks.
In greater detail:
https://learn.microsoft.com/en-us/windows/wsl/use-custom-distro
That is how I got RHEL8 into WSL on my computer - Exported a container based on the freely available/usable UBI8 image :)
We have a Leap OEM installer that we build with KIWI. It is a disk image (including the partition table). It is 'installed' by dd to the disk. KIWI makes a nice boot wrapper that lets you select the disk and does the dd. Or just dd the image yourself. When it is first booted, the usual locale questions are asked. Like a new laptop would usually do.
Maybe I can tar the OS partition and try this.
I'm mainly curious how the /etc/fstab is managed so all is found as expected. Maybe the OS's fstab is not used to start the OS?
Aren't the images in the Microsoft store available somewhere? In OBS?
Take a look at: https://en.opensuse.org/openSUSE:WSL If I remember correctly, the Leap .appx images aren't published directly to download.opensuse.org [as TW is], but you can get them from build.opensuse.org ; these are the items which we feed into the Microsoft Store. https://build.opensuse.org/package/binaries/openSUSE:Leap:15.4:WSL/kiwi-imag... As I said earlier, Microsoft has the `--web-download` flag available (so long as your version of WSL is up-to-date) to assist users who can't reach the Store directly. Unfortunately, there are issues w/ the DistributionInfo.json file which my github.com/microsoft/wsl PR is attempting to address. We'll be meeting with Microsoft in the not-too-distant future to sort the discrepancies out. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On Tue, Jan 17, 2023 at 7:28 PM Scott Bradnick <scott.bradnick@suse.com> wrote:
If I remember correctly, the Leap .appx images aren't published directly to download.opensuse.org [as TW is], but you can get them from build.opensuse.org ; these are the items which we feed into the Microsoft Store.
On OBS, I see these three files for Tumbleweed: openSUSE-Tumbleweed-20230116-WSL.ix86-23016.3.1035.0-Snapshot20230116.appx openSUSE-Tumbleweed-20230116-WSL.x86_64-23016.3.1035.0-Snapshot20230116.appx openSUSE-Tumbleweed-20230116-WSL.x86_64.appx What's the difference? Is there a description somewhere? -- Roger Oberholtzer
On Wed, 2023-01-18 at 09:01 +0100, Roger Oberholtzer wrote:
On Tue, Jan 17, 2023 at 7:28 PM Scott Bradnick <scott.bradnick@suse.com> wrote:
If I remember correctly, the Leap .appx images aren't published directly to download.opensuse.org [as TW is], but you can get them from build.opensuse.org ; these are the items which we feed into the Microsoft Store.
On OBS, I see these three files for Tumbleweed:
openSUSE-Tumbleweed-20230116-WSL.ix86-23016.3.1035.0-Snapshot20230116.appx openSUSE-Tumbleweed-20230116-WSL.x86_64-23016.3.1035.0-Snapshot20230116.appx openSUSE-Tumbleweed-20230116-WSL.x86_64.appx
What's the difference? Is there a description somewhere?
First one is an x86 version, 2nd one is an x86_64 version and the 3rd is [basically] a link back to the x86_64 version. And they're all "Snapshot"s from Jan 16th, 2023 since they're rebuilt in OBS when something changes to the underlying OS outside of it being run in WSL. ps - if you could refrain from responding directly to me and cc'ing the list, that would be great as it would save time of rearranging to/cc fields and removing the option of "Reply to List" ;) -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On Tue, Jan 17, 2023 at 1:26 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Am 17.01.2023 um 11:02 schrieb Andrei Borzenkov:
On Tue, Jan 17, 2023 at 12:52 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :)
Care to elaborate howto for dummies?
1. take any linux that supports docker
2. run a base container based on the linux distribution you want, apply customizations if required
3. once the container has terminated, export the container as a tar file
4. import that tarfile in WSL like so: |wsl --import <DistroName> <InstallLocation> <InstallTarFile>|
That's all folks.
Thanks, that sounds promising. One more question - do I need administrative privileges to deploy Linux under WSL2? I am in a restricted environment, I can enable WSL2 on my notebook but I do not have administrative privileges to do anything.
On Tue, 2023-01-17 at 14:00 +0300, Andrei Borzenkov wrote:
On Tue, Jan 17, 2023 at 1:26 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Am 17.01.2023 um 11:02 schrieb Andrei Borzenkov:
On Tue, Jan 17, 2023 at 12:52 PM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :)
Care to elaborate howto for dummies?
1. take any linux that supports docker
2. run a base container based on the linux distribution you want, apply customizations if required
3. once the container has terminated, export the container as a tar file
4. import that tarfile in WSL like so:
wsl --import <DistroName> <InstallLocation> <InstallTarFile>|
That's all folks.
Thanks, that sounds promising. One more question - do I need administrative privileges to deploy Linux under WSL2? I am in a restricted environment, I can enable WSL2 on my notebook but I do not have administrative privileges to do anything.
In general, no, you don't need [and really should use] any type of Windows privilege escalation w/ WSL day-to-day. A distro installed by Administator won't be visible to a non-admin user - and vice-versa. Same w/ 2 non-admin users. This link should be helpful too: https://en.opensuse.org/openSUSE:WSL -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On Tue, Jan 17, 2023 at 10:52 AM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
Am Freitag, 13. Januar 2023, 08:32:00 CET schrieb Roger Oberholtzer:
When installing WSL on Windows, one has a choice to install a Linux distro. SLED15 and an earlier one are amongst the distros available. But no openSUSE distros are available at that level. They are available in the Store. But not direct in Windows at the command line.
I'm curious why SLED is the only one available directly. Political?
I have Leap 15.4 in WSL, from the store. Before that I had 15.3 and 15.2.
Sidenote: it is extremely simple to "get" any linux into your WSL, I actually have a RHEL 8 in my WSL as well :)
That depends. As I wrote in the original message, our company IT limit what is available in the Microsoft store. Leap releases are not available. Can they be downloaded from elsewhere and then installed locally without using the MS store? -- Roger Oberholtzer
participants (8)
-
Andrei Borzenkov -
Bernd Ritter -
Carlos E. R. -
J Leslie Turriff -
Mathias Homann -
Per Jessen -
Roger Oberholtzer -
Scott Bradnick