new device entry for PC Card devices with NEWCARD.
I've not connected this to the build because I can't test it locally
on this machine. Feel free to fix any problems in this file, so long
as you don't change the semantic meaning without asking me. I write
code, not docs :-)
Thanks to the person who attended my devd talk in INTEROP+NETWORLD
2003 Tokyo BSD BOF via IRC who asked me how to do this in the Q&A
section. An excellent question that I glossed over at the BOF, but
hopefully this rectifies the problem.
Eventually, I'd like to expand this to include more information about
how to write a driver for a PC Card or CardBus device, but for now
this will have to do.
1) Use the new c99 initialization in the pci driver example. Also,
don't claim this device is a tty.
2) Add notes about caution needed during detach routine wrt interrupts
and locking.
3) Add note that vtophys is deprecated and to use busdma instead.
Since the busdma API isn't completely settled for 5.x yet,
don't document it. I'll leave that to others when the API is
done being frobbed.
- Add Management Interfaces (sysctls, tunables, et al).
- Add Concurrency and Synchronization (busy count handling to synchronize
policy loading).
- Add Policy Registration (management of active poliy lists).
- Flesh out Labeling Support to talk about label initialization and
life cycles, allocation semantics.
- Add System Calls.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
- Move Userland Architecture down to the Userland APIs section.
- Push most of the Policy-related subsections into the MAC Policy
Architecture section. Tweak a little language so it makes
sense.
Note that the MAC Framework can also be used to express DAC policies.
Push the MAC Framework Policy Elements section up a level to sect1 and
name it "MAC Policy Architecture".
Stick "MAC" in front of the Policy Entry Points section header to
improve consistency.
Developer's Handbook: break out the "Entry Point Framework" section
into a number of sections: MAC Policy Declaration, Entry Point
Introduction, MAC Policy Entry Point Reference. Re-order sections
a bit so there's a more logical progression and fewer large chunks
of text over many pages. This greatly improves readability.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
its possible interactions with the MPC_LOADTIME_FLAG_NOTLATE flag.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
the MAC Framework Chapter of the Developer's Handbook with a
cross-reference the the mac(3) man page for the time being.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
of the MAC Framework chapter of the Developer's Handbook into their
own <sect2> sections.
- Re-order the Policy Elements sect2 to the end of the section since
most of the remainder of the subsections talk about parts of the
Framework, not module structure.
- Add text relating to the support for persistent labeling using
extended attributes on supporting file systems.
- Add concurrency/synchronization primitives to the list of framework
elements.
This section needs more work, and will probably grow sub-sections on
most of the major elements in the element list.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
cases, the object pointer was still present as an argument to
label init/destroy calls, although it was removed in the source a
while back. In some cases, we've added blocking dispositions to
initialization calls that previously didn't have them (ipq), so
add that also. Generally call 'how' 'flag' instead to match the
prototypes in mac_policy.h.
- Add missing descriptions of mpo_destroy_vnode_label(), and the
recently added mpo_copy_mbuf_label().
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
of the Developer's Handbook: text on the APIs to access and manipulate
labels on objects, and a brief description of how labels may currently
be set on users using login.conf. This text could also use some more
work, but is probably an improvement over the previous lack of text.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
enable it in en_US.ISO8859-1/ and ja_JP.eucJP/.
- Add PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"
and l10n.ent for entity localization.
- Use share/misc/docbook.css for indentiation of <programlisting>
and <screen>.
- Add some missing $FreeBSD$.
bits of the Developer's Handbook some. Needs more work, but now
goes into a bit more detail.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
policies, but more generally about a framework for access control
extension.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
share/images. To link "generic" images (share/images ones) from
Makefiles use IMAGES_EN and to link localized images use IMAGES.
For an example look at en_US.ISO8859-1/books/handbook/Makefile
partially applicable. This does at least remove some mutex flags that
were obsoleted a long, long time ago as well as rename the lockmgr section
to be more generic.
map to 8 or 16 byte boundaries. Use 0x230 instead. Remove part of a
bullet item about documenting each device_t field here because a
device_t is supposed to be an opaque data structure to the client
drivers.
information on what MAC is, how the MAC framework supports MAC policies
in FreeBSD, etc.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
kernel access control.
Document the kernel side of the MAC policy architecture. This
is a little out of date at the moment. Some parts to be filled
in as things are developed, and much is subject to change. It
will, however, give developers a good idea of how things work.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
There is one remaining place in the fdp-primer, but that needs
a bit more work.
Inspired by: docs/36462 (Gary W. Swearingen <swear@blarg.net>)
Reviewed by: ceri, trhodes
have by far made the most commits to this document, and I have some
ideas about splitting out the kernel content into a seperate book.
The scope of this document is too large.
* Minor markup fix.
* Couple of grammatical/readability improvements.
* Mention that ddd is a port.
PR: docs/34921
Submitted by: Ceri <setantae@submonkey.net>
- Various grammar fixes.
- Change "ie." to "i.e."
- Convert quotes to <quote> or other more appropriate tags.
PR: docs/34967
Submitted by: Ceri <setantae@submonkey.net>
base system.
* Update links to FreeBSD packages to use the 'Latest/pkgname.tgz'
link so that we don't have to keep the version numbers updated.
* Expand some </> shorthand.
* Fix a few typos.
PR: docs/34884
Submitted by: Ceri <setantae@submonkey.net> (mostly)
* Add a new document-specific variable, HAS_INDEX, to specify if a
given document is marked up with <indexterm> entries.
* Rework the index support so that both HAS_INDEX and GEN_INDEX are
checked before trying to generate an index for a document.
* Only create index.sgml if both HAS_INDEX and GEN_INDEX are set.
This allows us to recursively build the documentation tree with
GEN_INDEX=1 and have it only try to create an index (very time
consuming) for the few documents that are ready for this. Previously,
running "make GEN_INDEX=1" from the top of the doc tree would look for
index terms in every single document.
With this, I hope we can start building our docs with GEN_INDEX set on
freefall so that users browsing the HTML docs will get the benefit of
the index we've been hiding in CVS for 6 months.
* Use ftp.hostname.com/directory rather than
ftp.hostname.com:directory.
* s/freebsd.org/FreeBSD.org/
* Use relative links for FreeBSD.org documents
PR: 31447
Submitted by: Cyrille Lefevre
Found by: linbot
