Up through FreeBSD 8.x, the ttyvN consoles had a TERM setting of cons25.
On FreeBSD 9.n, it appears to be xterm for ttyv0, but it's still cons25
for ttyv1-ttyv8 (even though they all appear to act like xterms). Not
surprisingly, this leads to less than desirable results when trying to
run vi (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/08/12 10:00, George Mitchell wrote:
> Up through FreeBSD 8.x, the ttyvN consoles had a TERM setting of cons25.
> On FreeBSD 9.n, it appears to be xterm for ttyv0, but it's still cons25
> for ttyv1-ttyv8 (even though they all appear to act like xt
On Sun, 08 Jul 2012 16:00:16 +0200, George Mitchell
wrote:
Up through FreeBSD 8.x, the ttyvN consoles had a TERM setting of cons25.
On FreeBSD 9.n, it appears to be xterm for ttyv0, but it's still cons25
for ttyv1-ttyv8 (even though they all appear to act like xterms). Not
surprisingly, this
On 07/08/12 10:14, Ronald Klop wrote:
On Sun, 08 Jul 2012 16:00:16 +0200, George Mitchell
wrote:
Up through FreeBSD 8.x, the ttyvN consoles had a TERM setting of cons25.
On FreeBSD 9.n, it appears to be xterm for ttyv0, but it's still cons25
for ttyv1-ttyv8 (even though they all appear to act
Hey,
after some back and forth and quite a few people asking me for it and having
asked re@ I have merged the IPv6 offload changes to stable/9 today rather than
after 9.1 as I had planned.
I did not merge driver changes and I am expecting that one or two might
follow-up,
as will SCTP be following
I have FreeBSD 9.0-STABLE r237285, In my systl -a output, I see
kern.eventimer.et.LAPIC.flags: 7
I am under the impression LAPIC timer may stop when CPU goes to sleep
state. Shouldn't the flag be 15 as the example in EVENTTIMERS(4) man
page?
I have H67MA-E35 motherboard with Intel H67 chipset, a
