| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
user to interrupt autoboot process at all. Currently, even when
`autoboot_delay' is set to 0, loader(8) still allows autoboot process to be
interrupted by pressing any key on the console when the loader reads kernel
and modules from the disk. In some cases (i.e. untrusted environment) such
behaviour is highly indesirable and user should not be allowed to interfere
with the autoboot process at all.
Sponsored by: PBXpress Inc.
MFC after: 3 days
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Fix comment to match.
|
|
|
|
|
|
|
| |
they would leave enough elements on the stack that if you escaped to the
loader prompt and then typed 'setenv', it would pull in all of the leaked
junk and cause an exception in the environment. There still seems to be
3 leaked elements, but they don't appear to be coming from this file.
|
|
|
|
| |
did anything, so this commit should be considered a NO-OP.
|
|
|
|
|
|
| |
PR: conf/73396
Submitted by: Aleksander Fafula <alex at fafula dot com>
Approved by: scottl
|
|
|
|
|
|
| |
keyboards to work if no PS/2 keyboard is attached. The position in the
menu was chosen to avoid moving option 6 (loader prompt). This should
be a no-op on non-i386/amd64 machines.
|
|
|
|
|
| |
Those changes were made on gmirror needs, but now gmirror handles this
by itself.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
after loading such a kernel, "module_path" will be set to
an insane value. Fixed example by providing an equivalent
setting. For the record, when automatically loading a
kernel (commands "boot" and "boot-conf"), the following is
tried, in this order:
path=/boot/${kernel} file=${bootfile}
path=/boot/${kernel} file=${kernel}
path=${kernel} file=${bootfile}
path=${kernel} file=${kernel}
path=${module_path} file=${kernel}
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reduce diffs between help.common and loader(8).
Mention that boot_userconfig is currently a no-op.
|
|
|
|
| |
Reminded by: ru
|
|
|
|
|
|
|
|
| |
will prepend the current kernel booting... This prevents a problem of
loading /boot/kernel's modules when a different kernel has no modules,
but you left your module_load="YES" in loader.conf...
Reviewed by: dcs (minus the help part)
|
|
|
|
| |
Approved by: jhb
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bootp -> BOOTP
bootp.nfsroot -> BOOTP_NFSROOT
bootp.nfsv3 -> BOOTP_NFSV3
bootp.compat -> BOOTP_COMPAT
bootp.wired_to -> BOOTP_WIRED_TO
- i.e. back out the previous commit. It's already possible to
pxeboot(8) with a GENERIC kernel.
Pointed out by: dwmalone
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BOOTP -> bootp
BOOTP_NFSROOT -> bootp.nfsroot
BOOTP_NFSV3 -> bootp.nfsv3
BOOTP_COMPAT -> bootp.compat
BOOTP_WIRED_TO -> bootp.wired_to
This lets you PXE boot with a GENERIC kernel by putting this sort of thing
in loader.conf:
bootp="YES"
bootp.nfsroot="YES"
bootp.nfsv3="YES"
bootp.wired_to="bge1"
or even setting the variables manually from the OK prompt.
|
|
|
|
| |
This is accomplished via device.hints now.
|
| |
|
|
|
|
| |
mixer channels via boot loader.
|
| |
|
|
|
|
|
|
|
| |
cf. revision 1.2 of src/sys/modules/speaker/Makefile
PR: conf/65195
Submitted by: daichi
|
|
|
|
| |
its own)
|
| |
|
|
|
|
|
|
|
| |
pf/pflog/pfsync as modules. Do not list them in NOTES or modules/Makefile
(i.e. do not connect it to any (automatic) builds - yet).
Approved by: bms(mentor)
|
|
|
|
|
|
| |
- Fix hard sentence breaks.
- Quote argument to the Nd macro.
- Use Pa for filenames.
|
|
|
|
|
|
|
|
|
|
| |
is reserved by the loader, and thus any tunable name with that suffix will
be silently discarded.
Document this in the header and man page so that other developers do not
develop so many bumps on the head after banging it against the wall.
Detective work by: Mark Santcroos, grehan
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
will disable both APIC interrupt routing and SMP.
|
| |
|
|
|
|
| |
Submitted by: dcs
|
|
|
|
|
|
| |
/boot/loader.conf to see the pretty colors =-)
loader_color="YES"
|
|
|
|
|
|
| |
boot menu on and off.
Reviewed by: scottl
|
|
|
|
|
|
|
| |
'YES'.
If the user selects to escape to the loader prompt, set 'autoboot_delay'
to 'NO' so that the prompt timer doesn't run.
|
|
|
|
| |
should make our beloved friend look less like he has a massive head wound.
|
|
|
|
| |
something with it.
|
|
|
|
|
|
|
| |
examples directory to support it. This is installed only on i386 for
now. It will be enabled in a later commit.
Approved by: re
|
|
|
|
|
|
| |
PR: kern/51911
Submitted by: David Yeske <dyeske@yahoo.com>
Approved by: re
|
|
|
|
|
| |
up with this further by excluding /modules from the (default)
kern.module_path.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
queue items that can be allocated by netgraph and the number of free queue
items that are cached on a private list.
Netgraph places an upper limit on the number of queue items it may allocate.
When there is a large number of netgraph messages travelling through the
system (100k/sec and more) there is a high probability, that messages get
queued at the nodes and netgraph runs out of queue items. In this case the data
flow through netgraph gets blocked. The tuneable for the number of free
items lets one trade memory for performance.
The tunables are also available as read-only sysctls.
PR: kern/47393
Reviewed by: julian
Approved by: jake (mentor)
|
|
|
|
|
| |
Approved by: re
PR: bin/43343
|
|
|
|
|
|
| |
knew about it, though. Now it does.
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Submitted by: David Yeske <dyeske@yahoo.com>
|
|
|
|
|
|
| |
kern.cam.scsi_delay tunable/sysctl.
Reviewed by: mdodd, njl
|
| |
|