User:Tonyr/Journal/Aug07 - Revision history

Tonyr: /* 11Aug07 */ link repair

2007-08-17T05:09:06Z

11Aug07: link repair

Tonyr: /* 15Aug07 */ eject button behavior enabled

2007-08-16T06:39:53Z

15Aug07: eject button behavior enabled

Tonyr: /* 15Aug07 */ more eject key comments.

2007-08-15T17:15:53Z

15Aug07: more eject key comments.

Tonyr: /* 15Aug07 */ add crossref

2007-08-15T15:23:21Z

15Aug07: add crossref

Tonyr: /* 15Aug07 */ unmap f11/f12 possibility

2007-08-15T15:18:15Z

15Aug07: unmap f11/f12 possibility

Tonyr: 15aug07 section; eject key problem

2007-08-15T07:30:35Z

15aug07 section; eject key problem

Tonyr: /* 11Aug07 */ triage and power supplies

2007-08-13T05:25:42Z

11Aug07: triage and power supplies

Tonyr: /* 11Aug07 */ old mac laptop triage

2007-08-13T04:51:50Z

11Aug07: old mac laptop triage

Tonyr: /* 11Aug07 */ triage revisited

2007-08-13T03:33:31Z

11Aug07: triage revisited

Tonyr: /* 11Aug07 */

2007-08-13T01:58:03Z

11Aug07

@@ Line 33: / Line 33: @@
 ''Triage''<br>
 The MacPile area, and the other connected shleves, are being dismantled to make way for a rearranged triage/eval/advanced-test space.  There will be triage/eval benches where the shelves are now.  I told Jeff that that I thought there would never be a need for mopre than two triage positions at such a bench. Jeff and Matteo suggested that a Mac Triage Flow description would be in order.  There is already a first pass MacTriage description that I developed several months ago, based on the workspace arrangements/assumptions at the time.
-It's at [[Tonys_MacTriage_Devel#iMacBuild]].  I'll use that as a starting point for a new description.  There
+It's at [[User:Tonyr/MacTriage/23May07#iMacBuild]].  I'll use that as a starting point for a new description.  There
 is also a build chart that details some of the steps at [[A_Mac_Rebuild_Table]].

← Older revision		Revision as of 06:39, 16 August 2007
Line 64:		Line 64:

	* Ref. [[User:Tonyr/Journal/Jul07#26Jul07\|26Jul07]] ''one button mouse'' entry.		* Ref. [[User:Tonyr/Journal/Jul07#26Jul07\|26Jul07]] ''one button mouse'' entry.
		+	Here's what I did, and it seems to provide reasonable behavior:
		+	1) removed package mouseemu with '''apt-get''',
		+	2) edited ''/etc/sysctl.conf'' to comment out definitions for mouse keys, leaving only 3button mouse
		+	emulation defined,
		+	3) defined Eject to be F12 in System->Preferences->Keyboard Shortcuts
		+
		+	This allows the default definitions for right-click and middle-click to be Fn+Option and Fn+Apple.

