Domain: nyud.net
Stories and comments across the archive that link to nyud.net.
Comments · 3,202
-
Folks, PLEASE
Use coral cache when submitting!
Even something like..
Nintendo Revolution controller ( Coralized Link )
would be just dandy.
Anyways here is the coralized link..use it!
http://www.1up.com.nyud.net:8090/do/newsStory?cId= 3143782 -
Folks, PLEASE
Use coral cache when submitting!
Even something like..
Nintendo Revolution controller ( Coralized Link )
would be just dandy.
Anyways here is the coralized link..use it!
http://www.1up.com.nyud.net:8090/do/newsStory?cId= 3143782 -
Mod you a Karma Whoring Slut
Don't moderate sluts, please.
Mirrordot
Coral Cache -
this is (what I can make of) the critisismThanks to the very generous move from slashdot to
/. the spoof site, it is not clear why others are critisising DCC.
the spoof site at http://www.dccalliance.biz.nyud.net:8090/faq.html is pretty slow too, here is my analysis (and a copy of their 'faq':
What is the DCC Alliance?
The DCC Alliance is a collection of invdividuals with a link to Debian. It exists in order to counter the idea that the use of the Debian trademark is permissable if it's hidden inside an acronym.
So somebody is upset about basing the name of a separate organisation on 'Debian' and abbreviate that to a 'D'. Well wanker, I tell you something: you cannot trademark a single letter, or we'd only have about 36 possible companies.
What Does "DCC" stand for?
"DCC" is an abbreviation for "Debian common core Cheerleaders and Critics". Since "Debian Common Core" is a trademark of the DCC Alliance, only the abbreviated form is used in referring to the DCC Alliance.
(this seems a rip-off from the 'real' DCC faq entry. see above, no trademarks on single letters.
Will the DCC "fork" Debian?
Yes, the Debian Common Core alliance will fork Debian. As an example, the Debian kernel will be modified. Maintaining a branch of a package that is not identical to the upstream one is a de-facto fork.
Aha, a somewhat real-ish bone to pick. Except that creating a patched kernel is not such a big deal. You can find several in testing, does that mean that testing has been forked with every new kernel release? As long as the new kernel is interoperable with the one it replaces you can hardly call that forking.
is DCC necesary?
Debian has grown into a big organisation, and thus also has it's share of people with 'uncommon personalities'. It is all a volunteer effort (and thus?) some people in debian react a little allergic to commerce baseed on Debian, even though the licence allows it. Commercial Debian-based distro's have a vested interest in Debian, so they seek some influence. It can be vey hard to have to argue with every maintainer whose package they have altered to get him to accept the changes(There are 1000's of developers and and at least ten times more packages in Debian). Even with proper conflict resolution it quickly becomes a nightmare, so a lot of distro makers don't feed their changes upstream/to Debian at all.
That is a problem and something that a separate repository can solve. Yes that is in effect a fork, in the same sense that Ubuntu or Knoppix is a fork (not for the silly reason above). If the Debian derived distromakers have their own repository where they can work together changing Debian to their common goals without getting bogged down in Debian rules/games, then that is just great, IMHO.
It is great for the Debian-derived-distro-makers(DDDM?), as it allows them to cooperate and improve Debian while they are at it. It is great because it avoids conflict and bottlenecks. Commercials distro's (can) have a different interest than induvidual Debain developers. With this construction no single Debain developer can obstruct a DDDM. It is great because It will concentrate all enhancements made by DDDM's into one place, so the Debian developers don't need to track all different DDDMs for changes to their packages. And most of all, it will concentrate efforts into coding and cooperating, and that is good for all. -
Re:MirrordotI've been beaten to it. Twice! Mod me redundant
:(Well here's the coral cache link then:
-
Try this url instead
http://www.dccalliance.org.nyud.net:8090/
Seems to work when you get the correct URL. Fancy. -
Coral Cache
-
Spoof mirror
Screw the real site, the spoof is what's important: http://www.dccalliance.biz.nyud.net:8090/
-
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Re:Coral link
Unfortunately, the images are (not) being served from another server entirely; tivac.com, which is now also slashdotted... Here are the images linked through Coral.
contacts.png (long lines make slashcode happy)
drag.png (long lines make slashcode happy)
nodrag.png (long lines make slashcode happy)
editcontact.png (long lines make slashcode happy)
message.png (long lines make slashcode happy)
resized.png (long lines make slashcode happy)
indent.png (long lines make slashcode happy)
centered.png (long lines make slashcode happy)
rightalign.png (long lines make slashcode happy)
addcontacts.png (long lines make slashcode happy)
colors.png (long lines make slashcode happy)
smilies.png (long lines make slashcode happy)
autocomplete.png (long lines make slashcode happy)
hyperlink.png (long lines make slashcode happy)
hyperlinkoptions.png (long lines make slashcode happy)
writing.png (long lines make slashcode happy)
confirm.png (long lines make slashcode happy) -
Wow. Tabs for multiple message windows!
It's too bad that I've been phasing out my Yahoo email account. Anyone know of an opensource webmail package that is even close to this interface? Squirrelmail is looking a little shabby in comparison.
PS. Screenshots are /.'ed. Try mirrordot or coral cache -
Coral link
The server is beginning to be sluggish...
Try the snappy Coral link:
http://patcavit.com.nyud.net:8090/2005/09/14/y-mai l-beta-impressions/ -
False advertising guys...
All but one of the renders on the company's online gallery page features gratuitous cleavage.
Don't listen to him, here's the page
http://www.daz3d.com.nyud.net:8090/program/studio/ 1_0gallery.php
and the graphics don't look very stunning... (from a male perspective i mean) -
Re:'universal' binaries ayyy
Universal Binaries aren't two executables concatenated into one big file. They are separate files that are sitting in a special kind of folder (a package) that the Finder presents as one file. On the filesystem level, they are most definately separate.
Oh, I'm afraid they're most definitely single files.
I'm an OS X developer, and I know whereof I speak because I deal with these things all the time. Not only do I write system-level software which at certain points involves scanning binary files to locate symbols, sections, and the like, but I also have access to a DTK, and can see first hand that the ppc/i386 binaries are formatted in exactly the same way as ppc/ppc64 (or ppc/ppc64/i386) binaries are when building for 64-bit support on OS X 10.3.
GUI applications are bundles (usually -- I've written command-line apps that show a UI before now); frameworks are (kinda, they don't have the 'bundle bit' set in their top-level folders, so they appear as a folder, not a file); plugins are (if they have the bundle bit set); and kernel extensions are. Lots of things are indeed bundles.
Command-line tools, however, are not bundles, yet they are (or can be) Universal Binaries.
However, go into the Finder, do Cmd-Shift-G, and type '/usr/bin' into the field, then click 'Go'. See all those files? They're not bundles. If you right-click or control-click on them, there is no 'show package contents' option: that's because they're not a package. And yet, these are exactly the type of files which use the universal/fat binary format to gain 64-bit support (since that's only available for non-GUI apps which link only against the system & c libraries).
In the Terminal, type file
/usr/lib/libSystem.B.dylib and press enter. You'll see two (or on a DTK, three) architectures listed. Now do ls -ld /usr/lib/libSystem.B.dylib and press enter again. Look at the leftmost character. Notice how it's a hyphen, not a 'd'? That means it's a file, not a folder. Now do the same thing for an application bundle (e.g. ls -ld /Applications/Calculator.app). See how the leftmost character here is a 'd'? That's because it's a folder, with (possibly) the bundle bit set, although that last doesn't matter since the Finder has special handling of the .app suffix anyway.Universal binaries are created by compiling separate binary files, one for each target architecture. These binaries are then passed to the lipo tool to concatenate them into a single binary file; here's the manual page for lipo.
Also, you can see here some instructions on how to build a universal binary from a configure-style project (i.e. not using Xcode). Scroll down particularly to the Merging Multiple Builds section, taking especial note of the bit about using the file command to verify the contents of the single file that was output.
For further information, please refer to the following:
- An entry in the blog of one Wilfredo Sanchez, an Apple software engineer.
- The second comment on this blog entry, made by one Alex Von Below.
- There's a whole page on Universal Binaries over at CocoaDev.
- And lastly, can we go without a visit to Wikipedia?. Well, obviously you did, but then, you don't s
-
Re:'universal' binaries ayyy
Universal Binaries aren't two executables concatenated into one big file. They are separate files that are sitting in a special kind of folder (a package) that the Finder presents as one file. On the filesystem level, they are most definately separate.
Oh, I'm afraid they're most definitely single files.
I'm an OS X developer, and I know whereof I speak because I deal with these things all the time. Not only do I write system-level software which at certain points involves scanning binary files to locate symbols, sections, and the like, but I also have access to a DTK, and can see first hand that the ppc/i386 binaries are formatted in exactly the same way as ppc/ppc64 (or ppc/ppc64/i386) binaries are when building for 64-bit support on OS X 10.3.
GUI applications are bundles (usually -- I've written command-line apps that show a UI before now); frameworks are (kinda, they don't have the 'bundle bit' set in their top-level folders, so they appear as a folder, not a file); plugins are (if they have the bundle bit set); and kernel extensions are. Lots of things are indeed bundles.
Command-line tools, however, are not bundles, yet they are (or can be) Universal Binaries.
However, go into the Finder, do Cmd-Shift-G, and type '/usr/bin' into the field, then click 'Go'. See all those files? They're not bundles. If you right-click or control-click on them, there is no 'show package contents' option: that's because they're not a package. And yet, these are exactly the type of files which use the universal/fat binary format to gain 64-bit support (since that's only available for non-GUI apps which link only against the system & c libraries).
In the Terminal, type file
/usr/lib/libSystem.B.dylib and press enter. You'll see two (or on a DTK, three) architectures listed. Now do ls -ld /usr/lib/libSystem.B.dylib and press enter again. Look at the leftmost character. Notice how it's a hyphen, not a 'd'? That means it's a file, not a folder. Now do the same thing for an application bundle (e.g. ls -ld /Applications/Calculator.app). See how the leftmost character here is a 'd'? That's because it's a folder, with (possibly) the bundle bit set, although that last doesn't matter since the Finder has special handling of the .app suffix anyway.Universal binaries are created by compiling separate binary files, one for each target architecture. These binaries are then passed to the lipo tool to concatenate them into a single binary file; here's the manual page for lipo.
Also, you can see here some instructions on how to build a universal binary from a configure-style project (i.e. not using Xcode). Scroll down particularly to the Merging Multiple Builds section, taking especial note of the bit about using the file command to verify the contents of the single file that was output.
For further information, please refer to the following:
- An entry in the blog of one Wilfredo Sanchez, an Apple software engineer.
- The second comment on this blog entry, made by one Alex Von Below.
- There's a whole page on Universal Binaries over at CocoaDev.
- And lastly, can we go without a visit to Wikipedia?. Well, obviously you did, but then, you don't s
-
Re:'universal' binaries ayyy
Universal Binaries aren't two executables concatenated into one big file. They are separate files that are sitting in a special kind of folder (a package) that the Finder presents as one file. On the filesystem level, they are most definately separate.
Oh, I'm afraid they're most definitely single files.
I'm an OS X developer, and I know whereof I speak because I deal with these things all the time. Not only do I write system-level software which at certain points involves scanning binary files to locate symbols, sections, and the like, but I also have access to a DTK, and can see first hand that the ppc/i386 binaries are formatted in exactly the same way as ppc/ppc64 (or ppc/ppc64/i386) binaries are when building for 64-bit support on OS X 10.3.
GUI applications are bundles (usually -- I've written command-line apps that show a UI before now); frameworks are (kinda, they don't have the 'bundle bit' set in their top-level folders, so they appear as a folder, not a file); plugins are (if they have the bundle bit set); and kernel extensions are. Lots of things are indeed bundles.
Command-line tools, however, are not bundles, yet they are (or can be) Universal Binaries.
However, go into the Finder, do Cmd-Shift-G, and type '/usr/bin' into the field, then click 'Go'. See all those files? They're not bundles. If you right-click or control-click on them, there is no 'show package contents' option: that's because they're not a package. And yet, these are exactly the type of files which use the universal/fat binary format to gain 64-bit support (since that's only available for non-GUI apps which link only against the system & c libraries).
In the Terminal, type file
/usr/lib/libSystem.B.dylib and press enter. You'll see two (or on a DTK, three) architectures listed. Now do ls -ld /usr/lib/libSystem.B.dylib and press enter again. Look at the leftmost character. Notice how it's a hyphen, not a 'd'? That means it's a file, not a folder. Now do the same thing for an application bundle (e.g. ls -ld /Applications/Calculator.app). See how the leftmost character here is a 'd'? That's because it's a folder, with (possibly) the bundle bit set, although that last doesn't matter since the Finder has special handling of the .app suffix anyway.Universal binaries are created by compiling separate binary files, one for each target architecture. These binaries are then passed to the lipo tool to concatenate them into a single binary file; here's the manual page for lipo.
Also, you can see here some instructions on how to build a universal binary from a configure-style project (i.e. not using Xcode). Scroll down particularly to the Merging Multiple Builds section, taking especial note of the bit about using the file command to verify the contents of the single file that was output.
For further information, please refer to the following:
- An entry in the blog of one Wilfredo Sanchez, an Apple software engineer.
- The second comment on this blog entry, made by one Alex Von Below.
- There's a whole page on Universal Binaries over at CocoaDev.
- And lastly, can we go without a visit to Wikipedia?. Well, obviously you did, but then, you don't s
-
Re:'universal' binaries ayyy
Universal Binaries aren't two executables concatenated into one big file. They are separate files that are sitting in a special kind of folder (a package) that the Finder presents as one file. On the filesystem level, they are most definately separate.
Oh, I'm afraid they're most definitely single files.
I'm an OS X developer, and I know whereof I speak because I deal with these things all the time. Not only do I write system-level software which at certain points involves scanning binary files to locate symbols, sections, and the like, but I also have access to a DTK, and can see first hand that the ppc/i386 binaries are formatted in exactly the same way as ppc/ppc64 (or ppc/ppc64/i386) binaries are when building for 64-bit support on OS X 10.3.
GUI applications are bundles (usually -- I've written command-line apps that show a UI before now); frameworks are (kinda, they don't have the 'bundle bit' set in their top-level folders, so they appear as a folder, not a file); plugins are (if they have the bundle bit set); and kernel extensions are. Lots of things are indeed bundles.
Command-line tools, however, are not bundles, yet they are (or can be) Universal Binaries.
However, go into the Finder, do Cmd-Shift-G, and type '/usr/bin' into the field, then click 'Go'. See all those files? They're not bundles. If you right-click or control-click on them, there is no 'show package contents' option: that's because they're not a package. And yet, these are exactly the type of files which use the universal/fat binary format to gain 64-bit support (since that's only available for non-GUI apps which link only against the system & c libraries).
In the Terminal, type file
/usr/lib/libSystem.B.dylib and press enter. You'll see two (or on a DTK, three) architectures listed. Now do ls -ld /usr/lib/libSystem.B.dylib and press enter again. Look at the leftmost character. Notice how it's a hyphen, not a 'd'? That means it's a file, not a folder. Now do the same thing for an application bundle (e.g. ls -ld /Applications/Calculator.app). See how the leftmost character here is a 'd'? That's because it's a folder, with (possibly) the bundle bit set, although that last doesn't matter since the Finder has special handling of the .app suffix anyway.Universal binaries are created by compiling separate binary files, one for each target architecture. These binaries are then passed to the lipo tool to concatenate them into a single binary file; here's the manual page for lipo.
Also, you can see here some instructions on how to build a universal binary from a configure-style project (i.e. not using Xcode). Scroll down particularly to the Merging Multiple Builds section, taking especial note of the bit about using the file command to verify the contents of the single file that was output.
For further information, please refer to the following:
- An entry in the blog of one Wilfredo Sanchez, an Apple software engineer.
- The second comment on this blog entry, made by one Alex Von Below.
- There's a whole page on Universal Binaries over at CocoaDev.
- And lastly, can we go without a visit to Wikipedia?. Well, obviously you did, but then, you don't s
-
Re:'universal' binaries ayyy
Universal Binaries aren't two executables concatenated into one big file. They are separate files that are sitting in a special kind of folder (a package) that the Finder presents as one file. On the filesystem level, they are most definately separate.
Oh, I'm afraid they're most definitely single files.
I'm an OS X developer, and I know whereof I speak because I deal with these things all the time. Not only do I write system-level software which at certain points involves scanning binary files to locate symbols, sections, and the like, but I also have access to a DTK, and can see first hand that the ppc/i386 binaries are formatted in exactly the same way as ppc/ppc64 (or ppc/ppc64/i386) binaries are when building for 64-bit support on OS X 10.3.
GUI applications are bundles (usually -- I've written command-line apps that show a UI before now); frameworks are (kinda, they don't have the 'bundle bit' set in their top-level folders, so they appear as a folder, not a file); plugins are (if they have the bundle bit set); and kernel extensions are. Lots of things are indeed bundles.
Command-line tools, however, are not bundles, yet they are (or can be) Universal Binaries.
However, go into the Finder, do Cmd-Shift-G, and type '/usr/bin' into the field, then click 'Go'. See all those files? They're not bundles. If you right-click or control-click on them, there is no 'show package contents' option: that's because they're not a package. And yet, these are exactly the type of files which use the universal/fat binary format to gain 64-bit support (since that's only available for non-GUI apps which link only against the system & c libraries).
In the Terminal, type file
/usr/lib/libSystem.B.dylib and press enter. You'll see two (or on a DTK, three) architectures listed. Now do ls -ld /usr/lib/libSystem.B.dylib and press enter again. Look at the leftmost character. Notice how it's a hyphen, not a 'd'? That means it's a file, not a folder. Now do the same thing for an application bundle (e.g. ls -ld /Applications/Calculator.app). See how the leftmost character here is a 'd'? That's because it's a folder, with (possibly) the bundle bit set, although that last doesn't matter since the Finder has special handling of the .app suffix anyway.Universal binaries are created by compiling separate binary files, one for each target architecture. These binaries are then passed to the lipo tool to concatenate them into a single binary file; here's the manual page for lipo.
Also, you can see here some instructions on how to build a universal binary from a configure-style project (i.e. not using Xcode). Scroll down particularly to the Merging Multiple Builds section, taking especial note of the bit about using the file command to verify the contents of the single file that was output.
For further information, please refer to the following:
- An entry in the blog of one Wilfredo Sanchez, an Apple software engineer.
- The second comment on this blog entry, made by one Alex Von Below.
- There's a whole page on Universal Binaries over at CocoaDev.
- And lastly, can we go without a visit to Wikipedia?. Well, obviously you did, but then, you don't s
-
Cached photos
-
Cached photos
-
End game? What end game?
Yeah, I've heard some people (I don't know if I'd say "many") complaining, too. Don't take this personally. Since "many people" are critical—not you—I'm giving you the benefit of a doubt that you're merely observing, not complaining.
COH is still lacking in any kind of end game content. Once you get the level 50, the only thing there is to do from there is to roll up a new character and start over.
(Insert standard lament about how people don't roleplay here, so I can move on to stuff that pertains to this comment...)
End game content? You mean after you've won? Isn't the point of a role-playing game that there is no end of the game?
Congratulations, you've reached level 50. So what? Keep logging on and give advice to new players. Hang out in Atlas Park and act like, well, a hero. Listen to The Cape Radio and dance with the DJ's. Write some articles for my virtual newspaper or my CoH wiki. Join the Taxibots and volunteer to teleport heroes around. Host a costume contest. Host a trivia contest. Host a scavenger hunt. Jeez, man, show us why the MM in MMORPG makes a game more fun!
And what's so bad about rolling up a new character? So your badass übertank finally snagged the Hero of the City badge. What would you do if your primary power was the ability to heal other heroes? How would a Warshade fare in the Arena? How can you make the most of those weird powers that hardly anyone else has? In other words, there's always something different to try and do, so get back out there and have some fun!
Look, I know that sometimes the game can be tedious. Whenever I find myself getting bored, I finish what I'm doing if I'm with a team, and bounce to something different, usually something a little more creative than doing Officer Dave's missions yet again. If all fails, ping me at @KingSkippus and we'll figure out something to do to break the monotony. Whatever you do, just please don't become one of those folks who follow this guy's satirical advice. (non-Coral)
-
Re:Please be nice ...
-
Tech support hates them alreadyFrom the signature dialog:
Type or ink your name below or click Select Image to select a picture to use as your signature:
I guaran-frickin'-tee our IT guy will get at least one call from a peeved user that can't 1) get Windows to recognize their inked signature or 2) get Sharpie off their LCD monitor.
I hereby propose "Strauser's Rule of UI Design":
Remember that stupid people will read your words, too. Consider the worst possible misinterpretation of anything you write, because it will always come back to you.
-
Re:Another site's Coral Link
And here's the coral cache link for it....
http://bink.nu.nyud.net:8090/photos/news_article_i mages/category1015.aspx
-
Re:even worse are misleading optionsCheck out this picture and despair.
Will be saved in: MS Word Document
File Type: C:\Users\Pat\Documents
If they can't figure out what goes where while they are rearranging the save dialog, what hope do the end users have of finding things. -
Server In Flames
[Rant] Is it so freaking hard to post the link as a Coral Cache link???
You just take the existing url www.test.com/stuff.htm and add ".nyud.net:8090"
www.test.com.nyud.net:8090/stuff.htm
Or for this site:
http://pdc.xbetas.com.nyud.net:8090/?page=o12previ ew1
That's it! It's easy and would let sooo many more people see the article.[/rant] -
Mirror
...here.
-
Re:slashdotted already
-
Re:RTFA?
Behold! The wonders of Coral Cache!
-
Coralized link
-
printable version and article mirror
-
Re:Definitely listen/watch the WoW music video...
http://x500.putfile.com.nyud.net:8090/videos/a3-1
9 100101925.wmv What about this one? -
You killed Ars! You bastards!
Server's running slow with less than 60 comments, so:
Coralized page 1
Coralized page 2
Coralized page 3
Coralized page 4 -
You killed Ars! You bastards!
Server's running slow with less than 60 comments, so:
Coralized page 1
Coralized page 2
Coralized page 3
Coralized page 4 -
You killed Ars! You bastards!
Server's running slow with less than 60 comments, so:
Coralized page 1
Coralized page 2
Coralized page 3
Coralized page 4