From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Year 2038 time set problem
Date: Mon, 5 Mar 2018 13:54:24 +0100 [thread overview]
Message-ID: <20180305125424.GA17802@kroah.com> (raw)
In-Reply-To: <2c86cc9d-a7df-7b08-f5d8-8329710be814@mrbrklyn.com>
On Mon, Mar 05, 2018 at 07:20:35AM -0500, Ruben Safir wrote:
> On 03/05/2018 06:29 AM, Bernd Petrovitsch wrote:
> > And why should "we" (whoever that is) fix the problems of others?
> >
> > The upstream can't do anything directly if the downstream simply
> > refuses to update (if there are fixes to real threats) and/or reboot
> > (if it's the kernel).
>
>
> So any system where you need to, or want to install it and forget about
> it for a long period of time, the Linux kernel can not be considered a
> choice for that usage because it needs contact oversite and upgrades.
No kernel can be considered for such a choice, this is not unique to
Linux or any other operating system, sorry.
good luck!
next prev parent reply other threads:[~2018-03-05 12:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 2:35 Year 2038 time set problem Alex Arvelaez
2018-03-05 3:14 ` Ruben Safir
2018-03-05 6:00 ` Greg KH
2018-03-05 6:15 ` Ruben Safir
2018-03-05 6:26 ` Greg KH
2018-03-05 19:52 ` Ruben Safir
2018-03-05 19:54 ` Ruben Safir
2018-03-05 15:43 ` Jeffrey Walton
2018-03-05 11:29 ` Bernd Petrovitsch
2018-03-05 12:20 ` Ruben Safir
2018-03-05 12:43 ` valdis.kletnieks at vt.edu
2018-03-05 12:54 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-05 15:35 Alex Arvelaez
2018-03-05 16:49 ` Greg KH
2018-03-05 4:07 Alex Arvelaez
2018-03-05 4:16 ` Ruben Safir
2018-03-05 5:53 ` Greg KH
2018-03-05 6:04 ` Ruben Safir
2018-03-04 20:47 Alex Arvelaez
2018-03-04 22:24 ` valdis.kletnieks at vt.edu
2018-03-05 2:21 ` Ruben Safir
2018-03-05 4:15 ` valdis.kletnieks at vt.edu
2018-03-05 4:50 ` Ruben Safir
2018-03-05 8:50 ` valdis.kletnieks at vt.edu
2018-03-05 12:15 ` Ruben Safir
2018-03-05 12:31 ` Ruben Safir
2018-03-05 12:34 ` Ruben Safir
2018-03-05 12:57 ` Darin Avery
2018-03-05 4:57 ` Ruben Safir
2018-03-05 5:03 ` Ruben Safir
2018-03-04 6:59 tali.perry at nuvoton.com
2018-03-04 18:31 ` valdis.kletnieks at vt.edu
2018-03-04 20:20 ` Ruben Safir
2018-03-04 20:54 ` Greg KH
2018-03-04 20:54 ` Greg KH
2018-03-04 22:25 ` valdis.kletnieks at vt.edu
2018-03-05 5:54 ` Greg KH
2018-02-23 9:43 techi eth
2018-02-23 13:18 ` valdis.kletnieks at vt.edu
2018-02-24 13:59 ` techi eth
2018-02-24 15:50 ` Greg KH
2018-02-26 13:15 ` Piotr Figiel
2018-02-26 14:16 ` Greg KH
2018-02-26 21:19 ` Dave Stevens
2018-02-27 9:22 ` Greg KH
2018-02-26 15:21 ` valdis.kletnieks at vt.edu
2018-02-26 15:36 ` Piotr Figiel
2018-03-01 9:19 ` techi eth
2018-03-01 12:04 ` Greg KH
2018-02-25 5:52 ` valdis.kletnieks at vt.edu
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=20180305125424.GA17802@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).