linux-kernel - Re: NTP time sync

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 27 Nov 2006 01:06:48 +0300
From:	Michael Raskin <a1d23ab4@...l.ru>
To:	Joakim Tjernlund <joakim.tjernlund@...nsmode.se>,
	linux-kernel@...r.kernel.org
Subject: Re: NTP time sync

Joakim Tjernlund wrote:
>>> Is that the way it is supposed to be? How do I create a 
>> static /dev/rtcN in my /dev
>>> directory if the major number isn't fixed?
>>> Maybe I am just missing something, feel free to correct me :)
>>  udev ;)
>>
>>  the concept of static numbers is quite old...
> 
> Yes it is old, but is the old way unsupported now? I have an embedded target
> which is using the old static /dev directory, do I need to make
> it udev aware to use newer features like the rtc subsystem?
Really you do not have to make it udev aware, it is enough to make it 
sysfs aware. You will be done by reading /sys/class/misc/rtc/dev on 
initialization and replacing /dev/rtcN with device with the address 
read. If you have configuration static enough, I guess you can even 
create it once and for life of current setup with current kernel.
-
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/