| Age | Commit message (Collapse) | Author |
|---|
|
|
|
netbooting from an rbootd server.
In this case, the pdc masquerades the boot device as a disk class device,
although keeping the device_path correct.
So, rather than trusting the device class the pdc reports, trust what the
kernel just configured - it must know better.
|
|
|
|
|
|
|
|
Also, better probe for leds on keyboard.
|
|
|
|
|
|
|
|
Thankfully HP's ps/2 mouse have no specific behaviour.
|
|
irq, but hppa has no generic shared interrupt code, we need to make sure
that gsckbc devices using the same irq know each other, and will pass
the interrupt notification to each other.
This allow a mouse and a keyboard to work together...
|
|
(does not solve the C++ ctor problem, sorry)
|
|
prom; tested on type4 by me and miod on type1
|
|
|
|
|
|
|
|
|
|
|
|
kernel/3097, waiting to hear).
|
|
|
|
|
|
|
|
|
|
shadows a global. rename.
|
|
des_crypt(3): Eric Young
aac(4): Michael Smith, BSDi, Niklas Hallqvist; ok niklas@
bktr(4): Amancio Hasty, Roger Hardiman
getopt(1): Henry Spencer (public domain)
pcnfds(8): Sun
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mcbride@, dhartmei@ ok
|
|
mcbride@, dhartmei@ ok
|
|
millert@ ok
|
|
the boundary could never ever be accidentally matched inside base64
data. Based on conversation with markus@, deraadt@, henning@. OK
deraadt@, henning@
|
|
Reduce the size of a GENERIC kernel by ~190k
Remove the nasty pointer/bus_space_handle_t casts
Adds debug bus_space code including the ability to trace
bus operations (it actually works now).
The following rules are now followed (and verfified by the debug
code):
1. A "bus_space_handle_t" may only be used with the
"bus_space_tag_t" that created it.
2. Only "bus_space_map()" may create "bus_space_handle_t"s.
3. A "bus_space_handle_t" may not be modified after it has
been created (other than being destroyed by "bus_space_unmap()").
Thanks to help from mcbride, marc, jason, drahn, to anyone that might
have slipped my mind at the moment.
ok jason@, deraadt@
|
|
|
|
Fix up default route selection by
a) Forcing user to explicitly chose 'dhcp' as a mechanism for
specifying a default route, rather than guessing based on one or more
interfaces being configured by dhcp.
b) If the user specified default route does not work, re-present the
existing default route rather than losing it.
c) Move default route selection to after nameserver activation so the
user can specify a hostname as the default route.
Change /etc/netstart so that /etc/mygate wins if a default route was
already specified (i.e. by dhcp).
ok deraadt@.
|
|
deraadt@ drahn@ ok, miod@ ok a while ago.
A few spelling tweeks, '{}' elimination, syntax error corrections
after ok.
Tested with HFS install and HFS upgrade. More testing, especially of
MBR installs, would be good.
|
|
|
|
to dale); espie@ ok
|
|
|
|
(okay theo, kettenis)
|
|
|
|
|
|
|
|
ETag (entity tag) header value. Instead of including
the file modification date, inode, file size, etc.
directly in the ETag header, return a SHA1 hash of
these values instead.
This SHA1 hash is initialized with a pseudorandom
secret, so that it's harder to brute force inode
numbers. This initialization secret is saved in a
file called "etag-state" in the httpd chroot logs/
directory, so that the ETag header values are consistent
across httpd restarts (if the secret were different
each time httpd started, ETags would change unnecessarily
and thereby cause caches to refresh unnecessarily).
An additional change is introduced: we add the dev
number to the hash when (and only when) we add the
inode number to the hash.
Before:
HTTP/1.1 200 OK
Server: Apache/1.3.27 (Unix) mod_ssl/2.8.12 OpenSSL/0.9.7-beta3
ETag: "b10d3-1e59-3e49cbe4"
In this case, we can tell the inode number of index.html
is is b10d3 hex.
After:
HTTP/1.1 200 OK
Server: Apache/1.3.27 (Unix) mod_ssl/2.8.12 OpenSSL/0.9.7-beta3
ETag: "3f3b3cb2ce2e278087960b3be6a6e9844166e371"
Idea and solution by deraadt@. OK deraadt@, henning@. Any
bugs are my fault :)
|
|
|
|
server code into the client; ok provos@
|
|
|
