Age | Commit message (Collapse) | Author |
|
|
|
|
|
ever seen one, but the spec describes how to do it.
|
|
of the machine we are running on in there.
makes my many green lines easier to deal with without using fiddly options to
set it.
ok nicm@
|
|
ok krw@ ramdisks checked by deraadt@
|
|
supplied from ftplist.cgi, ask if the user wants to set it accordingly.
Idea from deraadt@, feedback from sthen@, guenther@
ok deraadt@, krw@ (slightly different version)
|
|
|
|
|
|
|
|
|
|
but warn, set up some default values, and prod on.
Unbreaking the ports build for textproc/sgmlformat;
reported by naddy@, thanks.
|
|
with codecs like the ALC269 that have pins that need to be configured but
don't have an associated mixer item.
ok jakemsr@
|
|
|
|
|
|
modified with setenv -g) rather than with the environment tmux started
with.
|
|
function.
|
|
|
|
|
|
Fixing the x11/scrotwm build.
Problem reported by naddy@, thanks.
|
|
files at a time.
OpenCVS does the following:
# touch a b c
# opencvs add a b c
opencvs add: scheduling file 'a' for addition
opencvs add: use 'opencvs commit' to add this file permanently
opencvs add: scheduling file 'b' for addition
opencvs add: use 'opencvs commit' to add this file permanently
opencvs add: scheduling file 'c' for addition
opencvs add: use 'opencvs commit' to add this file permanently
This behaviour was added in -r 1.48 of add.c file.
This commit makes OpenCVS behave like GNU cvs:
# touch a b c
# opencvs add a b c
opencvs add: scheduling file 'a' for addition
opencvs add: scheduling file 'b' for addition
opencvs add: scheduling file 'c' for addition
opencvs add: use 'opencvs commit' to add these files permanently
ok deraadt@, xsa@
|
|
size chosen by the user, and not the suggested size; move to bigger
blocksize in two steps; ok krw@
|
|
The mandoc_char(7) manual is supposed to document standard characters
for man(7) and mdoc(7), and these are not standard in any sense.
So move the documentation to an implementation-specific manual.
noticed by kristaps@ and merged in 1.9.22
ok jmc@ who also noticed that \*(TH broke the nroff -Tps build
|
|
|
|
first name is used, and remove any #define foo_region foo compatibility
defines.
Also, on sparc64, do not provide a `raw' version of bus_space_copy.
|
|
|
|
|
|
is not yet available.
The combo WiFi/WiMAX devices need a separate firmware too (that is not
yet available), so do not use the firmware for WiFi-only devices as it
will likely not work.
Change the way active chains (the ones that have an antenna plugged in)
are detected to work around a firmware bug which could make us mark
non-existing chains as active.
|
|
|
|
|
|
|
|
It will require a lot of work in athn(4) to be supported though,
because of important differences (in DMA and registers) with
AR5008/AR9001/AR9002 series.
|
|
affect RT3572.)
Found (again!) by Yao Zhao (dragonlinux at gmail dot com)
|
|
settimeofday() does, so move those bits into settime()
"I like it" deraadt@
|
|
ever tried recording big endian samples with fms.
|
|
|
|
Diff from Tim van der Molen <tbvdm at xs4all dot nl>, thanks!
ok kristaps@
|
|
requested, just use a supported sample rate. makes paramter
negotiation much easier. problem noted and patch tested on
several sb(4) devices by J.C Roberts, thanks.
|
|
Currently a noop as the code for RL_FLAG_MACSLEEP hasn't been added yet.
From FreeBSD via Brad.
|
|
system, or something else.
Derive the fdisk instructions in `use the whole disk for OpenBSD' from this
knowledge, and set up a 32MB ext2fs partition on Gdium, and the 1MB elsewhere
(as was already been done).
On Gdium, format this partition in fancy mode (-O 1) and 4KB blocks, so that
PMON has a chance to load files larger than 4MB (such as bsd.rd)
without failing in a pathetic way, and also copy the kernel image to the ext2fs
partition after the installation has completed.
Note that, apart from creating a larger ext2fs partition on Gdium, there should
be no need for this.
Unfortunately, since regular PMON does not have ext2fs code, Lemote wrote its
own code to access ext2 filesystems. Saying that this code is full of
shortcomings and bugs would be an understatement. What is worse is that this
code has been written by people with no knowledge (or even insight) of how
error conditions ought to be handled, and their ext2fs code will happily
abort a read upon error with no error; if one does not compare the final
read size to the file size obtained by stat(), there is no way to figure out
that the read has been aborted. Of course since regular (upstream) PMON code
is written correctly, it does not expect this, so it is easy to end up with
PMON not loading a kernel image completely, yet proceeding happily to transfer
control to this broken image.
I guess the morale behind this is that system software is too difficult to get
done correctly, to be done by hardware people.
|
|
prompted by a suggestion from Rod Whitworth. ok jmc@ "Cool!" Rod.
|
|
|
|
ok deraadt@
|
|
excepting the tbl(1) pages, which are less than twenty.
"commit the diff that enables it, now" deraadt@
|
|
- clear initrd signature before returning to PMON or to the loaded kernel
- fail /etc/boot.conf access when loading from an initrd image, instead of
letting it point to the beginning of the kernel image and have the code
complain of lines being too long.
Bump minor version.
|
|
|
|
|
|
ok deraadt@
|
|
ok deraadt@
|
|
use the first, discard the second, and warn. No need to bail out.
ok deraadt@
|
|
* a missing NAME section in mdoc(7) need not be fatal
ok deraadt@
|