Re: jot: producing too much output?

2023-01-06 Thread is
On Thu, Jan 05, 2023 at 11:46:42PM +0700, Robert Elz wrote: > Date:Thu, 5 Jan 2023 11:16:22 -0500 (EST) > From:Mouse > | I'd do it myself except I don't know where to find an > | authoritative spec for jot. > > I'd tend to assume

Re: ZFS - mounting filesystems (Was CVS commit: src/etc)

2022-03-16 Thread is
hi, On Mon, Mar 14, 2022 at 08:53:23AM -0700, Paul Goyette wrote: > But there is no "if-you-can" option in fstab. :0 I want it to be > mounted if possible, but do not abort if not possible. Mark it as notauto, and put @reboot /sbin/mount /build into /etc/crontab. (and

Re: ZFS - mounting filesystems

2022-03-16 Thread is
On Mon, Mar 14, 2022 at 04:54:59PM +0100, Edgar Fuß wrote: > > I don't see a real problem with deciding to mount all local filesystems > > (marked auto of course) at mouncritlocal time. > What if /usr is on NFS and /usr/local is local? General case: you mount something that w

Re: Anyone still using YP support on NetBSD?

2021-09-28 Thread is
Hello, On Thu, Sep 23, 2021 at 02:06:51PM -0700, Jason Thorpe wrote: > Anyone? @work, a few machines in a leftover group. -is

Re: Summary of man-page formatting

2020-11-15 Thread is
Hi, On Sun, Nov 15, 2020 at 12:43:58PM -0500, Mouse wrote: > But, of course, that's predicated on someone going to the trouble to > (a) build a DVI-to-text backend (not hard, if it doesn't yet exist, Whether the whole TeX-idea is useful for the purpose, I don't know at the

Re: UTF-8 capable fmt(1)

2019-07-25 Thread is
etbsd-8 code. But > I'll check. Yes, works for the test sequence in my message above. Sorry, I'd assumed that the project died because of non-utf-8 requirements ... Thanks. -is

Re: UTF-8 capable fmt(1)

2019-07-25 Thread is
discussed. > > After this discussion, the fmt code was updated in -current. > Can you try again if this works for you now? Really? The discussion was in 2016 - I'm using netbsd-8 code. But I'll check. -is

Re: UTF-8 capable fmt(1)

2019-07-25 Thread is
if it doesn't understand them. The point fmt breaks for me is: It tries to skip over non-printable characters using this sequence if(!(isprint(c) || c == '\t' || c >= 160)) { c = getc(fi);

Re: ftp: verboselevel 1/2

2016-08-27 Thread is
gt; >do we want that in-tree? > > Why don't you do it for (interactive | verbose)? Because for verbose we get all the address information anyway when trying to connect. Actually - maybe we should do it even for !interactive, to have the information in log files of batch scripts (that is, the test would be !verbose, or a pure else {...}) Regards, -is