You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   166-190   191-215 
 216-240   241-265   266-290   291-315   316-340   341-365   366-390   391-415   416-440 
 441-465   466-490   491-515   516-540   541-565   566-590   591-615   616-640   641-665 
 666-690   691-715   716-740   741-765   766-790   791-815   816-840   841-865   866-870 
 
Author Message
25 new of 870 responses total.
gelinas
response 191 of 870: Mark Unseen   Jan 3 06:15 UTC 2005

Thanks for the note; I've corrected the dates in motd. :)
keesan
response 192 of 870: Mark Unseen   Jan 3 06:19 UTC 2005

I was able to ssh just now out of grex, but it is quite slow.  Is this related
to the full /var?   
gelinas
response 193 of 870: Mark Unseen   Jan 3 06:24 UTC 2005

Probably:  mail was rejected because it couldn't be written to disk.  Now it
is coming in.
jep
response 194 of 870: Mark Unseen   Jan 3 13:51 UTC 2005

Backtalk is running at OldGrex speeds.

The page which used to be the choice for bookmarking, now allows a user 
to log in but then gives a 404 "The page cannot be found" message:

   http://www.grex.org/cgi-bin/pw/bt/pistachio/begin

The solution is to bookmark this page:

   http://www.grex.org/cgi-bin/pw/backtalk/pistachio/begin

This might be confusing some users.
kalbaugh
response 195 of 870: Mark Unseen   Jan 3 15:25 UTC 2005

What happened to all my files?!!!
albaugh
response 196 of 870: Mark Unseen   Jan 3 15:51 UTC 2005

My files have returned just as mysteriously as they disappeared, and my mail
has been restored too.  :-)
albaugh
response 197 of 870: Mark Unseen   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?
albaugh
response 198 of 870: Mark Unseen   Jan 3 15:58 UTC 2005

BTW, for me, at the moment, telnetting in to nextgrex from the internet,
response is DOG SLOW.
jep
response 199 of 870: Mark Unseen   Jan 3 17:05 UTC 2005

Backtalk got a lot faster in the last hour or so.  Yay!
albaugh
response 200 of 870: Mark Unseen   Jan 3 17:37 UTC 2005

Just now when I tried to connect via the internet, I was shown:

telnetd: All network ports in use.

Is that a case of staff turning off connections for to do maintenance, 
or do we have a need for the telnet queue after all?  (this is being 
entered via backtalk)
dpc
response 201 of 870: Mark Unseen   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.
albaugh
response 202 of 870: Mark Unseen   Jan 3 19:44 UTC 2005

The "all ports in use" situation remains, 2 hours later...
gull
response 203 of 870: Mark Unseen   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.
gelinas
response 204 of 870: Mark Unseen   Jan 4 06:24 UTC 2005

Re #197:  I've been using vi since 1992, admittedly mostly on SunOS (both 4.x
and 5.x); I've noticed a line-count at the beginning of an editting session.
The command :number (or :nu) will precede each line with its number.

Re 201:  The option "-d" will give you the default "more" prompt.  You may
want to set this in your .cshrc (if you use csh), with the command

        setenv MORE -d
gelinas
response 205 of 870: Mark Unseen   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.
gelinas
response 206 of 870: Mark Unseen   Jan 4 10:58 UTC 2005

(I now see that I omitted a negative in the first sentence of 204.  Ah well.)
dpc
response 207 of 870: Mark Unseen   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.
blaise
response 208 of 870: Mark Unseen   Jan 4 15:04 UTC 2005

Sindi, two things.  First, the easy one: the pipe sign is an OR function
in regular expressions, so v|agra matches any line that contains either
a v or agra.

Second, on the "logout without disconnecting" issue: the "exec
/usr/bin/login" is a *workaround*, not a permanent solution.  Each time
you issue "exec /usr/bin/login" that command will log you out without
disconnecting, allowing someone else to log in.  If they want to log out
without disconnecting, they will have to issue "exec /usr/bin/login".
aruba
response 209 of 870: Mark Unseen   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.
rcurl
response 210 of 870: Mark Unseen   Jan 4 16:30 UTC 2005

The  usual motd and login list did not appear this morning. 
keesan
response 211 of 870: Mark Unseen   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).
keesan
response 212 of 870: Mark Unseen   Jan 4 17:19 UTC 2005

Talk - Couldn't bind to control socket, couldn't assign requested address.
I have not changed my permissions since old grex.  .
keesan
response 213 of 870: Mark Unseen   Jan 4 17:22 UTC 2005

I just got a tel   'help  ^U help  EOF (honeycut), in response to my offer
of help via tels since talk was not working.  My guess is vandalism but still,
talk is not working.
mcnally
response 214 of 870: Mark Unseen   Jan 4 17:37 UTC 2005

 The talk program that ships with OpenBSD is probably a different one than
 Grexers are used to.  I see that "ytalk" is not available, but it's one of
 several superior "talk" replacements.
tpryan
response 215 of 870: Mark Unseen   Jan 4 17:38 UTC 2005

I
s
t
i
l
l
c
a
n
'
t
t
a
b
o
r
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   166-190   191-215 
 216-240   241-265   266-290   291-315   316-340   341-365   366-390   391-415   416-440 
 441-465   466-490   491-515   516-540   541-565   566-590   591-615   616-640   641-665 
 666-690   691-715   716-740   741-765   766-790   791-815   816-840   841-865   866-870 
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss