| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
BOOT_BTX_NOHANG, then BTX will be compiled with the appropriate flags so
that it reboots after a fault instead of hanging forever.
Requested by: ps
Approved by: rnordier
|
|
|
|
| |
Requested by: obrien
|
| |
|
| |
|
|
|
|
|
| |
reduces /boot/loader from 163840 bytes to 155648 and pxeboot from 165888
bytes to 157696 bytes.
|
|
|
|
|
| |
PR: 20524
Submitted by: Peter Pentchev <roam@orbitel.bg>
|
|
|
|
|
|
| |
identifier to the DHCP server. Now you can check for this string
in your dhcp configuration to decide whether you will hand out a
lease to the client or not.
|
|
|
|
| |
can utilize them in the kernel and with kenv.
|
| |
|
|
|
|
|
|
| |
- Fixed comment.
Pointed out by: nyan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to 0x600 via a 'rep movsw'. Once that was done, %cx was zero, so we could
simply use 'movb' to update the lower byte of %cx in preparation for
zeroing out the fake partition entry used to boot to other drives via F5.
Well, in the new boot0, we don't actually relocate ourselves, instead it
is easier to create the fake partition entry first and then just use it to
get the BIOS to load all of boot0 into memory at 0x600. However, since we
aren't doing the relocate code anymore, we don't know that %cx == 0 when
we hit the 'movb' to setup %cx for clearning the fake partition entry.
Thus, if %ch != 0 when the BIOS started boot0, then it would end up zeroing
a lot more memory than just 8 words. The solution is to do a word move of
$8 into %cx.
Debugging help from: David Wolfskill <dhw@whistle.com>
|
|
|
|
| |
a second time does not rebuild the binary.
|
|
|
|
|
|
|
| |
<stand.h>. Also, since bcache_strategy() used to not have a prototype,
arcdisk happily called bcache_strategy() with 6 parameters instead of 7,
leaving out the disk unit number, which is the 2nd parameter. Add in the
unit number to the bcache_strategy() call to fix this.
|
|
|
|
| |
BOOT_FORTH as it is only used if BOOT_FORTH is not defined.
|
|
|
|
| |
- Fixed comment.
|
| |
|
|
|
|
| |
some added const's.
|
|
|
|
|
| |
for lsdev when printing out slice information. Now, you only get the
sizes and LBA's of slices if you use 'lsdev -v'.
|
|
|
|
| |
- Use shift by %cl instead of five shifts by 1.
|
|
|
|
|
|
|
|
|
|
|
|
| |
sector 0 of a disk and boot0.5 is the `boot selector' which starts
from address 0x400. The IPL loads boot0.5 and boot0.5 loads bootblock
of a slice.
The boot manager stuff was developed by me (kato) with Borland C++,
and then, translated into bcc in the ports collection by Nokubi-san.
After that, boot0 has been translated into gas with the .code16
directive by Takahashi-san (nyan) and boot0.5 has been rewritten in
gas by me.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
we just loaded from the disk. The code to call it was commented out, and
it easily fit into the extra sector, but remove it anyway as it is
unneeded.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Linux kernel image, and is designed to be dropped into a Linux system
and booted via LILO. Once booted, the user is greeted by the FreeBSD
loader. This still isn't quite complete, as the the root= specification
from LILO isn't currently passed to the loader yet.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Autodetection and support of the BIOS EDD extensions to work around the
1024 cylinder limit on all but really ancient BIOS's.
- To work around some BIOS's which break when EDD is used with older drives,
we only attempt to use EDD if the cylinder is > 1023.
- Since this new code required more space than we had left, expand boot0 to
2 sectors (1024 bytes) in length.
- Add support for boot0 being multiple sectors using predefined constants.
If boot0 needs to be extended in the future, all that is required is
bumping the NUM_SECTORS constant.
- Now that we have more room to work with, add a few more fs type
descriptions while making others more verbose.
|
|
|
|
|
|
|
| |
only doing so if loader.rc does not exist. This fixes the problem where
installworld doesn't update /boot/loader.4th, resulting in device.hints not
being loaded after updating past the config(8) changes, which resulted in
mcclock0 not being probed, and a nice kernel panic during boot.
|
| |
|
|
|
|
|
| |
vulnerability and could in principle be used to upload a new kernel from the
bootloader :-)
|
| |
|
|
|
|
|
|
| |
savings of 68 bytes in boot2.
- Also add a comment warning that you can't remove the empty exit()
function.
|
| |
|
|
|
|
|
| |
zeros, it is actually the disklabel itself. boot2.ldr is simply a
placeholder in the boot2 binary.
|
| |
|
|
|
|
|
|
| |
avoid confusion.
Submitted by: George Scott <George.Scott@its.monash.edu.au>
|
| |
|
|
|
|
|
| |
monitor so that the codepath is cleaner and easier to maintain in the
future.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
use the BIOS Equipment List to determine how many hard drives are
installed and if the drive number we received in %dl is valid.
- Don't bother to disable interrupts when setting up the stack. The 8086
and beyond implicitly disable interrupts after an instruction that sets
%ss (for example, a pop or a mov) so that you can safely set %ss and %sp
in two consecutive instructions. An exception to this is the lss
instruction, which can set both registers simultaneously and thus doesn't
need this hack.
- Add support for EDD BIOS extensions to support booting off of hard drives
of nearly arbitrary length.
|
| |
|
|
|
|
|
| |
method similar to that of the loader to avoid potentially breaking older
drives in that we only use EDD if the desired cylinder is > 1023.
|
|
|
|
|
| |
Backslash-parsing is not the role of printf(3), but is provided
by the C language.
|
|
|
|
|
|
| |
pre-cursor to other markup changes.
Accepted in principle by the author.
|
|
|
|
| |
have to spend a few hours reading the code to figure all this out.
|
|
|
|
|
|
|
|
|
|
| |
- Add in support for the EDD (Enhanced Disk Drive) BIOS extensions to
use LBA mode for accessing drives past cylinder 1024. This should allow
us to load a kernel from anywhere on a newer drive up to 2 TB. Part
of this came from the PR below.
PR: i386/13847
Submitted by: Tor Egge <Tor.Egge@fast.no>
|
| |
|
|
|
|
|
|
|
|
| |
theory, this should allow the K7V Athlon motherboard to boot ok with boot
virus protection enabled. However, I have no hardware to test this. It
shouldn't break anything though. :)
Prodded by: Kelly Yancey <kbyanc@posi.net>
|