Edward Tomasz Napierala
6283502e20
Remove pseudocode from VOP_* manual pages. It was out of date anyway.
...
Reviewed by: scottl
Approved by: rwatson (mentor)
2009-03-30 20:56:37 +00:00
Attilio Rao
0359a12ead
Decontextualize the couplet VOP_GETATTR / VOP_SETATTR as the passed thread
...
was always curthread and totally unuseful.
Tested by: Giovanni Trematerra <giovanni dot trematerra at gmail dot com>
2008-08-28 15:23:18 +00:00
Hiten Pandya
571dba6ec9
Use 'manual page' instead of 'man page' for consistency.
...
Approved by: re (hrs)
2005-06-28 20:15:19 +00:00
Ruslan Ermilov
0a57ea7df2
Mark lists as in the rest of section 9 manpages.
...
Submitted by: Joel Dahl (mostly)
2005-01-28 10:43:05 +00:00
Ruslan Ermilov
facc67676f
mdoc(7) police: Deal with self-xrefs.
2002-12-24 13:41:48 +00:00
Ruslan Ermilov
8d5d039f80
Uniformly refer to a file system as "file system".
...
Approved by: re
2002-12-12 17:26:04 +00:00
Don Lewis
81f8d226f9
Convert descriptions in the ERRORS section to full sentences if they
...
were not full sentences, elaborating as necessary.
2002-09-18 22:12:43 +00:00
Don Lewis
cc25845767
Style and markup changes only.
...
Capitalize the first letter of the descriptions for the entries in the ERRORS
section if they are complete sentences and end the sentences with periods.
2002-09-18 09:34:01 +00:00
Robert Watson
58616b1c69
s/VOP_NULL/VATTR_NULL/
2002-09-14 03:32:57 +00:00
Ruslan Ermilov
841b462f2a
mdoc(7) police: markup nits.
2002-05-29 17:37:32 +00:00
Robert Watson
cc0e549485
Various updates to VOP_ATTRIB(9): mention locks being shared/exclusive
...
for VOP_GETATTR() and VOP_SETATTR(), reference VOP_NULL() to suggest
clearing all of *vap with it before setting specific values. Cross
reference VFS(9). Indicate that failure modes are possible from
VOP_GETATTR() and that an errno value is returned.
Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
2002-05-03 20:28:38 +00:00
Dima Dorfman
82d0caaef1
mdoc(7) police: remove whitespace at EOL.
2002-03-28 12:57:48 +00:00
Robert Watson
b3b414b604
Revert 1.14: VOP_GETATTR() really does require a vnode lock.
...
Confirmed by: mckusick
2002-02-10 19:28:34 +00:00
Brian Feldman
6dad2ea974
Document that VOP_GETATTR(9) does not actually expect to hold an
...
exclusive lock on entry.
Sponsored by: DARPA, NAI Labs
2002-02-05 15:26:28 +00:00
Mike Pritchard
b82af3f5e4
ispell sweep of share/man/man9/*.
2002-01-09 11:43:48 +00:00
Andrew R. Reiter
c25081010f
- Fix a number of man pages broken by the KSE merger.
2001-11-20 18:19:19 +00:00
Ruslan Ermilov
32eef9aeb1
mdoc(7) police: Use the new .In macro for #include statements.
2001-10-01 16:09:29 +00:00
Chris Costello
bd79f8422f
Be consistent with struct vattr' naming. Half of this manual used
vpp'
...
while the other half used `vap', and in one case resulted in code that
made no sense. Replaced all of them with `vap'.
(Typically, `vpp' is a pointer to a pointer to a struct vnode anyway).
2000-03-16 22:40:38 +00:00
Matthew Dillon
bebac989cc
More clarification of locking requirements.
1999-09-24 10:42:45 +00:00
Matthew Dillon
065aee8253
Bring more VOP manual pages up to date in regards to locking
...
requirements.
1999-09-24 10:19:43 +00:00
Peter Wemm
7f3dea244c
$Id$ -> $FreeBSD$
1999-08-28 00:22:10 +00:00
Philippe Charnier
aaf1f16e39
.Sh AUTHOR -> .Sh AUTHORS according to mdoc specs.
...
Use .An/.Aq.
1998-03-12 07:31:21 +00:00
Bruce Evans
2e14815b84
Fixed #include and/or prototype bugs in synopsis.
1997-04-13 14:49:13 +00:00
Mike Pritchard
eaa8b244f1
Some minor mdoc cleanup.
1997-03-07 03:32:31 +00:00
Mike Pritchard
50e7a72d28
Update this man page to reflect how setattr manipulates time
...
values after the Lite2 merge.
1997-03-07 03:16:52 +00:00
Doug Rabson
ffdbee2566
Formatting tweaks.
1997-03-04 10:02:44 +00:00
Doug Rabson
fab63cc413
This is the current draft of my filesystem manpages. Some files are
...
incomplete and some are just placeholders but I wanted to try to get
something at least into 2.2 on the grounds that what I have is a lot
better than nothing. I also wanted to commit something which documents
the interfaces in 2.2 before I start updating the documentation for 3.0.
This is a definite 2.2 candidate and is also relavent to 2.1 if people
still care about that branch.
1997-03-03 18:01:01 +00:00