Odd ttyvN TERM settings
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 other such programs) on ttyv1 through ttyv8, unless you remember to setenv TERM xterm. Why did we change from cons25 to xterm? How can we get all the ttyvNs to get the correct TERM setting? -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Odd ttyvN TERM settings
-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 xterms). Not > surprisingly, this leads to less than desirable results when trying to > run vi (or other such programs) on ttyv1 through ttyv8, unless you > remember to setenv TERM xterm. > > Why did we change from cons25 to xterm? How can we get all the ttyvNs > to get the correct TERM setting? -- George Mitchell The console driver has been replaced/updated. You likely missed updating your /etc/ttys, imb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/5lP0ACgkQQv9rrgRC1JKkLQCeLzOuP1oCaplYpBAQIgFsU82r jwMAoKgHFQvdvSBK81Pf1wrOCuEJmkVD =YADR -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Odd ttyvN TERM settings
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 leads to less than desirable results when trying to run vi (or other such programs) on ttyv1 through ttyv8, unless you remember to setenv TERM xterm. Why did we change from cons25 to xterm? How can we get all the ttyvNs to get the correct TERM setting? -- George Mitchell What is in your /etc/ttys? This is the ttys file on 9-STABLE on amd64: http://svnweb.freebsd.org/base/stable/9/etc/etc.amd64/ttys?revision=225736&view=markup&pathrev=238244 Regards, Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Odd ttyvN TERM settings
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 like xterms). Not surprisingly, this leads to less than desirable results when trying to run vi (or other such programs) on ttyv1 through ttyv8, unless you remember to setenv TERM xterm. Why did we change from cons25 to xterm? How can we get all the ttyvNs to get the correct TERM setting? -- George Mitchell What is in your /etc/ttys? This is the ttys file on 9-STABLE on amd64: http://svnweb.freebsd.org/base/stable/9/etc/etc.amd64/ttys?revision=225736&view=markup&pathrev=238244 Regards, Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Apparently I raced through mergemaster too fast (on two different machines, as well). That's where the problem was. Thanks for the help! -- George ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Disturbance in IPv6 force in stable/9
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 most likely. I'd be very happy if people could test this the next days (this week) if using IPv6 to make sure nothing breaks for them. The changes have been in HEAD for more than a month but who knows:) In case you find something broke due to these MFCs please yell at me, loudly! Thanks, Bjoern -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Doesn't LAPIC timer stop when CPU goes to sleep state?
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, and G840 dual core CPU. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
