Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #225231 > unrolled thread
| Started by | Carl Fink <carl@finknetwork.com> |
|---|---|
| First post | 2020-07-25 04:20 +0200 |
| Last post | 2020-07-25 10:20 +0200 |
| Articles | 4 — 4 participants |
Back to article view | Back to linux.debian.user
node.js updates processor microcode? Carl Fink <carl@finknetwork.com> - 2020-07-25 04:20 +0200
Re: node.js updates processor microcode? mick crane <mick.crane@gmail.com> - 2020-07-25 05:40 +0200
Re: node.js updates processor microcode? Carl Fink <carlf@panix.com> - 2020-07-25 13:30 +0200
Re: node.js updates processor microcode? Sven Hartge <sven@svenhartge.de> - 2020-07-25 10:20 +0200
| From | Carl Fink <carl@finknetwork.com> |
|---|---|
| Date | 2020-07-25 04:20 +0200 |
| Subject | node.js updates processor microcode? |
| Message-ID | <AwhX3-6L5-1@gated-at.bofh.it> |
I just installed npm on a Stable (Buster) system with apt. It brought in dozens of other packages. Then I worked on other stuff while it downloaded and installed. When I came back, a curses prompt was informing me that it had already updated my kernel microcode. Is that something node.js is really supposed to do. That wasn't a confirmation prompt, it was, "I already did this, do you want to restart services?" -- Carl Fink carl@finknetwork.com https://reasonablyliterate.com https://nitpicking.com If you want to make a point, somebody will take the point and stab you with it. -Kenne Estes
[toc] | [next] | [standalone]
| From | mick crane <mick.crane@gmail.com> |
|---|---|
| Date | 2020-07-25 05:40 +0200 |
| Message-ID | <Awjct-7pK-3@gated-at.bofh.it> |
| In reply to | #225231 |
On 2020-07-25 03:17, Carl Fink wrote: > I just installed npm on a Stable (Buster) system with apt. It brought > in > dozens of other packages. Then I worked on other stuff while it > downloaded and > installed. When I came back, a curses prompt was informing me that it > had > already updated my kernel microcode. Is that something node.js is > really > supposed to do. That wasn't a confirmation prompt, it was, "I already > did > this, do you want to restart services?" I installed npm on Buster with apt a couple of days ago and did not get that message. mick -- Key ID 4BFEBB31
[toc] | [prev] | [next] | [standalone]
| From | Carl Fink <carlf@panix.com> |
|---|---|
| Date | 2020-07-25 13:30 +0200 |
| Message-ID | <Awqxj-3sU-1@gated-at.bofh.it> |
| In reply to | #225233 |
On 7/24/20 11:32 PM, mick crane wrote: > On 2020-07-25 03:17, Carl Fink wrote: >> I just installed npm on a Stable (Buster) system with apt. It brought in >> dozens of other packages. Then I worked on other stuff while it >> downloaded and >> installed. When I came back, a curses prompt was informing me that it >> had >> already updated my kernel microcode. Is that something node.js is really >> supposed to do. That wasn't a confirmation prompt, it was, "I already >> did >> this, do you want to restart services?" > > I installed npm on Buster with apt a couple of days ago and did not > get that message. > mick Maybe your microcode was current. -- Carl Fink nitpicking@nitpicking.com Read my blog at blog.nitpicking.com. Reviews! Observations!
[toc] | [prev] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2020-07-25 10:20 +0200 |
| Message-ID | <Awnzr-1JF-1@gated-at.bofh.it> |
| In reply to | #225231 |
Carl Fink <carl@finknetwork.com> wrote: > I just installed npm on a Stable (Buster) system with apt. It brought > in dozens of other packages. Then I worked on other stuff while it > downloaded and installed. When I came back, a curses prompt was > informing me that it had already updated my kernel microcode. Is that > something node.js is really supposed to do. That wasn't a confirmation > prompt, it was, "I already did this, do you want to restart services?" I guess, you have the package "needrestart" installed. This program warns you about services that need to be restarted after a library they use has been changed. It also warns if a new microcode-package was installed *sometime* in the past and the system hasn't rebooted yet. If you don't regulary install packages or use unattended-upgrades, the installation of the new microcode-package may have been days or weeks ago and you just didn't remember it, seeing the reminder from needrestart surprised you. Grüße, Sven. -- Sigmentation fault. Core dumped.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web