Commit Graph

9 Commits

Author SHA1 Message Date
jhb
c882f3a97e - When we save the existing MBR to a file, check to see if the MBR we are
saving is boot0.  If it is, use its version number so that we can grab
  all of boot0 (1024 bytes with version 1.1 for example) when we save it
  to a file via the 'f' option.  Otherwise, we just save the first sector.
- Cleanup this code a bit by splitting some functionality out into separate
  functions.

Suggested by:	Patrick Bihan-Faou <patrick@mindstep.com> (1)
2000-07-13 23:05:05 +00:00
jhb
f965e9b866 Update boot0cfg to handle the new boot0:
- Allow for boot0 to be more than one sector long.  However, ensure that it
  its length is a multiple of the sector length.
- Change the signatures used to determine a valid boot0 as some of the
  signature code changed.
- Use the old signature to detect version 1.0 of boot0, otherwise read the
  version number from boot0 itself.
2000-07-12 18:15:06 +00:00
peter
efabb9ccb1 $Id$ -> $FreeBSD$ 1999-08-28 01:35:59 +00:00
rnordier
5c8982f442 Check that we really have a boot0 mbr before treating it as one.
Suggested by: peter

Also add a few comments.
1999-06-22 18:57:49 +00:00
rnordier
f31af56e7f Ensure that an update takes place when the -m option is used. 1999-06-21 14:40:59 +00:00
rnordier
3229eb479d Implement -m option to enable/disable slices. 1999-06-19 21:44:43 +00:00
rnordier
1e2759ad39 Finish implementing "setdrv" option. This is intended to be used
(with care) in those instances where boot0 is not passed the
correct drive number by the PC BIOS.  (The symptoms are a
"F5   Drive 0" line, even though the current drive is drive 0.)
1999-02-26 14:57:17 +00:00
rnordier
f4ef1ef780 Make various minor corrections. 1999-02-22 09:36:54 +00:00
rnordier
5028d48a50 Add boot0cfg: this installs/configures the `boot0' boot manager. A
CLI utility to do this has been requested by a few people.
1999-02-21 21:23:42 +00:00