|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Cc: Camilla R Fox <cfox@mit.edu>, Oliver Thomas <othomas@mit.edu>, release-team@mit.edu Message-Id: <30345AD4-8B1B-49AE-8711-B7C4B02DEEFC@mit.edu> From: Jonathan Reed <jdreed@MIT.EDU> To: Jonathan Reed <jdreed@mit.edu> In-Reply-To: <DD7D6F09-D2CC-4FF1-A4D6-B26A4496737A@mit.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 6 May 2008 11:07:58 -0400 X-Spam-Flag: NO X-Spam-Score: 0.00 *dropping owls from CC* Revisiting this, I still like the idea of doing this through .environment. However, in order to kill two birds with one stone, I have also written a "fix-dotfiles" script, which I expect to reside in the consult locker. This has the added benefit that it's easier to say "athrun consult fix-dotfiles" over the phone than "cp / usr/prototype_user/..?* $HOME". Both the script, and the new .environment file are in /mit/jdreed/Public/dotfiles for review. Currently, the script backs up all the user's dotfiles and copies over the default. I went back and forth about whether that was the correct operation, as opposed to merely copying the Athena defaults and preserving the user-customizable files, however I find the most common failure mode is "I can't log in", in which case it's easiest to punt all the dotfiles and then help the user figure out later which one was broken. I am, however, open to being convinced that this is incorrect. What do people think? If we can come to a resolution by the beginning of next week, that would be best, since the new folks can register for their accounts soon. -Jon On Apr 16, 2008, at 2:45 PM, Jonathan Reed wrote: > It's equally easy for us to create a stock answer for "How do I make > single-sided printing the default?", so it doesn't really matter to > me which method we choose. If there's a chance of people's > customizations getting clobbered, than we can punt my suggestion. > > -Jon > > On Apr 16, 2008, at 2:38 PM, Camilla R Fox wrote: >> >> It may be Jon's standard practice, but it's never been mine; in the >> simple case that presents like "add isn't in my path" I prefer a >> solution that's idempotent and simple, over one that preserves data >> at >> all costs. >> >> But, the backups have only gotten easier to access over the years, >> so I >> think it's still an acceptable risk. >> >> -Camilla >
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |