| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
assure backward compatibility (conditional on !BURN_BRIDGES), look it up
by its old name first, and log a warning (but accept the setting) if it
was found. If both the old and new name are defined, the new name takes
precedence.
Also export vm.kmem_size as a read-only sysctl variable; I find it hard to
tune a parameter when I don't know its default value, especially when that
default value is computed at boot time.
|
|
|
|
|
|
|
|
|
| |
the root path. This is reported to make non-PXE netbooting, such as
is used on sparc64 systems, work correctly when the TFTP server is
not the same as the root server.
PR: kern/57328
Submitted by: Per Kristian Hove <Per.Hove@math.ntnu.no>
|
|
|
|
| |
Also some minor style cleanups.
|
|
|
|
|
| |
Submitted by: Andre Guibert de Bruet <andy@siliconlandmark.com>
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
(It does not modify NSFBUFS, but just overrides it if set.)
Approved by: re (blanket)
|
|
|
|
|
|
|
|
| |
common code, the non-trivial part is #ifdef'ed and only executes when
loading amd64 kernels. The rest is trivial but needed for the the amd64
case. (Two variables changed from char ** to Elf_Addr).
Approved by: re (amd64 "low-risk" stuff)
|
|
|
|
| |
instructions on the main help screen for disabling it.
|
|
|
|
|
|
| |
PR: docs/40234
Submitted by: Chris Pepper <pepper@rockefeller.edu> (mostly)
MFC After: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
things over floppy size limits, I can exclude it for release builds or
something like that. Most of the changes are to get the load_elf.c file
into a seperate elf32_ or elf64_ namespace so that you can have two
ELF loaders present at once. Note that for 64 bit kernels, it actually
starts up the kernel already in 64 bit mode with paging enabled. This
is really easy because we have a known minimum feature set.
Of note is that for amd64, we have to pass in the bios int 15 0xe821
memory map because once in long mode, you absolutely cannot make VM86
calls. amd64 does not use 'struct bootinfo' at all. It is a pure loader
metadata startup, just like sparc64 and powerpc. Much of the
infrastructure to support this was adapted from sparc64.
|
| |
|
|
|
|
|
|
|
|
|
| |
Move the remaining bits of <sys/diskslice.h> to <i386/include/bootinfo.h>
Move i386/pc98 specific bits from <sys/reboot.h> to
<i386/include/bootinfo.h> as well.
Adjust includes in sys/boot accordingly.
|
|
|
|
| |
Submitted by: Stefan Farfeleder <stefan@fafoe.dyndns.org> via -doc.
|
|
|
|
|
|
|
| |
nearby grammar fixup that saves a line of display while in the loader
(help set tunables), but reuses the line for kern.ipc.nsfbufs.
Approved by: roam
|
|
|
|
|
| |
up with this further by excluding /modules from the (default)
kern.module_path.
|
|
|
|
| |
both ufs1 and ufs2 support) on i386.
|
|
|
|
|
|
| |
so that boot loader once again will fit.
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
The former was incorrect and gave an `unknown oid' error.
|
|
|
|
|
|
|
|
| |
read from the raw kld files.
Submitted by: Hartmut Brandt <brandt@fokus.gmd.de>
PR: 46870
Tested on: alpha (obrien), i386, sparc64
|
|
|
|
| |
Requested by: Nate Lawson <nate@root.org>
|
|
|
|
| |
versions from the same basic function.
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the old 8-bit fs_old_flags to the new location the first time that the
filesystem is mounted by a new kernel. One of the unused flags in
fs_old_flags is used to indicate that the flags have been moved.
Leave the fs_old_flags word intact so that it will work properly if
used on an old kernel.
Change the fs_sblockloc superblock location field to be in units
of bytes instead of in units of filesystem fragments. The old units
did not work properly when the fragment size exceeeded the superblock
size (8192). Update old fs_sblockloc values at the same time that
the flags are moved.
Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk>
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
| |
Approved by: re
PR: bin/43343
|
|
|
|
|
|
|
| |
hw.pci.allow_unsupported_io_range.
Submitted by: Hiten Pandya <hiten@angelica.unixdaemons.com>
Approved by: re (murray)
|
|
|
|
|
|
|
|
| |
Sysctl of same name to reflect status.
Submitted by: jhb
Approved by: re (murray)
MFC after: 1 day
|
|
|
|
|
|
|
|
|
| |
divide/remainder calls. For reasons not resolved, compiling the
relevant routines from libkern into boot2 results in stack corruption.
Do the simple thing: Don't use 64bit divide/remainder operations.
Sponsored by: DARPA & NAI Labs
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
|
|
| |
Fix device hints entry for disabling acpi(4).
This also should fix the arbitration with apm(4) when both drivers
are enabled.
Note that your /boot/device.hints needs to be updated if you want to
stop auto-loading acpi.ko or disable acpi(4).
|
|
|
|
| |
never updated for the metadata infrastructure.
|
|
|
|
|
|
| |
this was quite broken, it never was updated for metadata support.
The a.out kld file support was never really used, as it wasn't necessary.
You could always load elf kld's, even in an a.out kernel.
|
|
|
|
| |
bits in rev. 1.45.
|
|
|
|
|
| |
Document the approved ways of disabling it.
Submitted by: Daniel O'Connor <doconnor@gsoft.com.au>
|
|
|
|
| |
to pick up, ala pxe.
|
|
|
|
| |
Most of them are not in a future tense already.
|
| |
|
|
|
|
|
|
|
|
| |
the actual code. Both use a ";" (not a ",") to delimit entries.
PR: 39679
Submitted by: Cyrille Lefevre <cyrille.lefevre@laposte.net>
MFC after: 3 days
|
|
|
|
| |
ufs2 filesystems seems to work fine.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
filesystem expands the inode to 256 bytes to make space for 64-bit
block pointers. It also adds a file-creation time field, an ability
to use jumbo blocks per inode to allow extent like pointer density,
and space for extended attributes (up to twice the filesystem block
size worth of attributes, e.g., on a 16K filesystem, there is space
for 32K of attributes). UFS2 fully supports and runs existing UFS1
filesystems. New filesystems built using newfs can be built in either
UFS1 or UFS2 format using the -O option. In this commit UFS1 is
the default format, so if you want to build UFS2 format filesystems,
you must specify -O 2. This default will be changed to UFS2 when
UFS2 proves itself to be stable. In this commit the boot code for
reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c)
as there is insufficient space in the boot block. Once the size of the
boot block is increased, this code can be defined.
Things to note: the definition of SBSIZE has changed to SBLOCKSIZE.
The header file <ufs/ufs/dinode.h> must be included before
<ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and
ufs_lbn_t.
Still TODO:
Verify that the first level bootstraps work for all the architectures.
Convert the utility ffsinfo to understand UFS2 and test growfs.
Add support for the extended attribute storage. Update soft updates
to ensure integrity of extended attribute storage. Switch the
current extended attribute interfaces to use the extended attribute
storage. Add the extent like functionality (framework is there,
but is currently never used).
Sponsored by: DARPA & NAI Labs.
Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
| |
Factor the ufs reading code out of the i386/boot2 loader so it can
be reused by for instance sparc64.
Sponsored by: DARPA and NAI Labs.
|
|
|
|
|
|
| |
Translators can ignore this commit.
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
| |
up the module_path string, we would walk one past the end of the buffer.
This hurting ia64 originally, but it was probably also happening on i386
occasionally as well. The effects were usually harmless, it would add
bogus "binary" search directories to the places it actually looked for
files.
|
|
|
|
|
| |
PR: 36308
Submitted by: dcs
|
|
|
|
| |
Elf_Hashelt.
|
|
|
|
|
| |
in the kernel side of things some time ago. The hash table entries are
always 32 bits wide, even on 64 bit machines.
|
| |
|