While it's true that it's part of the traditional 4.4BSD security model,
there may come a time where a different "primary" security model used for
fine-grained privileges (ie., splitting root's responsibilities to various
privileges that can be assigned) may want to still have a securelevel
setting.
Idea from Daniel Carosone:
http://mail-index.netbsd.org/tech-security/2006/08/25/0001.html
The location of the removed files, for reference, was:
src/secmodel/bsd44/secmodel_bsd44_securelevel.c
src/secmodel/bsd44/securelevel.h
don't assume that the cached route is a sockaddr_in6, and do the
right comparisions so that no out-of-bounds memory is accessed.
btw, the use of "#ifdef INET" throughout the source doesn't look clean
to me: There are 2 cases -- whether AF_INET is usable by userland
programs, and whether IPv4 is supported as on-wire protocol.
Nothing done in header files, nor in dev/pci/drm (we might not want to
touch this for the sake of merging) yet. Compile tested; please let
me know if this broke anything.
- Accept "-" for msgfile (STDIN) and catfile (STDOUT)
- Merge msgfile into formatted catfile. The catfile is created if
it does not exist (current behavior). If the catfile exists,
its messages are included in the new catfile. Collisions between
set and message numbers cause the msgfile message text to replace
the existing message text.
(The $delset directive now makes more sense.)
Standards: The Open Group Base Specifications Issue 6
IEEE Std 1003.1, 2004 Edition
- Replace corrupt()/nomem() with errx(). The replaced routines
called local error() -> warning() which prints an input file line
number. This probably makes no sense for these conditions (it
is not a syntax error in msgfile). Line numbers are completely
nonsense when dealing with reading a formatted catfile.
- Modify warning() to only print line number when reading from a
message file. Also print the current file being processed.
- Don't issue a warning when processing a line with only a message
number and no trailing space. This is valid and will delete any
existing message with that number from the current set.
- Reset lineno for each msgfile processed.
it's still reasonable and some kernel code seems to assume it
(otherwise some inode numbers of directories could be corrupted).
XXX: not sure if odd e2fs_ipg is valid or not in ext2fs spec.
will be extended to other appropriate ports in future. Note as such in the
bugs section.
This is an MI man page, so should not be flagged as i386 in the header.
Leave alone the Latency Timer set by the Cardbus bridge.
With version 1.152 of dev/pci/pccbb.c, we can power down the card
when it is not in-use, so do that.
an Atheros WLAN. That generates a CB_SOCKET_EVENT_CSTS event on
the bridge. The event isn't interesting to pccbb(4), so we used
to ignore the interrupt. Now, let the child devices try to handle
the interrupt, instead. The Atheros NIC produces interrupts more
reliably, now: used to be that it would only interrupt if the driver
avoided powering down the NIC's cardslot, and then the NIC would
only work after it was reset a second time.
arguments (enough for the majority of calls) or the maximum of 10 (8 plus
2 for sys__syscall).
Avoids all the unlikely-to-be-predicted-correctly in the unrolled loop.
This might be a problem if a thread's stack doesn't have the extra args
mapped - but that is extremely unlikely.
