I want to expose functionality to override grub with your own template and also inject files but not

I want to expose functionality to override grub with your own template and also inject files but not sure how to it yet

Gerblesh•9/9/23, 11:03 PM

Also curious, is everything in place to make an offline M1 Mac ISO? We have lorax compose, so we can easily make the ISO a different architecture, we just need to build an arm image

Gerblesh•9/9/23, 11:03 PM

I'm guessing we can also install different packages/drivers in the installer with lorax

Gerblesh•9/9/23, 11:04 PM

Though idk, need to look into lorax more

akdevOP•9/9/23, 11:04 PM

Not at all, there's not even apple silicon ostree images

Aakdev Not at all, there's not even apple silicon ostree images

Gerblesh•9/9/23, 11:04 PM

It's a different bootloader right?

akdevOP•9/9/23, 11:05 PM

I made one and was actually able to boot but my Macbook was really slow

akdevOP•9/9/23, 11:05 PM

Like 1 second on the clock would take minutes to pass

Gerblesh•9/9/23, 11:05 PM

And kernel + other packages

akdevOP•9/9/23, 11:05 PM

Those images still use grub but they chainload from m1n1

akdevOP•9/9/23, 11:06 PM

https://pagure.io/fedora-asahi-remix-ostree

Gerblesh•9/9/23, 11:06 PM

So still a lot of work to be done

akdevOP•9/9/23, 11:07 PM

Yeah, it's difficult to debug because I have no idea what I'm doing lmaoo

akdevOP•9/9/23, 11:07 PM

m1n1 chainloads to uboot and that chainloads to grub

Gerblesh•9/9/23, 11:07 PM

Would be nice if Marcan or someone on the asahi project helped out with it

akdevOP•9/9/23, 11:07 PM

And I tried converting a regular fedora Asahi Remix installation to ostree

akdevOP•9/9/23, 11:07 PM

Because there's no installer for this

akdevOP•9/9/23, 11:08 PM

Anaconda can't really I guess and Fedora Asahi people use calamares

Gerblesh•9/9/23, 11:08 PM

But I understand it's not a priority at all atm

akdevOP•9/9/23, 11:08 PM

They also use KIWI to compose the OS which i have no clue about lol

akdevOP•9/9/23, 11:08 PM

It's the tool used by opensuse

Gerblesh•9/9/23, 11:08 PM

Whar

Gerblesh•9/9/23, 11:08 PM

They use such weird tooling lol

Gerblesh•9/9/23, 11:09 PM

Like why calemares?

akdevOP•9/9/23, 11:09 PM

I think they just like it better

Gerblesh•9/9/23, 11:09 PM

Ah, yeah I'd prefer KDE first time setup + new anaconda webUI

Aakdev I want to expose functionality to override grub with your own template and also ...

EyeCantCU•9/9/23, 11:09 PM

That would be sweet. Don't mind looking into that this weekend but not sure I'd be able to figure it out

EyeCantCU•9/9/23, 11:10 PM

Oh wait. It's Saturday

akdevOP•9/9/23, 11:10 PM

I built mkocisomkociso to abstract away lorax so currently we can do like this: mkociso --image ghcr.io/ublue-os/bazzite:38mkociso --image ghcr.io/ublue-os/bazzite:38 and it will create an ISO

akdevOP•9/9/23, 11:12 PM

I think the goal is to add something like:

mkociso \
  --image ghcr.io/ublue-os/bazzite:38 \
  --efi-tmpl ./custom/efi.tmpl \
  --x86-tmpl ./custom/x86.tmpl

mkociso \
  --image ghcr.io/ublue-os/bazzite:38 \
  --efi-tmpl ./custom/efi.tmpl \
  --x86-tmpl ./custom/x86.tmpl

these two templates are what we need to override to hijack the boot menu

akdevOP•9/9/23, 11:14 PM

or maybe it should be like:

mkociso \
  --image ghcr.io/ublue-os/bazzite:38 \
  --append 'inst.resolution=1280x800' \
  --append 'inst.ks=/var/run/bazzite.ks' \
  --include './custom/bazzite.ks:/var/run/bazzite.ks'

mkociso \
  --image ghcr.io/ublue-os/bazzite:38 \
  --append 'inst.resolution=1280x800' \
  --append 'inst.ks=/var/run/bazzite.ks' \
  --include './custom/bazzite.ks:/var/run/bazzite.ks'

EyeCantCU•9/9/23, 11:20 PM

Either would be perfect and accomplish what we need to do

EyeCantCU•9/9/23, 11:20 PM

I personally like the second approach

Gerblesh•9/10/23, 12:12 AM

@tulili hi, I can't respond on github atm but the bling module only pulls in the items specified, sure it's copied into the image, but it's in /tmp, so all of the rpms are removed from the image. Only the ones that are installed are kept inside the image (specified in bling module) bling module also isn't needed in the recipe.yml

Gerblesh•9/10/23, 1:30 AM

This also isn't too streamlined, but technically one could define their own repo and add it in the container file, and write an installer script in modules. Would work just fine

tulip•9/10/23, 1:38 AM

Oh hi!

GGerblesh @tulili hi, I can't respond on github atm but the bling module only pulls in the...

tulip•9/10/23, 1:40 AM

No, no, it wasn't exactly that that I was trying to convey, I just thought that maybe by separating where the modules are declared from the repos themselves might be a good idea

tulip•9/10/23, 1:41 AM

Like, before all files that were cloned onto the images based off of StartingPoint were declared in their own repos, and that made updating things like the ublue-nix-install script a lot worse, since it wasn't necessarily centralized onto one repo (in this case, bling!)

tulip•9/10/23, 1:43 AM

I just thought that maybe my moving the "modules" folder in the Startingpoint template to other repo, like bling, we could have a better way to keep everyone up-to-date with their module implementations, without requiring them to sync their repos with github's fork thing (which can be very annoying at times when merge conflicts happen)

tulip•9/10/23, 1:45 AM

Having this pattern someone could just clone their own if they want, too