Vanilla OS (@vanillaos@fosstodon.org)
fosstodon.org
Attached: 1 image Hey folks! Did you hear the news? Vanilla OS 2 Orchid Developer Previews are now available for download 🚀 Let us know what you think :) Please note that these builds are unstable and are not recommended for daily use. https://vanillaos.org/blog/article/2023-07-05/vanilla-os-orchid---developer-preview #Linux #FLOSS #OpenSource
  • drspod@lemmy.ml
    0·
    1 year ago

    Some notes from my experience of trying to test this:

    • There is no live-cd functionality, just the installer, so don’t expect to try before you install.
    • The installer will tell you that it needs at least 28.1Gb of space. I tried installing to a 32Gb (virtual) drive which allowed the installer to proceed, but then the installation failed with a “No space left on device” error.
    • After increasing the virtual drive to 50Gb the installer then failed with an error that it failed to run grub-install

    I didn’t get any further than this. I was attempting to install in a VirtualBox VM.

    • russjr08@outpost.zeuslink.netEnglish
      1·
      1 year ago

      Regarding the failed install error, you need to make sure that VirtualBox is using UEFI - Legacy Boot isn’t currently supported at the moment.

      Had the same issue while using Boxes, switching it to UEFI allowed the install to complete successfully!

      • drspod@lemmy.ml
        1·
        1 year ago

        Thanks, it gets a bit further, but this time fails with:

        grub-install: warning: Cannot set EFI variable Boot0003.
grub-install: warning: efivarfs_set_variable: writing to fd 6 failed: Read-only file system.
grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Read-only file system.
grub-install: error: failed to register the EFI boot entry: Read-only file system.
panic: Failed to run grub-install: exit status 1
        • russjr08@outpost.zeuslink.netEnglish
          1·
          1 year ago

          Interesting, I’m not too sure what could be causing that, but if I had to take a guess VirtualBox’s UEFI implementation doesn’t allow for writes from the VM, at least by default. It’s been a long time since I’ve used VirtualBox (since before UEFI was even really a thing), I don’t suppose there’s any sort of setting that might resemble making it writable?

          • drspod@lemmy.ml
            1·
            1 year ago

            My version of VirtualBox is a few years old so I wouldn’t be surprised if it was lacking some features.

            • jayandp@sh.itjust.works
              1·
              1 year ago

              If you’re using UEFI in VB, definitely update to the latest version. UEFI support in older VB was pretty bad. Works a lot better now, though I haven’t had time to test this new version of Vanilla OS, so YMMV.