Am I the only one dealing with issue with the kernel fix for spectre and meltdown ?
All my VM excepted my BBS that for legacy reason is a 32bit Ubuntu are affected, had to boot them with a previous kernel.
Am I the only one dealing with issue with the kernel fix for spectre and meltdown ?
All my VM excepted my BBS that for legacy reason is a 32bit Ubuntu are affected, had to boot them with a previous kernel.
I probably *should* be doing that, but I haven't. I'm just living on the edge and hoping nothing happens. I assume a fix will be coming down the pipeline
too for my distro (debian) soon
You should let your sysop know there's no QWK tagline on your messages.:-)
Hello,
On Wed, 24 Jan 2018 20:41:42 -0800, Digital Man -> Naga wrote:
You should let your sysop know there's no QWK tagline on your messages.:-)
That's odd. Seeing as though I'm looking at SCFG -> Networks -> QWK Packet Networks -> Default Tagline right now, and it's definitely there.
Just as well, SCFG -> Message Areas -> Dovenet -> Message Sub-boards -> <insert
any Dovenet sub-board here> -> Network Options -> QWK Tagline is also filled in
what what has always been there.
Append Tag/Origin line is also set to "Yes."
I haven't changed any settings here in regards to QWK networking, so was something changed in sbbsecho that may have broke the QWK tagline when gating between net types?
I probably *should* be doing that, but I haven't. I'm just living on the edge and hoping nothing happens. I assume a fix will be coming down the pipeline too for my distro (debian) soon
I'm just a compulsive updated, first thing i do in the morning is :
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get autoremove
sudo apt-get autoclean
and a sudo shutdown -r now
if required.
Is there a cure ?
Sure, script it and throw it in a cron. You only really need to reboot if the kernel is updated, or glibc. (and there are ways around having to
reboot if you update glibc).
I probably *should* be doing that, but I haven't. I'm just living on the edge and hoping nothing happens. I assume a fix will be coming down the pipeline too for my distro (debian) soon
I'm just a compulsive updated, first thing i do in the morning is :
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get autoremove
sudo apt-get autoclean
and a sudo shutdown -r now
if required.
i'm scared i would have to reinstall.
Are you the sysop of "ABINARY"? That's the system I was referring to.
Sure, script it and throw it in a cron. You only really need to
reboot if the kernel is updated, or glibc. (and there are ways around
having to reboot if you update glibc).
Still what to do it myself, hate to makeup to a machine locked in a loop because the update did something messy.
But less important machine I agree it's automatic.
apt and yum probably won't cause anything horrific to happen, unless you're running bleeding-edge custom repositories.
Odd, I'll check my system to see why the tag line is not there. I am the sysop of ABINARY.
Sysop: | CyberNix |
---|---|
Location: | London, UK |
Users: | 18 |
Nodes: | 10 (0 / 10) |
Uptime: | 138:06:34 |
Calls: | 819 |
Files: | 3,552 |
Messages: | 558,406 |