Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't really think that this is relevant to anyone, except hardcore nostalgics and developers of the few embedded boards that still use a 386 based core.
If that simplifies kernel developing and makes development faster and less bug prone due to the simplification I am totally for it. If you really still need to use 386 hardware I doubt that the changes to the kernel that will be made in the future are relevant for your hardware at all, so you can simply stick with a current stable kernel. Or switch to one of the BSDs.
16-Bit Linux?
Strictly speaking, the previous statement regarding Linux’s inability to run on any pro-
cessor below 32 bits is not entirely true. There have been Linux ports to a number of
odd processors. The Embeddable Linux Kernel Subset (ELKS) project found at http://
elks.sourceforge.net/, for example, was aimed at running Linux on 16-bit processors,
such as the Intel 8086 and 286. It has seen several attempts at revival over the past few
years, and even may well work for some users by the time you read this edition, but it
is really strictly a research project at this point—you won’t see a vendor offering support
for Linux on an 80286. The point here is that if you choose to use Linux on a processor
lower than 32 bits, it is absolutely certain that you will be on your own. Even if you get
the kernel to boot, the range of applications is limited.
You can find other references (Google or DuckDuckGo) if you really want to work with older arch but do not expect to get very far.
EDIT: Notice the above reference is for embedded but you can find other information. As I said good luck!
There does come a point in time when you can safely-enough say that, even if the hardware is "386-compatible," in the sense that it is capable of running software which assumes no more than "386," the chip itself most certainly is not an 80386 microprocessor. You can, at some point, "sunset" support for that particular physical CPU. That time has reasonably come.
I agree with the sunset rule. World users may still need to run a Gnu/Linux on older equipment but they should not expect newer releases to run on legacy equipment. Those users will still have access to earlier releases of Gnu/Linux that could be used.
Some maintainers do support security updates for earlier releases. One example would be Slackware, PV did drop some earlier release from the support list this past year.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.