Re: Wondows 10 Craters' Pupdate
-
Two (forced) "feature updates" per year.
-
Wondows 10 'Curious Caribou', anyone?
-
@RaceProUK said in Re: Wondows 10 Craters' Pupdate:
Wondows 10 'Curious Caribou', anyone?
Don't give them any ideas
http://i.imgur.com/qB2tIbj.gifv
-
IMO this is great. What's with all the hate?
-
@LB_ said in Re: Wondows 10 Craters' Pupdate:
IMO this is great. What's with all the hate?
Supposedly, the vast majority are immeasurably against new things and changes.
-
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
the vast majority are immeasurably against new things and changes
so ... that's the reason for using the CLI?
Hey look that trolleybus just spontaneously burst into flames!
-
@Luhmann said in Re: Wondows 10 Craters' Pupdate:
Hey look that trolleybus just spontaneously burst into flames!
IKR? I mean, you can't even see it anymore that's how hard it blew up!
-
@Luhmann said in Re: Wondows 10 Craters' Pupdate:
so ... that's the reason for using the CLI?
No, it's just how we pass the time while waiting for more puppies to kick.
-
@LB_ said in Re: Wondows 10 Craters' Pupdate:
IMO this is great. What's with all the hate?
Because it means I need to reinstall GRUB twice a year
-
Protip: if you switch to Current Branch for Business and set the feature update delay to 365 days, you'll be able to use this version for another 16~18 months after the next one is out.
-
@LB_ said in Re: Wondows 10 Craters' Pupdate:
What's with all the hate?
New Coke Syndrome.
More bloat. More pointless new "features" that nobody gives a shit about, that you can't remove/disable without breaking something.
Changes that are forced on you, that add no value and just change things for the sake of making things different, and arguably make things worse.
Sorry, not interested.
-
@El_Heffe Also, it's an excuse to "accidentally" reset your privacy settings.
-
@Scarlet_Manuka actually the upgrade doesn't even download until you choose your privacy settings in the privacy popup.
-
@LB_ said in Re: Wondows 10 Craters' Pupdate:
@Scarlet_Manuka actually the upgrade doesn't even download until you choose your privacy settings in the privacy popup.
And you think the "privacy settings" actually mean something?
-
Windows 10 will create a pool of eight features, and the two features in your update will be randomly chosen. We'll call it Windows Roulette.
- Feature 1: Surprise reformatting from NTFS to FAT16
- Feature 2: Enhanced telemetry
- Feature 3: Windows will be only controllable using Cortana voice commands
- Feature 4: Explorer will be replaced with metro-based file navigation
- Feature 5: Update source/schedule is changed to the Windows Insider / Beta track
- Feature 6: Competitor software will be ransomed and replaced with equivalent Windows apps
- Feature 7: Surprise deleting of other paritions
- Feature 8: Unicorn UI colors (nonswitchable)
-
@El_Heffe said in Re: Wondows 10 Craters' Pupdate:
@LB_ said in Re: Wondows 10 Craters' Pupdate:
@Scarlet_Manuka actually the upgrade doesn't even download until you choose your privacy settings in the privacy popup.
And you think the "privacy settings" actually mean something?
They provide interesting telemetry.
-
@Sumireko said in Re: Wondows 10 Craters' Pupdate:
Feature 7: Surprise deleting of other paritions
Windows 10 @fbmac's Update?
I found another strange bug after upgrading my mother's computer. Apparently, the update breaks DHCP on her system. The DNS server was set correctly, but neither was the gateway detected not was the interface successfully assigned an IP address. In the end, the interface got assigned a link-local IP address and my mother was wondering why she could only access the WiFi router and nothing else.
How the fuck can that even happen?
-
@Luhmann said in Re: Wondows 10 Craters' Pupdate:
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
the vast majority are immeasurably against new things and changes
so ... that's the reason for using the CLI?
Yes.
Hey look that trolleybus just spontaneously burst into flames!
If you think you're trolling you don't understand the appeal of a stable CLI.
-
@asdf said in Re: Wondows 10 Craters' Pupdate:
I found another strange bug after upgrading my mother's computer. Apparently, the update breaks DHCP on her system. The DNS server was set correctly, but neither was the gateway detected not was the interface successfully assigned an IP address. In the end, the interface got assigned a link-local IP address and my mother was wondering why she could only access the WiFi router and nothing else.
How the fuck can that even happen?
I've occasionally seen that happen even without the Craters' Pupdate. I've never been able to figure out why.
-
@RaceProUK said in Re: Wondows 10 Craters' Pupdate:
I've occasionally seen that happen even without the Craters' Pupdate.
Thanks for confirming, for a moment I thought I had lost my mind. ???
I've never been able to figure out why.
The only reasonable explanation I have is that some of the DHCP packages got lost, but not the NetBIOS (or whatever) packages. What doesn't make sense at all is that the behavior was reproducible.
-
@gleemonk said in Re: Wondows 10 Craters' Pupdate:
If you think you're trolling
I don't think that. I know it. And the fact you seem agitated over that jab seems to indicate that it was a nice one.
-
@RaceProUK said in Re: Wondows 10 Craters' Pupdate:
@asdf said in Re: Wondows 10 Craters' Pupdate:
I found another strange bug after upgrading my mother's computer. Apparently, the update breaks DHCP on her system. The DNS server was set correctly, but neither was the gateway detected not was the interface successfully assigned an IP address. In the end, the interface got assigned a link-local IP address and my mother was wondering why she could only access the WiFi router and nothing else.
How the fuck can that even happen?
I've occasionally seen that happen even without the Craters' Pupdate. I've never been able to figure out why.
See, that's why Linux can never be used by non-technical people: it can't even do the basic stuff reliably, like getting DHCP to work properly.
-
@Luhmann said in [Re: Wondows 10 Craters' Pupdate](/post
I don't think that. I know it. And the fact you seem agitated over that jab seems to indicate that it was a nice one.
It's easy to mock the CLI because you can mock the same flaws for thirty years. If you want to mock graphic environments you have to stay current with the constantly introduced new flaws. It's a huge effort and I applaud the people who try to keep up.
-
@Sumireko said in Re: Wondows 10 Craters' Pupdate:
Windows will be only controllable using Cortana voice commands
Did that. Was only slowed down approx 14x.
@Sumireko said in Re: Wondows 10 Craters' Pupdate:
Competitor software will be ransomed and replaced with equivalent Windows apps
What do you mean "Competitor software"?!? They're doing it for their OWN STUFF! (Looking at you, Internet Explorer!)
@Sumireko said in Re: Wondows 10 Craters' Pupdate:
Unicorn UI colors (nonswitchable)
I forgot I enabled the "Night light" (Totally deceptive name, doesn't behave like my night light at all, except maybe that it's activated by "night").
Was totally surprised when my screen spent about 4 seconds to bleed to complete red (I think with f.lux at least you can have it transition over a much larger time).
-
@RaceProUK said in Re: Wondows 10 Craters' Pupdate:
@asdf said in Re: Wondows 10 Craters' Pupdate:
I found another strange bug after upgrading my mother's computer. Apparently, the update breaks DHCP on her system. The DNS server was set correctly, but neither was the gateway detected not was the interface successfully assigned an IP address. In the end, the interface got assigned a link-local IP address and my mother was wondering why she could only access the WiFi router and nothing else.
How the fuck can that even happen?
I've occasionally seen that happen even without the Craters' Pupdate. I've never been able to figure out why.
This just happened last week. Someone went and power cycled the main router while I was busy reconfiguring it and soft-bricked it, so I had to factory reset it. Luckily not so many alterations need to be done, except I missed one: The default DHCP pool is set to be 50 wide. Naturally in an office containing 35 computers that's not too big a deal, until people connected to the wifi with their phones and junk.
It just so happened that the end of the day saw exactly 50 DHCP-needing devices connected (successfully, of course).
Come the next day, the President (and two others that weren't in the office yesterday) can't get their devices connected. Nearly lost my mind trying to figure out why they weren't connecting, had flashbacks to the mystery Dec 2016 update from Microsoft that broke DHCP.
Turns out, "Couldn't get an IP address from the DHCP server" should have subtext, "No DHCP server gave us an IP when we asked. And we did ask."
-
@Sumireko said in Re: Wondows 10 Craters' Pupdate:
- Feature 7: Surprise deleting of other paritions
That's already in. "Surprise" being the operative word, seems to happen only sometimes. When it feels like it. On a Wednesday. But it does happen.
Signed: Lucky winner
-
@Onyx said in Re: Wondows 10 Craters' Pupdate:
On a Wednesday
The 15th Wednesday after Pentecost?
-
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
Turns out, "Couldn't get an IP address from the DHCP server" should have subtext, "No DHCP server gave us an IP when we asked. And we did ask."
My natural assumption would be that, as opposed to "We didn't even try getting a DHCP address, and we'll tell you about it"
-
@Onyx said in Re: Wondows 10 Craters' Pupdate:
@Sumireko said in Re: Wondows 10 Craters' Pupdate:
- Feature 7: Surprise deleting of other paritions
That's already in. "Surprise" being the operative word, seems to happen only sometimes. When it feels like it. On a Wednesday. But it does happen.
Signed: Lucky winner
It's a feature to teach you about proper backup discipline.
-
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
Turns out, "Couldn't get an IP address from the DHCP server" should have subtext, "No DHCP server gave us an IP when we asked. And we did ask."
On every error message, there should be a "debug this" button that showed you the stack of function calls and responses that led to it.
(I know I know, the quixotic ideas thread is )
-
@hungrier said in Re: Wondows 10 Craters' Pupdate:
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
Turns out, "Couldn't get an IP address from the DHCP server" should have subtext, "No DHCP server gave us an IP when we asked. And we did ask."
My natural assumption would be that, as opposed to "We didn't even try getting a DHCP address, and we'll tell you about it"
Unless the network status dialog said "sent: 12 bytes. Received: 20 Mb"...
-
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
Unless the network status dialog said "sent: 12 bytes. Received: 20 Mb"...
Well, yes. An IP packet is a minimum of 20 bytes, so a DHCPREQUEST can't possibly have gone out.
That makes me wonder whether that count does include the IP header, it almost certainly doesn't include the Ethernet frame, what happens with raw sockets vs. stream/datagram sockets... hmmm. #showerthoughts
-
@heterodox said in Re: Wondows 10 Craters' Pupdate:
Well, yes. An IP packet is a minimum of 20 bytes, so a DHCPREQUEST can't possibly have gone out.
well, actually it could have. see the network status dialog doesn't report traffic overhead. if you sent an IP datagram with a single byte payload (a total of 21 bytes once you add the 20 byte IP header, and more if you add the overhead of the Ethernet layer) that dialog would happily report the single byte of upload, because that's what it's supposed to report. :-P
-
@accalia said in Re: Wondows 10 Craters' Pupdate:
well, actually it could have. see the network status dialog doesn't report traffic overhead. if you sent an IP datagram with a single byte payload (a total of 21 bytes once you add the 20 byte IP header, and more if you add the overhead of the Ethernet layer) that dialog would happily report the single byte of upload, because that's what it's supposed to report. :-P
Do you know that to be the case? I don't know that to be the case, that's why I was musing about it. I suspect that to be the case; it'd be good to know either way.
And fine, it could not have because the minimum size for a DHCP message appears to be 236 bytes. So there; don't try to out- me. :P
-
@heterodox said in Re: Wondows 10 Craters' Pupdate:
@accalia said in Re: Wondows 10 Craters' Pupdate:
well, actually it could have. see the network status dialog doesn't report traffic overhead. if you sent an IP datagram with a single byte payload (a total of 21 bytes once you add the 20 byte IP header, and more if you add the overhead of the Ethernet layer) that dialog would happily report the single byte of upload, because that's what it's supposed to report. :-P
Do you know that to be the case? I don't know that to be the case, that's why I was musing about it. I suspect that to be the case; it'd be good to know either way.
And fine, it could not have because the minimum size for a DHCP message appears to be 236 bytes. So there; don't try to out- me. :P
Unless... Windows is hiding network traffic from the user! Gasp! Shock! 😱 horror!
-
@Tsaukpaetra said in Re: Wondows 10 Craters' Pupdate:
Unless... Windows is hiding network traffic from the user! Gasp! Shock! 😱 horror!
OMG ROOTKIT
-
@heterodox said in Re: Wondows 10 Craters' Pupdate:
Do you know that to be the case?
yep, yep.
@heterodox said in Re: Wondows 10 Craters' Pupdate:
So there;