I have not tested it, but my understanding is that the Makefile puts different files on the floppy images depending on the type selected. So a 360 Kb image has fewer files than a 1.44 image. As long as the list of files for each format in the Makefile is maintained I think this would be sufficient for now. With the new ethernet support one could set up a repository ;) Georg > Marc-François LUCCA-DANIAU <mfld.fr@xxxxxxxxx> hat am 28. Februar 2017 um 10:31 geschrieben: > > > > Well, see...that's a problem. The ELKS kernel uses a really old copy of > > Kconfig from Linux and when I looked at extracting the one used in a more > > modern Linux source code base the task was far from trivial. A lot of ELKS > > was cobbled together well over a decade ago. I'm open to moving to a more > > all-encompassing build system if someone wants to do it, but it certainly > > will not be a simple task. > > Mmm... let us be pragmatic and stop dreaming with stuff like "changing > the compiler", "moving to another build system", etc. ELKS is > definitively a "hobby" / "educational" project, with a few active > contributors, and is intended to have fun, not for business (except > data erasing / recovery on antic machines ?). So our development > strategy should be consistent with that matter of fact : little steps > forward, and keep consistency and stability. Obsolescence is > absolutely NOT a concern here, as long we find compatible emulators > and embedded systems to play with. > > Back to the current Kconfig: it works quite well, fulfills the need, > so why breaking it with an hazardous upgrade ? I only propose to use > it not only for the kernel, but also for the applets and image format > selection. Not to upgrade it. > > MFLD > -- > To unsubscribe from this list: send the line "unsubscribe linux-8086" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
