On Fri, Sep 13, 2019 at 10:41:24AM -0500, David Wright wrote:
On Fri 13 Sep 2019 at 08:35:51 (-0400), Michael Stone wrote:
I'm saying that /etc/timezone and /etc/localtime should be consistent
and valid, in which case they both do the same thing. There isn't one
that uses "the actual rules and
On Fri, Sep 13, 2019 at 10:41:24AM -0500, David Wright wrote:
> On Fri 13 Sep 2019 at 08:35:51 (-0400), Michael Stone wrote:
> > I'm saying that /etc/timezone and /etc/localtime should be consistent
> > and valid, in which case they both do the same thing.
> Perhaps we'll just have to beg to
On Fri 13 Sep 2019 at 08:35:51 (-0400), Michael Stone wrote:
> On Sun, Sep 01, 2019 at 08:32:56PM -0500, David Wright wrote:
> > On Wed 28 Aug 2019 at 14:08:47 (-0400), Michael Stone wrote:
> > > On Wed, Aug 28, 2019 at 12:25:32PM -0500, David Wright wrote:
> > > > On Mon 12 Aug 2019 at 08:38:47
On Sun, Sep 01, 2019 at 08:32:56PM -0500, David Wright wrote:
On Wed 28 Aug 2019 at 14:08:47 (-0400), Michael Stone wrote:
On Wed, Aug 28, 2019 at 12:25:32PM -0500, David Wright wrote:
> On Mon 12 Aug 2019 at 08:38:47 (-0400), Greg Wooledge wrote:
> > The first one is the /etc/timezone file,
On Wed, 28 Aug 2019 at 19:25 David Wright wrote:
> On Mon 12 Aug 2019 at 08:38:47 (-0400), Greg Wooledge wrote:
> > On Sat, Aug 10, 2019 at 12:16:04PM -0500, David Wright wrote:
> > > If you're desparate to get the timezone altered earlier in your
> > > installation process, you could always do
On Wed 28 Aug 2019 at 14:08:47 (-0400), Michael Stone wrote:
> On Wed, Aug 28, 2019 at 12:25:32PM -0500, David Wright wrote:
> > On Mon 12 Aug 2019 at 08:38:47 (-0400), Greg Wooledge wrote:
> > > The first one is the /etc/timezone file, which as you say, is a
> > > simple text file that a (root)
On Wed, Aug 28, 2019 at 12:25:32PM -0500, David Wright wrote:
On Mon 12 Aug 2019 at 08:38:47 (-0400), Greg Wooledge wrote:
The first one is the /etc/timezone file, which as you say, is a
simple text file that a (root) user can edit. I believe this is the
backward-compatibility one.
And
On Mon 12 Aug 2019 at 08:38:47 (-0400), Greg Wooledge wrote:
> On Sat, Aug 10, 2019 at 12:16:04PM -0500, David Wright wrote:
> > If you're desparate to get the timezone altered earlier in your
> > installation process, you could always do it manually: try switching
> > to VC2 and editing the file
On Lu, 12 aug 19, 08:38:47, Greg Wooledge wrote:
>
> I don't have any kind of statistics for how many programs use one vs.
> the other. It's not trivial to find out.
/etc/localtime gets many more hits on https://codesearch.debian.net, if
you consider this to be a relevant metric.
FWIW,
On Mon, Aug 12, 2019 at 08:38:47AM -0400, Greg Wooledge wrote:
> On Sat, Aug 10, 2019 at 12:16:04PM -0500, David Wright wrote:
> > If you're desparate to get the timezone altered earlier in your
> > installation process, you could always do it manually: try switching
> > to VC2 and editing the
On Sat, Aug 10, 2019 at 12:16:04PM -0500, David Wright wrote:
> If you're desparate to get the timezone altered earlier in your
> installation process, you could always do it manually: try switching
> to VC2 and editing the file /target/etc/timezone to the string UTC
> (the alternatives are simply
On Sat 10 Aug 2019 at 09:25:22 (+), Russell L. Harris wrote:
> On Sat, Aug 10, 2019 at 08:56:01PM +1200, Richard Hector wrote:
> > That's true of the timestamps that are part of the filesystem metadata,
> > but not true of any timestamps included in the file content itself - eg
> > as part of
On Sat 10 Aug 2019 at 09:01:27 (+), Russell L. Harris wrote:
> On Sat, Aug 10, 2019 at 09:14:08AM +0200, deloptes wrote:
> > Why? The non expert lives somewhere relative to UTC, why should I use UTC.
> > AFAIK it is always UTC in the background adding or substracting the
> > timezone and
Russel writes:
> As to file creation and access datestamps, what time is shown by, for
> example, the "ls -al" command if I select central time zone? Do I see
> Central times, or UTC? When examining file creation and access times,
> I simply wish all files always to be datestamped in UTC.
Make
On 10/08/19 9:25 PM, Russell L. Harris wrote:
> On Sat, Aug 10, 2019 at 08:56:01PM +1200, Richard Hector wrote:
>> That's true of the timestamps that are part of the filesystem metadata,
>> but not true of any timestamps included in the file content itself - eg
>> as part of log lines. I don't
On Sat, Aug 10, 2019 at 08:56:01PM +1200, Richard Hector wrote:
That's true of the timestamps that are part of the filesystem metadata,
but not true of any timestamps included in the file content itself - eg
as part of log lines. I don't know which Russell is concerned about.
In the non-expert
Russell L. Harris wrote:
> To each his own. I remember the explanation of an airline pilot as to
> the reason he kept his wristwatch set to GMT. Constantly crossing
> from one time zone to another, he said that the mental conversion
> quickly became automatic and painless, and was much less
On Sat, Aug 10, 2019 at 09:14:08AM +0200, deloptes wrote:
Why? The non expert lives somewhere relative to UTC, why should I use UTC.
AFAIK it is always UTC in the background adding or substracting the
timezone and perhaps summer time and other specifics. I do not want to
calculate each time on
On 10/08/19 8:49 PM, Andrei POPESCU wrote:
> On Vi, 09 aug 19, 21:38:23, Russell L. Harris wrote:
>> Is there a work-around, so that files written during the
>> installation process have the correct datestamp?
>
> It seems to me like you are confusing the hardware clock (the internal
> clock of
On Vi, 09 aug 19, 21:38:23, Russell L. Harris wrote:
> The netinst cd image for Buster 10.0.0 does not offer a UTC option for
> English -> United States.
>
> This is a critical bug; every installer without exception should offer UTC.
>
> Is there a work-around, so that files written during the
>
Russell L. Harris wrote:
> But I still think that even the non-expert should be allowed, if not
> strongly encouraged, to use UTC.
Why? The non expert lives somewhere relative to UTC, why should I use UTC.
AFAIK it is always UTC in the background adding or substracting the
timezone and perhaps
On 8/10/2019 7:42 AM, Russell L. Harris wrote:
> On Fri, Aug 09, 2019 at 10:39:23PM -0500, David Wright wrote:
>> It's not clear to me why you couldn't select this, nor why your files
>> would have the wrong timestamp. Here's some output from a buster
>> installation on acer. As it was my first, I
On Fri, Aug 09, 2019 at 10:39:23PM -0500, David Wright wrote:
It's not clear to me why you couldn't select this, nor why your files
would have the wrong timestamp. Here's some output from a buster
installation on acer. As it was my first, I kept the typescript.
...
Thanks, David. For some
On Fri 09 Aug 2019 at 21:38:23 (+), Russell L. Harris wrote:
> The netinst cd image for Buster 10.0.0 does not offer a UTC option for
> English -> United States.
>
> This is a critical bug; every installer without exception should offer UTC.
>
> Is there a work-around, so that files written
On Fri, 9 Aug 2019 21:38:23 +
"Russell L. Harris" wrote:
> The netinst cd image for Buster 10.0.0 does not offer a UTC option for
> English -> United States.
Mine did. IIRC it was part of the timezone choice at install. Last in
the list. Stock Buster Netinstall CD. I don't use UTC, but
Charlie Kravetz writes:
> The installer attempts to allow all actual timezones for a
> country. The United States does not actually have a timezone called
> UTC.
UTC isn't a timezone. It should be offered, though.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Fri, 9 Aug 2019 21:38:23 +
"Russell L. Harris" wrote:
>The netinst cd image for Buster 10.0.0 does not offer a UTC option for
>English -> United States.
>
>This is a critical bug; every installer without exception should offer UTC.
>
>Is there a work-around, so that files written during
The netinst cd image for Buster 10.0.0 does not offer a UTC option for
English -> United States.
This is a critical bug; every installer without exception should offer UTC.
Is there a work-around, so that files written during the
installation process have the correct datestamp?
One suggestion
28 matches
Mail list logo