Support for T2 chip install using patches

[theokeist]

How is GoboLinux support on this topic? T2Linux
Gobo is one of last ideas on this topic for me to start macOS -> Linux migration
But all these drivers and patches are not realy my cup of tea..

[nuc1eon]

I sincerely advise you to start migrating to another distro, like ubuntu or its derivates, or even archlinux. GoboLinux is not for linux beginners, it requires a solid base understanding.

[rubyFeedback]

But all these drivers and patches are not realy my cup of tea..

They are not my cup of tea either, as I don't really know C and C++ well. I just read the LFS/BLFS pages and try to learn from them for the most part. You can learn a lot from BLFS by the way: https://www.linuxfromscratch.org/lfs/view/stable/ - tons of programs are registered there, with useful information. (Well, LFS and BLFS combined actually)

GoboLinux is not that much "special" in that it is basically "stock" Linux really (you even have the default directories such as /usr/bin/, just hidden by default via gobohide if I recall correctly), but for some things you may need some knowledge that may not be available for a newcomer. For instance, I still don't fully understand which patches are applied to GoboLinux, why and how, even though the source code is all available in the gobolinux repository; but I don't know C/C++ that well, so I can't progress in this regard. GoboLinux's documentation is also somewhere around average or so, give or take; some parts are well-documented, others are in my opinion missing documentation/explanations. I think this may change in the long run, depending on how motivated Nuc1eoN may be, as well as others who can help him (or try to), but right now I think the documentation could be improved. You can sometimes see this in questions e. g. Nuc1eoN asking Lucas or Hisham why this or that was added, and even they may not always remember offhand. But it is all one's unpaid spare time investment, so one can not expect perfection everywhere, at all times.

So in this regard, I think Nuc1eoN's advice is more realistic right now. You may learn a lot from other distributions, and if you want to test the GoboLinux way - which I still think is cleaner and more logical than the default Linux "experience" - you can easily do so and perhaps even with some useful feedback, just from testing it.

I currently use manjaro linux; while it uses systemd (I am not a big fan of it), in many ways it feels a LOT like oldschool slackware, which I also like. I compile from source there, primarily into the /usr/ directory, but I keep on improving my set of ruby scripts too (using compiled AppDir prefixes as target, although I use a slightly different scheme, e. g. my target is /home/Programs/Ruby/3.4.1/ for instance, always capitalized first letter for the program name, and rest is always downcased, but by and large it is in many ways similar to GoboLinux). Once I can have a better testing-environment, as well as more time, I'll test my scripts too; I should be able to batch-create tons of GoboLinux recipes. Right now I have 3864 programs registered, and most of GoboLinux programs on the repository too (need to check this again automatically in the future though).