commit c6175ee145b3474a6ae1c89d7faf12cca15ad7aa parent 510c9ab6dc101432f53c3241ba47c33e613ebfb0 Author: viznut_web <viznut_web@web> Date: Sat, 25 Jun 2022 06:37:43 +0200 i guess we'll have to spell this out Diffstat:
| M | bedrock_platform.mdwn | | | 9 | +++++++++ |
1 file changed, 9 insertions(+), 0 deletions(-)
diff --git a/bedrock_platform.mdwn b/bedrock_platform.mdwn @@ -1,5 +1,14 @@ A **bedrock platform** is a [[hardware]] platform or a universal [[virtual machine]] that can be expected to remain compatible with any [[software]] that has ever been written for it. Bedrock platforms can be used to prevent [[software rot]]. +Note that this is **not** a "shopping list" or a list of "allowed" hardware. Bedrock platform support is simply a way of maximizing the probability that a program can be run in an indefinite future and a way to keep its [[dependencies|dependency]] reliable. The concept of bedrock platform is **not** relevant to e.g. embedded-system-type projects that are designed for a very specific hardware, or the kind of software that is known to have a short lifespan. + +A simple bedrock platform guide based on the IBM PC line: + +* Can you compile and run the program in FreeDOS? + * If yes, you have the bedrock support (just make sure that the compiler and other needed tools are archived somewhere). + * If not, can you create an x86 operating system image that compiles and runs the program without accessing any external resources? + * If yes, you have the bedrock support (just archive the image and/or everything you've put in it). + Some possible criteria for bedrock hardware: * The hardware has been popular and commonly available at some point of history (and preferably remains that way).