| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
The driver doesn't look any less safe without Giant than with, and works
with IS_MPSAFE set to 1 here, so others should probably test it as such.
|
| |
|
|
|
|
|
| |
# Yes, this is the right thing to do: we keep assignments for 4.x here
# to document them, and Sam has a nearly completed driver.
|
| |
|
|
|
|
| |
be necessary here. Also, use killproc() instead of psignal().
|
|
|
|
|
| |
may block to swap in p1. Instead, call _PHOLD earlier, at a
point where the only lock held happens to be p1's.
|
|
|
|
|
| |
in pseudofs. Moreover, PHOLD() may block between the p_candebug()
access check and the actual operation.
|
|
|
|
|
|
|
|
|
|
|
| |
1. Process p1 is currently being swapped in.
2. Process p2 calls linux_ptrace(PTRACE_GETFPXREGS, p1_pid, ...)
3. After acquiring a reference to FIRST_THREAD_IN_PROC(p1),
p2 blocks in faultin() while p1 finishes being swapped in.
This means p2 won't get back the lock on p1 until after p1's
threads are runnable.
4. After p1 is swapped in, the first thread in p1 exits.
5. p2 now uses its dangling reference to p1's first thread.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ports/ tree on it. This makes putting the ports/ tree on disc2 at
all dependent on the NOPORTREADMES knob as well as the NOPORT knob
(at the moment NOPORT may be set while NOPORTREADMES isn't, that
should probably be revisited). And it hardcodes ia64 for NOPORTREADMES
by request the ia64 release builder.
While here really get rid of the temp file 'make index' leaves behind.
Tested by: i386 and ia64 'make release'
Reviewed by: marcel
MFC after: 1 day
|
|
|
|
|
| |
For novice users, beastie.4th can just do it. Expert users can
read ACPI instructions by typing "help ACPI".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
after loading such a kernel, "module_path" will be set to
an insane value. Fixed example by providing an equivalent
setting. For the record, when automatically loading a
kernel (commands "boot" and "boot-conf"), the following is
tried, in this order:
path=/boot/${kernel} file=${bootfile}
path=/boot/${kernel} file=${kernel}
path=${kernel} file=${bootfile}
path=${kernel} file=${kernel}
path=${module_path} file=${kernel}
|
|
|
|
|
|
|
|
|
|
|
| |
Document this. These changes make it possible to write something like
set device "!/usr/bin/rfcomm_sppd -a BD_ADDR"
inside the /etc/ppp/ppp.conf file. Very convenient for the users :)
Submitted by: Konstantin Stepanenkov <kstepanenkov AT oilspace DOT com>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
the tool one needs to partition a disk is more important than some poor
man's network interface.
|
| |
|
| |
|
|
|
|
| |
Submitted by: many
|
|
|
|
| |
add corrupt ipfw rules would not potentially panic the system or worse.
|
| |
|
|
|
|
| |
happens if $prompt is unset.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MP machines (hopefully). CPU timers are OK on UP machines but we
don't keep the timers in sync on MP machines so if the CPU's timer
is chosen as the primary timecounter it's possible for time to
not be monotonically increasing because different CPU's counters
may be used at different times. But the CPU's counters are otherwise
one of the higher quality counters available. So, on UP machines
we'll use a relatively high quality value but on MP machines we'll
use a quality that should prevent the CPU's counters from being chosen.
Requested by: green (who did the first version of the patch)
Reviewed by: marius, green
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
the structure space had been obtained from malloc() its contents is
random garbage. The choice of value being set is part of a larger effort
to solve some timecounter issues on MP machines (while working on that
we noticed this problem).
Noticed by: marius
Reviewed by: marius, green
MFC after: 3 days
|
| |
|
|
|
|
| |
the `?' command.
|
| |
|
|
|
|
|
| |
Reduce diffs between help.common and loader(8).
Mention that boot_userconfig is currently a no-op.
|
|
|
|
|
|
| |
currently not possible to do this while the volume is mounted.
MFC in: 1 week
|
| |
|
|
|
|
|
|
|
| |
the new subr_unit.c code.
For now assert Giant in ttycreate() and ttyfree(). It is not obvious that
it will ever pay off to lock these with anything else.
|
|
|
|
|
|
|
|
| |
of relying on the symlink in ${DESTDIR}/etc/namedb.
This is functionally equivalent, but doesn't rely on the symlink to work.
Requested by: ru
|
|
|
|
|
|
|
|
|
|
| |
- Document better what the -C option means.
- The -c option is currently a no-op.
- The -D and -h options do not allow switching between
single/dual console modes and internal/video consoles.
(This used to be true for the old biosdisk boot code,
but now they just force the multiple consoles mode and
serial console, respectively.)
|
|
|
|
|
|
|
|
|
| |
authoritative servers.
2. Add an IPv4 listen-on option for 127.0.0.1, which is appropriate
for the default use as a local resolver.
3. Add a commented out listen-on-v6 option.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
o Remove an assumption sizeof(struct timeval) == 8 (this is not
true on sparc64).
Reviewed by: imp, -hackers
Obtained from: NetBSD (rev. 1.75)
MT5 after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allocation is always lowest free unit number.
A mixed range/bitmap strategy for maximum memory efficiency. In
the typical case where no unit numbers are freed total memory usage
is 56 bytes on i386.
malloc is called M_WAITOK but no locking is provided (yet). A bit of
experience will be necessary to determine the best strategy. Hopefully
a "caller provides locking" strategy can be maintained, but that may
require use of M_NOWAIT allocation and failure handling.
A userland test driver is included.
|
|
|
|
|
|
|
|
|
| |
synapticshw_t structure and the MOUSE_SYN_GETHWINFO ioctl() which
reads it.
MT5 candidate
Approved by: njl
|
|
|
|
|
| |
if_em "wedging" problem, large numbers of perror() calls impacts send
performance. As such, just count the error, don't print it.
|
|
|
|
|
|
| |
characteristic system calls. I've been sending this to people for
a while, and figured it would be more efficient to just put it in
CVS.
|
|
|
|
| |
Submitted by: Manfred Antar <null@pozo.com>
|
|
|
|
| |
Submitted by: Roselyn Lee
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
date: 2004/09/26 02:01:27; author: sam; state: Exp; lines: +0 -5
Correct handling of SADB_UPDATE and SADB_ADD requests. key_align may
split the mbuf due to use of m_pulldown. Discarding the result because
of this does not make sense as no subsequent code depends on the entire
msg being linearized (only the individual pieces). It's likely
something else is wrong here but for now this appears to get things back
to a working state.
Submitted by: Roselyn Lee
This change was also made in the KAME CVS repository as key.c:1.337 by
itojun.
|
|
|
|
|
|
|
|
|
|
|
| |
people have reported problems (stickyness, aiming difficulty) which is proving
difficult to fix, so this will default to disable until sometime after 5.3R.
To enable Synaptics support, set the 'hw.psm.synaptics_support=1' tunable.
MT5 candidate.
Approved by: njl
|
|
|
|
|
|
| |
well, but I'll let Marcel decide whether he wants to build a .so or not.
Without this, building certain ports that use objc have fatal errors.
|
|
|
|
|
|
|
|
|
|
|
| |
longer than 'normal'. The cause is still being tracked down but
in the meantime there are machines where raising IPI_RETRIES does
help - it's not just a case of the machine staying locked up longer
and then panic-ing anyway. Several helpful folks on sparc64@ tried
a patch that helped figure out what to raise this number to.
Discussed on: sparc64@
MFC after: 3 days
|