You are not logged in. Login Now
 0-24   20-44   45-69   70-94   95-119   120-144   145-169   170-194   195-219 
 220-223          
 
Author Message
25 new of 223 responses total.
papa
response 45 of 223: Mark Unseen   Feb 1 22:48 UTC 2017

I confirm that #42 is fixed. Thanks, Dan.
tonster
response 46 of 223: Mark Unseen   Feb 18 16:40 UTC 2017

Grex took an extended vacation due to problems with my ISP. AT&T was
never able to determine (well, honestly, they didn't even look) the
reason for the packet-loss i was getting, so they ultimately assigned a
new block of IP's. Things should be returning to normal as DNS continues
to propagate out.
kentn
response 47 of 223: Mark Unseen   Feb 18 20:41 UTC 2017

Thanks for getting things going again, Tony!
papa
response 48 of 223: Mark Unseen   Feb 18 20:55 UTC 2017

Glad to find Grex back on-line. Missed y'all while it was down.
jhesse
response 49 of 223: Mark Unseen   Feb 19 00:16 UTC 2017

jhesse
response 50 of 223: Mark Unseen   Feb 20 18:49 UTC 2017

Ack.  Not sure what happened on #49.  Sorry about that.
 
Update:  Mail to Yahoo is working now.  Thank you, if the fix was on this end.
tonster
response 51 of 223: Mark Unseen   Feb 21 13:17 UTC 2017

Ironically, this would have fixed that issue as Grex's IP changed so
Yahoo won't have blocked this one (yet).
telnetuserid
response 52 of 223: Mark Unseen   Mar 12 13:26 UTC 2017

 I just performed ssl test for grex.org on ssllabs. The result is 'F',
 which is probably caused by old software.
 https://www.ssllabs.com/ssltest/analyze?d=grex.org
 I am looking forward for grex to improve in this area, i.e. supporting 
 TLS best practice.
tod
response 53 of 223: Mark Unseen   Mar 12 16:41 UTC 2017

can we read your report with netscape navigator?
nharmon
response 54 of 223: Mark Unseen   Mar 12 17:16 UTC 2017

I recommend nobody transmit any protected health information or processes any 
payment cards via Grex. You've been warned.
kentn
response 55 of 223: Mark Unseen   Mar 13 03:21 UTC 2017

For improving in any such area, it takes time and effort to do so.  And
if staff don't have time (which is quite often in the past few years),
then it won't likely happen.  The last time we updated the OS, a number
of home-grown applications had to change significantly and it was a lot
of work for staff to get things working again.  Updating the OS would
go a long way toward fixing any TLS issues, I'd expect, but that won't
happen without a lot of staff effort.
telnetuserid
response 56 of 223: Mark Unseen   Mar 13 18:33 UTC 2017

telnetuserid
response 57 of 223: Mark Unseen   Mar 13 18:53 UTC 2017

 For this to happen, a planned downtime and maintenance 
 need to be performed.
 Just gather the staffs and discuss everything.
 Getting in touch with devio.us maintainer is also a 
 good thing to do, since they've successfully updated 
 their system to 5.8 without any major issue.
tod
response 58 of 223: Mark Unseen   Mar 13 23:54 UTC 2017

We'll conduct a change management review with the change advisory board
in the cone of silence tunnel below our facility over by the COTS
area.  Those of you who have not been on the calls for this are free
to dialin on our closed circuit line by the entrance.
No cell phones or biomed bracelets are permitted.
Bring a dixie cup of hand sanitizer.
papa
response 59 of 223: Mark Unseen   Mar 14 10:51 UTC 2017

Does not sound pretty.
tonster
response 60 of 223: Mark Unseen   Mar 14 13:14 UTC 2017

downtime isn't the issue, it's for the staff to have the time to plan
and execute the upgrade. I've created VM's for the new system, but we
haven't had a lot of time to go beyond that stage. At some point
hopefully that'll change, but right now we're just trying to keep the
last remaining light on.
tod
response 61 of 223: Mark Unseen   Apr 7 17:40 UTC 2017

*sound of poopy trombones*

grex% slrn -f /a/t/o/tod/.jnewsrc --create
slrn 0.9.9p1

Loading /usr/local/share/slrn/slang/slrn.sl
Using newsrc file /a/t/o/tod/.jnewsrc for server news.provide.net.
Connecting to host news.provide.net ...
Failed to resolve news.provide.net

Run-Time Error
slrn fatal error:
Failed to initialize server.
kentn
response 62 of 223: Mark Unseen   Apr 8 00:03 UTC 2017

I think I had to get a free news account outside of grex to
get it to work.  I don't think we can access provide.net for
news any more.
mijk
response 63 of 223: Mark Unseen   Apr 8 21:51 UTC 2017


kentn
response 64 of 223: Mark Unseen   Apr 9 02:31 UTC 2017

See:  http://dotsrc.org/usenet/ as one way to get usenet news.
You need to register but I don't think costs anything.
cross
response 65 of 223: Mark Unseen   Apr 10 14:54 UTC 2017

Eternal September is popular with the kids these dats.
mijk
response 66 of 223: Mark Unseen   Apr 10 21:14 UTC 2017

I was just about to say the same, accept i probably am one of the kids. :)
kentn
response 67 of 223: Mark Unseen   Apr 10 23:36 UTC 2017

It takes some time to set things up, and of course, we need to
(according to some) start over with just a few of standard starter
items.  So, we could see how it would work...Spring/Summer.  We
don't really have a cfadmin any more, who would normally do this.
tod
response 68 of 223: Mark Unseen   Apr 11 03:39 UTC 2017

re #62
Once upon a time I could rely on UM ITD but they removed me like Napoleon
Bonaparte
ryan
response 69 of 223: Mark Unseen   Apr 28 14:13 UTC 2017

Just a FYI -

When logging in, the default tset command in my .profile was choking on what it
was finding my terminal to be: "screen.xterm-256color".

Fixed it by export TERM="vt100" in my .profile.

 0-24   20-44   45-69   70-94   95-119   120-144   145-169   170-194   195-219 
 220-223          
Response Not Possible: You are Not Logged In
 

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