kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Year 2038 time set problem
Date: Mon, 5 Mar 2018 07:26:23 +0100	[thread overview]
Message-ID: <20180305062623.GA13208@kroah.com> (raw)
In-Reply-To: <7d98c653-a64b-628d-e461-17962c6e8015@mrbrklyn.com>

On Mon, Mar 05, 2018 at 01:15:03AM -0500, Ruben Safir wrote:
> On 03/05/2018 01:00 AM, Greg KH wrote:
> > "How many security issues were those systems
> > vulnerable to over that period of time?  All of them."
> 
> 
> So I'm understanding.  And yet, the kernel is getting harder and harder
> to manage.  It takes hours to just walk through all the choices.

You're doing it wrong.  Don't ever walk through "all the choices".

Take a distro kernel, boot your box, plug in all of the devices you want
to support, then do:
	'make localmodconfig'
in your own kernel drectory and spend 5 minutes building your new
kernel and then booting into it.

> I went from using opensuse to using a rolling release of Artix, which is
> arch based.  One of the things I've noticed is that the number of kernel
> upgrades are brisk, which with opensuse, it was rare for a kernel
> upgrade.  I thought most of these upgrades was updated hardware options
> and features, and not security.  Opensuse would get upset if you didn't
> use their derivative of the kernel.

Then use your distros version of a kernel.  opensuse is great, as is
arch, and a few other community-based distros, like Fedora.  I trust
them to get it right with kernel updates.  If you don't want to do it
yourself, use one of those "big 3" and feel quite comfortable with
rebooting every few weeks and all will be fine.

thanks,

greg k-h

  reply	other threads:[~2018-03-05  6:26 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 [this message]
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
  -- 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=20180305062623.GA13208@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).