Date: Mon, 5 Oct 2015 06:39:29 +0100 From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> To: supervision@list.skarnet.org, FreeBSD Hackers <freebsd-hackers@freebsd.org>, debian-user@lists.debian.org Subject: nosh version 1.21 Message-ID: <56120D11.4080506@NTLWorld.com> In-Reply-To: <56089268.6080007@NTLWorld.com> References: <54430B41.3010301@NTLWorld.com> <54B86FD5.3090203@NTLWorld.com> <554E53EF.4080600@NTLWorld.com> <554E93AF.3070709@NTLWorld.com> <556BA130.50708@NTLWorld.com> <55902328.8080602@NTLWorld.com> <55D5CFA2.5010402@NTLWorld.com> <55D8B9AC.6010209@NTLWorld.com> <CADQ2Nw-506S3Gm4s40t%2BWzJu3Wzpwp=wPBWCFoQGZ2yrctCM_w@mail.gmail.com> <56089268.6080007@NTLWorld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The nosh package is now up to version 1.21 . * http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html console-terminal-emulator now has a mouse input event protocol, and speaks both the DEC VT Locator protocol and the xterm Private Mode 1006 protocol over the terminal interface to applications. These are the protocols that you get with ttymouse=dec and ttymouse=sgr in vim. Since support for the 1006 protocol is fairly widespread in the relevant places nowadays, it seemed not worthwhile implementing the inferior Private Mode 1005 and Private Mode 1015 protocols. Moreover, console-terminal-emulator is UTF-8 and the Private Mode 1005 protocol has ambiguities once one introduces UTF-8. console-fb-realizer as yet only talks to real mouse input devices on Linux, but handling FreeBSD/PC-BSD mouse input devices is on the roadmap. This has necessitated a change in the command-line syntax of console-fb-realizer, and concomitant changes in the pre-supplied realizer service bundle, which will need to be updated in tandem if you are using user-space virtual terminals. This change allows the mouse input device to be specified in addition to the keyboard input event device. It also slightly regularizes display-only mode, which is signified now by the simple lack of any mouse or keyboard device specifications, rather than by an explicit option. Yes, I am aware that there's no mouse cursor sprite drawn yet. Acutely so. FreeBSD improvements include the completion of geli and gbde import that the sharp-eyed might have noticed quietly part-done in version 1.20. /etc/fstab entries for volumes using these should now be translated into appropriate interdependent mount@*, gbde@*, and geli@* service bundles. This is rather difficult for me to test, though, as noted on the roadmap. The big PC-BSD improvement is jails support, which has lurked at the bottom of the roadmap page for a while. Both PC-BSD Warden and FreeBSD 9 jails are now recognized by the external configuration import subsystem, and converted into appropriate service bundles. The mechanism here is fairly straightforward: The jails themselves are one service bundle, and the programs that run in the jails are another. The latter service is after/ and wants/ the former service. The jexec command is a chain loading tool that modifies process state in the same vein as setuidgid, softlimit, and envdir, and one can simply employ it as such. The jail command can be used analogously, with jail -c and jail -r, to how the mount and umount commands in mount@* service bundles are used. Those are what the import subsystem does. Importing Warden Linux jails isn't available yet; and some of the more esoteric FreeBSD 9 rc.conf and PC-BSD Warden METADIR/* jail options are not yet imported. Enabling jails to be autostarted at bootstrap is via the "jails" and "warden" targets, by the way. The rc.d conversion project has progressed, with a few more things wiped off. As mentioned in the version 1.20 message, all assistance in wiping the final 40-odd FreeBSD rc.d scripts off the list, to be found on the roadmap page, is welcome. And if any PC-BSD people have ideas on how to turn things like /usr/local/etc/rc.d/pc-samba into service bundles, those are welcome too. (Note that pre-supplied service bundles already exist for the Linux flavours of some of these, which may or may not be a starting point.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56120D11.4080506>