I ordered one. First units should be shipped early December. Right now they seem to be some out - just few days ago you could order with 7-8 weeks delivery, now it’s just ‘notify when available’.
You could do some automated/scripted installation VM-image builder thingy and release that. Would probably also save some manual work for you. (bash script fetching install image & run qemu, autounattend.xml, etc. all nicely released on github.) And it’d be auditable.
Not a good idea, to share copyrighted material with your university account. Especially in DE. Archive.org would suit better!
Nevertheless thanks for your work and I would recommend to include Dism++ and maybe use an Enterprise version of Win11. But yeah, versions can be easily changed with Massgravel’s activator.
Usually less bloat ootb and less/no feature updates, longer update support. But actually I haven’t compared those Win11 versions by myself. I use Enterprise versions since Win7, with Win10 Iot Enterprise LTSC being the best version of all (at least currently) and it has support till 2032 :)
Okay thats crazy! I think Win10 is unusable and Win11 us a bit better and also worse, like an Explorer with Tabs wtf how long did that take? But the apps seem very bloated too, using bad libraries or something, its just slow. But I am quite happy with my setup currently, will switch the VM to Win11 enterprise if Win12 is even worse
I find that really cool, BUT, you should delete that link.
First, installing a tweaked Windows version from somebody else is risky. It’s hard to check if you included malware for example. I mean, I trust you that you didn’t do that, but it’s still risky. That alone isn’t the reason you should delete it. If I install a malware-version, it’s my fault, who cares.
The real reason you should delete that immediately is because it’s illegal! The licence doesn’t allow you to share Windows. With scripts on your own install its a grey area, but sharing installs or isos is definitely not allowed and everyone here could report you for that to MS, the police, the admins, whoever.
Instead of sharing the image, why not share the scripts or steps used to make it? Other people raised some fine points, but for me, my German is very poor.
I think there would be a way to test it with docker, you could find a image that has systemd installed and use something like distrobox to test it with the GUI.
If it were me and I was intending to automate this I would probably do the following. Set up each test distro as a VirtualBox image and take a snapshot so I could easily roll back. Then I would write a script for each distro that downloaded the package, installed and launched the app. I would then probably query the window system to make sure the gui showed up, wait a period of time if I had to and take a screenshot.
This can probably all be done as a set of bash scripts.
Yes, my order status has been at preparing to ship for awhile now. I been wanting a good Linux tablet to replace aging iPad and hoping this works well enough for me. I’ll try to remember to update post on how I like it when it does arrive.
Open.qa it is an OpenSUSE tool but it can be used to auto test installs of any OS/software. Their open build service also automates and tests package building
This kind of integration testing is best left up to the individual distros. Same as the integration (as in: packaging) itself.
Distros don’t want your binary package, they want your source code, build instructions and a build system that won’t make them cry. Some distros even explicitly disallow re-packaging external binary distributions.
As a distro maintainer, I appreciate your wish to do QA on all the distros but that’s just too much work. You focus on making your software better, we focus on making it work with the rest of the software ecosystem.
Providing a package for one or two distros (i.e. your favourite one) is good practice to ensure your software can be reasonably packaged but it’s not the primary way your users should receive your package in the traditional Linux distro model.
Additionally, you might want to package your software for one of the cross-distro package managers such as Flatpak, AppImage, Snap, Nix, Guix, distri or homebrew. This can serve distro maintainers as a point of reference; showing how it is intended to work so they can compare their packaging effort. If there’s some bug present in the distro package but not the cross-distro package, that’s a good sign the issue lies in the distro packaging for example.
Again, don’t put much time in this. Focus on your app.
I use NixOS but I don’t bother with automatic deployment or even automatic formatting. I don’t feel it’s necessary in a homelab setting as hardware failure rarely happens at such small scale and the manual steps left aren’t that significant.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.