Age | Commit message (Collapse) | Author |
|
look further at the signature if we can actually compare things)
|
|
then packages with an older version will be filtered out.
|
|
|
|
fails after an escape character, and while there put explicit casts to
l1_command_build() variadic arguments.
|
|
|
|
ajacoutot@.
|
|
the MAC event register.
fix from atte dot peltomaki at iki dot fi
tested by me on 5708 and 5709
|
|
expanded version of a diff from Vadim Zhukov.
ok henning@ claudio@
|
|
|
|
- add some unknown Intel devices in dmeslog from infinst911_autol.zip
ok jsg@
|
|
ok jmc@
|
|
|
|
|
|
|
|
ok espie
|
|
|
|
|
|
|
|
so that a bridge-etherip-tunnel host can join into the bridge itself.
It is ridiculous that this capability was missing from our network
stack portfolio, considering we have bgp and ospf daemons...
discussed at length with claudio
|
|
internally when and where required. Macros in <stdio.h> are updated
to automatically call the underlying functions when the process is
threaded to obtain the necessary locking. A private mutex is added
to protect __sglue, the internal list of FILE handles, and another
to protect the one-time initialization. Some routines in libc that
use getc() change to use getc_unlocked() as they're either protected
by their own lock or aren't thread-safe routines anyway.
committing on behalf of and okay guenther@ now that we have install
media space available.
|
|
|
|
|
|
|
|
no longer have a direct mapping between structures saved in aliases/virtual
db and structures used at runtime during expansion.
side effects ? struct alias is smaller, databases are smaller and it is no
longer necessary to rebuild aliases/virtual databases each time jacekm@ or
I make changes to some obscure structure used indirectely during expansion
rebuild databases, flush queues, make clean
|
|
for IP35 systems with IOC3 onboard Ethernet to get their Ethernet address
since it's no longer stored as an owmac(4) device on the IOC3 device itself.
|
|
load. This makes it possible to load bsd.rd on the RB600.
Bump version number.
ok dms@
|
|
doesn't take advantage of the new structure yet, but this was a needed
change for upcoming improvements.
- introduce aliasestree_{lookup,insert,remove} to the aliases api
- rename queue_generate_id() to generate_uid() and move it to utils.c as
it is used all over the place and not only in queue
tree idea discussed with jacekm@, if you update rebuild aliases db, make
clean and flush queue
|
|
ok miod@, dms@
|
|
|
|
which is probably the most complex code in smtpd right now. no longer use a
single list to hold aliases to be resolved and resolved aliases, and do not
use struct alias to hold resolved aliases. instead use a delivery list that
is a list of struct path, and populate it with resolved aliases.
idea discussed with jacekm@, this needs some testing to make sure it does
not introduce a regression with aliases. flush your queue and make clean.
|
|
ok deraadt
|
|
cache size; might skirt some cache hazards.
ok deraadt@
|
|
attach, print it, and decide how many RX descriptors to use accordingly.
|
|
lack of such hardware.
|
|
Move stuff from being a fatal error to an error that displays at end, together
with an error code.
|
|
|
|
|
|
- wakeup device earlier in read_prom
- fix ampdu_tx_start (not used yet)
- initialize ht_caps field and rx mcs set (not used yet)
- start processing compressed blockack notifications (does nothing for now)
|
|
non-existent location...
|
|
|
|
create updatesets with nothing but a hint of what to install. Have
Update.pm do the dirty work.
More importantly, make Tracker aware of what's going on.
|
|
|
|
full-duplex streams. Fixes, streams with different modes not
starting simultaneously.
|
|
was breaking non GNUC defining compilers.
Came up during a conversation with ragge@, positive
comments from several.
|
|
|
|
|
|
as the onboard ioc device, if one has already been found on this node.
Also, on Origin 300, do not attempt to attach the PS/2 controller on the
onboard ioc(4) since PS/2 ports are not wired.
|
|
|
|
|
|
TGT_ORIGIN, which enables support for all IP27 and IP35 systems. The original
two options have always been used together, and go back to when pefo thought
supporting multiple nodes would be significant work. Since an Origin 200
can be a dual-node system, making a distinction between single node and
multiple node systems is a moot point anyway.
Be sure to rerun config(8) before rebuilding a kernel.
|