| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
vt220 will not work better. Even though it probably will remove warnings
about unknown terminal types, a cons25 emulator is not compatible with
vt220 at all.
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
memory with 4MB pages was added to pmap_object_init_pt(). This code
assumes that the pages of a OBJT_DEVICE object are always physically
contiguous. Unfortunately, this is not always the case. For example,
jhb@ informs me that the recently introduced /dev/ksyms driver creates
a OBJT_DEVICE object that violates this assumption. Thus, this
revision modifies pmap_object_init_pt() to abort the mapping if the
OBJT_DEVICE object's pages are not physically contiguous. This
revision also changes some inconsistent if not buggy behavior. For
example, the i386 version aborts if the first 4MB virtual page that
would be mapped is already valid. However, it incorrectly replaces
any subsequent 4MB virtual page mappings that it encounters,
potentially leaking a page table page. The amd64 version has a bug of
my own creation. It potentially busies the wrong page and always an
insufficent number of pages if it blocks allocating a page table page.
To my knowledge, there have been no reports of these bugs, hence,
their persistance. I suspect that the existing restrictions that
pmap_object_init_pt() placed on the OBJT_DEVICE objects that it would
choose to map, for example, that the first page must be aligned on a 2
or 4MB physical boundary and that the size of the mapping must be a
multiple of the large page size, were enough to avoid triggering the
bug for drivers like ksyms. However, one side effect of testing the
OBJT_DEVICE object's pages for physical contiguity is that a dubious
difference between pmap_object_init_pt() and the standard path for
mapping devices pages, i.e., vm_fault(), has been eliminated.
Previously, pmap_object_init_pt() would only instantiate the first
PG_FICTITOUS page being mapped because it never examined the rest.
Now, however, pmap_object_init_pt() uses the new function
vm_object_populate() to instantiate them all (in order to support
testing their physical contiguity). These pages need to be
instantiated for the mechanism that I have prototyped for
automatically maintaining the consistency of the PAT settings across
multiple mappings, particularly, amd64's direct mapping, to work.
(Translation: This change is also being made to support jhb@'s work on
the Nvidia feature requests.)
Discussed with: jhb@
|
| |
|
| |
|
|\
| |
| |
| | |
Approved by: re
|
| |
| |
| |
| |
| | |
expension disabled on the vendor tree means merges to head
removes the attributes there which clutters the merge.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
FIPS works but at least now we have the support source in case it
does.
- Do not exclude rsaref - it's not part of the OpenSSL distribution
archive anymore.
|
| | |
|
| |
| |
| |
| |
| | |
- Remove all of include as there is only the openssl subdir with
symlinks (which were always removed).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
(last vendor import).
The file were removed in different earlier releases, but were not
removed from the CVS vendor branch at the time.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
In the past there have been some reports of PRINTF_BUFR_SIZE not
functioning correctly. Instead of having garbled console messages, we
should just see whether the issues are still there and analyze them.
Approved by: re
|
| |
| |
| |
| |
| |
| | |
Tested by: Alexander Best <alexbestms at math uni-muenster de>
Approved by: kib (mentor)
MFC after: 3 days
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
compiler doing argument type checking. Since the prototypes in
kgss_if.h used the generic gss_ctx_id_t for the context argument,
but the functions in sys/kgssapi/krb5/krb5_mech.c used the
KerberosV specific context argument, the file would no longer build.
This patch fixes it so it will build by replacing the argument with
a gss_ctx_id_t one and setting a local "struct krb5_context *" variable
to it for use by the function.
Reviewed by: dfr
Approved by: kib (mentor)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
queue was drained. It will never fire for a directly dispatched packet.
You will most likely never want to use this for any ordinary netisr usage
and you will never blame netisr in case you try to use it and it does
not work as expected.
Reviewed by: rwatson
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even though I thought this bug was somewhere in the TTY layer, it turns
out init(8) doesn't make sure /dev/console is opened initially properly.
I've added revoke() to two pieces of code:
- death(): Apart from killing the gettys on shutdown, this doesn't
guarantee the TTY to be closed immediately.
- runshutdown(): Just like setctty(), we should revoke /dev/console.
Applications like syslogd may have file descriptors to the console.
|
| |
| |
| |
| | |
Approved by: imp (mentor)
|
| |
| |
| |
| | |
Approved by: ed (mentor)
|
| |
| |
| |
| |
| |
| |
| |
| | |
/etc/make.conf properly.
Only one SCM?
I do not think this is right.
Now I have fixed it.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
also be able to print information about...
- length of the terminal capabilties
- dump of one terminal definition
- relationship overview for a terminal definition
|
| |
| |
| |
| | |
two termcap entries.
|
| |
| |
| |
| | |
Submitted by: Pawel Worach
|
| |
| |
| |
| | |
Submitted by: Pawel Worach
|
| |
| |
| |
| | |
Submitted by: Pawel Worach
|
| | |
|
| |
| |
| |
| | |
Submitted by: Pawel Worach
|
| |
| |
| |
| |
| | |
function declaration bottom rather than the new function declaration
start.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Characters between 0x07 and 0x0d are now also mapped, which means we can
display almost 256 different characters. Also remap certain types of
dashes and quotes, which means we can finally read our manual pages
without red question marks in them.
Submitted by: Christoph Mallon
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
in /etc/termcap:
VT100 spec indicates that passthrough printing can be enabled
by sending ESC[5i and disabled by sending ESC[4i These entries
should be listed as po and pf in /etc/termcap, but are absent.
See http://www.vt100.net/docs/vt102-ug/chapter5.html#S5.5.2.23
PR: conf/71549
Submitted by: Andrew Webster <andrew@pubnix.net>
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
screen entry: F11-F20 keys added
linux entry: F10-F20 keys added, ACS line graphics added
PR: kern/108899
Submitted by: Joseph Terner<jtsn@gmx.de>
MFC after: 1 week
|
| |
| |
| |
| |
| |
| | |
PR: 129554
Submitted by: gavin
MFC after: 3 weeks
|
| |
| |
| |
| |
| |
| | |
PR: 132135
Submitted by: Craig Leres
MFC after: 3 weeks
|
| |
| |
| |
| |
| |
| |
| | |
PATH then they can expect things to break.
PR: 135417
MFC after: 3 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Although the PR contains also the definitions of the Wyse 60, they
are not copied into it since there are already definition for them
in the termcap file since 1997.
Also, the PR didn't use the :tc=xxx: feature, so I've imploded them.
PR: conf/81882
Submitted by: Meister des Chaos <meister@netz00.com>
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The termcap database does not have an entry for rxvt-unicode.
This means that programs that need an entry such as vi fail
to work when connecting via ssh using this terminal emulator.
The added data is not the same as the PR submitted by Richard, it
uses the :tc=xxx: option to inherit everything from rxvt-mono.
PR: conf/117323
Submitted by: Richard Bradshaw <richard.bradshaw@blueyonder.co.uk>
MFC after: 1 week
|
| | |
|
| |
| |
| |
| |
| | |
and rxvt-unicode) so see which fields should don't need to be copied
if the :tc=xxx: option is used.
|
| |
| |
| |
| |
| | |
uart_8250. Remove it here since the UART on the ADM5120 isn't the
typical 16550: its completely different.
|
| | |
|
| | |
|