> On May 26, 2025, at 11:17 AM, tom ehlert via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > Hallo Herr Jerome Shidel via Freedos-devel, > > am Montag, 26. Mai 2025 um 16:52 schrieben Sie: > >> Hi Tom, > >>>> On May 26, 2025, at 10:03 AM, tom ehlert via Freedos-devel >>>> <freedos-devel@lists.sourceforge.net> wrote: >>> >>> Hallo Herr Jerome Shidel via Freedos-devel, >>> >>> am Montag, 26. Mai 2025 um 14:49 schrieben Sie: >>> >>>> Hi Bernd, >>> >>>>>> On May 26, 2025, at 7:12 AM, Bernd Böckmann via Freedos-devel >>>>>> <freedos-devel@lists.sourceforge.net> wrote: >>>>> >>>>> Hi, >>>>> >>>>> for testing I want to update the kernel binaries for the next interim >>>>> release with builds from the latest commit [1]. >>>>> >>>>> I have a question regarding the Gitlab kernel package [2]. It contains >>>>> several variants of the kernel (8086 / 386 etc.). None of them is named >>>>> KERNEL.SYS. >>>>> >>>>> Which of the files get installed as the KERNEL.SYS under the root >>>>> directory, and how is this accomplished? >>> >>>> It Depends. >>> >>>> * KERNL86N.SYS - without LFS support. Not used. Only provided. >>>> * KERNL86.SYS - with LFS support. >>>> * KERNL386.SYS - with LFS support. >>> >>>> (LFS = really big disk partitions, >>> >>> Whoever invented "LFS" can he please stay somewhere in the 100+ years >>> future, (or simply OFF this list) >>> so I don' have to turn in my grave so often? >>> >>>> LFN = really long file names) >>> it has been "long file names" for ~30 years. Maybe you lived under a rock >>> for all the time, >>> but there is absolutely no need to invent new names for old stuff. >>> >>> Bye > >> I often get complaints about just using acronyms. > But you don't care anyway?
Not really. Just trying to avoid the need for a follow up message to explain anything. That worked extremely well. Not. >> I was not giving the technical definitions for those. > That's obvious. You were just throwing uppercase letters into the air, > waiting to see which ones stick? Mostly. But, ones that should have been understood. > >> Only, a reminder of what that the kernels are not LFN. Because, as we know, >> LFN support is provided be a driver. Like DOSLFN or sometimes LFNDOS. > >> Even my usage of LFS was not technically accurate. > Even that is wrong; LFS isn't an acronym. So it can't be "accurate" or not. True. At least for now, under this context. Git LFS - Git Large File Storage LFS - Linux From Scratch LFS - Logic-Focused Solutions And many more, technically. >> That would be FAT-32 support. > This acronym has been available for ~30 years. Any reason not to use it that > you can explain? Typed on phone. Saved some letters. Went back and added that to prevent confusion that I could have been referring to Long File Name Support and not File Allocation Table (32). > > Tom > :-) Jerome > > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
