The absolute worst-case would be to use the elevated access to leverage the superbrick bug (another hole out in the wild on the majority of exynos based phones) and permanently damage the emmc chip, which requires a system-board replacement to revive the phone.
And how exactly do you plan on portscanning a/64, something as large as the the IPv4 internet would be if every IP address had another internet NATted behind it? The sparse nature of v6 addressing renders dumb scanning moot.
And every home router I've had for the last 8 years has been v6-capable. (Yamaha RT54i, Yamaha RTX1000, NEC BL172HV)
Actually there IS an analog to jailbreak in android. Some carriers disable the "Unknown Sources" checkbox in Settings -> Applications. The act of re-enabling this is almost exactly the same thing as an iphone jailbreak.
Tell this to the japanese ISPs, most of whom are planning on deploying bind9.7's AAAA-filter (which only returns AAAA records if the recursive dns server gets the query via a v6 connection) for v6-day, which will mitigate most of the interesting breakage scenarios and edge-cases in the name of avoiding customer complaints.
Disclaimer: I work for a VoIP carrier, I was the the process of an eat-our-own-dogfood trial.
On friday the voice/text network was pretty much unusable, but the 3G data network was pretty much business as usual. Between Skype for sending out international SMS on my iphone (Skype, please get going and add this to the android client) and a SIP VoIP client on my android phone I had no problem notifying all my loved ones that I was safe.
I don't know whether I should feel good that VoIP worked so well or that the conventional telephony systems fared so poorly.
Spamhaus doesn't do a whole ISP-level block unless something pretty egregious is happening.
The usual process goes: 1. Complaint to ISP, no response 2./32 block, more spam, complaint to ISP, no response 3. escalation to block somewhere between/25 and/29 depending on identification of block size, more spam, complaint to ISP, no response 4. escalation to/24, more spam, complaint to ISP, no response 5. escalation to ISP's corporate mail servers - usually something happens at this point when suits notice their own mail getting blocked 6. escalation to ISPs entire allocation
Anything's going to be better than pcie-mini, given the damage that was done to it by Dell and ASUS using the form factor and connector but systematically violating the pinouts.
The recommendations have been that end-users get a/64 (a single subnet with 64 bits worth of addresses to work with)
Originally when more subnets were required the recommendations were to allocate a/48 per business customer (65,535/64 subnets) but that has been since relaxed to/56 (256 subnets) for small businesses.
I had to write some CPU/Mem stats code to monitor our program in realtime. On Linux It's simple a nightmere. The standard POSIX calls always returns 0. So I need to dig into top code and stated to decode the/proc files.
Could have probably ended the post there./proc on linux is and always has been a total cesspool.
Having lived in Japan going on 13 years now, its not that.
The japanese mindset is irrationally afraid of change and after years of crappy UIs they're conditioned to want something similar to the last phone they had.
This is incorrect, you cannot subscribe to a Softbank iPhone plan without the "Packet Full" data option, which is price-capped at about 4400 yen. (Its a sliding scale with both floor/ceiling caps - you have to pay at least 1000 yen and can't get charged over 4400). In practice, every iPhone user pays the 4400 yen price unless all they do is use email.
When a reasonable percentage of the content is actually used this may be true. However USENET works on a flood-fill mechanism, and (in theory) every site has every article sent to it at least once (and sometimes multiple times and duplicates are tossed depending on the feed type).
When under 0.1% of the content is actually then getting touched by an end-user that bandwidth-savings rapidly turns into a bandwidth money-pit.
Only the Giganewses/largest carriers/etc. have a big enough economy of scale that it might being to make sense.
The iphone's GPS is pretty inaccurate in my experience. If they wanted to keep it keitai-based they could just have felica readers at the doors and swipe them as you go in, since other than the iphone its basically been impossible to get a phone without felica for a few years now.
Re:Includes ZFS and DTrace production ready !
on
FreeBSD 7.2 Released
·
· Score: 4, Informative
The ZFS in 7.2 is v6, and pretty much can't be brought up to date without breaking 7.x ABI.
ZFS v13 is in 8-CURRENT and pretty much is as production-ready as what's in opensolaris.
Don't expect miracles on a 32-bit platform. The opensolaris people don't recommend it on their 32-bit codebase either.
True, however having at least a v6/32 (minimum allocation from an RIR) to work with means you have plenty of space to aggregate properly so a typical device will see a lot less of them.
What a coincidence that they make an enormous overreaction which frees up countless gigabits of bandwidth! Perhaps not. Isn't the whole point of carrying newsgroups for a provider to have a local copy (local to the ISP, that is)? Bandwidth from that local copy to users is cheap for an ISP. It is cheaper ONLY if the amount of data served to end-users exceeds the amount of data in the feed.
In our case that ratio simply wasn't there and it was a simple decision to axe it. Of our ~100,000 end-users there were less than 100 using usenet, and to my knowledge zero cancels when it went.
The question is if the weakness in security lies with Comcast (i.e. a weak password for the panel) or Network Solutions (i.e. weakness in their portal, weak transmission of passwords, etc). Total negligence.
Their parent company specializes in PKI and they don't eat their own dogfood and deploy client certificates to their own customers?
DIX-IE and JPIX (and NSPIXP3 if Osaka is your thing) are the must-be-present-at IXes in Japan. I'd very nearly but not quite prioritize even MEX over JPNAP.
Slashdot Mirror
The absolute worst-case would be to use the elevated access to leverage the superbrick bug (another hole out in the wild on the majority of exynos based phones) and permanently damage the emmc chip, which requires a system-board replacement to revive the phone.
If PC-BSD is so good, why do I always see FreeBSD committers at technical conferences carrying Macbooks more than any other notebook?
And how exactly do you plan on portscanning a /64, something as large as the the IPv4 internet would be if every IP address had another internet NATted behind it? The sparse nature of v6 addressing renders dumb scanning moot.
And every home router I've had for the last 8 years has been v6-capable. (Yamaha RT54i, Yamaha RTX1000, NEC BL172HV)
Actually there IS an analog to jailbreak in android. Some carriers disable the "Unknown Sources" checkbox in Settings -> Applications. The act of re-enabling this is almost exactly the same thing as an iphone jailbreak.
Tell this to the japanese ISPs, most of whom are planning on deploying bind9.7's AAAA-filter (which only returns AAAA records if the recursive dns server gets the query via a v6 connection) for v6-day, which will mitigate most of the interesting breakage scenarios and edge-cases in the name of avoiding customer complaints.
Disclaimer: I work for a VoIP carrier, I was the the process of an eat-our-own-dogfood trial.
On friday the voice/text network was pretty much unusable, but the 3G data network was pretty much business as usual. Between Skype for sending out international SMS on my iphone (Skype, please get going and add this to the android client) and a SIP VoIP client on my android phone I had no problem notifying all my loved ones that I was safe.
I don't know whether I should feel good that VoIP worked so well or that the conventional telephony systems fared so poorly.
Spamhaus doesn't do a whole ISP-level block unless something pretty egregious is happening.
The usual process goes: /32 block, more spam, complaint to ISP, no response /25 and /29 depending on identification of block size, more spam, complaint to ISP, no response /24, more spam, complaint to ISP, no response
1. Complaint to ISP, no response
2.
3. escalation to block somewhere between
4. escalation to
5. escalation to ISP's corporate mail servers - usually something happens at this point when suits notice their own mail getting blocked
6. escalation to ISPs entire allocation
Anything's going to be better than pcie-mini, given the damage that was done to it by Dell and ASUS using the form factor and connector but systematically violating the pinouts.
Even so, the only Cisco certs that really mean anything are the CCIE level ones due to the practical section.
The recommendations have been that end-users get a /64 (a single subnet with 64 bits worth of addresses to work with)
Originally when more subnets were required the recommendations were to allocate a /48 per business customer (65,535 /64 subnets) but that has been since relaxed to /56 (256 subnets) for small businesses.
ipv6 already has an addressing scheme for private networks, Unique Local Addresses.
There's no justification for using that as support for need for nat.
What a disappointment, I saw the title and was thinking DNSSEC key-rollover screwup. THAT would have made for a righteous thread.
I had to write some CPU/Mem stats code to monitor our program in realtime. On Linux It's simple a nightmere. The standard POSIX calls always returns 0. So I need to dig into top code and stated to decode the /proc files.
Could have probably ended the post there. /proc on linux is and always has been a total cesspool.
Having lived in Japan going on 13 years now, its not that.
The japanese mindset is irrationally afraid of change and after years of crappy UIs they're conditioned to want something similar to the last phone they had.
This is incorrect, you cannot subscribe to a Softbank iPhone plan without the "Packet Full" data option, which is price-capped at about 4400 yen. (Its a sliding scale with both floor/ceiling caps - you have to pay at least 1000 yen and can't get charged over 4400). In practice, every iPhone user pays the 4400 yen price unless all they do is use email.
(Note, tethering is not included in Packet Full)
When a reasonable percentage of the content is actually used this may be true. However USENET works on a flood-fill mechanism, and (in theory) every site has every article sent to it at least once (and sometimes multiple times and duplicates are tossed depending on the feed type).
When under 0.1% of the content is actually then getting touched by an end-user that bandwidth-savings rapidly turns into a bandwidth money-pit.
Only the Giganewses/largest carriers/etc. have a big enough economy of scale that it might being to make sense.
The iphone's GPS is pretty inaccurate in my experience. If they wanted to keep it keitai-based they could just have felica readers at the doors and swipe them as you go in, since other than the iphone its basically been impossible to get a phone without felica for a few years now.
The ZFS in 7.2 is v6, and pretty much can't be brought up to date without breaking 7.x ABI.
ZFS v13 is in 8-CURRENT and pretty much is as production-ready as what's in opensolaris.
Don't expect miracles on a 32-bit platform. The opensolaris people don't recommend it on their 32-bit codebase either.
Yamaha's consumer broadband router line has supported v6 for at least 5 years.
True, however having at least a v6 /32 (minimum allocation from an RIR) to work with means you have plenty of space to aggregate properly so a typical device will see a lot less of them.
But once you start talking SAN, then you start to have very few choices but to pay the outrageous prices.
Or whitebox-thumper the SAN with Solaris, ZFS volumes, iSCSI target and multiple gbe interfaces using LACP/PAGP.
In our case that ratio simply wasn't there and it was a simple decision to axe it. Of our ~100,000 end-users there were less than 100 using usenet, and to my knowledge zero cancels when it went.
Their parent company specializes in PKI and they don't eat their own dogfood and deploy client certificates to their own customers?
Someone needs to float a new rfc updating 1032. Its over 20 years old and dreadfully outdated.
DIX-IE and JPIX (and NSPIXP3 if Osaka is your thing) are the must-be-present-at IXes in Japan. I'd very nearly but not quite prioritize even MEX over JPNAP.