Remove /mnt/partner_partition

Remove /mnt/partner_partition

BUG=chromium-os:6840
TEST=Build and install Chrome OS image, no issues observed

Change-Id: I24ea3a96490a81c8926852eff6d2451e57e196f7

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=0a649b5

[gauravsh, 2011-02-22 19:03:37]

(Adding Will and Bill as reviewers. Please list people who were major
contributors to the files that you change as reviewers.)

This looks fine to me. But please wait for an LGTM from Will or Bill.

Also, please test this change and ensure it doesn't break anything (and
optionally, update the TEST field in the issue description). Thanks!

[Will Drewry, 2011-02-22 19:07:00]

On 2011/02/22 19:03:37, gauravsh wrote:
> (Adding Will and Bill as reviewers. Please list people who were major
> contributors to the files that you change as reviewers.)
> 
> This looks fine to me. But please wait for an LGTM from Will or Bill.
> 
> Also, please test this change and ensure it doesn't break anything (and
> optionally, update the TEST field in the issue description). Thanks!


Why are we removing this now?  Is it blocking anything in particular?  Will
removing this here cause problems during OOBE boot or has that already been
fixed in advance?

(If using this approach is still our long-term goal, I'm not sure we should nix
the supporting code right now, but if we're really expecting to not exercise it
for a long while, then maybe it makes sense :)

thanks!

[Dmitry Polukhin, 2011-02-22 19:20:03]

On 2011/02/22 19:07:00, Will Drewry wrote:
> Why are we removing this now?  Is it blocking anything in particular?  Will
> removing this here cause problems during OOBE boot or has that already been
> fixed in advance?

OEM partition is not actually used. Moreover I fixed Chrome to read /opt/oem
already. This code is not needed. 

> (If using this approach is still our long-term goal, I'm not sure we should
nix
> the supporting code right now, but if we're really expecting to not exercise
it
> for a long while, then maybe it makes sense :)

Real OEM specific partition (if it is created) will be much larger and will be
mounted all the time. So having this insecure partition in image has no sense.
This CL is part 1/3 of removing OEM partition. Two other pieces are here:
http://codereview.chromium.org/6542043/
http://codereview.chromium.org/6469078/

[Will Drewry, 2011-02-22 19:42:29]

On 2011/02/22 19:20:03, Dmitry Polukhin wrote:
> On 2011/02/22 19:07:00, Will Drewry wrote:
> > Why are we removing this now?  Is it blocking anything in particular?  Will
> > removing this here cause problems during OOBE boot or has that already been
> > fixed in advance?
> 
> OEM partition is not actually used. Moreover I fixed Chrome to read /opt/oem
> already. This code is not needed. 
> 
> > (If using this approach is still our long-term goal, I'm not sure we should
> nix
> > the supporting code right now, but if we're really expecting to not exercise
> it
> > for a long while, then maybe it makes sense :)
> 
> Real OEM specific partition (if it is created) will be much larger and will be
> mounted all the time. So having this insecure partition in image has no sense.
> This CL is part 1/3 of removing OEM partition. Two other pieces are here:
> http://codereview.chromium.org/6542043/
> http://codereview.chromium.org/6469078/

Cool, works for me then.

Thanks!

[gauravsh, 2011-02-23 19:51:17]

lgtm too