| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
details of libkvm, and just tell what the getbootfile(3) function
will return, by using the text from netstat(1) and dmesg(8).
|
| |
|
|
|
|
| |
the getopt() case statement).
|
|
|
|
|
|
|
| |
sysctl(3) interface in kvm(3).
- Document the correct default when no -N is specified.
- Remove stale reference to /var/db/kvm_kernel.db.
- Remove stale reference to /var/run/dev.db.
|
|
|
|
|
| |
"corefile" argument, to access the running system via sysctl(3)
if possible, thus not requring special setgid privileges.
|
| |
|
| |
|
|
|
|
| |
it to the build.
|
|
|
|
|
|
|
| |
MAC support on the file system, if supported, which causes MAC to treat
each object as having its own label, rather than using a single label
for all objects on the file system. This doesn't have to be used in
combination with the tunefs/newfs flags -- it's an alternative.
|
| |
|
|
|
|
| |
(this is a probably temporary option, and is not to be documented)
|
|
|
|
|
|
| |
the "Take the appropriate action" section).
Obtained from: the sysutils/pkill port
|
|
|
|
|
|
| |
needed because off_t == __int64_t, while size_t == __uint64_t. This
also compiles with WARNS=5 on amd64, but I haven't tested the other
platforms yet.
|
| |
|
| |
|
|
|
|
| |
a cross-reference to killall(1).
|
|
|
|
|
|
|
|
|
|
|
|
| |
what are supported in `ps':
-M Extract values associated with the name list from the
specified core instead of the default /dev/kmem.
-N Extract the name list from the specified system instead
of the default /kernel.
Written by: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org>
Obtained from: the sysutils/pkill port
|
|
|
|
|
|
|
| |
when compiling with WARNS=3
Written by: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org>
Obtained from: the sysutils/pkill port
|
|
|
|
|
| |
Written by: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org>
Obtained from: the sysutils/pkill port
|
|
|
|
|
|
|
| |
wild. This one is marketed by D-Link model DWL-650, but appears to be
a ISL3710P-10 under the hood.
Reported by: Brian O'Shea
|
| |
|
|
|
|
| |
Reported by: Brian O'Shea
|
|
|
|
|
| |
Submitted by: kan
Approved by: alfred
|
|
|
|
| |
- Reenable boot floppies for Alpha.
|
| |
|
| |
|
|
|
|
|
|
|
| |
2. Check for bad return value from twe_map_request in places where there
was no checking.
Reviewed by: ps
|
|
|
|
|
|
|
|
|
| |
straight from NetBSD (except to add the RCS-ID lines for FreeBSD).
These will probably require a few updates before they are added to
the FreeBSD buildworld. I might MFC these to 4.x-stable after 4.10.
Discussed on: freebsd-arch
Obtained from: NetBSD (and OpenBSD also has these)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
objects rather than synchronization objects. When a sync object is
signaled, only the first thread waiting on it is woken up, and then
it's automatically reset to the not-signaled state. When a
notification object is signaled, all threads waiting on it will
be woken up, and it remains in the signaled state until someone
resets it manually. We want the latter behavior for NDIS events.
- In kern_ndis.c:ndis_convert_res(), we have to create a temporary
copy of the list returned by BUS_GET_RESOURCE_LIST(). When the PCI
bus code probes resources for a given device, it enters them into
a singly linked list, head first. The result is that traversing
this list gives you the resources in reverse order. This means when
we create the Windows resource list, it will be in reverse order too.
Unfortunately, this can hose drivers for devices with multiple I/O
ranges of the same type, like, say, two memory mapped I/O regions (one
for registers, one to map the NVRAM/bootrom/whatever). Some drivers
test the range size to figure out which region is which, but others
just assume that the resources will be listed in ascending order from
lowest numbered BAR to highest. Reversing the order means such drivers
will choose the wrong resource as their I/O register range.
Since we can't traverse the resource SLIST backwards, we have to
make a temporary copy of the list in the right order and then build
the Windows resource list from that. I suppose we could just fix
the PCI bus code to use a TAILQ instead, but then I'd have to track
down all the consumers of the BUS_GET_RESOURCE_LIST() and fix them
too.
|
|
|
|
| |
Submitted by: ru
|
|
|
|
| |
Approved by: imp (mentor)
|
|
|
|
| |
It was used in FreeBSD 4.x, but now we're using cr_canseesocket().
|
|
|
|
| |
I meant to do this a week ago, but I forgot.
|
|
|
|
| |
Approved by: imp (mentor)
|
|
|
|
| |
Approved by: imp (mentor)
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Reviewed by: ru
|
| | |
|
| |
| |
| |
| | |
Nudged by: ru
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Compute the payload checksum for a locally originated IP multicast where
God intended, in ip_mloopback(), rather than doing it in ip_output() and
only when multicast router is active. This is more correct as we do not
fool ip_input() that the packet has the correct payload checksum when in
fact it does not (when multicast router is inactive). This is also more
efficient if we don't join the multicast group we send to, thus allowing
the hardware to checksum the payload.
|
| |
| |
| |
| |
| |
| | |
within the running system.
Sponsored by: Ralf the Wonder Llama
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
which pulls a job off a thread work queue (assuming it hasn't run yet).
This is needed for KeRemoveQueueDpc().
- In subr_ntoskrnl.c, implement KeInsertQueueDpc() and KeRemoveQueueDpc(),
to go with KeInitializeDpc() to round out the API. Also change the
KeTimer implementation to use this API instead of the private
timer callout scheduler. Functionality of the timer API remains
unchanged, but we get a couple new Windows kernel API routines and
more closely imitate the way thing works in Windows. (As of yet
I haven't encountered any drivers that use KeInsertQueueDpc() or
KeRemoveQueueDpc(), but it doesn't hurt to have them.)
|
| |
| |
| |
| | |
with a larger kernel stack.
|