linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Robin <robin@india.tejasnetworks.com>
Cc: Linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: TZ variable setting for denx 2.4.20
Date: Thu, 06 Jan 2005 13:12:33 +0100	[thread overview]
Message-ID: <20050106121238.BB99AC108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 05 Mar 2005 23:05:55 +0530." <4229EDFB.2040402@india.tejasnetworks.com>

In message <4229EDFB.2040402@india.tejasnetworks.com> you wrote:
>
> I am trying to find a way of setting TZ environment variable with DST

Your subject is misleading. Timezone handling is a user space  issue.
It has nothing to do with the kernel verison.

> I am using 2.4.20 linux kernel from denx.I am running date command from

This has nothing to do with your problems.

> busybox version 0.6 which in is using strftime. The processor is ppc860T.

BB 0.6 ? AFAICT there is no such version. Do you mean  busybox-0.60.5 ?

This is awfully old. Maybe  you  should  try  running  an  up-to-date
version  of  busybox  first?  If  this doesn;'t work, please consider
using the real GNU date  command.  You  should  understand  that  the
busybox  tools  only provide limited functionality, so fancy features
like complex timezone support may not be available.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Status quo. Latin for "the mess we're in."

  reply	other threads:[~2005-01-06 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 10:04 TZ variable setting for denx 2.4.20 Robin
2005-01-06 12:12 ` Wolfgang Denk [this message]
2005-01-06  1:33   ` Robin
2005-01-06 13:56     ` Marius Groeger
2005-01-07  7:28       ` Robin
2005-01-09  3:30         ` Tony Lee
2005-01-19 22:11 ` annamaya

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=20050106121238.BB99AC108D@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=robin@india.tejasnetworks.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).