My reference was the update page in settings said the download was 1.1 gig
Grant
Sent from my iPhone
> On Sep 17, 2014, at 7:04 PM, JoeSox wrote:
>
> Grant,
> Do you have a reference? Someone just told me it is more around 5GB.
>
> --
> Later, Joe
>
> On Wed, Sep 17, 2014 at 10:31 AM, Grant
Slight differences depending on platform. For my 5S, the OTA patch is 1.1GB,
and the clean install is 2.05GB. Both compressed, of course.
-Bill
> On Sep 17, 2014, at 19:15, "Alexander Neilson"
> wrote:
>
> According to devices I have seen numbers have been between 800M
Someone just told me its 5GB free space needed. That makes sense where
someone could have read it wrong. Thanks.
5GB for for iphone seemed a bit odd.
--
Later, Joe
On Wed, Sep 17, 2014 at 7:04 PM, JoeSox wrote:
> Grant,
> Do you have a reference? Someone just told me it is more around 5GB.
>
> -
According to devices I have seen numbers have been between 800MB and 1.3GB
iPhone 4S, iPhone 5, iPad 2 (3G), iPad Air (LTE)
Regards
Alexander
Alexander Neilson
Neilson Productions Limited
alexan...@neilson.net.nz
021 329 681
022 456 2326
On 18/09/2014, at 2:04 pm, JoeSox wrote:
> Grant,
> Do
+--
| On 2014-09-17 19:04:13, JoeSox wrote:
|
| Do you have a reference? Someone just told me it is more around 5GB.
The download is 1.1GB. 5.6GB is required for the actual upgrade.
--
bdha
Later,
I think it requires 5.7G of free space on the device -- but the download
is not that big.
On 9/18/2014 午前 11:04, JoeSox wrote:
Grant,
Do you have a reference? Someone just told me it is more around 5GB.
--
Later, Joe
On Wed, Sep 17, 2014 at 10:31 AM, Grant Ridder
wrote:
For those
Grant,
Do you have a reference? Someone just told me it is more around 5GB.
--
Later, Joe
On Wed, Sep 17, 2014 at 10:31 AM, Grant Ridder
wrote:
> For those that are curious, it looks like the download is 1.1 gigs.
>
> -Grant
>
> On Wed, Sep 17, 2014 at 10:04 AM, Nick Olsen wrote:
>
> > I've be
On Sep 17, 2014, at 6:01 PM, Jimmy Hess wrote:
> On Wed, Sep 17, 2014 at 11:09 AM, Jay Ashworth wrote:
>
>> The latter would seem to be avoidable by making sure that *DNS resolution
>> of bare TLDs always returns NXDOMAIN*.
> [snip]
>
> Not NXDOMAIN.When TLD. is looked up, they should
On Wed, Sep 17, 2014 at 11:09 AM, Jay Ashworth wrote:
> The latter would seem to be avoidable by making sure that *DNS resolution
> of bare TLDs always returns NXDOMAIN*.
[snip]
Not NXDOMAIN.When TLD. is looked up, they should always return NOERROR.
And yield, either (1) the NS recor
On Wed, Sep 17, 2014 at 10:02:45AM +0200, Tei wrote:
> http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Decoding_table
>
> GO [...] seems to be free :D
1600 Amphitheatre Parkway... the newest independent state.
- Matt
On Thu, Sep 18, 2014 at 07:39:08AM +1000, Mark Andrews wrote:
> You want gethostbyname, getaddrinfo to return HOST_NOT_FOUND/EAI_NONAME
I was unaware that getaddrinfo returned "NXDOMAIN", which is what I
read in the thread being talked about. Not return values from the OS
calls. I guess I misse
Doug Barton wrote:
> In the case
> you specify you get the combination of NOANSWER + NOERROR
> if there is no address record, but there are other records
> (like there are at a zone apex).
valdis.kletni...@vt.edu wrote:
> NXDOMAIN means "There are no records of *any* type at that node".
Not.
T
Fred,
On Sep 17, 2014, at 3:04 PM, Fred Baker (fred) wrote:
> IMHO, since ICANN has created the situation,
ICANN has created ill-specified domain search path heuristics and truly
fascinating implementations of those heuristics? ICANN has caused people to
use non-allocated TLDs in environment
In message <21906507.2046.1410990673107.javamail.r...@benjamin.baylink.com>, Ja
y Ashworth writes:
> - Original Message -
> > From: "Mark Andrews"
>
> > Search lists are for hosts and host like things. Resolver libraries
> > have different interfaces for different purposes. Single label
IMHO, since ICANN has created the situation, the ball is in ICANN’s court to
say how this works without disrupting name services. Their ill-informed hipshot
is not our emergency.
On Sep 17, 2014, at 9:09 AM, Jay Ashworth wrote:
> Pursuant to
>
> https://www.icann.org/resources/pages/name-col
- Original Message -
> From: "Doug Barton"
> > I want to return NXDOMAIN *because there is no record of that type
> > at that node*.
> >
> > That was the underlying point here; I thought that was pretty clear.
>
> But that's not what NXDOMAIN means. :) You get an NXDOMAIN response
> when
Original Message -
> From: "Nick Crocker"
> Can someone shed some light on how you might be accomplishing this, I have
> a hard time believing that customers are being told they cannot dial TF
> numbers in their own country.
In the US, it's always been my understanding that what we call
On Wed, 17 Sep 2014 17:48:58 -0400, Jay Ashworth said:
> I want to return NXDOMAIN *because there is no record of that type at that
> node*.
NXDOMAIN means "There are no records of *any* type at that node".
NOERROR means "There are no records of *that* type at that node (but the
node exists and
On 9/17/14 2:48 PM, Jay Ashworth wrote:
- Original Message -
From: "Andrew Sullivan"
On Wed, Sep 17, 2014 at 04:57:52PM -0400, Jay Ashworth wrote:
- Original Message -
No, I was confusing you for someone who understood -- as everyone else
here seems to have -- that I meant "
- Original Message -
> From: "Mark Andrews"
> Search lists are for hosts and host like things. Resolver libraries
> have different interfaces for different purposes. Single label
> hostnames for reaching non local equipment was deliberately phase
> out in the 1980's as it was clearly a ba
- Original Message -
> From: "Andrew Sullivan"
> On Wed, Sep 17, 2014 at 04:57:52PM -0400, Jay Ashworth wrote:
> > - Original Message -
> > No, I was confusing you for someone who understood -- as everyone else
> > here seems to have -- that I meant "querying for an A, , or MX
In message <20140917211336.gt89...@dyn.com>, Andrew Sullivan writes:
> On Wed, Sep 17, 2014 at 04:57:52PM -0400, Jay Ashworth wrote:
> > - Original Message -
> > No, I was confusing you for someone who understood -- as everyone else
> > here seems to have -- that I meant "querying for an A
On Wed, Sep 17, 2014 at 04:57:52PM -0400, Jay Ashworth wrote:
> - Original Message -
> No, I was confusing you for someone who understood -- as everyone else
> here seems to have -- that I meant "querying for an A, , or MX
> record".
You want to return NXDOMAIN for a name only when th
- Original Message -
> From: "John Levine"
> >The latter would seem to be avoidable by making sure that *DNS resolution
> >of bare TLDs always returns NXDOMAIN*.
> >
> >Is that a requirement for a TLD?
>
> No. In fact, a TLD lookup that returned NXDOMAIN would be utterly
> broken since t
>The latter would seem to be avoidable by making sure that *DNS resolution
>of bare TLDs always returns NXDOMAIN*.
>
>Is that a requirement for a TLD?
No. In fact, a TLD lookup that returned NXDOMAIN would be utterly
broken since that would mean the TLD had no SOA, no NS, and no
subdomains. Perha
On Sep 17, 2014, at 11:08 AM, Eric Brunner-Williams wrote:
> On 9/17/14 10:45 AM, David Conrad wrote:
>> To be clear, generic TLDs (gTLDs) can’t have bare (dotless) TLDs (or
>> wildcards).
> um. .museum. …
.MUSEUM gave up their wildcard some time ago.
Regards,
-drc
signature.asc
Description
On 9/17/14 10:45 AM, David Conrad wrote:
To be clear, generic TLDs (gTLDs) can’t have bare (dotless) TLDs (or wildcards).
um. .museum. ...
- Original Message -
> From: "David Conrad"
> > A records being returned for bare TLDs *is* formally banned?
> >
> > (Oh: specifically for cctlds. Got it.)
>
> To be clear, generic TLDs (gTLDs) can’t have bare (dotless) TLDs (or
> wildcards). ICANN has no mechanism by which policy can be
Jay,
On Sep 17, 2014, at 10:36 AM, Jay Ashworth wrote:
> We're talking, largely, about error cases *that used to break as you wanted,
> and now might not*.
Yep. Well, it used to break if you happened to be using the right version of
resolver library. There have been cases where operating syst
On 9/17/14 10:36 AM, Jay Ashworth wrote:
A records being returned for bare TLDs*is* formally banned?
(Oh: specifically for cctlds. Got it.)
No, ICANN doesn't ban anything for the ccTLDs.
Citation?
The gTLD registry contracts describe the fact that they cannot add A
records at the zone
At first we saw traffic going directly to Apple (swcdn.apple.com) via our
commercial link, then it went to llnw.net, and now it is going to Akamai.
access1-srp#traceroute swcdn.apple.com
Translating "swcdn.apple.com"...domain server (132.206.44.21) [OK]
Type escape sequence to abort.
Tracing the
Original Message -
> From: "David Conrad"
> A common case of name collision is driven by the “DNS search path”,
> e.g., if you have a “search path” of “bar.com;foo.bar.com” and you
> type “telnet baz”, _some_ resolver libraries will try to resolve
> “baz.bar.com”, if that fails then “baz
For those that are curious, it looks like the download is 1.1 gigs.
-Grant
On Wed, Sep 17, 2014 at 10:04 AM, Nick Olsen wrote:
> I've been waiting all morning.
>
> Expedited repair of a primary link to prepare for the traffic. Not that it
> didn't have multiple backups. But one doesn't trifle
On 9/17/14 9:10 AM, Jay Ashworth wrote:
- Original Message -
From: "David Conrad"
Right. Similarly, .SU has been assigned. SU is a bit odd in the sense
that it was moved to “transitionally reserved” when the Soviet Union
broke up and a batch of new country codes were created (e.g., RU,
I've been waiting all morning.
Expedited repair of a primary link to prepare for the traffic. Not that it
didn't have multiple backups. But one doesn't trifle with IOS8 release
traffic.. If it's anything like IOS7 was..
Nick Olsen
Network Operations (855) FLSPEED x106
---
So Apple is about to release iOS 8... Have you done anything special to
your network setup to accommodate the traffic flood ie traffic shaping
rules, cache servers, etc?
I heard that Apple Caching servers won't work with this update, so I'm
guessing it will be pushed through Akamai servers as is u
On Sep 17, 2014, at 9:10 AM, Jay Ashworth wrote:
>> The .SU ccTLD is also a bit odd in that
>> it is the only code that does not (officially) have a nation-state
>> (and hence a legal framework) behind it. In practice, I believe it
>> falls under the Russian legal framework.
>
> The European Unio
Jay,
On Sep 17, 2014, at 9:09 AM, Jay Ashworth wrote:
> it seems there are two major potential points of possible collision:
>
> 1) User network uses "fake" TLD which is no longer fake, and local
> resolver server blows it
>
> 2) User network blows it worse, and tries to resolve a monocomponen
- Original Message -
> From: "David Conrad"
> Right. Similarly, .SU has been assigned. SU is a bit odd in the sense
> that it was moved to “transitionally reserved” when the Soviet Union
> broke up and a batch of new country codes were created (e.g., RU, UA,
> etc.) and then, in 2007 (or
Pursuant to
https://www.icann.org/resources/pages/name-collision-2013-12-06-en)
mentioned in the Scotland thread... it seems there are two major potential
points of possible collision:
1) User network uses "fake" TLD which is no longer fake, and local
resolver server blows it
2) User network
- Original Message -
> From: "manning bill"
> Perhaps a dose of factual information may temper this thread.
> If we are talking about ISO-3166-2 - the basis for the CCTLD
> delegations, then:
>
> 1_ Scotland has no say in the country code selected.
Am I missing something, or is the Finn
On 9/17/14 8:03 AM, manning bill wrote:
> Perhaps a dose of factual information may temper this thread.
> If we are talking about ISO-3166-2 - the basis for the CCTLD delegations,
> then:
>
> 1_ Scotland has no say in the country code selected.
This is not actually true. We have prior art on co
well, apropos to point #2, the iso3166/ma includes representatives from
ten agencies, of which a certain 501(c)(3) originally in marina del rey,
now in los angeles, is included.
however, i can't imagine staff offering an opinion of record on the subject.
"ay" for "aye" would work for me.
-e
On
Perhaps a dose of factual information may temper this thread.
If we are talking about ISO-3166-2 - the basis for the CCTLD delegations, then:
1_ Scotland has no say in the country code selected.
2_ ICANN has no say in the country code selected.
3_ The choice is up to an ISO committee.
See:
David Conrad writes:
>> A friend told me that .su domains are quite common in windows
>> environments after the admins discovered that .local is not a good
>> choice. ;-)
>
> That would be an *exceptionally* bad idea.
I agree. On the other hand: People pay me to fix network problems,
including
On Sep 17, 2014, at 7:17 AM, Jens Link wrote:
> Owen DeLong writes:
>> On Sep 16, 2014, at 8:55 AM, Majdi S. Abbas wrote:
>>> su is not available.
>> I think it is now, since the break up of the Soviet Union.
No it is not.
> A friend told me that .su domains are quite common in windows
> e
Hi,
On Sep 17, 2014, at 5:18 AM, David Cantrell wrote:
> On Tue, Sep 16, 2014 at 09:26:24AM -0700, David Conrad wrote:
>
>> SU is the Soviet Union, now classified as ?exceptionally reserved? which
>> IANA treats as available for assignment (other exceptionally reserved codes
>> are EU, UK, and
Owen DeLong writes:
> On Sep 16, 2014, at 8:55 AM, Majdi S. Abbas wrote:
>> su is not available.
> I think it is now, since the break up of the Soviet Union.
A friend told me that .su domains are quite common in windows
environments after the admins discovered that .local is not a good
ch
On Tue, Sep 16, 2014 at 09:26:24AM -0700, David Conrad wrote:
> SU is the Soviet Union, now classified as ?exceptionally reserved? which IANA
> treats as available for assignment (other exceptionally reserved codes are
> EU, UK, and AC)...
Do you not mean *un*available for assignment? They're n
http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Decoding_table
VR, GO, ON, NY, ...these seems to be free :D
Clearly New York must declare independence.
--
--
ℱin del ℳensaje.
50 matches
Mail list logo
