| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and writev() except that they take an additional offset argument and do
not change the current file position. In SAT speak:
preadv:readv::pread:read and pwritev:writev::pwrite:write.
- Try to reduce code duplication some by merging most of the old
kern_foov() and dofilefoo() functions into new dofilefoo() functions
that are called by kern_foov() and kern_pfoov(). The non-v functions
now all generate a simple uio on the stack from the passed in arguments
and then call kern_foov(). For example, read() now just builds a uio and
calls kern_readv() and pwrite() just builds a uio and calls kern_pwritev().
PR: kern/80362
Submitted by: Marc Olzheim marcolz at stack dot nl (1)
Approved by: re (scottl)
MFC after: 1 week
|
| |
|
|
| |
for more than INT_MAX bytes.
|
| | |
|
| |
|
|
| |
Discussed with: bde
|
| |
|
|
|
|
|
| |
Now readers won't get an impression that pointing to beyond
the current end of file will result in EINVAL.
MFC after: 1 week
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
better represent failures of special files accessed over NFS.
Approved by: schweikh (mentor)
Reviewed by: bde (as a description)
MFC after: 6 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See e.g. nfsclient/nfs_vnops.c
static int
nfs_read(struct vop_read_args *ap)
{
struct vnode *vp = ap->a_vp;
if (vp->v_type != VREG)
return (EPERM);
return (nfs_bioread(vp, ap->a_uio, ap->a_ioflag, ap->a_cred));
}
Approved by: schweikh (mentor)
MFC after: 6 weeks
|
| |
|
|
| |
Submitted by: Craig Rodrigues <rodrigc@attbi.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Stop calling system calls "function calls".
Use "The .Fn system call" a-la "The .Nm utility".
When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.
|
| |
|
|
|
|
| |
which do not match the reality anyway.
Approved by: deischen, bde
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
``.Ar errno'' -> ``.Va errno''
``.Nm ops'' -> ``.Fa ops''
``.Va fd'' -> ``.Fa fd''
|
| |
|
|
| |
More libraries manpages updates following.
|
| |
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
| |
|
|
| |
Obtained from: NetBSD (mostly)
|
| | |
|
| |
|
|
|
|
| |
use ``is expected to conform to'' phrase, not ``conforms to''
Pointed out by: Bruce->NIST-PCTS
|
| |
|
|
|
|
|
|
| |
in a bunch of man pages.
Use the correct .Bx (BSD UNIX) or .At (AT&T UNIX) macros
instead of explicitly specifying the version in the text
in a bunch of man pages.
|
| |
|
|
|
|
| |
Submitted by: John Birrel(L?)
changes for threadsafe operations
|
| |
|
