Kevin Cernekee
unread,Apr 19, 2016, 4:50:35 PM4/19/16Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Mike Frysinger, Marc Herbert, Chromium OS dev, Anand
On Tue, Apr 19, 2016 at 1:07 PM, Mike Frysinger <
vap...@chromium.org> wrote:
> i think we were talking about generally disabling AU vs messing with the
> OOBE flow. iirc there's a flag file that gets created in /var or /home
> somewhere that says OOBE has happened. you might be able to touch that to
> bypass OOBE.
When I've wanted to do the opposite (force the system to repeat OOBE)
I've deleted /home/chronos/{.oobe_completed,Local\ State}
Maybe restoring those files from known-good backups will bypass OOBE,
but I haven't tried it. It is possible that other critical stuff gets
generated during OOBE.
> if you have ssh access, you prob could insert some iptables rules to
> outright reject connections instead of letting them time out ...
You could try changing CHROMEOS_AUSERVER in /etc/lsb-release to e.g.
http://127.0.0.1:8080/ and see if that fails more quickly.
Modifying other fields in that file, such as CHROMEOS_RELEASE_BOARD or
CHROMEOS_RELEASE_TRACK, should also cause the AU server to reject your
requests. But if you really need to run on an isolated network that
won't help much.