Changeset 132


Ignore:
Timestamp:
Apr 8, 2017, 12:27:30 AM (8 years ago)
Author:
Ben Rietbroek
Message:

Added method to force build failure [v1.1.1-testing]

Usually, commits are buildable and some minor checking has been done
that whole disks do not get wiped. However, there are situations where
stuff is in such a flux that it would be better to do non-buildable
commits. That makes it possible to record the changes piecemeal without
the danger of accidently using the resulting loader. Of course everyone
is clever enough to _never_ build commits marked as 'testing' and
install the result in environments where wiping all attached disks and
sticks would be a problem...

CAUTION:
This is a testbuild !
AirBoot uses the BIOS to access disks and a small coding error can trash
partition tables or other vital disk structures. You are advised to make
backups of TRACK0 and EBRs before using this testbuild. More info at:
https://rousseaux.github.io/netlabs.air-boot/pdf/AirBoot-v1.1.0-manual.pdf

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/bootcode/airboot.asm

    r131 r132  
    25102510CurrentSS                   dw      ?
    25112511                            ALIGN   16
     2512
     2513; Usually, commits are buildable and some minor checking has been done that
     2514; whole disks do not get wiped. However, there are situations where stuff is
     2515; in such a flux that it would be better to do non-buildable commits.
     2516; That makes it possible to record the changes piecemeal without the danger of
     2517; accidently using the resulting loader. Of course everyone is clever enough
     2518; to _never_ build commits marked as 'testing' and install the result in
     2519; environments where wiping all attached disks and sticks would be a problem...
     2520;~ force_build_error           dd      0f000h  dup(?)
     2521
    25122522;
    25132523; End of BSS segment.
Note: See TracChangeset for help on using the changeset viewer.