A FrankenSystem can have minor incompatibilities if the kernel level is not exactly right (though usually only major numbers matter). Note that there are some “issues” with this. I did that back when the aarch64 userland still had some buggy bits like browsers and I wanted things a bit more stable.
#Recoverit ultimate 2020 v8.3.0.12 free crack 64 Bit
I made one FrankenSystem that used a v7 armhf 32 bit userland on an aarch64 64 bit kernel and device drivers. That 2nd one works when the kernel is of a compatible release level to the userland in question and when the base system is ported to that SBC (Single Board Computer) while the userland is one that works on that base system and is compatible with that hardware (so, for example, aarch64 code runs on ARM 64 bit processors and armhf code runs on V7 32 bit AND ARM v8 64 bit processors. In particular, a Devuan “Userland” (all those programs you normally use and interact with) over the system side stuff (kernel, dtb device tree bundle, kernel modules, firmware, /boot commands) from some other system already ported to your computer.
The other is creating a “FrankenSystem” via grafting together parts of other divergent systems. This lets you take, for example, a Devuan Ascii 2.0 release from the mirror site and turn it into a Devuan Beowulf 3.0 release via changing the entries in /etc/apt/sources.list and using the command “apt-get dist-upgrade” (then waiting a few hours for “stuff to happen” -) One is the “normal” Debian / Devuan / Ubuntu distribution upgrade via the “apt dist-upgrade’ command. There’s 2 different processes being documented here. For now, I’m going to document what I remember from doing it a few times, and then when I do it some more, clean up the details. After I’m done I’ll remove this ‘heads up’. To some extent this will be a ‘work in progress’ for a little while.
0 kommentar(er)
