Comment 4 for bug 251056

I don't understand the rationale for this. Using oem as a user name
SHOULD work, as the bug reporter expected. The fact that oem as a user
doesn't work like it did before is a recent regression. Disallowing
completely the oem user name makes the problem WORSE.

We should return to the former behavior that allowed iterative use of
oem-config simply by using the oem user name. The technique provides
great flexibility and efficiency by enabling the system builder to
test and refine the set up for the customer, without having to
reinstall and reconfigure the entire system.

The use oem-config is a dollars-and-cents issue for us because the
margins on hardware sales are so thin. Oem-config's utility is
directly tied to the labor cost savings it provides in customizing
systems. If we cannot iteratively test the system setup after
configuration but before shipment, the labor savings are lost.

Note: Simply rebooting into oem before executing oem-config-prepare is
no substitute. We've often found that the initial user's setup after
firing off oem-config-prepare was not as expected. By running
oem-config iteratively, we've been able to trap mistakes in
configuration and keep product quality high.

Happy Trails,

Loye Young
Isaac & Young Computer Company
Laredo, Texas
http://www.iycc.net