| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
as they are at boot time.
Original concept submitted by: ume
|
| |
|
|
|
|
|
|
|
|
|
| |
to proceed anyway as this most likely mean that the process has been
terminated.
PR: bin/140397
Submitted by: Dan Lukes <dan obluda cz>
MFC after: 1 month
|
|
|
|
|
| |
commented out since 1.1 and has not been present in <sys/systm.h> since at
least 1.1 of that file. It is also not needed in FreeBSD due to SYSINIT().
|
| |
|
| |
|
|
|
|
|
|
| |
PR: bin/140496
Submitted by: Jeremy Huddleston <jeremyhu apple.com>
MFC after: 1 month
|
|
|
|
| |
o Remove register keyword.
|
|
|
|
|
|
| |
PR: bin/140530
Submitted by: Jeremy Huddleston <jeremyhu apple.com>
MFC after: 1 month
|
|
|
|
| |
MFC after: 1 month
|
| |
|
|
|
|
|
|
| |
the results of localtime() instead of using a pthread mutex directly.
MFC after: 1 week
|
|
|
|
| |
Reviewed by: rwatson
|
|
|
|
|
|
|
|
| |
recodring speed.
PR: bin/140530
Submitted by: Alexander Best <alexbestms wwu.de>
MFC after: 1 month
|
|
|
|
|
|
| |
PR: bin/141835
Submitted by: Henning Petersen <henning.petersen t-online.de>
MFC after: 2 weeks
|
|
|
|
|
|
| |
PR: bin/141836
Submitted by: Henning Petersen <henning.petersen at t-online.de>
MFC after: 2 weeks
|
|
|
|
|
| |
OK'ed by: delphij
Approved by: trasz (mentor)
|
|
|
|
|
|
|
|
|
| |
i386-fbsd.c. Add pipe(2) to syscall table to decode it's pointer
argument properly and re-add special handling for pipe(2) return value
to print_syscall_ret().
PR: bin/120870
Approved by: trasz (mentor)
|
|
|
|
|
| |
Submitted by: infofarmer@
MFC after: 2 weeks
|
|
|
|
| |
within watchdogd(8) fails. This is also consistent with watchdog(8).
|
|
|
|
| |
code returns EOPNOTSUPP, not EINVAL.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
People who collect ISOs from more than just us have been requesting
this for a while.
MFC after: 1 week
|
|
|
|
|
| |
- Fixed spelling of EINVAL.
- Sorted sections.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flag. Besides providing the redundand information, need to update both
vnode and object flags causes more acquisition of vnode interlock.
OBJ_MIGHTBEDIRTY is only checked for vnode-backed vm objects.
Remove VI_OBJDIRTY and make sure that OBJ_MIGHTBEDIRTY is set only for
vnode-backed vm objects.
Suggested and reviewed by: alc
Tested by: pho
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Read the pci capability register to identify AGP 3 support
* Add missing smaller aperture sizes for AGP3 chips.
* Fix the aperture size calculation on AGP2 chips.
All sizes between 32M and 256M reported as 256M.
* Add \n to error string.
This all seems to get the CLE266 EPIA-M board agp working properly, now
back to work on drm.
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Quite contrary to VT6130 datasheet which says it supports up to 8K
jumbo frame, VT6130 does not seem to send jumbo frame that is
larger than 4K in length. Trying to send a frame that is larger
than 4K cause TX MAC hang.
Even though it's possible to allow 4K jumbo frame for VT6130, I
think it's meaningless to allow 4K jumbo frame. I'm not sure VT6132
also has the same limitation but I guess it uses the same MAC of
VT6130.
|
|
|
|
|
|
|
|
|
| |
controller will split the jumbo frame into multiple RX buffers.
However it seems the hardware always dma the frame to 8 bytes
boundary for the split frames. Only the first part of the fragment
can have 4 byte alignment and subsequent buffers should be 8 bytes
aligned. Change RX buffer the alignment requirement to 8 bytes from
4 bytes.
|
| |
|
|
|
|
|
| |
PR: kern/121521
Tested by: Alex Deiter
|
|
|
|
| |
Previous implementation could only limit mode, but not rise it back.
|
|
|
|
|
|
|
|
|
| |
processes by setting the FD_CLOEXEC flag for the output file.
PR: bin/140493
Submitted by: Erik Lax
OK'ed by: delphij
Approved by: trasz (mentor)
|
|
|
|
|
|
|
|
| |
getpgrp(2), getppid(2), getsid(2) and getuid(2) to syscall table to
decode their arguments correctly.
OK'ed by: delphij
Approved by: trasz (mentor)
|
|
|
|
|
|
| |
Its primary purpose is to start and stop services provided by
the rc.d scripts, however it can also be used to list the scripts
using various criteria.
|
|
|
|
| |
timer for Tx queue is at 0x3E.
|
|
|
|
| |
we use excessive delays quite habitually.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically this commit changes two things, which improves access to TTYs
in exceptional conditions. Basically the problem was that when you ran
jexec(8) to attach to a jail, you couldn't use /dev/tty (well, also the
node of the actual TTY, e.g. /dev/pts/X). This is very inconvenient if
you want to attach to screens quickly, use ssh(1), etc.
The fixes:
- Cache the cdev_priv of the controlling TTY in struct session. Change
devfs_access() to compare against the cdev_priv instead of the vnode.
This allows you to bypass UNIX permissions, even across different
mounts of devfs.
- Extend devfs_prison_check() to unconditionally expose the device node
of the controlling TTY, even if normal prison nesting rules normally
don't allow this. This actually allows you to interact with this
device node.
To be honest, I'm not really happy with this solution. We now have to
store three pointers to a controlling TTY (s_ttyp, s_ttyvp, s_ttydp).
In an ideal world, we should just get rid of the latter two and only use
s_ttyp, but this makes certian pieces of code very impractical (e.g.
devfs, kern_exit.c).
Reported by: Many people
|
|
|
|
|
|
|
|
| |
PR: docs/140986
Submitted by: Glen Barber (glen dot j dot barber at gmail dot com)
MFC after: 4 days
Reviewed by: sam
Approved by: sam, jkois (mentor)
|
|
|
|
|
|
|
|
|
|
| |
filesystem was busy
(onnv revision 8989)
Submitted by: mm
Approved by: pjd
Obtained from: OpenSolaris
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
(onnv revision 8986)
Requested by: mm
Submitted by: pjd
Obtained from: OpenSolaris
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
filesystem was busy.
Submitted by: mm
Approved by: pjd
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and /.profile. The problem is that install(1) will unlink the old file
before it installs the new one, which means that in the best case we
have to compare the changes for the old file twice.
So, change the logic to first test to see if the link exists, then
install the file. Then if the link was there and we're using -i, just
create the link in /root and be done with it. Otherwise display the
message to the user and give them the option.
Because we are now sorting things before doing the comparison we can
know conclusively that the files in / should be the sources, and the
files in /root will be the targets, so adjust the paths accordingly.
While I'm here, split a too-long error message into two lines and
just return at the end of handling these files instead of setting
the variable that says "do nothing" and then returning at the end
of the function anyway.
|
| |
|
|
|
|
|
| |
first pipe it to sort so that order of processing will be deterministic
and like things will be grouped together.
|
|
|
|
|
| |
busmastering/memory address in resume path. Bus driver will handle
that.
|