I can make it a one time message (I thought it did this already, but
guess not).
I lose vi files by SSH problems, and I don't reboot the server, so I
only found out about ancient virecover'd files a few months later.
I am planning (well, have more or less implemented, but not committed)
a small change to the way "sh -x" works, to cause the trace output (from -x)
to continue appearing on the stderr that existed when the -x option was
turned on - rather than following stderr around as the script alters it.
An ex
My concern about this is the same as it would be about moving
anything from system-wide stuff to personal stuff or updates to
the default dot files. The concern is that people's personal dot
files aren't going to be updated when an OS update is done.
Generally, only new installs and new users
Back in 2014, I proposed to import a simple SHA-3 implementation into
libc and libkern. There were two main objections:
1. SHA-3 wasn't finalized yet, so it might change.
2. OpenSSL might add an incompatible SHA-3 API like they did SHA-2.
The SHA-3 standard has since been finalized (with no chan
Date:Sat, 11 Nov 2017 15:50:58 + (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Just set virecover=NO in /usr/src/etc/defaults/rc.conf and have people
| who want it turn it on manually from now on.
Or just leave it as it always has been, and h
In article <14853.1510405...@andromeda.noi.kre.to>,
Robert Elz wrote:
>Date:Sat, 11 Nov 2017 11:25:20 +
>From:co...@sdf.org
>Message-ID: <2017112520.ga17...@sdf.org>
>
> | I lose vi files by SSH problems, and I don't reboot the server, so I
> | only found ou
Date:Sat, 11 Nov 2017 11:25:20 +
From:co...@sdf.org
Message-ID: <2017112520.ga17...@sdf.org>
| I lose vi files by SSH problems, and I don't reboot the server, so I
| only found out about ancient virecover'd files a few months later.
There is nothing wrong
On Sat, Nov 11, 2017 at 12:44:53AM +, co...@sdf.org wrote:
> This is missing:
> - Moving virecover to /usr/bin
> - Regen'ing autoconf
> - Adding it to default ~/.profile
won't work for peoples using a shell that doesn't load .profile.
Also, I'm not sure running virecover everytime a user logs
Date:Sat, 11 Nov 2017 00:44:53 +
From:co...@sdf.org
Message-ID: <2017004451.ga...@sdf.org>
| This is missing:
| - Moving virecover to /usr/bin
| - Regen'ing autoconf
| - Adding it to default ~/.profile
| - Removing virecover rc script
This is all ver
