os VS installer

Cool. My goal in asking is to find out if there's anything I should know before trying to update the build script myself.. This is my first time trying to build an OS, so if I'm getting in way over my head, I'd definitely like to know that in advance.

From what I understand, OSTree-based images[0] are in progress and will remediate this.

[0] https://github.com/elementary/os/pull/582

elementaryOS is licensed under GPLv3. You may absolutely sell hardware that comes with it pre-installed, so long as any modifications you have made to the software are also released under GPLv3. There are non-commercial licenses, but they are not free and open source.

Problem still occurs, here’s a bug report: https://github.com/elementary/os/issues/634

Go to https://github.com/elementary/os

Sounds like it's probably a bug that you'll wanna report to the eOS developers. They prefer getting those on their GitHub Issues page if you have a GitHub account

I really hope it does. I have a discussion open here: https://github.com/elementary/os/discussions/552

with elementary OS working on an OSTREE image what is the possibility of linux mint also joining in and also working on an OSTREE image for their distro?

I’m not sure tbh. I generally stay away from Nvidia because of issues like this. It’s probably worth opening a new issue report and maybe someone else has access to this hardware https://github.com/elementary/os

Surprising enough (expectations set by decades of Debian/Ubuntu) that I had to look it up, but it's true https://github.com/elementary/os/wiki/Release-Upgrades#perfo...

This is an ongoing issue with the Installer. https://github.com/elementary/installer/issues/702

But making an installer is hard to do from scratch. So you may want to modify an existing one, such as the one that elementaryOS uses, or the general-purpose calamares framework, in which case your installer is bound by the terms of their license to the extent you modified or are redistributing their code.

The installer is currently broken for the 2017 12 inch MacBook, and for pretty much all Macs 2017 and onwards. I’m in the same boat as you. It’s because the Installer is not correctly configured to see the NVME SSD’s cluster size. There’s an issue open on GitHub, namely this onethat has instructions to fix it, but I could not get it to work. There was a PR with the fix, but has not hit the 6.1 ISOs so here’s hoping it’s fixed with OS 7.

I think you have to post your feature request here: https://github.com/elementary/installer/issues

Afterwards, I'd give it a shot again, and see what the results are. If it still occurs, you may be able to try disconnecting the other drives, though this is not something that should stop the installer from working. If it does, please file a bug report at your convenience! https://github.com/elementary/installer/issues

I had that same problem, see [here](https://github.com/elementary/installer/issues/514). A workaround I discovered is to first go into demo and mount my large ntfs partition. Then going back to the custom installation, disks show up normally.