Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenBSD folklore and share/misc/airport

cambus.net

Post reply on HN
Print view View original

51–60 of 79 posts

Re: OpenBSD folklore and share/misc/airport

#51

Post by thesuitonym »

justusthane wrote: post #43
efortis wrote: post #2

Not your everyday caveats section: https://man.openbsd.org/airport.7#CAVEATS

There seems to be a conflict here. The author of the linked article interprets the guideline, "New airports can only be added by OpenBSD developers who have visited an airport and thereby have verified its existence," as only requiring that you have been to the airport, not necessarily having flown from: > Once again, the more astute reader will not have missed the fact that the rules do not stipulate any flying requ…

>New airports can only be added by OpenBSD developers who have visited an airport and thereby have verified its existence

This says nothing about rail stations. For a rail station to be added, you must land on it. Presumably, taking off from there does not count.

Re: OpenBSD folklore and share/misc/airport

#52

Post by reaperducer »

splonk wrote: post #45
gspr wrote: post #30

Earlier quoted context omitted.

And they list OSL as "all airports around Oslo, Norway". That's not the case, OSL is one particular airport (the main one, Gardermoen). They correctly list the second airport as TRF.

OSL is also the IATA metropolitan city code for Oslo, basically meaning "all airports around Oslo". Some booking engines support these for convenience - for example, ones using Sabre as a backend may support QSF (also listed in this file) for all airports around San Francisco. I flew to Oslo recently and know I saw OSL used as a metro code first on at least one booking engine. It doesn't really make sense to put thes…

See also: NYC for metropolitan New York airport, and HOU for Houston's airports, even though Houston Hobby Airport is also HOU.

Re: OpenBSD folklore and share/misc/airport

#53

Post by compsciphd »

splonk wrote: post #45
gspr wrote: post #30

Earlier quoted context omitted.

And they list OSL as "all airports around Oslo, Norway". That's not the case, OSL is one particular airport (the main one, Gardermoen). They correctly list the second airport as TRF.

OSL is also the IATA metropolitan city code for Oslo, basically meaning "all airports around Oslo". Some booking engines support these for convenience - for example, ones using Sabre as a backend may support QSF (also listed in this file) for all airports around San Francisco. I flew to Oslo recently and know I saw OSL used as a metro code first on at least one booking engine. It doesn't really make sense to put thes…

I'll be pedantic and say that technically OSL as a metropolitan city code isn't an airport (i.e. should fall under the same caveat as the railway portion of the man page)

Re: OpenBSD folklore and share/misc/airport

#54

Post by gspr »

reaperducer wrote: post #52
splonk wrote: post #45

Earlier quoted context omitted.

OSL is also the IATA metropolitan city code for Oslo, basically meaning "all airports around Oslo". Some booking engines support these for convenience - for example, ones using Sabre as a backend may support QSF (also listed in this file) for all airports around San Francisco. I flew to Oslo recently and know I saw OSL used as a metro code first on at least one booking engine. It doesn't really make sense to put thes…

See also: NYC for metropolitan New York airport, and HOU for Houston's airports, even though Houston Hobby Airport is also HOU.

> NYC for metropolitan New York airport

Sure, but NYC isn't also a specific New York City airport (JFK, EWR, LGA). The problem here is that OSL is apparently used both for the metropolitan area and for one specific airport (in the metropolitan area).

Re: OpenBSD folklore and share/misc/airport

#55

Post by raynigon »

SSLy wrote: post #17
traceroute66 wrote: post #5

Earlier quoted context omitted.

> Which makes you wonder why some railway stations would have a IATA code. Such locations, which can also be bus stations and ferry ports, are known as "intermodal locations". TL;DR its for ticketing purposes to enable flight and rail/bus/ferry legs to be issued on the same ticket. Or at least that's the theory. To be honest its probably going be extinct in due course, given the complexities of integrating the airlin…

