Discuss Components of an ID File to Track OEM Installations

Registered by Robbie Williamson on 2008-11-17

Right now, for systems installed using "OEM mode", we ask the OEM for an identifier during installation and save that identifier in /var/log/installer/oem-id on the target system. This file is just a text file with a single line containing an identifier for that batch of systems from the OEM. All of this was done before we really had a need for it. Now that we have OEMs requesting this feature, we need to discuss how we create the file, where we should store it, its format, and what info it should contain.

Blueprint information

Status:
Complete
Approver:
Colin Watson
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Evan
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Evan on 2009-02-18
Completed by
Evan on 2009-05-14

Related branches

Sprints

Whiteboard

2008-12-17 cjwatson: Reviewed; still needs quite a bit of work.

2008-12-24 installshield_freak:
I think we should have a line in the GNOME About dialog that states:
"Manufactured and supported by: " and *companyname* and something to create oem configuration netboot sets for windows and ubuntu for multiusers. for a quick oem installation. and in the configuration sets have it to where we can configure drivers, packages, type of install, OEM Branding. etc I hope this makes some sense. to the developers.that way we can track the OEM's by name as well as tracking id's for support.

2009-02-18 evand: Code to copy the DCD to the target filesystem is present in ubiquity.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.