| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
bypass it. Doing otherwise did not allow compiler to detect and disable
conflicting options generated from specs.
Reported by: jake
|
|
|
|
| |
be going away after a short while but still available in ports.
|
|
|
|
| |
This doesn't break anything on my laptop and some claim it helps them.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
1) avoid immediately calling bzero() after malloc() by passing M_ZERO
2) do not initialize individual members of the global context to zero
3) remove an unused assignment of ifctx in bootpc_init()
Reviewed by: tegge
|
| |
|
|
|
|
|
|
| |
/etc/syslogd.conf -> /etc/syslog.conf
MFC after: 3 days
|
|
|
|
|
|
| |
with different vendor id.
Submitted by: Shizuka Kudo-san
|
| |
|
|
|
|
|
|
|
| |
has the same product id, but different vendor id. It also appears
that the MELCO's id should be 0x18a instead of 0x8a01. Fix this.
Submitted by: Shizuka Kudo-san
|
|
|
|
|
| |
to ${DESTDIR}${KODIR}.old if we have booted from ${DESTDIR}${KODIR},
and always keep kern.bootfile in a good shape.
|
|
|
|
|
|
| |
in order not to shadow err(3).
Tested by: make universe
|
|
|
|
| |
i386/i386/pmap.c 1.423
|
|
|
|
|
|
|
| |
- Normalize doRELEASE to avoid seeing "`ftp.1' is up to date." warning
when doing "make rerelease", and ftp.1 was already built.
Reviewed by: jhb
|
|
|
|
|
|
|
|
|
| |
netstat -s -p pim
2. Print information about the bandwidth meters installed in the kernel with
netstat -g
Submitted by: Pavlin Radoslavov <pavlin@icir.org>
|
|
|
|
| |
Submitted by: Pavlin Radoslavov <pavlin@icir.org>
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| | |
submitted to the vendor.
Obtained from: iwasaki
|
| |
| |
| |
| | |
Submitted by: Pavlin Radoslavov <pavlin@icir.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Disabled by default. To enable it, the new "options PIM" must be
added to the kernel configuration file (in addition to MROUTING):
options MROUTING # Multicast routing
options PIM # Protocol Independent Multicast
2. Add support for advanced multicast API setup/configuration and
extensibility.
3. Add support for kernel-level PIM Register encapsulation.
Disabled by default. Can be enabled by the advanced multicast API.
4. Implement a mechanism for "multicast bandwidth monitoring and upcalls".
Submitted by: Pavlin Radoslavov <pavlin@icir.org>
|
| | |
|
| |
| |
| |
| | |
negative value of the index of the new file, so just use -1.
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| | |
Obtained from: acpicatools port by Iwasaki-san
|
| |
| |
| |
| |
| | |
Add an explicit range check to those same arguments to reduce risk of
cardiac arrest in future code readers.
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| | |
that uses strupr().
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
ushort. In most of these files, there was a mixture of both styles and
this change just makes them self-consistent.
Requested by: bde (kern_ktrace.c)
|
| | |
|
| |
| |
| |
| |
| |
| | |
struct to be able to turn polling on/off.
Tested by: Larry Rosenman <ler@lerctr.org>
|
| |
| |
| |
| | |
would follow the 6 valid chars of the table entry.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tools such as chmod(1) and ls(1) when it comes to acting on objects
that have POSIX.1e extended ACLs. Specifically, discuss the
substitution of the mask entry for the group entry in the mode
representation of the ACL. Differently worded from the submission,
and could probably use further refinement.
PR: 55319
Submitted by: Grzegorz Czaplinski <G.Czaplinski@prioris.mini.pw.edu.pl>
|
| |
| |
| |
| |
| | |
PR: 55318
Submitted by: Grzegorz Czaplinski <G.Czaplinski@prioris.mini.pw.edu.pl>
|
| |
| |
| |
| |
| | |
that are not currently closing when the interface is configured down
will be brough up as soon as the interface is configured up.
|
| |
| |
| |
| |
| | |
since the bootblocks have their own local includes. Sorry for breaking
world.
|
| |
| |
| |
| |
| |
| |
| | |
semaphore and doing so can lead to a possible reversal. WITNESS would have
caught this if semaphores were used more often in the kernel.
Submitted by: Ted Unangst <tedu@stanford.edu>, Dawson Engler
|
| |
| |
| |
| |
| |
| |
| | |
and up commands. When configuring the interface down only the
connections that are currently closing are deleted from the connection
table. When the interface is configured up, all connections that
are in the table are re-opened.
|
| |
| |
| |
| |
| |
| | |
connections that have been open (and were not closing) when
the interface was stopped. This makes the behaviour of fatm(4) more like
the behaviour of en(4).
|
| |
| |
| |
| |
| | |
and to simplify things. This is only valid until we start supporting
state-dependent encodings.
|
| | |
|
| |
| |
| |
| | |
as a wrapper around wcsrtombs().
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
happens, the context of the interrupted thread is exported to
userland. Unlike most contexts, it will be an async context and
we cannot easily use our existing functions to set such a
context.
To avoid a lot of complexity that may possibly interfere with
the common case, we simply let the kernel deal with it. However,
we don't use the EPC based syscall path to invoke setcontext(2).
No, we use the break-based syscall path. That way the trapframe
will be compatible with the context we're trying to restore and
we save the kernel a lot of trouble. The kind of trouble we did
not want to go though ourselves...
However, we also need to set the threads mailbox and there's no
syscall to help us out. To avoid creating a new syscall, we use
the context itself to pass the information to the kernel so that
the kernel can update the mailbox. This involves setting a flag
(_MC_FLAGS_KSE_SET_MBOX) and setting ifa (the address) and isr
(the value).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
when we create contexts. The meaning of the flags are documented in
<machine/ucontext.h>. I only list them here to help browsing the
commit logs:
_MC_FLAGS_ASYNC_CONTEXT
_MC_FLAGS_HIGHFP_VALID
_MC_FLAGS_KSE_SET_MBOX
_MC_FLAGS_RETURN_VALID
_MC_FLAGS_SCRATCH_VALID
Yes, _MC_FLAGS_KSE_SET_MBOX is a hack and I'm proud of it :-)
|