Might be the wrong /dev/rtc device - it should be major 254 minor 0
hwclock attempts to open /dev/rtc which is symlinked to rtc0 if udev is
Actually, it should be /dev/rtc0 (according to my Debian system)
With no helpers at all, the devices need to be static files present in
/dev. The old makedev scripts
(/dev/MAKEDEV) probably need to be overhauled to create the correct
files to cover this case.
and you can find out the correct major number like this:
root@ara5:~ # ll /dev/rtc*
crw------- 1 root root 254, 0 Dec 26 16:48 /dev/rtc0
root@ara5:~ # fgrep rtc /proc/devices
This is auto-created from devtmpfs (no udev here), FWIW.
My copy on the Falcon will still create a misc device for RTC,
My ARAnyM command line contains devtmpfs.mount=1 coupled
with a few lines in /etc/rc.local:
(test -e /dev/fd || ln -s /proc/self/fd /dev/fd || :)
(test -e /dev/stdin || ln -s /proc/self/fd/0 /dev/stdin || :)
(test -e /dev/stdout || ln -s /proc/self/fd/1 /dev/stdout || :)
(test -e /dev/stderr || ln -s /proc/self/fd/2 /dev/stderr || :)
rc.local hacks are always possible as a last resort :-) Good one, though.
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html