[6585] in Release_7.7_team
Re: dialup churn in process
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Wed Dec 30 17:02:12 2009
Message-Id: <200912302200.nBUM0jFx016720@speaker-for-the-dead.mit.edu>
From: Jonathon Weiss <jweiss@MIT.EDU>
To: "Mark W. Manley" <mmanley@MIT.EDU>
cc: Jonathan Reed <jdreed@MIT.EDU>, Oliver Thomas <othomas@MIT.EDU>,
ops@MIT.EDU, release-team@MIT.EDU
In-reply-to: Your message of "Wed, 30 Dec 2009 12:32:29 EST."
<alpine.DEB.2.00.0912301229350.6950@green-arrow.mit.edu>
Date: Wed, 30 Dec 2009 17:00:45 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00
> > I wonder if we need to think harder about outreach to the community or
> > something. I don't know of a good way to do that. Maybe update the current
> > dialup MOTDs now to at least make people aware of the upcoming transition?
> > I'm primarily concerned that we'll see a significant number of people who
> > gave up on Debathena for whatever reason and fellback to the dialups instead,
> > and now will be forced to actually report their problem.
> >
>
> I'll leave that to your collective user support wisdom. My past
> experiences with these kinds of migrations is that you are correct and
> notthing, even a laser light show and full-on parade announcing the
> change, will get some users' attention.
I'd worry more about having a MOTD pointing at sun.dialup on the linux
machines when they go into the regular pool, than on the suns warning
of the change in advance. Though when we have a specific date for the
cutover, somthing in the sun MOTDs can't hurt. We should put
something on 3down prior to the cutover too. However, you're right,
whatever we do, a bunch of users won't read it.
Jonathon
