SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So this week wasn't as calm as the previous weeks have been, but despite that I suspect this is the last rc.
This week we had the whole "spectre v4" thing, and yes, the fallout from
that shows up as part of the patch and commit log. But it's not actually
dominant: the patch is pretty evenly one third arch updates, one third
networking updates, and one third "rest".
The arch updates are largely - although not exclusively - spectre v4.
The networking stuff is mostly network drivers, but there's some core
networking too.
And "the rest" is just that - misc drivers (rdma, gpu, other),
documentation, some vfs, vm, bpf, tooling..
The bulk of it is really pretty trivial one-liners, and nothing looks
particularly scary. Let's see how next week looks, but if nothing really
happens I suspect we can make do without an rc8.
Shortlog appended as usual. Go out and test.
Linus
---
Last edited by cwizardone; 05-27-2018 at 04:16 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,109
Original Poster
Rep:
A few days ago after installing the 4.16.12 kernel I started receiving messages from Netflix that, "New device signed into your account." That has never happened in all the years I've been using Netflix.
So, I went into the Netflix account and looked at the activity log. It appears that when using the 4.14.xx series Netflix only logs my IP address, but when using the 4.16.xx series it logs a 26 digit address that looks like it might be a MAC address, but I'm not sure. Each time I've installed a new version of the 4.16.xx series the last 16 digits of the 28 digit number (alpha/numeric) changes.
All seems a little spooky to me.
As they say, "Just because you are paranoid doesn't mean they are not out to get you."
Last edited by cwizardone; 05-30-2018 at 05:57 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,109
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
A few days ago after installing the 4.16.12 kernel I started receiving messages from Netflix that, "New device signed into your account." That has never happened in all the years I've been using Netflix.
So, I went into the Netflix account and looked at the activity log. It appears that when using the 4.14.xx series Netflix only logs my IP address, but when using the 4.16.xx series it logs a 26 digit address that looks like it might be a MAC address, but I'm not sure. Each time I've installed a new version of the 4.16.xx series the last 16 digits of the 28 digit number (alpha/numeric) changes.
All seems a little spooky to me.
As they say, "Just because you are paranoid doesn't mean they are not out to get you."
It is getting worst. Now it is happening with the 4.14.47 kernel. A few minutes after every sign-in I receive an e-mail warning me a new device has signed on to my account. I don't know if the problem is on Netflix side or if it has something to do with the recent kernel updates, but it does appear to be kernel related.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,109
Original Poster
Rep:
Well, it doesn't appear to be the kernel.
I dug around in my backup and found the 4.16.6 kernel, installed it and the problem remains. I delete an add-on in Firefox, Privacy Badger, but that didn't change anything.
At the moment I'm running 4.16.13 and the problem remains.
..............
So this last week was pretty calm, even if the pattern of most of the
stuff coming in on a Friday made it feel less so as the weekend
approached.
And while I would have liked even less changes, I really didn't get
the feeling that another week would help the release in any way, so
here we are, with 4.17 released.
No, I didn't call it 5.0, even though all the git object count
numerology was in place for that. It will happen in the not _too_
distant future, and I'm told all the release scripts on kernel.org are
ready for it, but I didn't feel there was any real reason for it. I
suspect that around 4.20 - which is I run out of fingers and toes to
keep track of minor releases, and thus start getting mightily confused
- I'll switch over. That was what happened for 4.0, after all.
As for the actual changes since rc7 - the shortlog is appended - it's
mostly drivers, networking, perf tooling, and a set of nds32 fixes.
With some random other stuff thrown in. Again, the shortlog is
obviously only the last calm week, the overall changes since 4.16 are
much too big to list in that format.
The big 4.17 stuff was mentioned in the rc1 email when the merge
window closed, but I guess it's worth repeating how 4.17 is actually a
slightly smaller kernel than 4.16, thanks to the removal of a number
of effectively dead architectures (blackfin, cris, frv, m32r, metag,
mn10300, score, and tile). Obviously all the other changes are much
more important, but it's always nice to see spring cleaning like that.
And with this, the merge window for 4.18 is obviously open. I actually
have some travel the second week of the merge window, which is very
inconvenient for me, but I do hope that we'll get all the big stuff
merged the first week and it won't impact any release scheduling. But
we'll have to see.
Linus
---
Last edited by cwizardone; 06-03-2018 at 06:22 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.