Hi everyone,
This is an old and pretty moot point for LFS, but I thought I'd make a
post about it anyway. A few months back, Greg Schafer pointed out
that gcc-3.4.x PCH doesn't handle a kernel feature introduced in
2.6.12. Details can be found in this post
http://linuxfromscratch.org/pipermail/l
Ken Moffat wrote:
On Thu, 3 Nov 2005, Duncan Webb wrote:
What I don't understand is why anybody would have a problem syncing
the hardware clock to the system clock at reboot/power off. After all
the system clock is synced to the hardware clock at boot.
In that case, please search the l
On Fri, Nov 04, 2005 at 12:29:23AM -0100, Duncan Webb wrote:
>
> Sort of guessed this by Archaic reaction. Never would have questioned it
> had the start case not synced to the hardware clock.
That's a fair question. However, where would the system clock be
initially set if not from the hwclock?
On Thu, Nov 03, 2005 at 11:02:49PM -0100, Duncan Webb wrote:
> >
> Running a NTP daemon requires a permanent internet connection. Dual boot
> usually requires the clock in local time, that's clear.
Absolutely and totally false. Please do your research before making such
statements.
> What I don'
On Thu, 3 Nov 2005, Duncan Webb wrote:
What I don't understand is why anybody would have a problem syncing the
hardware clock to the system clock at reboot/power off. After all the system
clock is synced to the hardware clock at boot.
In that case, please search the lfs archives and warm
Bryan Kadzban wrote:
On Thu, Nov 03, 2005 at 08:28:12AM -0700, Archaic wrote:
On Thu, Nov 03, 2005 at 09:47:54AM -0100, Duncan Webb wrote:
Maybe I was not too clear.
No, you were perfectly clear.
If the system clock is set to local time then when you shut-down the
hardwa
On Thu, Nov 03, 2005 at 08:28:12AM -0700, Archaic wrote:
> On Thu, Nov 03, 2005 at 09:47:54AM -0100, Duncan Webb wrote:
> > >
> > Maybe I was not too clear.
>
> No, you were perfectly clear.
>
> > If the system clock is set to local time then when you shut-down the
> > hardware clock should be se
On Thu, Nov 03, 2005 at 09:47:54AM -0100, Duncan Webb wrote:
> >
> Maybe I was not too clear.
No, you were perfectly clear.
> If the system clock is set to local time then when you shut-down the
> hardware clock should be set to system time.
And again, no. LFS cannot assume the sanity of the sys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm installing a LFS ona VIA Epia platform (next step: kernel ;-)),
that has neither an Intel nor AMD processor (VIA C3 Nehemiah aka c3-2).
And after applying the coreutils-5.2.1-uname-2.patch, uname -p returned
"i686", which is better than "u
Archaic wrote:
On Thu, Nov 03, 2005 at 05:58:51AM -0100, Duncan Webb wrote:
Now that we're no longer in summer time in the Makefile for
LFS-Bootscripts-3.2.1 there are no rules to install setclock during a
reboot or shutdown. So the hardware clock is not being synchronised with
the system
On Thu, 3 Nov 2005 01:28:11 -0700
Archaic <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 03, 2005 at 05:58:51AM -0100, Duncan Webb wrote:
> >
> > Now that we're no longer in summer time in the Makefile for
> > LFS-Bootscripts-3.2.1 there are no rules to install setclock during a
> > reboot or shutdow
On Thu, Nov 03, 2005 at 05:58:51AM -0100, Duncan Webb wrote:
>
> Now that we're no longer in summer time in the Makefile for
> LFS-Bootscripts-3.2.1 there are no rules to install setclock during a
> reboot or shutdown. So the hardware clock is not being synchronised with
> the system clock.
It
12 matches
Mail list logo
