ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: John Stultz <john.stultz@linaro.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Dealing with 2038
Date: Tue, 06 May 2014 20:20:47 +0200	[thread overview]
Message-ID: <5252732.F3YIzHDqI3@wuerfel> (raw)
In-Reply-To: <536921B5.8090100@linaro.org>

On Tuesday 06 May 2014 10:53:57 John Stultz wrote:
> On 05/06/2014 05:57 AM, Theodore Ts'o wrote:
> > I suspect the only real way of dealing with the problem for 32-bit
> > architectures is to consider doing a major version bump for all shared
> > libraries, and for a while, 32-bit distributions might have to ship
> > two versions of all of the more popular shared libraries.
> ...
> > OTOH, if the main issue is "industrial control and security systems"
> > as stated in the original problem description,, I very much doubt they
> > would need GNOME shared libraries.  :-)
> 
> Well, there's also things like in-car-infotainment systems (which would
> annoy future car collectors should they stop working), which may require
> GUI toolkits. But I suspect the most problematic cases will be embedded
> systems in the literal sense of "embedded in the wall".

Medical equipment (and I assume military, which is often in the same
category) is probably a big thing. I remember we had a big discussion
about a product at a former employer when a customer asked for support
beyond 2038. I think we ended up saying that the hardware is fine but
no supported distro would handle this.

	Arnd

  reply	other threads:[~2014-05-06 18:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 18:33 John Stultz
2014-05-05 19:23 ` Andy Lutomirski
2014-05-05 20:53 ` josh
2014-05-05 23:20   ` Andy Lutomirski
2014-05-06  2:12   ` H. Peter Anvin
2014-05-06  2:21     ` Josh Triplett
2014-05-06 12:57       ` Theodore Ts'o
2014-05-06 17:53         ` John Stultz
2014-05-06 18:20           ` Arnd Bergmann [this message]
2014-05-06 20:19             ` Theodore Ts'o
2014-05-06 20:33               ` josh
2014-05-06 20:50                 ` Theodore Ts'o
2014-05-06 22:06                   ` John Stultz
2014-05-07  2:07                     ` Theodore Ts'o
2014-05-07 11:19                       ` Jonathan Corbet
2014-05-07 17:28                       ` John Stultz
2014-05-09 15:05                         ` Theodore Ts'o
2014-05-08 20:37                       ` Ben Hutchings
2014-05-09 15:10                         ` Theodore Ts'o
2014-05-09 20:39                           ` Arnd Bergmann
2014-05-09 22:33                             ` Josh Triplett
2014-05-10  0:16                               ` H. Peter Anvin
2014-05-10  1:44                                 ` Rafael J. Wysocki
2014-05-15 12:18                                 ` Grant Likely
2014-05-15 17:20                                   ` H. Peter Anvin
2014-05-16  2:50                                     ` Jason Cooper
2014-05-10  0:19                               ` Andy Lutomirski
2014-05-06 21:17               ` Daniel Phillips
2014-05-06 21:56                 ` Luck, Tony
2014-05-07  1:56                   ` Daniel Phillips
2014-05-07 14:00         ` Grant Likely
2014-05-09 17:30       ` H. Peter Anvin
2014-05-06  1:25 ` Li Zefan

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=5252732.F3YIzHDqI3@wuerfel \
    --to=arnd@arndb.de \
    --cc=john.stultz@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox