From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2221 Path: news.gmane.org!not-for-mail From: Jonathan de Boyne Pollard Newsgroups: gmane.os.freebsd.devel.hackers,gmane.linux.debian.user,gmane.comp.sysutils.supervision.general Subject: nosh version 1.19 Date: Sat, 22 Aug 2015 19:04:28 +0100 Message-ID: <55D8B9AC.6010209@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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1440266713 24909 80.91.229.3 (22 Aug 2015 18:05:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 22 Aug 2015 18:05:13 +0000 (UTC) To: debian-user@lists.debian.org, "supervision@list.skarnet.org" , FreeBSD Hackers Original-X-From: owner-freebsd-hackers@freebsd.org Sat Aug 22 20:05:03 2015 Return-path: Envelope-to: freebsd-hackers@m.gmane.org Original-Received: from mx2.freebsd.org ([8.8.178.116]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZTDA6-0005Ip-7B for freebsd-hackers@m.gmane.org; Sat, 22 Aug 2015 20:05:02 +0200 Original-Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.freebsd.org (Postfix) with ESMTPS id CA0AA2519; Sat, 22 Aug 2015 18:04:58 +0000 (UTC) (envelope-from owner-freebsd-hackers@freebsd.org) Original-Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A1DD7195F; Sat, 22 Aug 2015 18:04:58 +0000 (UTC) (envelope-from owner-freebsd-hackers@freebsd.org) Original-Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A47859BF823 for ; Sat, 22 Aug 2015 18:04:51 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Original-Received: from know-smtprelay-omc-3.server.virginmedia.net (know-smtprelay-omc-3.server.virginmedia.net [80.0.253.67]) by mx1.freebsd.org (Postfix) with ESMTP id EFD0C191B for ; Sat, 22 Aug 2015 18:04:50 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Original-Received: from [192.168.1.100] ([86.10.211.13]) by know-smtprelay-3-imp with bizsmtp id 7u4g1r00B0HtmFq01u4hsV; Sat, 22 Aug 2015 19:04:41 +0100 X-Originating-IP: [86.10.211.13] X-Spam: 0 X-Authority: v=2.1 cv=TYVrzkkh c=1 sm=1 tr=0 a=SB7hr1IvJSWWr45F2gQiKw==:117 a=SB7hr1IvJSWWr45F2gQiKw==:17 a=NLZqzBF-AAAA:8 a=n40ctHC_h8IA:10 a=N659UExz7-8A:10 a=7mOBRU54AAAA:8 a=yashrJDmAAAA:8 a=6JoKIJvD939b3KE__7UA:9 a=pILNOxqGKmIA:10 a=XdyKOaxJwVsA:10 a=4dEWTFd_fAAA:10 User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 In-Reply-To: <55D5CFA2.5010402@NTLWorld.com> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: owner-freebsd-hackers@freebsd.org Original-Sender: owner-freebsd-hackers@freebsd.org Xref: news.gmane.org gmane.os.freebsd.devel.hackers:56184 gmane.linux.debian.user:501128 gmane.comp.sysutils.supervision.general:2221 Archived-At: nosh is now up to version 1.19 * http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html The important news is that the embarrassment with the post-install setup = script for the Linux nosh-run-kernel-vt package is fixed. It was a = missing 1-line escape() shell function. I apologize. Other terminal management news is that there's now a console-clear = command that does pretty much the same thing as the Bourne Again shell's = clear_console command (also coming with that name as a symbolic link = alias) but better. * The bash clear_console tries to open a lot of device files, as can be = seen in Ubuntu bug #39068. This tool by comparison doesn't need = anything more than its standard output, and doesn't attempt to open any = terminal devices itself at all. * The bash tool is specific to the Linux kernel terminal emulator. It = had to be turned off for Debian kFreeBSD in Debian bug #355336, patched = to make it stop when run as the superuser in xterm in Debian bug = #355815, and worked around again in Debian bug #793883. This tool, = contrastingly, actually works with xterm and PuTTY and clears their own = scrollback buffers. It uses a different mechanism that both they and = (ironically) the Linux kernel terminal emulator since 2011, all support. * Debian bug #791342 would be fixed by it, because it doesn't use the = bodge of attempting to switch virtual terminals away and back (using = either tty1 or tty2 as the "other" terminal) to clear the scrollback buffer. On the gripping hand, this is something that one doesn't actually need = if one is using the nosh-run-user-vt package. console-terminal-emulator = supports the same extension to ECMA-48 Erase Display as xterm and PuTTY = do, but the raison d'=EAtre for clear_console is the likes of Debian bug = #331504. clear_console is in fact a ten-year-old bodge, addressing a = security/privacy concern that's a lot older still. With user-space = virtual terminals, one has the freedom to do things right, without the = need for such bodges. (-: As the console-terminal-emulator manual page = explains, when a login session terminates and the terminal is hung up, = the terminal emulator erases the whole display buffer. In more other news: On Linux, fsck at bootstrap time is now monitored. = What this means from a user standpoint is that if your system reaches = its "maximum mounts before a forced full fsck" point, it doesn't just = sit there with nothing visibly happening (if one cannot see the hard = disc activity light) for ages. The fsck@* services now invoke = "monitored-fsck" rather than fsck directly. This is an ordinary = chain-loading tool that opens a client connection to a local (i.e. = AF_LOCAL) socket and then chains to fsck adding in its (Linux-specific) = -Cfd option. There's a new monitor-fsck-progress service that runs the = server for that socket, and displays progress information on the = console. This latter is intentionally replaceable by alternative = services, of course. I'm intending to make its output somewhat = prettier, rather than just dumping the raw information at you as it does = in this release. But if you want to write your own ... You'll have to delete /etc/system-control/convert/volumes (or modify the = contents of /etc/fstab) and run "redo all" to get your existing = auto-created fsck@* service bundles regenerated with the new command. = Or just edit the run files replacing fsck with monitored-fsck . The big news is that as promised in the 1.18 announcement the = nosh-run-busybox-mdev package is now functional. Also as promised in = that announcement, here's more on the subject. The nosh toolset doesn't come with a bunch of rules for your = plug-and-play manager, be that (BSD) devd, (Linux) udev, or busybox = mdev. Your plug-and-play manager does, or should do. As packaged up = for Debian Linux, udev comes with a whole bunch of pre-supplied rules in = /lib/udev/rules/ that gets one the "usual" device file tree in /dev/ . = And it almost goes without saying that the BSDs come with devd rules in = the box. The same is not true for the busybox Debian package. There's = no /etc/mdev.conf supplied. You MUST write one before using busybox mdev. busybox mdev's default = behaviour as packaged, in the absence of /etc/mdev.conf , may be logical = and straightforward; but it does not result in a working Debian system. = Some things that I've hit myself are /dev/null not being accessible to = anyone except the superuser, which affects loads of things all over the = shop, and event device files not being under /dev/input/ where other = parts of the system expect them to be. There's plenty to read on this subject in the non-Debian world, starting = with but not limited to: * https://wiki.gentoo.org/wiki/Mdev * http://linuxfromscratch.org/clfs/view/clfs-3.0/mips/bootscripts/mdev.html You'll have to adapt these for Debian. There are also the examples in = /usr/share/doc/busybox/examples/ , of course, the larger of the two = fixing both of the aforementioned problems. The positive news is that = the busybox-mdev service implicitly serializes invocations of mdev, so = that there's no need for mucking around with mdev's sequence number = mechanism. The recovery mode problem mentioned in the 1.18 announcement turns out = to have a simple local fix, which I'll incorporate into a more = comprehensive service fix: # ln -s rescue /etc/service-bundles/targets/single _______________________________________________ freebsd-hackers@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"