Commit Graph

10 Commits

Author SHA1 Message Date
christos
8ce2d80d7a back out previous; it is better for now to handle the dependencies in
bsd.prog.mk
2001-01-14 09:41:41 +00:00
christos
c26e2519ac add .NOTMAIN for good measure. 2001-01-14 09:24:30 +00:00
christos
726afedd26 don't use OBJS in the dependency line because it is not defined yet. 2001-01-14 09:22:01 +00:00
hubertf
04a9ed5842 Revert last change, it was caused by the build not picking the
right files if DESTDIR is set.
2000-02-11 16:14:32 +00:00
hubertf
e597c0a106 s/STRIP/STRIPPROG/ 2000-02-11 15:36:25 +00:00
tsutsui
c539ff5d84 STRIPPROG -> STRIP 2000-02-01 06:00:35 +00:00
fvdl
7d18a1432b Tighten check for bad drive numbers to avoid passing garbage to the
2nd stage loader.
1999-05-02 12:20:01 +00:00
fvdl
a6f7895b92 Only use int13 extensions if the sectors can not be read through the
older CHS interface. This works around stupid BIOSs who report that
int13 extensions are present and functional, but fail when you actually
use them. Like Adaptec SCSI BIOSs.

For the bootselector, there was no space to get the CHS info from
the BIOS. Instead, use a flag that can be set by fdisk. fdisk will
set it if one of the partitions on the disk is out of CHS reach
for this disk/BIOS, so that the bootselector will use int13 extensions.
This isn't so bad, because it needs to be configured via fdisk anyway.

Change the mbr manualpage to reflect some shorter error messages.
1999-04-28 23:27:01 +00:00
fvdl
48c1c25ba5 Make the bootselector configurable by fdisk. Add a -B flag to this
effect (i386 only of course). Also change one branch in the
bootselector code to an explicit 16 bit one, and check both
the boot menu and partition tables to see if the partition
requested by the user should be booted. This check just in case,
should the bootselector menu and partition table get out of sync
somehow. (mmm, bytesqueezing)
1999-04-17 01:38:00 +00:00
fvdl
fa9bff9be1 Add and build a bootselecting MBR (i386). 1999-04-15 22:31:23 +00:00