How often do you update -current?

solarfields · 04-15-2019, 06:08 AM

Quote:

solarfields, I particularly thank you for your post and going into the details for why you don't update more often.

you're most welcome

Quote:

You and I are in the same boat, to an extent, but you are definitely in the engine room while I'm just sauntering on the deck.

to be honest, i feel like swimming (sailing?) against the current lately, but that's a topic for another discussion...

Didier Spaier · 04-15-2019, 08:27 AM

I use -current in a VM to check new things that I could use in Slint. As I do this only once in while, I prefer to just reinstall every time, thanks to Eric's -current ISO.

chrisretusn · 04-16-2019, 08:29 AM

Quote:

Originally Posted by chrisretusn

Right now I am behind on updates, way behind in fact (last update applied: Fri Mar 22 20:41:23 UTC 2019). I am very busy and just have not had the time to do the update and deal with possible problems. Of course the longer I wait, the more there is a chance sometime may not go well. Then again, all may go well (my experience). Perhaps tomorrow will be the day I tackle this on my main box. Then proceed to my laptop as well.

Well tomorrow was yesterday. All caught up on my main box, all went well. Doing my laptop right now.

linustalman · 04-18-2019, 01:20 PM

As a Debian user, once a week is fine.

Lysander666 · 04-27-2019, 01:18 PM

Because of security fixes I updated a few packages, namely bind, dovecot, openssh, libpng and samba.

Now with the first three I wasn't sure whether to keep or overwrite the config files [there weren't any new configs for the last two]. Seeing as I thought the packages would have been updated with suitable configs in mind, I overwrote the configs [the old ones are kept anyway]. Is this the right thing to do?

The only time I have ever had a problem with overwriting configs has been when slackpkg+ is updated.

orbea · 04-27-2019, 04:04 PM

With configuration files I first view the diff and then I will either overwrite the file or merge it with my already installed file if I have made custom changes. For files I have never touched I almost always overwrite the file after reviewing the changes.

hitest · 04-27-2019, 04:23 PM

Updated -current today! New kernel.

Code:

bash-5.0$ uname -rpm
4.19.37 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

Lysander666 · 04-27-2019, 08:34 PM

Quote:

Originally Posted by orbea

With configuration files I first view the diff and then I will either overwrite the file or merge it with my already installed file if I have made custom changes. For files I have never touched I almost always overwrite the file after reviewing the changes.

Thank you very much indeed, orbea.

Quote:

Originally Posted by hitest

Updated -current today! New kernel.

Code:

bash-5.0$ uname -rpm
4.19.37 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

I'm sticking with 4.19.34 for performance and nostalgia!

Lysander666 · 04-29-2019, 07:54 AM

Quote:

Originally Posted by hitest

Updated -current today! New kernel.

Code:

bash-5.0$ uname -rpm
4.19.37 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

OK, so I updated so 4.19.37. I'm keeping .34 for the meantime as a backup. lilo.conf now looks like this:

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.19.37
initrd = /boot/initrd-4.19.37.gz
  root = /dev/nvme0n1p1
  label = 4.19.37-Generic
  read-only

image = /boot/vmlinuz-huge-4.19.37
  root = /dev/nvme0n1p1
  label = 4.19.37-Huge
  read-only

#4.19.34

image = /boot/vmlinuz-generic-4.19.34
initrd = /boot/initrd.gz
  root = /dev/nvme0n1p1
  label = 4.19.34-Generic
  read-only

image = /boot/vmlinuz-huge-4.19.34
  root = /dev/nvme0n1p1
  label = 4.19.34-Huge
  read-only
# Linux bootable partition config ends

Now I'm aware that I don't need two initrds, but I'm going to do things this way for the moment anyway.

hazel · 05-02-2019, 06:18 AM

Usually once a month for binary distros, but I update my laptop weekly because I've had key updating problems occasionally with AntiX when there was too big a gap.

When I was using Crux, I updated weekly because the builds took so much time with a big update. I don't usually update LFS at all unless there is a security scare; I just build a new one every six months.

hitest · 05-02-2019, 06:17 PM

Kernel updates are coming fast. Updated today.

Code:

Thu May  2 21:37:38 UTC 2019
a/kernel-firmware-20190502_92e17d0-noarch-1.txz:  Upgraded.
a/kernel-generic-4.19.38-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.19.38-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.19.38-x86_64-1.txz:  Upgraded.
d/ccache-3.7.1-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.19.38-x86-1.txz:  Upgraded.
d/mercurial-5.0-x86_64-1.txz:  Upgraded.
k/kernel-source-4.19.38-noarch-1.txz:  Upgraded.
l/glib-networking-2.60.2-x86_64-1.txz:  Upgraded.
l/imagemagick-6.9.10_43-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
+--------------------------+

http://slackware.osuosl.org/slackwar.../ChangeLog.txt

Richard Cranium · 05-02-2019, 06:56 PM

Quote:

Originally Posted by linustalman

As a Debian user, once a week is fine.

You update your Slackware -current version once a week in Debian? How does that work?

oddius_oddone · 05-05-2019, 04:25 PM

I typically update both my 14.2 and -current once a week on Friday. That way if something happens I have the weekend to figure it out. I've never had issues with either, but an ounce of prevention and such.