Bug#536552: console-setup: /bin/setupcon: line 319: /etc/console-setup/cached.kmap.gz: Read-only file system
Anton Zinoviev wrote, on 12/07/09 05:46:
On Sat, Jul 11, 2009 at 12:40:27PM +0930, Arthur Marsh wrote:
I noticed the following on the boot log:
Setting preliminary keymap.../bin/setupcon: line 319:
/etc/console-setup/cached.kmap.gz: Read-only file system
Thats a bit strange. Line 319 is surrounded by the followin 'if' statement:
if ..... && [ -d /usr/share/X11/xkb]; then
# line 319
fi
The test for /usr/share/X11/xkb is in order to assure that /usr is
mounted. And when /usr is mounted the access to /etc is not read-only.
Have you intentionaly made /etc read only?
It was probably read-only as it hadn't had fsck run on it at that stage:
Sat Jul 11 12:17:46 2009: Setting preliminary keymap.../bin/setupcon:
line 319:
/etc/console-setup/cached.kmap.gz: Read-only file system
Sat Jul 11 12:17:46 2009: done.
Sat Jul 11 12:17:46 2009: Setting parameters of disc: /dev/hda.
Sat Jul 11 12:17:46 2009: Setting the system clock.
Sat Jul 11 12:17:46 2009: System Clock set to: Sat Jul 11 12:17:46 CST 2009.
Sat Jul 11 12:17:46 2009: Activating swap:swapon on /dev/hda5
Sat Jul 11 12:17:46 2009: swapon: /dev/hda5: found swap v1 signature
string for
4 KiB PAGE_SIZE
Sat Jul 11 12:17:46 2009:
Sat Jul 11 12:17:46 2009: swapon: /dev/hda5: pagesize=4096,
swapsize=2253692928,
devsize=2253694464
Sat Jul 11 12:17:46 2009: .
Sat Jul 11 12:17:46 2009: Will now check root file system:fsck 1.41.7
(29-June-2
009)
Sat Jul 11 12:17:46 2009: [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0
/dev/hda7
Sat Jul 11 12:17:46 2009: /dev/hda7: clean, 397679/16777216 files,
6656857/67107
505 blocks
Is this any kind of a problem?
Not realy. Because console-setup is unable to store information in
cached.kmap.gz it has to compute the keymap twice on every boot. This
will slow down the boot process by few seconds. Another (small?)
problem will occur when fsck requires manual interraction during the
boot and /usr is not part of the root file system. In this case
console-setup will be unable to compute the proper keymap so it will
have to use cached.kmap.gz. But I suppose that cached.kmap.gz contains
your real keymap unless you have experimented with strange keyboards. :)
Anton Zinoviev
Regards,
Arthur.
Reply to: