Slashdot Mirror
Small Form Factor PCs
JoshuaBenuck writes "Make Projects: Small Form Factor PCs provides detailed step-by-step instructions on building a variety of small form factor systems, starting from the larger ones (about the size of a shoe box) and working its way down to the smallest (which is about the size of a pack of gum). It includes instructions on creating a digital audio jukebox, digital video recorder, wireless network range extender, home network gateway, network monitor, portable firewall, cheap Wi-Fi SSH client, and a Bluetooth LED sign." Read on for the rest of Joshua's review.
Make Projects: Small Form Factor PCs
author
Duane Wessels, Matthew Weaver
pages
232
publisher
rating
8
reviewer
Joshua Benuck
ISBN
summary
A detailed step-by-step instructions on building a variety of small form factor systems
First off, this is a PDF that, as far as I can tell, is only available from oreilly's website. Most of the projects in the book will require at least $300 dollars to complete.
If you who don't know why you would want to use a small form factor PC there is a good discussion of why you might want to consider using one in the introduction along with a list of some of the currently available small form factor PCs. You'll need to keep in mind that some of the systems mentioned would be more commonly referred to as embedded systems so the authors have expanded the definition of what 'small form factor PC' means. Not all of the systems mentioned are used in one of the projects in the book so if you get bored or are looking for another small system to play with, this may be a good resource.
The remaining chapters deal with projects that each use one of the systems mentioned in the introduction. The chapter headings show a picture of the finished product, a list of needed components, a bar showing the time it will take, and a rating of difficulty from 'easy' to 'difficult'. The bars and pictures provide a quick indication of what you are getting yourself into with one glaring exception; they do not tell you how much money you'll need to sink into the project. In order to find this information you'll need to go back to the introduction and read through the paragraph that tells you about the system used in the chapter.
This is followed by an overview of what is going to be built and which system was chosen for the implementation along with a description of its unique characteristics that made it a good fit for the project. A lot of emphasis is put on the power consumption of the various components. They even measure it at startup, shutdown, and during normal operations. This is used to make a couple of power and cooling design decisions.
If you're like me, you don't like when your systems makes a lot of noise (Especially ones that aren't supposed to look like they have a computer in them). This book gives a good overview on what to look for when building a system that you want to be as quiet as possible. They mention whether the system can get away with passive cooling (e.g. no fans) and they show some very non-conventional ways to reduce the noise production of a system (such as hanging a hard drive from wires within an enclosure).
The step-by-step instructions on assembling the hardware components of the systems include plenty of good quality pictures that should make it easy to follow along with the various projects. The pictures are about a third the width of the page which I feel is a good size. They are crisp, clear, and add to the discussion of the topic at hand.
If you are an experienced Linux or BSD user you'll probably be able to skim most of the step-by-step operating system installation instructions. If you are new to Linux and BSD the steps should help you find your way to project completion. Just don't expect the book to have all of the answers all of the time. I feel it is impossible for one book to contain the answers to all the questions that someone new to this area may have. That said, I think this book does an admirable job at giving you what you need to succeed.
Littered throughout the text are various warnings, other options, and lessons learned which I found to be valuable. Some of these include mistakes the authors made (such as using a WinTV-Go card instead of a higher model with a built-in MPEG decoder), using a CF Card Reader if you are unable to use NFS to transfer files to a system that uses a Compact Flash card, and numerous other practical tidbits that should serve to save you some frustration when trying to do the projects on your own.
You don't have to use the hardware platforms or components recommended in this book to gain benefit from its contents. I've used the instructions on setting up the Linux Infrared Remote Control (lirc) project to help with an Iguanaworks USB Infrared Transceiver (a device that sends and receives infrared signals) while the authors used an Irman receiver. The MythTV box I've setup uses Ubuntu Linux instead of Gentoo Linux and uses a spare system instead of the Shuttle XPC used in the book. I found the instructions in the book to be indispensable as I worked through this.
I've never done a case mod before, but I like the idea of being able to hide away a computer in something that looks like a decoration. There is a detailed explanation of how the authors used an old antique radio as a cover for their digital jukebox. I enjoyed the discussion of the various places they could put the power supply, infrared receiver, and other design considerations. It really gave me a feel for what types of questions I'll need to answer as I do a case mod myself.
That leads me to what I think is the biggest strength of this book. It is the very conversational way in which the authors tell you what they did, why they did it, and what they could have done. Along the way they provide links for further information, and search terms that can help you learn more about the topic at hand. The book is packed with information that is up-to-date, accurate, valuable, and easy-to-read.
That said, some of the information will lose value over time. For example, the specific gumstix computer that was used does not appear to be available anymore. This is probably a good thing since the authors had to make some adjustments to get the 200 Mhz Bluetooth enabled version to work. I mention it only to point out that the information on the specific systems and the other instructions will lose value over time. It is impossible to future proof a work likes this.
The projects in this book opened my mind to a whole new world of what is possible with small systems. I haven't had a chance to purchase of the specific systems mentioned, but the information on setting up the various software and hardware components has already proven the book's worth. I look forward to one day getting my hands on the systems mentioned so I can gain the full advantage that small form factors provide. So if you don't mind spending $300+ to play with some a small form factor PC or you love to tinker with networking, or multimedia applications then you might want to give this book a try. I certainly don't regret it.
Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
First off, this is a PDF that, as far as I can tell, is only available from oreilly's website. Most of the projects in the book will require at least $300 dollars to complete.
If you who don't know why you would want to use a small form factor PC there is a good discussion of why you might want to consider using one in the introduction along with a list of some of the currently available small form factor PCs. You'll need to keep in mind that some of the systems mentioned would be more commonly referred to as embedded systems so the authors have expanded the definition of what 'small form factor PC' means. Not all of the systems mentioned are used in one of the projects in the book so if you get bored or are looking for another small system to play with, this may be a good resource.
The remaining chapters deal with projects that each use one of the systems mentioned in the introduction. The chapter headings show a picture of the finished product, a list of needed components, a bar showing the time it will take, and a rating of difficulty from 'easy' to 'difficult'. The bars and pictures provide a quick indication of what you are getting yourself into with one glaring exception; they do not tell you how much money you'll need to sink into the project. In order to find this information you'll need to go back to the introduction and read through the paragraph that tells you about the system used in the chapter.
This is followed by an overview of what is going to be built and which system was chosen for the implementation along with a description of its unique characteristics that made it a good fit for the project. A lot of emphasis is put on the power consumption of the various components. They even measure it at startup, shutdown, and during normal operations. This is used to make a couple of power and cooling design decisions.
If you're like me, you don't like when your systems makes a lot of noise (Especially ones that aren't supposed to look like they have a computer in them). This book gives a good overview on what to look for when building a system that you want to be as quiet as possible. They mention whether the system can get away with passive cooling (e.g. no fans) and they show some very non-conventional ways to reduce the noise production of a system (such as hanging a hard drive from wires within an enclosure).
The step-by-step instructions on assembling the hardware components of the systems include plenty of good quality pictures that should make it easy to follow along with the various projects. The pictures are about a third the width of the page which I feel is a good size. They are crisp, clear, and add to the discussion of the topic at hand.
If you are an experienced Linux or BSD user you'll probably be able to skim most of the step-by-step operating system installation instructions. If you are new to Linux and BSD the steps should help you find your way to project completion. Just don't expect the book to have all of the answers all of the time. I feel it is impossible for one book to contain the answers to all the questions that someone new to this area may have. That said, I think this book does an admirable job at giving you what you need to succeed.
Littered throughout the text are various warnings, other options, and lessons learned which I found to be valuable. Some of these include mistakes the authors made (such as using a WinTV-Go card instead of a higher model with a built-in MPEG decoder), using a CF Card Reader if you are unable to use NFS to transfer files to a system that uses a Compact Flash card, and numerous other practical tidbits that should serve to save you some frustration when trying to do the projects on your own.
You don't have to use the hardware platforms or components recommended in this book to gain benefit from its contents. I've used the instructions on setting up the Linux Infrared Remote Control (lirc) project to help with an Iguanaworks USB Infrared Transceiver (a device that sends and receives infrared signals) while the authors used an Irman receiver. The MythTV box I've setup uses Ubuntu Linux instead of Gentoo Linux and uses a spare system instead of the Shuttle XPC used in the book. I found the instructions in the book to be indispensable as I worked through this.
I've never done a case mod before, but I like the idea of being able to hide away a computer in something that looks like a decoration. There is a detailed explanation of how the authors used an old antique radio as a cover for their digital jukebox. I enjoyed the discussion of the various places they could put the power supply, infrared receiver, and other design considerations. It really gave me a feel for what types of questions I'll need to answer as I do a case mod myself.
That leads me to what I think is the biggest strength of this book. It is the very conversational way in which the authors tell you what they did, why they did it, and what they could have done. Along the way they provide links for further information, and search terms that can help you learn more about the topic at hand. The book is packed with information that is up-to-date, accurate, valuable, and easy-to-read.
That said, some of the information will lose value over time. For example, the specific gumstix computer that was used does not appear to be available anymore. This is probably a good thing since the authors had to make some adjustments to get the 200 Mhz Bluetooth enabled version to work. I mention it only to point out that the information on the specific systems and the other instructions will lose value over time. It is impossible to future proof a work likes this.
The projects in this book opened my mind to a whole new world of what is possible with small systems. I haven't had a chance to purchase of the specific systems mentioned, but the information on setting up the various software and hardware components has already proven the book's worth. I look forward to one day getting my hands on the systems mentioned so I can gain the full advantage that small form factors provide. So if you don't mind spending $300+ to play with some a small form factor PC or you love to tinker with networking, or multimedia applications then you might want to give this book a try. I certainly don't regret it.
Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
go get a cheapo mac mini, it even comes pre-installed with BSD
Just get a Mac mini... BSD included!
but how can i turn my new iPod shuffle into a comp? a pack of gum form factor is still too big for my needs
mini ITX form factor Mobos cost 2x what they should. Their cabinets cost 3x what they should. I want a mini ITX computer, with as small a fan as possible to be a NAS. But the whole project is absurdly expensive compared to what it would cost for a big ugly mATX. So that's what I'll be forced to do - build yet another intrusive grey box and save myself $150.
And while we're at it, why do so many mini ITX cabinets look like early '70's stereo equipment? Just give me a cheap box that's as blank as possible and mounts a CD drive horizontally. That means the case on;y has to be 6" wide, not 11".
Sounds like a good resource for someone who was planning on building an embedded/SFF PC in the immediate future.
Not sure if it would be of any benefit to the more casual reader, or one on a longer time horizon. It sounds like they make specific hardware recommendations, which would be invaluable to someone building a system today, is probably just going to be a source of frustration in twelve months, when none of the stuff they recommend will be available anymore.
Their choice to produce it as an ebook is probably a smart one, for this reason. They would barely have time to get it out the door in paper format, before the recommendations were less than cutting-edge; by the time it made its way to most readers, they'd have to hunt on eBay to get the particular parts used in the articles.
I can't tell you the number of times I've read various HOWTOs and other 'How to make a...' articles, only to meet frustration when some small key part is out of production, and the currently-produced alternative creates problems that aren't addressed. That's the limitation of HOWTOs: they only tell you how to go down one particular path, not how to survive in the proverbial woods. They're a map, not a survival guide.
So I guess if you're in the market for a 'map,' getting one that's as new as possible is probably a smart idea, and one that's been written and is produced straight to PDF, without months of waiting to be printed and sold, is probably the best thing going.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Or my interest in it, anyway. Once upon a time, PCs were huge, but had lots of wasted space. You could put them into a smaller box, or make them really tiny once motherboards were all integrated and you could do the whole thing without PCI cards sticking out. I used several SFF Compaq Deskpros over the years and they've all been great--fast, small, cheap, and bulletproof. Then along come tiny ATX boards and neat machines can be made even smaller.
Then along comes the Mac Mini and in the last two years I've seen lots of "We took a Mac Mini and stuck it in something bigger" and I'm like, what's the point? I've got two Minis and they're great. (Though I'll buy a Mac Pro next time they're revved because I need a little more juice (mine are G4s) and a lot more disk than these little guys can hold.) I also plan to play around with a PC mini clone I saw somewhere, or maybe one of these little guys that Cringley recently had some fun with.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
I have bad eyesight (-13 diopters) and it's hard for me to read long documents on the computer but I have no trouble printing them out and reading them. Does this $15.99 PDF have DRM protection against printing? I've run into that once or twice and it's a pain for me :(
All I want in the world is basically a rack-sized iPod. A convenient screen, a cute interface, and a 3.5" HDD with a ethernet jack for transferring songs. Does that exist yet? I've seen all sorts of wired and wireless models that require a 250W file server running in another room. I just want an mp3 player with a screen you can see from across the room and a remote. Is that too much to ask?
They run XNU (perhaps known to you as Darwin or MacOS X) which has exactly as much relationship to BSD as a chevy does to a ford - they use similar interfaces and are derived from the same original innovations.
One of the many contradictions inherent in the Apple Religion is that BSD is bad, but Mac OSX is BSD in all ways that matter, and Mac OSX is good. Go read the wikipedia article if you want to get past the religious dogma.
In reality MacOS is not BSD (BSD is tighter, faster, and uglier). It's the latest version of XNU, and XNU probably has no more BSD code in it than Solaris, linux or Windows does.
PS: I use a mac, so the faithful need not crucify me for these comments. I'm sure simple flogging will do.
I own two Shuttle boxes and the XPC is the best computer I ever owned. They're extremely easy to assemble, actually fun to build, and I've never had a problem with one. A pair of them stacked are smaller than most single towers. I wish they could handle 2 gig memory chips but that's my biggest complaint. Both have firewire connections and frontside USB and sound. My 3200 has a frontside mini firewire plug but my XPC has a fullsize frontside firewire and both have full size backside plugs. I strongly recommend them. The only machine I'd consider for a living room multimedia machine. They even look good.
I want to flip open my satch and have a flexible keyboard and monitor with WIFI for surfing the web, ssh, and reading email (which for me is ssh since I read in PINE). Some way to put this into a satchel and still be able to use it as a bag would rock. I still want to carry around my sketch book and pens/pencils in the cafe.
The hard part seems to be the monitor. How to keep it safe and light weight.
Power is another problem.
Here's a nice video of how to build a Shuttle XPC.
http://www.my-pc-help.com/video/v10016.htm
Mike @ The Geek Pub. Let's Make Stuff!
The cheapest Mac Mini is $600.
The most expensive Mac Mini without monitor is $1600.
Cheapo, huh? You could build three utility PC's $600.
- It's not the Macs I hate. It's Digg users. -
I was looking at the gumstix line yesterday. They have the basic MB & an audio daughter card. Since the daughter card also has pinouts for LCD displays, I was considering putting together a wall mount box for remote connection to the MP3 server. But totalling it up, I couldn't see spending $300+ in addition to however long it took me to hook up the display & create a mounting case - for that I can get a junk laptop & do more.
ok, you know how people build MAME cabinets?
Ok, you know how there are VST software synths, many of which emulate real hardware, and do a great job of it?
ok... merge these ideas...
make tiny boxes the size of a TB303 or so, with MIDI knobs and buttons mounted on the top with a tiny PC running only a dedicated VST on the inside...
I imagine you could design a box that would run several different VSTs, selectable from the outside...
Add a 3" LCD screen, and kickass.
ok... someone make this into a DIY project so I can build one. yeah, i'm that lazy.
music - http://www.subatomicglue.com
Once you get used to their good looks you'll understand that other kinds of pcs are better for practically all kinds of tasks. Disclaimer: this message was submitted using SFF PC.
At least, not when you are "on the go", use the "virtual display goggles" I've seen on occasion. Expensive, perhaps, but will fit in your "satchel" and be relatively protected.
A goal is a dream with a deadline
Doesn't Windows have some BSD code in some of the networking backends? I seem to remember there was a big stink about that here on Slashdot when the Win2000 source code got leaked.
I've upped my standards, so up yours.
I just built a machine for a gift this last Christmas, and I used the Apevia Q-Pack case. I know the measurements were given on NewEgg, but the case just seemed go big when I actually took it out of the box. One of my ideas had been that it would be possible to push the machine back on the desk and park the mousepad in front of it, but when I swapped out the old computer it was replacing (ancient HP minitower running Win98) I found the Apevia case to be exactly the same depth as the taller, but much narrower, machine it was replacing.
I was expecting the Q-Pack to be a cube in terms of measurements. But due to its wider dimensions with "normal" depth, things seem more crowded than ever on the desk now.
Why wouldn't you just buy one of these Stream Box Core for $99?
The TCP/IP stack was (still is?) BSD code. They acknowledge it, however. No stink to be had.
Not in Vista! Rewritten to have brand new bugs!
Define BSD. Is it the kernel, the POSIX API, the userspace tools, or some combination? Is it FreeBSD, NetBSD, OpenBSD, 4.4BSD, etc.? I would say that the POSIX API and the userspace tools are the essence of BSD. OS X includes those, therefore I would argue that OS X does include BSD.
47% of all statistics are made up on the spot.
I don't know about current versions (perhaps someone else will enlighten us?) but years ago I ran the GNU version of the unix utility "strings" on some of the executables in a win98 install, and found BSD code in the ftp client.
/windows_partition -type f -exec strings {} \; | grep -i regent ...might do the trick.
If you are on a dual-boot system, mount your windows partition and do "strings" on the files, look for something obvious like "regents"...
find
Well, here comes your flogging. XNU == BSD kernel on top of Mach. Mach is doing practically nothing in Apple's implementation, and basically acts like a HAL. The benefit of using Mach is that someone else already had written it. The drawback is that it is a crap-ass microkernel and is basically only good for, well, what Apple is using it for.
The entire BSD userland is available on OSX. So I'd say that's pretty much BSD.
If you don't install the BSD userland, you're still using the BSD kernel on top of Mach. Has Apple tweaked the living hell out of it? Yes, that's why it's called Darwin. It's still based on BSD and bears every resemblance. The fact that it also has the NeXT stuff (Objective C runtime and the various libraries) and the other new Apple APIs on top of it doesn't change the fact that it's also BSD. It does however make things potentially a lot less reliable. My own (anecdotal) experience with it suggests that in fact any mainstream *BSD is a hell of a lot more stable than OSX.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
FreeBSD is the primary reference codebase for the BSD portion of the XNU kernel. It's fair to say that there is more FreeBSD-derived code in MacOS than in Windows, Solaris, or Linux.
There are 0x40000000 types of people: those who understand 32-bit IEEE 754 floating point, and those who don't.
I'd argue that an OS is BSD if it's a direct descendant of the Berkeley Systems Distribution. I don't have much truck with Humpty Dumpty definitions, personally.
;)
Are you sure that we agree on what the definition of "is" is?
By your argument, Cheslov is actually the dead guy he got his replacement heart from. Or is he still Cheslov, since your nebulously defined word "essence" implies air and he just got a heart, not a full heart-lung job? I'm not buying it. Mac OSX is not BSD. Neither is Solaris, and neither is Windows 98se. All three contain BSD code but that's the extent of it.
I bought a book on overclocking, which at the time was quite useful. I would have written a similarly enthusiastic review. Now that it is 4 years old, the overclocking book is an amusing historical artifact for the average, power-hungry geek.
:-) I am now looking for articles on underclocking for a low heat, low-noise PC - HTPC for me. The biggest challenge is, it has to play modern games like Q4 and HL2. So it is a bit of a hybrid HTPC.
I've aged as well.
"No matter where you go, there you are." -- Buckaroo Banzai
Can anyone recommend a MiniITX board that has a graphic chip that is fully supported by XGL? With a DVI port?
Give it a couple of days.
---- Booth was a patriot ----
My pc had a trojan and the file was stolen.
Just beacuse its 'out' doent mean I did it.
---- Booth was a patriot ----
I only balk when people equate XNU with BSD. Share the love with Carnegie-Mellon's mach kernel, I say.
DEC's OSF/1 unix was also a choreographed train-wreck of mach and BSD; a pretty nice OS, in some ways quite similar to XNU.
And wasn't AIX's microkernel derived from mach as well?
> Doesn't Windows have some BSD code in some of the networking backends?
No, it was based off SysV STREAMS, and it took til Winsock2 to add a compatibility interface. It has BSD header files, and FTP and tracert are straight ports of the BSD versions, and those all have the BSD copyright in them.
If only Windows HAD used BSD networking code, it might not have sucked so much.
Saying something contains your favorite parts of something_else and therefore is something_else is sounds highly illogical to me.
You can run Linux on the Mach microkernel (or you used to be able to anyway, dunno about now) but that doesn't make it not-Linux.
XNU is just a BSD kernel on top of Mach. It's still BSD.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Convert the book to a wiki.
I've already bought the book. What if I now want to upload my own storyline as well as pictures of my project to a community maintaining an on-line version of same book? A wiki would allow anyone who has bought the book (thus they have an ID/PWD for accessing the PDF originally) to use the same login to access an online wiki based version of the book. You won't lose any revenue from account sharing, since the same person sharing their login could just as easily share the PDF file. *But*, by putting it into an access controlled wiki for those of us who have bought the book, you give us the opportunity to share our stories... to make major and minor changes as necessary as we go through the different howtos and find that things have changed slightly, components have uprev'd, etc. And, if you managed the wiki properly you might even maintain a revenue stream on the publication long after it has originally published, not because techies will want to buy an old book, but because when they do they know they'll also get access to the latest updates in the "community of users" participating in the wiki. You might be able to harvest the best that the wiki has to offer and spin that back into a PDF version, then spin that back into a wiki again. And of course all this community activity on an O'Reilly hosted site means traffic, eyeballs, impressions, etc. etc....
I know this won't work for every book and every topic. But in the case of this one it seems like a no brainer to try since the book is really just a short intro followed by a bunch of essentially standalone howto chapters. Perfect for a wiki IMO...
That would be XNU's Paradox?
If it fits, wear it.
And a zebra's a horse. I mean, pretty much.
Build a Linux box with mt-daapd to stick the tunes on. Use a VIA EDEN motherboard, it'll run on about 6W and needs no fans, and Linux has open source drivers for all the hardware.
Plug in a Squeezebox or Roku Soundbridge to be your UI. They should find the server automatically, as should any iTunes system on the same network.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
No, more like a zebra mounting a horse is still a zebra... mounting a horse. The zebra is still a zebra and the horse is still a horse.
And how exactly are they going to make money? Selling access to a wiki page?
Everybody Lies. But it doesn't matter since nobody listens.
If you have wifi and a computer that contains your music and is allways on then try one of these. They look great, sound great and hell, you can even program the things.
I've got two now and can't live without them.
Squeeze Box 3
Next time, please log in, so I can friend you :D
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Sure. Have registered, paid user accounts, a small staff of professional editors, and give people service credits for significant, useful contributions. Restrict posting edits to main content (but not "Talk" pages) to the paid pros (who each also periodically review the Talk pages in their area) and maybe "trusted" users with good contribution history. Why not?
You could even use a wiki-like editing and viewing system with a format that can be converted on the fly to a book-format PDF for downloading and nice-looking printing.
My (slimserver) media server is based on a Via Epia 10k and housed in an Antec Aria case. On paper, the Epia is impressive; and the Aria is a thing of beauty -- that is to say, it has a calm design and a nice silent 120mm PSU fan for main ventilation. But I have learned that smallness can work against you.
The Epia 10k came with a choleric little 40mm fan; the first thing I did (ordered it along with the board, actually) was to replace the heat sink and mount a slower 80mm fan -- bigger fans provide better cooling at lower noise levels. I will need to further replace this setup with a 120mm intake fan and some crafty airflow management, because it still makes too much of a swooshing noise as it sits here beside my desk (small home, ugh).
So I have a hard time understanding why you might want a smallest-possible fan (again, unless you have severe size constrains rather than a desire for inconspicuousness). Also, most hard disks (of any useful size) generate a respectable amount of heat. You can't stick a number of them in a box and not ventilate it properly.
My point? My next system will more likely be cased in an Antec P-180. It's rather large, but then it is both very stylish and very plain; and the size affords the use of so many more noise-reducing methods to make it much less conspicuous than my present setup.
"Good news, everyone!"
"You know, some people do enjoy building things and getting them to work on their own."
Somebody thoughtfully provided a site for them
"Not everything is about having something, the journey to get it can be very important too."
I get excited driving to the pharmacy to pickup my viagra.
Personally I don't need a conference room (Though it'd be nice) so I can get a FXO SIP gateway for my big-ass Mac, but if I were doing a build for a customer I'd want to use Linux and hardware I could slap a digium card into.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
"At $150+ I'd hope so at any rate. But do you see what I mean? a small expanable computer shouldn't command such a premium."
Gosh darn economic laws. Why are they always spoiling my fun? Everything should be at commodity prices, I tell you. Commodity!
Yes
It's the information that is valuable not the delivery method.
"Call us when the New age is old enough to drink" Beck
Huh? Solaris is SysV. I remember when it came out, and the noise of gnashing teeth rose up to disturb heaven. Prior to Solaris (aka SunOS 5) all the Sun fan-boys I knew were die-hard BSD bigots, and spoke of SysV with great disdain - when Sun switched over they were in the same position as mac users who loudly trumpeted the inferiority of intel hardware.
If the chart you linked shows OS-X as "a direct descendant" of BSD, it also shows linux as a "direct descendant" of minix. The author of minix has publically stated that linux does not have any code from minix in it. I admire the dedication of the person who created the chart, but I don't think it is relevant to the discussion of whether MacOSX = BSD. It doesn't even distinguish between kernels and utility suites, I don't think the author intends it to be a canonical reference.
...you're on slashdot trying to make a point. I shall counter your extension with one of my own!
The offspring of a zebra and a horse is not a horse
Something derived from two other things, containing elements of both, is not merely one of those things.
I don't know why people are so vehement that the mach part of XNU doesn't count... but having just found the kernelthread article where Apple zealots flame the hell out of Amit Singh for saying Mac OSX isn't unix (horrors! the sky is falling!) I do believe I will give up now.
Never mind.
Similarly, when Sun switched to SysV-derived Solaris the boot disk you had to use to install the system booted BSD-derived SunOS. I thought it was very funny at the time that it needed to use BSD to install SysV.
I think the DEC VAX 8800 had a PDP-11 inside it for a boot device, probably running TSX (but that was a long time ago, I forget the details). It was funny to open up the giant blue cabinet (we called it "The IBM" because it was big and blue, our DEC sales rep was not amused) and see the old school PDP hiding inside.
> such as hanging a hard drive from wires within an enclosure
That's what's wrong with all the plastic computer cases out there. The hard drive produces heat, and good thermal conduction can reduce the amount of fans needed. The above statement is a good way to replace a noisy hard drive with a noisy fan, or simply a good way to significantly shorten the lifespan of your hard drive.
Dekker Dreyer
The big clue about the unix origins was the hosts file. I mean really, it's found at ...\etc\hosts after all.
Build ?
I read the description, and it sounds like this is a book about "Buy" not "Build"
Time travel is possible. We are quickly heading for 1984.
I think Microsoft rewrote the network stack for Vista - so this it might be or it might be not BSD code
Someone has seen such beast?
There are many guides to create your Make Project available for free. So why bother to buy the book. For example: here are guides to "create a [homemade portable] digital audio jukebox" and here is a list of tutorials explaining how to build a "wireless network range extender".
For $15, I'd rather buy a dead tree. I know I can print it, but my time is more valuable.
No, I will not work for your startup