lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 14 Jun 2008 13:33:27 +0200 From: Alessandro Zummo <alessandro.zummo@...ertech.it> To: rtc-linux@...glegroups.com Cc: bunk@...nel.org, david-b@...bell.net, Ingo Molnar <mingo@...e.hu>, Lior Dotan <liodot@...il.com>, "Rafael J. Wysocki" <rjw@...k.pl>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, bugme-daemon@...zilla.kernel.org Subject: Re: [rtc-linux] Re: [Bug 10866] /dev/rtc was missing until I disabled CONFIG_RTC_CLASS On Sat, 14 Jun 2008 14:18:06 +0300 Adrian Bunk <bunk@...nel.org> wrote: > > If Lior's problem was due to something like CONFIG_RTC_CLASS=y, > CONFIG_RTC_DRV_CMOS=n that's a kernel configuration that would > anyway break when the old driver gets removed, and it just broke > earlier. I haven't seen the .config, but CONFIG_RTC_CLASS=y and CONFIG_RTC_DRV_CMOS=n is perfectly legal. It just don't have to be put in the default x86 config maybe, but it's legal.. > Everyone seems to focus on this kconfig related case, what about my > point of no /dev/rtc with a static /dev ? When talking about existing > setups and embedded systems that's a real issue for some systems. the device node creation is yet another option of the rtc class. it should be on by default in any defconfig, I'd guess. But then you'll get /dev/rtc0 without any specific device node. As I said in the past, I'd accept a patch to handle this special case of having /dev/rtc with a specific major and minor, but I'm against it. It would be better to upgrade your userspace when such big changes happens in the kernel. In fact, it the first time that the rtc has been touched in the last.. 10 year? I think it's not unreasonable to ask to upgrade userspace. wrto embedded systems, having worked with them for years, you are expected to check every detail of every new kernel you want to use before releasing it or, say, uploading it to your lander on the moon :) -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists