it allows you to turn the pi into your own cloud server.
I got sick of fighting my isp's throttling rules, which kicked in at the most frustrating and inopportune times, like halfway through downloading linux ISO's to play with on my raspberry pi.
That's very interesting and something I'm inclined to do, too. Do you have any resources about that?
I have the same annoying problems - particularly as I like to offer up my bandwidth for Linux ISOs and creative commons works (I don't always contribute money to these projects (wife+kids usually see my wages before I do) so it's nice to contribute something even if the net effect is minute). Yet HTTP/HTTPS is completely unthrottled.
considering my ADSL only syncs at 6MB, and not 200MB or whatever, it's fine for my purposes. Most of my machines are also still connected with 802.11g, so locally is not really a big problem either.
I would think twice about using it as a straight fileserver though, because the ethernet and usb ports share bandwidth.
Of course I can't route my primary internet connection (about 330-340 Mbps typical throughput) over it, but Asus RT-N56U does that just fine.
Fileserver is not an issue, because there's about 300 Mbps total USB bandwidth and the NIC is just 100 Mbps. IRQs are a bit of an issue, full 100 Mbit bandwidth generates 2k IRQ/s, USB disk will probably take it to 8k IRQ/s, consuming a significant portion of CPU (maybe about 20%?).
But if 10 MBps (80-90 Mbps throughput) fileserver performance is enough, RPi is just fine. About 3.5 MBps over ssh, like when using for example sshfs. For comparison, 3.5 MBps more than enough to saturate "54 Mbps" 11g for example, which can do 24 Mbps under ideal conditions (~3 MBps).
The built in line out jacks have just horrible quality. (And I'm someone who doesn't believe in gold cables so for 'audiophiles' it must be torture.) Rather get a USB sound card and hook it up to your pi.
Also try out MPD (Music Player Daemon) if you want a juke box. MPD clients are widely available for any platform - you can sit on the couch and control your pi's MPD with a client running on your phone.
The problem is much more likely to be the DAC rather than the audio jack. However using a USB audio adapter may fix that as well as they'd have their own DAC. Earlier in this thread I did discuss another issue with audio on the Pi though: https://news.ycombinator.com/item?id=5969424
> Also try out MPD (Music Player Daemon) if you want a juke box. MPD clients are widely available for any platform - you can sit on the couch and control your pi's MPD with a client running on your phone.
Funny enough I did address that in this thread as well: https://news.ycombinator.com/item?id=5967949
Use the HDMI audio, or a USB audio device if you want decent quality sound out of a Pi.
As much as I'm an audiophile at times (less so now than I used to be), this is only being used as an in-car MP3 / FLAC player. My car speakers are much worse than the spec of the Pi's audio chipset. In fact they're not even balanced right so my next job is applying some bespoke EQing to the output in real time (hopefully the Pi will be powerful enough to perform this) to lessen the harshness of the heavy top-end and complete lack of sound in the mid-range frequencies (whoever authorised the inbuilt sound system in my car was clearly death!)
Thankfully I can usually distract myself from the shit sound quality by driving :P But sometimes (usually when really tired) it's too annoying to bare. Which is a pity as I love most other things about that car.
If you're tight for space, then that might be a problem, but the cost of these things is negligible these days.
Sadly space is the issue. The one I bought (which was more along the lines of £3) sadly pushes the dimensions of the device I'm building much too much. At some point I'm going to have to re-investigate the issue though - as I plan on adding voice control which means I'll need a mic in.
As for sound quality, that's really a non-issue given the it's going in a car with crappy speakers. So there's no point wasting money on a decent audio chip if I can't reproduce that sound accurately. (in an ideal world, I'd throw in some zero frequency curve studio monitors and use my spare Terratec Phase 96 as the Pi's sound device - but then the price really starts to jump. So instead I make do with what I've got)
* Controlling my TV/AC/other infrared devices around the house: http://www.stavros.io/posts/how-turn-your-raspberry-pi-infra...
* Controlling my garage door/RF sockets/other RF stuff around the house (pretty good range on this, too): http://www.stavros.io/posts/how-remote-control-rf-devices-ra...
* Writing an Android app to make HTTP calls to the Go server that launches the LIRC process, really low latency: http://www.stavros.io/posts/how-turn-your-raspberry-pi-infra...
This is the Pi B v1 (256MB) I'm thinking about getting a v2 now.
How I did it: http://thule.mine.nu/html/about.html
This pattern has repeated throughout Minecraft's release cycle. Though with Minecraft 1.0 it is no longer considered in "beta", each major version has brought incompatible changes. Mojang doesn't use semantic versioning, needless to say. Had a book been written around 1.2, it would have undoubtedly focused on the singleplayer/multiplayer split, and the steps needed for modders to develop SSP-only or SMP-compatible mods, but this distinction was blurred or eliminated in 1.3. 1.3 was mostly a dead zone for modding, only to come back in 1.4. With 1.4 we saw the introduction of new server implementations or administration mods, combining either analogous functionality or proper support for both leading modding frameworks, Forge and Bukkit (including MCPC+, BukkitForge, ForgeEssentials, etc.).
Modding toolkits come and go: about a mere year ago, you might be modding with ModLoader, ModLoaderMP, AudioMod. Or pure Minecraft Coder Pack (MCP), with no APIs. Or lesser-known custom APIs. Nowadays, Forge ModLoader has basically taken over ModLoader, and many modders have been moving to Forge for compatibility and other reasons. IndustrialCraft, BuildCraft, Mystcraft, Forestry.. all leaders in the Forge modding world. But there are still factions of modders sticking with Risugami ML, or even using raw jarmod edits like Better than Wolves. Not to mention - server-only "plugin" development using Bukkit is almost a completely separate community. You have the vanilla original CraftBukkit server implementation, then performance-focused forks like Spigot, or other forks with their own goals like SportBukkit, Libigot, or the mod-compatible MCPC+.. each with their own benefits. Fortunately most have similar plugin compatibility, but a few add new APIs, or otherwise change Minecraft behavior..
Bottom line, Minecraft modding is a hodgepodge of often-incompatible rapidly-changing frameworks, built on an unstable rapidly-changing foundation (which is obfuscated and has to be reverse-engineered each release, nonetheless). There have been advancements to streamline this problem, and it is getting better, but we're not out of the woods yet. Even tutorials you can find online for modding – such as on the Minecraft Forge wiki, are frequently outdated. A book would even be more so.
Nonetheless, I think you're right, it would be very nice if someone could pull it off, putting out an informative yet updated book on Minecraft modding. Maybe things will settle down and stabilize after the infamous Mojang modding/plugin API is released.
Do any of you guys experience a bottleneck on the RPi's 100Mbps nic?
Alternatively use composite video out. Raspberry Pis are cheap, so getting another Model B (or Model A) for HD video output isn't a big deal..
That said, there are alternatives to the Pi around if you require more power.
Pretty common setup, people do stuff like this quite often with their routers.
the pi is a just a tiny computer, the usual rules and best practices apply.
ffs, if you want, you can run a mail server on your _phone_ which has more raw computing power than a pi and similar power consumption.