Re: /etc/conf.d/hwclock and /etc/conf.d/adjkerntz
Sven Vermeulen <[email protected]> Mon, 12 Sep 2011 16:29:26 +0200
| Newsgroups | gmane.linux.gentoo.documentation |
|---|---|
| Message-ID | <CAPzO=NzUdghPsFW0wo5zbXWFfFf+3-zW7pcAHoKSmvhn_xKQog@mail.gmail.com> |
On Mon, Sep 12, 2011 at 12:26 AM, Francisco Blas Izquierdo Riera (klondike) <[email protected]> wrote: > Well what I want to ask here is how should we aproach this. As things stand > now: > The open rc upgrade guide mentions both (which is ok) > The gentoo bsd guide just refers to adjkerntz (which is ok) > The hand book refers only to hwclock (which is "ok" as long as there doesn't > appears a gentoo-bsd handbook). > Tthe localization guide still refers to the older clock one, here I'd like > to say: > > If, > for some reason, you need your hardware clock not to be in UTC, > you will need to edit <path>/etc/conf.d/hwclock</path> (or if you > use Gentoo BSD <path>/etc/conf.d/hwclock</path> and change > the value of <c>clock</c> from <c>UTC</c> to <c>local</c>. My main concern here is that there will be a place where the number of choices is too big. Also, you'll risk getting a higher frequency on bug reports on such paragraphs. Think for instance bootloaders, how would we deal with guides there? I'm sure we do not want to generate separate guides for just all this sort of stuff (and then use keywords)... What about making it generic (edit your clock management configuration like, like /etc/conf.d/hwclock on ... )? Wkr, Sven Vermeulen