From: "Michael J. Accetta" <mja@laurelnetworks.com>
To: Stephen Williams <612dlag102@sneakemail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Hardware Requrements for Linux on 405GPr
Date: Fri, 15 Aug 2003 17:05:47 -0400 [thread overview]
Message-ID: <3F3D4B2B.9000700@laurelnetworks.com> (raw)
In-Reply-To: 3F3BEE49.4050806@mvista.com
Mark Hatle wrote:
> An RTC is not required for Linux. Many designs I have seen do not have
> one. However, an RTC is an excellent device to have available! Various
> applications and services may require a consistant, ever increasing
> time. NFS is the one that comes to mind immediatly. If the device is
> rebooted and the time goes back to default, NFS may have problems.
You can defintely run into problems with NFS and no RTC. We have a setup
like this and without a RTC, NFS would end up allocating (I think)
request id's based on the time that might be cached on the server to
handle replay. With the time always starting at 0, different requests
with the same id could be issued from the card across boot sessions and
the server would have cached the old request, producing some confusing
results when it replied to the cached rather than new request. Our
solution was to add a TIME protocol probe in the ipv4 BOOTP path so the
card always got the right time before continuing the boot.
Mike Accetta
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-15 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 20:05 Hardware Requrements for Linux on 405GPr Stephen Williams
2003-08-14 20:17 ` Mark Hatle
2003-08-14 20:30 ` Stephen Williams
2003-08-15 21:05 ` Michael J. Accetta [this message]
2003-08-14 20:26 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F3D4B2B.9000700@laurelnetworks.com \
--to=mja@laurelnetworks.com \
--cc=612dlag102@sneakemail.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.