Userland Subarch Detection for ARM
Currently, there is no standardized mechanism in userland to determine which specific subarchitecture we are on, and at least three different and unique implications of said detections. This spec moves towards moving a standardized detection method into the base installer, usable by any script.
Blueprint information
- Status:
- Complete
- Approver:
- David Mandala
- Priority:
- High
- Drafter:
- Michael Casadevall
- Direction:
- Approved
- Assignee:
- Michael Casadevall
- Definition:
- Approved
- Series goal:
- Accepted for natty
- Implementation:
-
Implemented
- Milestone target:
-
natty-alpha-3
- Started by
- Colin Watson
- Completed by
- Michael Casadevall
Whiteboard
Work Items (natty-alpha-3):
[cjwatson] Determine archdetect package naming (upstream discussion inconclusive, just punting to 'archdetect-deb' for now): DONE
[cjwatson] Deploy archdetect as userspace tool: DONE
[cjwatson] Colin to handle trivial packaging changes in ubiquity: DONE
Work Items: (natty-alpha-3):
[persia] Prepare best-practice examples for use in maintainer scripts: POSTPONED
[mcasadevall] Investigate kernel postinst scripts to see if we need this: POSTPONED
[mcasadevall] Ensure image build tools have a means to declare environment: POSTPONED
[mcasadevall] Confirm same behavior of archdetect in standard userland to installer environment: DONE
[mcasadevall] Confirm userland guessing (archdetect -g) works properly in userland environment: DONE
[mcasadevall] Confirm kernel and distro upgrades still work as expecting with new flash-kernel code: POSTPONED
[mcasadevall] Discuss upstreaming into Debian with cjwatson: POSTPONED
[mcasadevall] Clean up flash-kernel to use archdetect: POSTPONED
Work Items
Dependency tree

* Blueprints in grey have been implemented.