Tonys Mac Page

I'm moving all of my development stuff from Mac to here. There is a link there back to here.

What are we building: an iMac or a Linux box?
 * There seems to be some thought in the community that the rebuilt iMacs should retain an Apple Mac personality: hardware configuration should match the original label, one-button mouse, etc. I have a some of arguments against this.


 * 1. Rebuilt iMac boxes are already have a significantly different hardware configuration than is indicated on any label. Ubuntu installation requires/suggests 256MB of ram; the labels we see say 32MB, 64MB, or 128MB.  Many iMacs that we see have hard drives that are 4GB or 6GB. Those are being replaced with 10-15GB drives.


 * 2. Macs that arrive may already have been upgraded with larger drives and/or more memory. The suggested practice of retaining those configurations, or trying to match label configurations, has led to the suggestion to test memory and hard drives in place. Testing in place adds several hours to the Mac Eval/Build process.  It would be more efficient, and more in keeping with the existing build process, to remove all memory and hard drives, send them to Advanced Testing, and replace them from the tested memory and hard drive stacks to produce a standard store configuration.


 * 3. The Mac 'personality' is a combination of hardware, Mac OS, Mac software, and Mac UI. The installation of Linux replaces three of the four parts. With the exception of the way  the box looks, the Mac personality is gone.


 * 4. The Mac OS 9 (and OS X ?) UI is tailored to a one-button mouse. The Linux/Ubuntu UI expects a two-button or three button mouse.  Getting at the 2-3 button functionality of the Ubuntu UI is awkward at best with a one-button mouse.


 * My contention is that we are rebuilding the Macs to be, for the moment, Freegeek Store Linux Boxes. They should be configured as a standard low-end store box with 256MB, 10-15G HD, and a 3-button mouse.  This approach aloows for a better use of the existing triage/test/build process.

Drivers
 * Unused available hardware
 * Contribute to revenue stream
 * Expand HW knowledge in Programs

Constraints
 * Storage space limitation
 * Few knowledgeable volunteers
 * CRT hazard in recycle

To Do:
 * Flesh out Mac Rebuild section
 * Rework MacPile/Triage relationship (currently MacPile is Triage Entry and MacRenewal Pickup)
 * Distinguish between iMac 'bubble' boxes and Towers during Triage
 * Can/Should rejected Towers be recycled by FG?
 * Decide about mining from slot loaders (under the cutoff) destined for MacRenewal
 * Add suggestion for freegeek mac acceptance criteria

Here is first cut at an overview

Overview
digraph macProcess { MacProcess     [label="Mac Process" shape=tripleoctagon] Start          [label="MacPile" shape=box] FGkeep         [label="Does FG want it?\n(FG keep criteria)"] MRkeep         [label="Does MacRenewal want it?\n(MacRenewal reject criteria)"] CRT            [label="Does Recycle\ninvolve CRT hazard?"] Recycle        [lable="Recycle" shape=box] SpecialRecycle [label="Special recycle" shape=box] MacPile        [label="Return to MacPile" shape=box] MacRebuild     [label="Send to Mac Triage" shape=box]

Start      -> FGkeep FGkeep     -> MRkeep [label="No"] FGkeep     -> MacRebuild [label="Yes"] MRkeep     -> CRT [label="No"] MRkeep     -> MacPile [label="Yes"] CRT        -> Recycle [label="No"] CRT        -> SpecialRecycle [label="Yes"] }

FG Keep Criteria
 * FG Mac lowend cutoff
 * Mac Triage storage available

MacRenewal Reject Criteria
 * (Lorraine's rejection list goes here)

Special Recycle
 * Requires special training to avoid CRT flyback transformer hazard
 * Carcass sent to Monitor Recycle

Mac Triage
digraph macTriage { MacTriage     [label="Mac Triage" shape=box] BlownCaps     [label="Are there blown caps\non the system board?"] HaveCpu       [label="Does it have a CPU?"] MinimumReqs   [label="Does it have\nmemory, hard drive,\ngood battery?"] PowerPost     [label="Does it power up and POST?"] MinTestConfig [label="Install missing pieces\nfrom Mac HW Test Pool" shape=box] MiningRequests [label="Are there any\nmining requests?"] Mining        [label="Mine requested items" shape=box] MacPile       [label="Mark Rejected\nReturn to MacPile" shape=box] PmuReset      [label="Reset PMU" shape=box] Reclaim       [label="Remove Mac Test Pool HW\nif necessary" shape=box] MacRebuild    [label="Send to Mac Rebuild" shape=box] PostAfterPmu  [label="Does it power up\nand POST now?"] DeadAfterPmu  [label="Remove Mac Test Pool HW\n if necessary" shape=box]

MacTriage     -> HaveCpu HaveCpu       -> BlownCaps [label="Yes"] HaveCpu       -> MiningRequests [label="No"] BlownCaps     -> MiningRequests [label="Yes"] BlownCaps     -> MinimumReqs [label="No"] MiningRequests -> Mining [label="Yes"] MiningRequests -> MacPile [label="No"] MinimumReqs   -> PowerPost [label="Yes"] MinimumReqs   -> MinTestConfig [label="No"] Mining        -> MacPile MinTestConfig -> PowerPost PowerPost     -> PmuReset [label="No"] PowerPost     -> Reclaim [label="Yes" shape=box] Reclaim       -> MacRebuild PmuReset      -> PostAfterPmu PostAfterPmu  -> Reclaim [label="Yes"] PostAfterPmu  -> DeadAfterPmu [label="No"] DeadAfterPmu  -> MacPile

}

Notes
 * Mac Triage should maintain a pool of good memory sticks (64MB will do), small hard drives, good batteries
 * Should we mine PPC cpu's? Wouldn't this require some kind of Advanced Testing support?
 * Should we mine memory and hard drive as a matter of course on good boxes?
 * Should any hard drive or memory be tested in place?

Mac Rebuild
digraph macRebuild { MacRebuild      [label="Mac Rebuild" shape=box] }