Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cache keymap before first boot #38

Closed
asb opened this issue Jun 13, 2012 · 5 comments
Closed

cache keymap before first boot #38

asb opened this issue Jun 13, 2012 · 5 comments
Labels
Milestone

Comments

@asb
Copy link
Owner

asb commented Jun 13, 2012

There is no need for this to be regenerated locally for every user on the first boot. jojopi suggests setupcon --force --save will do the trick http://www.raspberrypi.org/phpBB3/viewtopic.php?p=97886#p97886

@asb asb closed this as completed in eb9b172 Jun 13, 2012
@asb asb reopened this Jun 15, 2012
@asb
Copy link
Owner Author

asb commented Jun 15, 2012

Reopening, upon testing it seems the attempted fix was insufficient.

@asb
Copy link
Owner Author

asb commented Jun 17, 2012

I'm slightly baffled by this. As far as I can see from diffing rootfs from a booted and unbooted image, /etc/console-setup/cached_UTF-8_del.kmap.gz is the only relevant file (and the gunzipped version is identical). I've played with fake-hwclock and the reason this is regenerated on first boot doesn't seem to be related to the timestamp on the files...

@jojopi
Copy link

jojopi commented Jun 18, 2012

Looks like you run setup_console_setup after cache_keymap. The test in setupcon is that both /etc/default/keyboard and /etc/default/console-setup must be older than the cached file.

@asb
Copy link
Owner Author

asb commented Jun 18, 2012

You are completely right! Doh! I should have looked for something rather more trivial than that. This is almost definitely the culprit, thanks for taking a look.

@asb
Copy link
Owner Author

asb commented Jul 13, 2012

Fixed for some time now.

@asb asb closed this as completed Jul 13, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants