Hi Bernd,
I would assume the kernel parameter is neither meant to be queried
at runtime nor is it used by a significant number of people at all.
There is no external API, but you may pull it from RAM, possibly.
Alternatively, you could extract settings from the kernel file of the
boot drive or (better?) try and compare your view of which drive is
which to the kernel in terms of sizes and labels for local drives.
But if you ask me, a command line option for that non-default,
but POSSIBLE sort order should be enough for FDISK. Anything
beyond that feels like unnecessary luxury and complexity to me.
I guess it could be more interesting to improve detection of whether
a disk is completely empty - no risk of damaging previous partitions
and/or boot code. Maybe improve boot code blobs offered by FDISK, too?
Also, that detection thing could provide a command line way for some
"just detect and return errorlevel" mode for use in batch processing.
Or maybe that feature even already is there? :-)
Greetings and happy new year everybody, Eric
Hi,
while hunting a FDISK bug reported to me on Github regarding the order
of the drive letters FDISK assigns, I noted that the FreeDOS Kernel
actually supports different drive sorting algorithms via its
DLASortByDriveNo config setting. While it is unrelated to the bug, this
may impose a problem if the FreeDOS Kernel and FDISK disagree over the
drive letters. For example, the user could be confused and delete the
wrong drive.
Taking this under account I think it would make sense for FDISK to adapt
to the Kernel setting, or does anything speak against it? Can I query
the DLASortByDriveNo Kernel parameter at runtime? And if so, is there an
intended way to do this?
Greetings, Bernd
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
