According to: http://www.grsecurity.net/confighelp.php it looks like hwclock works if rtc is enabled in the kernel, if disable i/o is enabled. I think either grsecurity changed, or our bootscripts changed, since I last tried the setclock script. Can you confirm the LFS setclock script works, with all but the 'disable i/o' and 'kmem' options enabled?
robert On March 22, 2006 01:13 pm, Sebastian Faulborn wrote: > Hello everybody! > > In "HLFS/Chapter07/Configuring the setclock Script" it says that the > setclock script does not work with grsec enabled kernels. > > However when I issue "hwclock --hctosys --utc" or "hwclock --hctosys > --localtime" my output of "date" shifts correctly by 1 hour and > grsec correctly logs the change in time to syslog (I am +1hr GMT). I > have all grsec/pax options enabled except for those which make X-Windows > fail. > > Similarly writing to the hardware clock also works. > > Is it possible that grsec now supports setting the clock correctly? > > Sebastian Faulborn > EMail: info _at_ aliensoft _dot_ org > Homepage: www.secure-slinux.org <http://www.secure-slinux.org> -- http://linuxfromscratch.org/mailman/listinfo/hlfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
