response 189 of 870:

Jan 3 04:57 UTC 2005

You can edit your file, you just can't save recovery information.

I power-cycled the modem some time between 22:30 and 23:00 this evening.
I left it off for several minutes, while I tried to deal with the full /var
partition.

I realise now that the state of /var contributed to the network problem: mail
was being rejected almost as fast as it was being received because the
messages couldn't be written to disk.

I have turned off incoming mail for the duration.

response 191 of 870:

Jan 3 06:15 UTC 2005

Thanks for the note; I've corrected the dates in motd. :)

response 193 of 870:

Jan 3 06:24 UTC 2005

Probably:  mail was rejected because it couldn't be written to disk.  Now it
is coming in.

response 195 of 870:

Jan 3 15:25 UTC 2005

What happened to all my files?!!!

response 197 of 870:

Jan 3 15:56 UTC 2005

Under old grex, vi (as it does under Solaris, HP-UX, etc.) when started up
showed the number of lines in the file being edited.  Under nextgrex, vi
instead shows the following:

<filename>: unmodified: line 1

Is there some way to get vi to show the number of lines upon startup?

response 199 of 870:

Jan 3 17:05 UTC 2005

Backtalk got a lot faster in the last hour or so.  Yay!

response 201 of 870:

Jan 3 18:14 UTC 2005

I got the same "telnetd" message that Kevin did for serveral tries
at dialing in.  Then finally I was able to dial in.  I have *never*
gotten this message bfefore.  I hope the dialin users won't have
to wait in the telnet queue.

Also - the ^H backspace problem and the "byte abcd" problem are still
with us.

response 203 of 870:

Jan 3 19:57 UTC 2005

Re resp:127,resp:179: Pine uses those "internal data" messages to store
various information, I think.  I don't know what happens if you delete one.

Re resp:157: In BSD, filesystems have an area that's reserved for only
the root user.  The percentage full takes into account only the
user-accessable part of the filesystem.  So if the filesystem is filled
by a user, then root (or a process owned by root) puts some stuff on it,
it will be over 100%.

Re resp:201: The 'Byte abcd' problem isn't really a "problem", it's just
a different prompt.  more is telling you how many bytes into the file
you are, instead of giving an information-free 'More' prompt.

response 205 of 870:

Jan 4 10:57 UTC 2005

So I was wrong: vi on on the old machine did give the file name, number of
lines and number of characters.  On OpenBSD and linux (2.4.26, I don't know
which distribution), it doesn't.

I note that the man page here, as well as on the Linux machine I now use, is
for the "nex/nvi" versions.  According to the man page, "Nex/nvi  are
intended as bug-for-bug compatible replacements for the original  Fourth
Berkeley  Software  Distribution (4BSD)  ex  and vi programs."

The man pages for vi and nvi do not hint at how to change the initial
information.  For what's worth, <CTRL>G still reports the current line number
and the total number of lines in the file.

response 207 of 870:

Jan 4 14:20 UTC 2005

What about the ^H that I get on my screen instead of the backspace?
With OldGrex, I was told upon login that abackspace was ^H, but
it never appered on my screen.

response 209 of 870:

Jan 4 15:49 UTC 2005

Re #207: Dave, you can set your backspace character to be either
/------------------\
|  ^H (ascii 8) or |
| DEL (ascii 127). |
\------------------/
Some people use one, and some people use another.  It only matters that what
your terminal program sends is what your account on Grex expects to receive.

I have my terminal program set to send ^H, and I have a line in my .login
file which says:
/-------------------------------------\
| stty intr '^C' kill '^K' erase '^H' |
\-------------------------------------/
to tell Grex (among other things) that ^H is my erase key.

When you see those ^Hs on the screen it means your terminal is sending ^H
but Grex is expecting DEL.  So you can either tell your terminal to send
DEL, or tell Grex to expect ^H.

response 211 of 870:

Jan 4 17:09 UTC 2005

Is DEL ^?   Thanks for explaining that I need to login back to my own account
rather than exiting to it.  But I set up an alias to use ssh instead.
In .procmailrc can I use | to set up one long filter instead of many short
ones, for instance    v.agra|vi.?agra|viag.?ra  (to catch v1agra and vi.agra
and viaggra)?  In fact is there some way to not have to use three lines
starting with :0: to filter on each subject, but put everything on one line,
and have one filter for Subject, one for From, one for To, one for message
body (0B)?  Or even one that combines Subject, From and To:  

My filter, now that I removed the white list, has been rejecting roughly every
other mail from each person so I am turning on the verbose log again but it
produces pages of text for each spam and someone just sent seven nearly
identical ones.  So I would like to shorten .procmailrc.  
Is anyone working on a grex-wide spam filter yet, that people could modify
(for instance spamassassin throws out all my electric bills for five causes).