|
|
| Author |
Message |
| 25 new of 292 responses total. |
jep
|
|
response 100 of 292:
| 
Oct 21 13:46 UTC 1999 |
I use ^U if I make a mistake on the login: or password: line, then I
re-type it. It works great.
|
scott
|
|
response 101 of 292:
|
Oct 21 13:59 UTC 1999 |
(Control-U is "erase line" in UNIX)
|
janc
|
|
response 102 of 292:
|
Oct 21 15:39 UTC 1999 |
I don't understand why login can't treat *both* ^H and ^? as delete
characters when logins and passwords are being entered. That seems the
only sane solution. Only catch is that the change over would annoy
anyone whose password includes a ^?, but any such person pretty much
deserves it.
|
janc
|
|
response 103 of 292:
|
Oct 21 15:41 UTC 1999 |
Oh, and I agree that there should be a way to turn off talk requests
seperately from write/tel requests. Someone who has a couple days free
should write this sometime.
|
mooncat
|
|
response 104 of 292:
|
Oct 21 16:22 UTC 1999 |
Back there for the person who suggested 'mesg n' for the .login file...
Doesn't that turn off *all* messages? I don't want that. I like
tels, and I tend to talk to many people at once via tels while
in party or something. What I don't like, or use is !talk...
|
other
|
|
response 105 of 292:
|
Oct 21 19:39 UTC 1999 |
if i remember correctly, the manual for mesg or for nowrite/yeswrite includes
a flag to select between tel/talk/chat/all requests. i have a yeswrite file
and am flagged for tels only.
|
other
|
|
response 106 of 292:
|
Oct 21 19:40 UTC 1999 |
mesg ne -p t -r y -b y -m l
|
jazz
|
|
response 107 of 292:
|
Oct 21 22:43 UTC 1999 |
mesg -2 -m -a -n -y -o -p -t -i -o -n -s.
|
other
|
|
response 108 of 292:
|
Oct 21 23:33 UTC 1999 |
i dunno, i spent half an hour and got it to do exactly what i wanted...
|
orinoco
|
|
response 109 of 292:
|
Oct 22 00:13 UTC 1999 |
For those who were asking somwhere about making telk requests not beep at you,
the manual makes it look like mesg -b y will do that.
|
pfv
|
|
response 110 of 292:
|
Oct 22 01:04 UTC 1999 |
I think what they said was they didn't want to: see, hear,
smell, taste, touch or SENSE "talk requests".
OTOH, they wanted to live without losing telegrams.
|
krj
|
|
response 111 of 292:
|
Oct 22 06:18 UTC 1999 |
Question from arabella: has anything changed which would break the
combination of "setenv TERM ansi" and the more pager?
Today Leslie starts getting the message: "WARNING: terminal cannot
scroll backwards". We don't think she changed anything in her
configuration files.
|
jor
|
|
response 112 of 292:
|
Oct 22 14:12 UTC 1999 |
it's not April Fool's??
10:11am up 10:26, 1 user, load average: 0.08, 0.01, 0.00
User tty login@ idle JCPU PCPU what
jor ttys0 10:06am 5 w
|
goose
|
|
response 113 of 292:
|
Oct 22 15:16 UTC 1999 |
Yeah, something's not right. First a traceroute stopped at blackrose.org,
then a couple minutes later it was hung up somewhere within cyberspace.org.
|
krj
|
|
response 114 of 292:
|
Oct 22 16:20 UTC 1999 |
Late last night I found that I could not telnet to Grex from
Michnet or tir.com; but when I dialed in I found lots of other people
telnetted in. Today I can't telnet in from Michnet, tir.com, or msen.com,
and apparently no one else can telnet in either.
|
keesan
|
|
response 115 of 292:
|
Oct 23 00:42 UTC 1999 |
Aruba says the two of us are alone on grex now. So why is it taking a minute
or two to send off a short e-mail? All evening.
|
kaplan
|
|
response 116 of 292:
|
Oct 23 02:29 UTC 1999 |
Grex's connection to the Internet is down. Blame Ameritech. Why is it taking
you minutes? I don't know. Do you mean it took a long time for your mail
client to accept the message? Are you using pine? If it's being delivered
to someone else on grex, that should be no problem. But if you're trying to
deliver to someplace out on the Internet, it won't get there until the link
is fixed!
|
keesan
|
|
response 117 of 292:
|
Oct 23 03:21 UTC 1999 |
Sending to someone outside of grex, took over a minute to go from 0% to 100%
using pine. Where did it go? Have not tried lynx recently. There are four
of us dialled in at the moment, including someone in Party, signed on for 20
minutes. Who are they partying with? It takes two to party.
|
scg
|
|
response 118 of 292:
|
Oct 23 03:33 UTC 1999 |
The long delay was probably something trying to do a DNS lookup, which
requires network connectivity.
|
aruba
|
|
response 119 of 292:
|
Oct 23 14:01 UTC 1999 |
I had to wait several minutes at the "Welcome to Grex! (it may take a few
seconds to connect)" prompt. Does that have to do with the net connection
being down?
|
cmcgee
|
|
response 120 of 292:
|
Oct 23 16:24 UTC 1999 |
This morning it took 2:45 (minutes and seconds) to get from the Welcome to
Grex to the login prompt using dial-in lines. And all my mail that I sent
yesterday (which took over a minute per message to send) has mailerdeamon
messages this morning saying it didn't go through.
|
krj
|
|
response 121 of 292:
|
Oct 23 17:25 UTC 1999 |
Colleen, you're mail's not going anywhere until the Internet connection
is fixed. There ought to be a large motd message explaining this, staff.
I confirm the two minute 45 second wait for a login prompt.
|
scg
|
|
response 122 of 292:
|
Oct 23 17:41 UTC 1999 |
The delay waiting for the login prompt was DNS timing out. That should be
fixed now.
Ameritech says they've found the ISDN problem, and are working on it.
|
scg
|
|
response 123 of 292:
|
Oct 23 20:51 UTC 1999 |
Since it had been almost three hours since Ameritech had called to say
it was a cable problem and was being actively worked on, I took a walk
over to the Pumpkin to see if I could find any evidence of that.
I started by walking around the building, looking for where the phone
cables come out. I had assumed they came out the front of the building
and then went straight up Huron to the CO, but there don't appear to be
any overhead phone cables in that part of Huron.
The phone lines come out of the side of the building, fairly near the
back, and then head out behind the homeless shelter and the rental car
place to Chapin Street. From there, they head towards Huron. I didn't
have to follow them any farther than that.
Near the corner of Chapin and Huron, there were two Ameritech trucks,
next to two utility poles, maybe 100 feet apart. Running between them
were a phone cable at normal height, and a another cable hanging down at
about half the normal phone cable height. On each pole was an Ameritech
guy. One of them was covered by a big cloth tent-type thing, so I
couldn't see what he was doing. The guy at the other end had both cables
split out into the individual wire pairs, and appeared to be going
through, pair by pair, and replacing one cable with the other.
It's currently drizzling and 43 degrees in Ann Arbor. It didn't look
like pleasant work.
Assuming they're doing what I think they were doing, we will probably
lose each of the POTS lines briefly, one by one, as they work on this.
I'm also guessing that we probably weren't the only customer affected, if
they're replacing the whole cable. I wonder if we lost any of the
dial-in lines, without noticing.
|
senna
|
|
response 124 of 292:
|
Oct 23 23:11 UTC 1999 |
The net is up, but everything is extremely slow.
|
