Plus, in the photo of the tile in the article, it looks to me like the tile was stuck in a conviently shaped pothile.
I'm sure it wouldn't be hard in a big city to wander around for a little bit till you found a pothole that's a good fit for your tile. The you just come back at night and drop it in, maybe tap it with a brick for good measure.
I've read some other articles that claim the cluster will be running Linux, but you bring up an interesteing point with XCode.
XCode does have distributed compiling support. I don't know how common this is or isn't with Linux development tools, but with this type of cluster compile times would be incredibly reduced. Yet another reason an OS X cluster is attractive.
Mac freaks have been speculating that the iPod will get 802.11 for a long time now... and sony beats them to it.
I wonder how customizable the Linux install is. This type of device will be very usefull with ZeroConf. Any services it provides (mp3, divx streaming...) will automagically appear as soon as it joins the network. yippee.
What I did, and things I haven't seen here yet
on
Pinewood Derby Tips?
·
· Score: 1
I killed my den, and tied for 2nd in the regionals, or whatever they were. So here's my tips...
1) Polish. Polish everything. Use pumice powder on the axels. Take a 1cm strip of old t-shirt and get it wet, then put some wet pumice powder on it. Use a drill to hold the axel and spin it while using the cloth strip to polish the axel. Thread the same strips through the wheel to polish the inside. Use 000 steel wool to polish the wood.
2) Shape the wheels. This might be illegal now, but if you can shape the wheels so that the wheel edge it slopes in and is not perpendicular to the axel then the car will run just on the outside edge, drastically reducing friction.
3) Use small weight adjusters. I found some screw-in types at the hardware store and had stable weight adjustment.
4) shape doesn't really matter, but make it thin.
5) Graphite lubricant. the way to go.
ok, hope it helps. One more thing though: make your kid do all the work. I did it all and it was fun, even if my dad helped with the ideas.
This is something I just don't understand about Apple and it's failed clone attempt. Why wasn't Apple making money off the clones? Why weren't the clone makers paying Apple for the R&D, was there no licensing agreements?
You make the comparison to IBM, but it's a little different than that since Apple owns the OS as well, it's more like IBM + Microsoft. At least one of those companies benefited from the clones.
Apple should have recouped their R&D costs through license fees from the clone makers. They should have charged appropriately for every copy of Mac OS, they should have charged for hardware reference designs. Maybe they could just sell motherboards to clone makers. There are companies that are profitable that only sell motherboards.
I understand killing the clones because of Apples obsession with quality and complete control of the user experience more than I do for economic reasons. Apple thinks too much like just a hardware company and doesn't run their software side to make a profit.
I don't really understand including so many connectors in a mini computer. Why have two PS/2 ports, a serial port, a parallel, analog and digital audio in/out, 2 ethernet, and 2 non powered firewire ports?
USB should replace the PS/2, serial and parallel ports, and I'd rather have one powered firewire ports then two unpowered ones, and I don't need 2 ethernet ports, or even a modem port on htat kind of computer.
I wouldn't mind a PC Card slot though, and where's the DVI?
Any one have a good reccomendation for a super-mini that can boot with LinuxBIOS so it doesn't need a HD or CD drive, but does have ethernet and USB?
Can anyone explain this or give a good link? I've read about them from a news point of view, but I'm interested in how a buffer underun allows someone to execute arbitrary code.
I have Stuffit Deluxe 6.5 and Stuffit Expander, they work fine together. Just set.sit,.zip,.gz, etc to open with Stuffit Expander. It sounds like the problem is just with extracting, not archiving, so you should be ok.
I'd like to hear those who dislike the APSL comment on this. If Apple's reasons for thier license terms are to keep a BSD tcp/ip like scenario from happening with Apple code, does that justify their license?
Any open source prject that would use this code, and modidy it, would release the code anyways, so the only people who it hurts are companies who would modify the code, but want to keep it secret. It seems this is perfect protection from those who would like to Apple as their R&D department.
APL is compatible with BSD, and they do give back the the *BSD projects, even though the BSD license doesn require it, as well as release Darwin as open source.
You can't be happy that Apple is participating in open source, you want them to give away everything. It's simple business that Apple has to retain some value added features in order to have something to sell (of course I'm sure you'd rather they gave everything away). Plus they wrote Aqua from scratch, it doesn't use open source code. Originally based on Display PostScript, they had to re-write the entire windowing and graphics system, and you want them to give that away? Basically, you're jealous.
They are not using open source like M$ used BDS tcp/ip stack, this is pure FUD. By all accounts they are contributing back to the projects they use, and are releaseing the core of their operating system as open source that even comes ready to run on open x86 hardware. They also hired Jordan Hubbard in part to make sure that they were able to work better with the *BSD projects.
The big deal isn't necessarily the 11.1 MP resolution, it's that the sensor is a full 35mm. Since most digital SLR's have a smaller sensor they only capture a small portion of the frame. This changes the effective focal length of lenses. A 300mm zoom may be a 500mm zoom on a digital SLR, and it will only capture a portion of the light, increasing exposure times. With a 33mm sensor the focal length is what it should be. This will be great for professionals.
Besides the backwards compatability, how is this better than FireWire?
I'd really like to see one standard for internal and external drives and other devices. Internal FireWire hasn't caught on because the drive are just ATA. I'd bet Serial ATA catches on much faster... oh well.
This isn't a PBX reccomendation, but you should look into VoiceXML for your frontend/voicemail. You can all sorts of cool things like branching with DTMF, or speech recognition. You can record speech, playback messages depending on input, use speech sysnthesis.
One thing I'd like to use that for is to leave messages for people who call in by letting them enter a PIN.
The only problem is the software, the projects on sourceforge don't seem to be that far along yet
I'd also check out VoIP for intercoms. There is opensource software for that. You could build your own VoIP intercoms/phones with a single board computer with built-in sound, or a usb soundcard, or the Creative Labs VoIP Blaster (there's oss called Fobbit to use that with Linux)
Slashdot Mirror
I'm sure it wouldn't be hard in a big city to wander around for a little bit till you found a pothole that's a good fit for your tile. The you just come back at night and drop it in, maybe tap it with a brick for good measure.
XCode does have distributed compiling support. I don't know how common this is or isn't with Linux development tools, but with this type of cluster compile times would be incredibly reduced. Yet another reason an OS X cluster is attractive.
Mac freaks have been speculating that the iPod will get 802.11 for a long time now... and sony beats them to it.
I wonder how customizable the Linux install is. This type of device will be very usefull with ZeroConf. Any services it provides (mp3, divx streaming...) will automagically appear as soon as it joins the network. yippee.
I killed my den, and tied for 2nd in the regionals, or whatever they were. So here's my tips...
1) Polish. Polish everything. Use pumice powder on the axels. Take a 1cm strip of old t-shirt and get it wet, then put some wet pumice powder on it. Use a drill to hold the axel and spin it while using the cloth strip to polish the axel. Thread the same strips through the wheel to polish the inside. Use 000 steel wool to polish the wood.
2) Shape the wheels. This might be illegal now, but if you can shape the wheels so that the wheel edge it slopes in and is not perpendicular to the axel then the car will run just on the outside edge, drastically reducing friction.
3) Use small weight adjusters. I found some screw-in types at the hardware store and had stable weight adjustment.
4) shape doesn't really matter, but make it thin.
5) Graphite lubricant. the way to go.
ok, hope it helps. One more thing though: make your kid do all the work. I did it all and it was fun, even if my dad helped with the ideas.
I think you need to read the How-To-Be-A-Player Mini-HOWTO.
This is something I just don't understand about Apple and it's failed clone attempt. Why wasn't Apple making money off the clones? Why weren't the clone makers paying Apple for the R&D, was there no licensing agreements?
You make the comparison to IBM, but it's a little different than that since Apple owns the OS as well, it's more like IBM + Microsoft. At least one of those companies benefited from the clones.
Apple should have recouped their R&D costs through license fees from the clone makers. They should have charged appropriately for every copy of Mac OS, they should have charged for hardware reference designs. Maybe they could just sell motherboards to clone makers. There are companies that are profitable that only sell motherboards.
I understand killing the clones because of Apples obsession with quality and complete control of the user experience more than I do for economic reasons. Apple thinks too much like just a hardware company and doesn't run their software side to make a profit.
I don't really understand including so many connectors in a mini computer. Why have two PS/2 ports, a serial port, a parallel, analog and digital audio in/out, 2 ethernet, and 2 non powered firewire ports?
USB should replace the PS/2, serial and parallel ports, and I'd rather have one powered firewire ports then two unpowered ones, and I don't need 2 ethernet ports, or even a modem port on htat kind of computer.
I wouldn't mind a PC Card slot though, and where's the DVI?
Any one have a good reccomendation for a super-mini that can boot with LinuxBIOS so it doesn't need a HD or CD drive, but does have ethernet and USB?
Can anyone explain this or give a good link? I've read about them from a news point of view, but I'm interested in how a buffer underun allows someone to execute arbitrary code.
I have Stuffit Deluxe 6.5 and Stuffit Expander, they work fine together. Just set .sit, .zip, .gz, etc to open with Stuffit Expander. It sounds like the problem is just with extracting, not archiving, so you should be ok.
I'd like to hear those who dislike the APSL comment on this. If Apple's reasons for thier license terms are to keep a BSD tcp/ip like scenario from happening with Apple code, does that justify their license?
Any open source prject that would use this code, and modidy it, would release the code anyways, so the only people who it hurts are companies who would modify the code, but want to keep it secret. It seems this is perfect protection from those who would like to Apple as their R&D department.
APL is compatible with BSD, and they do give back the the *BSD projects, even though the BSD license doesn require it, as well as release Darwin as open source.
How is Aqua a "core protocol"?
You can't be happy that Apple is participating in open source, you want them to give away everything. It's simple business that Apple has to retain some value added features in order to have something to sell (of course I'm sure you'd rather they gave everything away). Plus they wrote Aqua from scratch, it doesn't use open source code. Originally based on Display PostScript, they had to re-write the entire windowing and graphics system, and you want them to give that away? Basically, you're jealous.
They are not using open source like M$ used BDS tcp/ip stack, this is pure FUD. By all accounts they are contributing back to the projects they use, and are releaseing the core of their operating system as open source that even comes ready to run on open x86 hardware. They also hired Jordan Hubbard in part to make sure that they were able to work better with the *BSD projects.
Same post every thread. This guy's a tool.
There should be a way that Slashcode can recognize this message and mod it down.
The big deal isn't necessarily the 11.1 MP resolution, it's that the sensor is a full 35mm. Since most digital SLR's have a smaller sensor they only capture a small portion of the frame. This changes the effective focal length of lenses. A 300mm zoom may be a 500mm zoom on a digital SLR, and it will only capture a portion of the light, increasing exposure times. With a 33mm sensor the focal length is what it should be. This will be great for professionals.
Oh, 150MBytes/s... ok that's faster than current FireWire.
I'd really like to see one standard for internal and external drives and other devices. Internal FireWire hasn't caught on because the drive are just ATA. I'd bet Serial ATA catches on much faster... oh well.
One thing I'd like to use that for is to leave messages for people who call in by letting them enter a PIN.
The only problem is the software, the projects on sourceforge don't seem to be that far along yet
I'd also check out VoIP for intercoms. There is opensource software for that. You could build your own VoIP intercoms/phones with a single board computer with built-in sound, or a usb soundcard, or the Creative Labs VoIP Blaster (there's oss called Fobbit to use that with Linux)