If memory serves me right, it's still used in Germany for trips outbound from FRA. You buy a ticket with a train somewhere → FRA leg, and an airplane FRA → somewhere-else.

It gets even better. One of the big Software Systems at Fraport has a „Flight“ class, which exposes the method „isTrain“… On another german airport the same class was extended by a „isTruck“ method for parcel trucks…

Re: OpenBSD folklore and share/misc/airport

#56

Post by sophacles »

justusthane wrote: post #43
efortis wrote: post #2

Not your everyday caveats section: https://man.openbsd.org/airport.7#CAVEATS

There seems to be a conflict here. The author of the linked article interprets the guideline, "New airports can only be added by OpenBSD developers who have visited an airport and thereby have verified its existence," as only requiring that you have been to the airport, not necessarily having flown from: > Once again, the more astute reader will not have missed the fact that the rules do not stipulate any flying requ…

I don't see a requirement that the OpenBSD developer needs to have flown into the railway station. Just that someone survived landing a plane at the railway station for it to count as an airport.

Re: OpenBSD folklore and share/misc/airport

#57

Post by sophacles »

half-kh-hacker wrote: post #37
leugim wrote: post #8

I visited 4 airports that aren't in the list. Do you think I can add them to the list? Never committed before to OpenBSD so I do not know if I compute as a "OpenBSD developers" in "New airports can only be added by OpenBSD developers who have visited an airport and thereby have verified its existence."

I think maybe this could be workable if an OpenBSD developer were to visit you in person to verify your existence and thereby transitively verify the existence of the claimed "visited airport".

What if I know a guy who knows a guy?

Re: OpenBSD folklore and share/misc/airport

#58

Post by bawolff »

mrweasel wrote: post #29
em500 wrote: post #10

Ok, I'll ask the obvious. Why is OpenBSD trying to maintain a list of IATA airport codes? (And before you ask why not, try to think of some answers yourself first. I can come up with a few drawbacks, though I'm nowhere close to a subject expert.)

There's also share/misc/birthtoken with a list of birth stones and flowers. That's actually much more weird than a list of airport codes. https://cvsweb.openbsd.org/src/share/misc/birthtoken

I think mac os also has the list of birthstones

Re: OpenBSD folklore and share/misc/airport

#59

Post by bityard »

justusthane wrote: post #43
efortis wrote: post #2

Not your everyday caveats section: https://man.openbsd.org/airport.7#CAVEATS

There seems to be a conflict here. The author of the linked article interprets the guideline, "New airports can only be added by OpenBSD developers who have visited an airport and thereby have verified its existence," as only requiring that you have been to the airport, not necessarily having flown from: > Once again, the more astute reader will not have missed the fact that the rules do not stipulate any flying requ…

> However, the Caveat in the man page seems to contradict this, and indicates that you do have to fly in

This is an attempt at humor, because railway stations are not airports.

Re: OpenBSD folklore and share/misc/airport

#60

Post by cestith »

mellavora wrote: post #24
netsharc wrote: post #21

Earlier quoted context omitted.

Sigh, bot-generated content litters the whole internet. I was doing some address completion stuff and learned about virtual ZIP codes in my country, i.e. ZIP codes that are just for routing and don't have a geographical area, but if you look them up on the Internet of course there are sites that say "$ZIP is a city in the state of $STATE". Hey Elon, can you pay $15 billion to get rid of bots on the Internet?

to be pendantic, all (US) ZIP codes are just for routing. Any correspondence to a geographical area is an artifact of this, and subject to change. Also, it is possible for two ZIP codes to overlap geographically.

In particular some numbered zones are entirely contained geographically within others. In some places in the US, there's a ZIP for delivery to private homes and businesses but another for delivery within the Postal Service network, including delivery to post office boxes. The one I remember most readily is Quincy, Illinois. The city is 62301 and the surrounding county 62305, but PO boxes are 62306, located within the post offices that sit within the 62301 zone.
Post reply on HN