@@ Line 55: / Line 55: @@
 ''Unmap F11/F12''<br>
 This article [http://ubuntuforums.org/showthread.php?t=468298 http://ubuntuforums.org/showthread.php?t=468298] says uninstalling package '''mouseemu''' will free up the keys for redefinition.
 * Ref. [[User:Tonyr/Journal/Jul07#26Jul07|26Jul07]] ''one button mouse'' entry.

← Older revision		Revision as of 15:23, 15 August 2007
Line 55:		Line 55:
	''Unmap F11/F12''<br>		''Unmap F11/F12''<br>
	This article [http://ubuntuforums.org/showthread.php?t=468298 http://ubuntuforums.org/showthread.php?t=468298] says uninstalling package '''mouseemu''' will free up the keys for redefinition.		This article [http://ubuntuforums.org/showthread.php?t=468298 http://ubuntuforums.org/showthread.php?t=468298] says uninstalling package '''mouseemu''' will free up the keys for redefinition.
		+	* Ref. [[User:Tonyr/Journal/Jul07#26Jul07\|26Jul07]] ''one button mouse'' entry.

← Older revision		Revision as of 15:18, 15 August 2007
Line 52:		Line 52:
	They are defined basically with '''gconf'''. There is a CLI tool for modifying gconf preference values, '''gconftools-2'''. The GUI tool is System->Preferences->Keyboard Shortcuts, but it is not very flexible.		They are defined basically with '''gconf'''. There is a CLI tool for modifying gconf preference values, '''gconftools-2'''. The GUI tool is System->Preferences->Keyboard Shortcuts, but it is not very flexible.
	The Eject key is defined as '0xcc'. but I have no idea which key on the keyboard that is. The Eject key is defined in a schema defined in the file ''/usr/share/gconf/schemas/apps_gnome_settings_daemon_keybindings.schemas''. The general problem is to get the F12 key to NOT be mouse-right-click, but be eject, and choose a set of keys for right-mouse-click and middle-mouse-click that are NOT F12 and F11.		The Eject key is defined as '0xcc'. but I have no idea which key on the keyboard that is. The Eject key is defined in a schema defined in the file ''/usr/share/gconf/schemas/apps_gnome_settings_daemon_keybindings.schemas''. The general problem is to get the F12 key to NOT be mouse-right-click, but be eject, and choose a set of keys for right-mouse-click and middle-mouse-click that are NOT F12 and F11.
		+
		+	''Unmap F11/F12''<br>
		+	This article [http://ubuntuforums.org/showthread.php?t=468298 http://ubuntuforums.org/showthread.php?t=468298] says uninstalling package '''mouseemu''' will free up the keys for redefinition.

← Older revision		Revision as of 07:30, 15 August 2007
Line 47:		Line 47:

	The other unresolved issue is power supply reclamation and test. Power supplies should be reclaimed from otherwise rejected G3/G4 towers. It would be nice if power supply testing could be integrated into the existing power supply testing process, but I think it is too specialized. Apple has published testing procedures for the tower models, but they require that the power supplies be connected to an appropriate logic board and tested ''in situ'', both with power off and power on. It would be necessary to set this up somewhere, and the existing power supply testing station may not be the best choice for a number of reasons.		The other unresolved issue is power supply reclamation and test. Power supplies should be reclaimed from otherwise rejected G3/G4 towers. It would be nice if power supply testing could be integrated into the existing power supply testing process, but I think it is too specialized. Apple has published testing procedures for the tower models, but they require that the power supplies be connected to an appropriate logic board and tested ''in situ'', both with power off and power on. It would be necessary to set this up somewhere, and the existing power supply testing station may not be the best choice for a number of reasons.
		+
		+	==15Aug07==
		+	''Keyboard shorcuts''<br>
		+	They are defined basically with '''gconf'''. There is a CLI tool for modifying gconf preference values, '''gconftools-2'''. The GUI tool is System->Preferences->Keyboard Shortcuts, but it is not very flexible.
		+	The Eject key is defined as '0xcc'. but I have no idea which key on the keyboard that is. The Eject key is defined in a schema defined in the file ''/usr/share/gconf/schemas/apps_gnome_settings_daemon_keybindings.schemas''. The general problem is to get the F12 key to NOT be mouse-right-click, but be eject, and choose a set of keys for right-mouse-click and middle-mouse-click that are NOT F12 and F11.

@@ Line 42: / Line 42: @@
 Before leaving triage for whatever reason, hard drives, memory and batteries are removed.
-Anything else is rejected and marked for recycling.
+Anything else is rejected and marked for recycling, unless there is a special request for it.
 The unresolved issue in this overview is what to do with rejected laptops.  Rejected all-in-one iMacs can be stripped down to monitor-only status and recycled as such; there is informal precedent in Eval-1 for PC all-in-one machines (and Mac all-in-one Performas).  Older Apple/Mac machines after mining are sent to recycling. PC laptops have their own workspace and process.  Mac laptops are lumped together with all other Apple hardware.  Currently, since all Apple/Mac hardware shares one process, old laptops are taken apart in the MacBuild area.  Taking apart old laptops is not very difficult or time consuming, and can probably be done at the triage station.

← Older revision		Revision as of 04:51, 13 August 2007
Line 42:		Line 42:
	Before leaving triage for whatever reason, hard drives, memory and batteries are removed.		Before leaving triage for whatever reason, hard drives, memory and batteries are removed.

−	The unresolved issue in this overview is what to do with rejected laptops. Rejected all-in-one iMacs can be stripped down to monitor-only status; there is informal precedent in Eval-1 for PC all-in-one machines (and Mac all-in-one Performas).	+	Anything else is rejected and marked for recycling.
		+
		+	The unresolved issue in this overview is what to do with rejected laptops. Rejected all-in-one iMacs can be stripped down to monitor-only status and recycled as such; there is informal precedent in Eval-1 for PC all-in-one machines (and Mac all-in-one Performas). Older Apple/Mac machines after mining are sent to recycling. PC laptops have their own workspace and process. Mac laptops are lumped together with all other Apple hardware. Currently, since all Apple/Mac hardware shares one process, old laptops are taken apart in the MacBuild area. Taking apart old laptops is not very difficult or time consuming, and can probably be done at the triage station.

← Older revision		Revision as of 03:33, 13 August 2007
Line 35:		Line 35:
	It's at [[Tonys_MacTriage_Devel#iMacBuild]]. I'll use that as a starting point for a new description. There		It's at [[Tonys_MacTriage_Devel#iMacBuild]]. I'll use that as a starting point for a new description. There
	is also a build chart that details some of the steps at [[A_Mac_Rebuild_Table]].		is also a build chart that details some of the steps at [[A_Mac_Rebuild_Table]].
		+
		+	Here's the general idea. Triage still separates things we want to consider for rebuild (keeper) from things that we don't (reject). The basic criteria for 'keeper' are
		+	* slot-load iMac, G3/G4/G5 tower, or any other desktop model in the G4/G5 generation that can be made to POST
		+	* if iMac (all-in-one), displays video.
		+	* any G3 Pismo or newer laptop
		+	Before leaving triage for whatever reason, hard drives, memory and batteries are removed.
		+
		+	The unresolved issue in this overview is what to do with rejected laptops. Rejected all-in-one iMacs can be stripped down to monitor-only status; there is informal precedent in Eval-1 for PC all-in-one machines (and Mac all-in-one Performas).