[5822] in Release_7.7_team
Re: Linux Athena and SATA operation modes
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Aug 30 18:03:56 2007
In-Reply-To: <200708302153.l7ULr1Ck023028@pothole.mit.edu>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A4182443-56A4-4E6C-90F8-31B22456BD78@mit.edu>
Cc: release-team@mit.edu
Content-Transfer-Encoding: 7bit
From: Jonathan Reed <jdreed@MIT.EDU>
Date: Thu, 30 Aug 2007 18:03:04 -0400
To: "andrew m. boardman" <amb@mit.edu>
X-Spam-Flag: NO
X-Spam-Score: 0.00
On Aug 30, 2007, at 5:53 PM, andrew m. boardman wrote:
> I have a basic shell script that deals with the conversion,
> specifically
> /afs/dev/user/amb/scripts/convert-to-sata.sh. Any objections to
> moving
> this to the release locker and publishing a stock answer on using it?
> (It's moderately fraught with peril, as a bios setting change must be
> made concurrently, and doing it wrong yields a non-booting system.)
>
If someone does manage to shoot themselves in the foot, what is the
recovery process? If it's booting with rescue mode or something like
that, that sounds like something that is difficult at best to talk
users through over the phone. Looking at it, I assume the shell
script is run first, and then the user makes the BIOS change upon
reboot? I'd kind of like the script to trap SIGINT et al and after
the conversion, inform the user that they must now reboot and frob
the BIOS settings, and prompt them to press a key to reboot, or
something, so it's all a one step process, rather than having them
run the script and then reboot 2 hours later and forget what they
were supposed to do.
Of course, if recovery is either trivial, or trivial to talk users
through on the phone, I have little to know objection.
-Jon
