How to roll your own Mac for under $240(uselessninjas.com)
uselessninjas.com
How to roll your own Mac for under $240
http://www.uselessninjas.com/guides/msiwindosx/
36 comments
You are misinformed. See this fantastic diagram: http://i33.tinypic.com/2yor21y.png
Yeah, but with software, there really is no "original" to steal. They can make new copies and ship them to the store for like $0.50 tops.
The real value of software is the information, the compiled code that makes it do something valuable. You're not paying your share towards development costs that make that happen. So you're robbing the company of the money you would pay for the software.
With software, the idea of theft only being taking the physical product is stupid because the physical aspect is practically worthless. Some software isn't even distributed through physical means at all.
The real value of software is the information, the compiled code that makes it do something valuable. You're not paying your share towards development costs that make that happen. So you're robbing the company of the money you would pay for the software.
With software, the idea of theft only being taking the physical product is stupid because the physical aspect is practically worthless. Some software isn't even distributed through physical means at all.
[deleted]
There's always jury nullification.
Why is this being voted up? He advocates downloading Leopard from the pirate bay. The only 'Mac' thing about this computer is the OS and he recommends stealing it.
Why would that stop it being voted up? Things don't stop being interesting just because they are illegal.
Also, he advocates stealing it or buying it.
Also, he advocates stealing it or buying it.
The stuff you need to know to hack osx on your own isn't something you can read on a forum randomly. Buying -> hacking isn't an option for many people.
Where do you find that knowledge?
If you actually want to do the hacking on your own:
Learn x86 or x86_64 (be prepared for Snow Leopard) asm in depth for the kernel. Lots of C/IOKit knowledge for writing your own kext's (drivers for osx). Examine memory dumps and to figure out what gets loaded when (not to mention how. There's a few cryptographically signed things that had to be dumped; Dont Steal Mac OS X.kext is a good example). Look at tons of device and vendor id's and find the corresponding plists within apple-provided kext's. Find where and what to modify in them.
Talk to people on IRC (there's some very talented people around there still, and even more talented folks that have quit the scene already). If you can, find old forum posts from osx86project - or concretesurf/win2osx (I'm talking stuff 2.5-3 years old, before they were big and worth indexing)
In short: Explore the system at as low of a level as possible. Don't leave a stone unturned.
If you just want to copy others work, you can stick with the "Talk to people on IRC.." part and you should manage, assuming you have an idea of what you're doing.
All that being said, I'd recommending spending the time working on something more worthwhile.
Talk to people on IRC (there's some very talented people around there still, and even more talented folks that have quit the scene already). If you can, find old forum posts from osx86project - or concretesurf/win2osx (I'm talking stuff 2.5-3 years old, before they were big and worth indexing)
In short: Explore the system at as low of a level as possible. Don't leave a stone unturned.
If you just want to copy others work, you can stick with the "Talk to people on IRC.." part and you should manage, assuming you have an idea of what you're doing.
All that being said, I'd recommending spending the time working on something more worthwhile.
Oh no... not... software piracy!
Also, stealing/not-stealing blah blah blah.
Also, stealing/not-stealing blah blah blah.
Consider HN is a hacker + entrepreneurial site you could see why people would not welcome Reddit/Digg support for piracy.
Being a hacker and a sometime entrepreneur doesn't mean that I have to think copyright makes sense. These are quite orthogonal to each other, and I would lose respect for someone if I found that they'd believed copyright invalid until they wanted to make a living off of it.
...I'm unclear why you are conflating support for piracy and Digg/Reddit.
I understand the attitudes of those so grossly offended by copyright and DMCA violations. But suggesting copyright infringement doesn't automatically disqualify an article from Hacker News.
I understand the attitudes of those so grossly offended by copyright and DMCA violations. But suggesting copyright infringement doesn't automatically disqualify an article from Hacker News.
Voting up does not necessarily mean you agree with the article. It means that the subject is interesting and you would like more people to see it and share their thoughts. Apple employees read HN and now they are aware of it and can take the necessary steps if they want to stop this (maybe by hiring the guy/gal).
Does Xcode run on this? Does the iPhone emulator work? Can you do iPhone development with this setup?
Yes. I have a friend who has shipped an iPhone game developed on a hackintosh.
That said, I've personally found them to be problematic over time. We're a 6-person Mac-based game developer, and we picked up a Psystar hackintosh out of curiosity. We had an intern work on it for awhile, but it had some weird quirks. The biggest problem is updating must be done manually and carefully. The longer you have it the more work you're creating for yourself, if you want to keep current, which is pretty much opposite the goal of using a Mac (less work/maintenance over time).
That said, I've personally found them to be problematic over time. We're a 6-person Mac-based game developer, and we picked up a Psystar hackintosh out of curiosity. We had an intern work on it for awhile, but it had some weird quirks. The biggest problem is updating must be done manually and carefully. The longer you have it the more work you're creating for yourself, if you want to keep current, which is pretty much opposite the goal of using a Mac (less work/maintenance over time).
Used genuine Macs are available if you want cheap (or cheaper, at least).
I'm not sure how this is better than dual-booting on your current machine, or using an old pc.
Am I missing something?
Yeah well, driver headaches if you don't pick your hardware carefully. Nobody will release OSX drivers & you don't want to depend on third party drivers. They all suck.
I actually hit this hard a few months ago while trying to turn my laptop into a hackintosh. It would only boot once every 3 tries. And ultimately there's nothing special about the OS. I missed my apt & kde4
I actually hit this hard a few months ago while trying to turn my laptop into a hackintosh. It would only boot once every 3 tries. And ultimately there's nothing special about the OS. I missed my apt & kde4
ultimately there's nothing special about the OS
I would dispute that... except that I suspect that it might be much more true if you're foolish enough to go the Hackintosh route.
The whole point of the Mac OS is that everybody is using more or less the same thing: similar OS, similar software, similar hardware, similar drivers. That makes it fairly easy to adopt tips and techniques from the community, or to Google for applicable advice, and it makes the user experience smoother and simpler. Once you throw away much of the ease of installation and maintenance, the consistency, and the stability the Mac OS is not that much more than Unix with pretty windows and a stricter set of UI guidelines -- and there are plenty of ways to prettify your Linux windows!
You do get access to well-designed, closed-source, Mac-only apps. (The open source Mac apps can generally be cross-compiled for Linux, or more likely vice versa.) But if you're too cheap to buy actual Mac hardware you're less likely to care about the power to pay for nicely designed Mac apps. Especially when some of those apps might exhibit mysterious bugs on your hackintosh hardware.
Just spend those hours you'd waste trying to maintain a hackintosh learning more about Linux. It's a better use of your time. Or buy a real Mac like everybody else.
I would dispute that... except that I suspect that it might be much more true if you're foolish enough to go the Hackintosh route.
The whole point of the Mac OS is that everybody is using more or less the same thing: similar OS, similar software, similar hardware, similar drivers. That makes it fairly easy to adopt tips and techniques from the community, or to Google for applicable advice, and it makes the user experience smoother and simpler. Once you throw away much of the ease of installation and maintenance, the consistency, and the stability the Mac OS is not that much more than Unix with pretty windows and a stricter set of UI guidelines -- and there are plenty of ways to prettify your Linux windows!
You do get access to well-designed, closed-source, Mac-only apps. (The open source Mac apps can generally be cross-compiled for Linux, or more likely vice versa.) But if you're too cheap to buy actual Mac hardware you're less likely to care about the power to pay for nicely designed Mac apps. Especially when some of those apps might exhibit mysterious bugs on your hackintosh hardware.
Just spend those hours you'd waste trying to maintain a hackintosh learning more about Linux. It's a better use of your time. Or buy a real Mac like everybody else.
Once you throw away much of the ease of installation and maintenance, the consistency, and the stability the Mac OS is not that much more than Unix with...
Oh, I don't know anything about Unix, but you might want to keep a few of those if you want to keep up with Ubuntu.
You do get access to well-designed, closed-source, Mac-only apps.
If I used windows, I'd also get the privilege of paying for lots of well-designed closed-source windows-only apps.
Oh, I don't know anything about Unix, but you might want to keep a few of those if you want to keep up with Ubuntu.
You do get access to well-designed, closed-source, Mac-only apps.
If I used windows, I'd also get the privilege of paying for lots of well-designed closed-source windows-only apps.
apt and KDE 4 both run on Mac OS X.
Important caveat at the end:
"Also, doing the non-program updates (system updates) seems to screw it up. I'm not sure why and I am finding a fix but for now just update iTunes and the like."
"Also, doing the non-program updates (system updates) seems to screw it up. I'm not sure why and I am finding a fix but for now just update iTunes and the like."
Factually inaccurate. The computer described is not a Mac.
The joy of getting things done..
it's a copyright violation to use OS X on any non-Apple manufactured computer, so this isn't a great idea. nice cheap computer though, and it was interesting to read the steps the guy had to go through. I don't think HN advocates copyright violations, do they?
If you buy a copy of OS X it's probably not copyright violation.
At worst it is breach of contract (possibly attracting actual damages of as little as $0, as you bought the software), but that depends on your legal jurisdiction.
Not that I advocate installing OS X at all. It seems churlish to insist on using something the creator doesn't want you too when there are free alternatives that benefit from a large user base.
At worst it is breach of contract (possibly attracting actual damages of as little as $0, as you bought the software), but that depends on your legal jurisdiction.
Not that I advocate installing OS X at all. It seems churlish to insist on using something the creator doesn't want you too when there are free alternatives that benefit from a large user base.
In theory, since you cannot buy this hacked copy of OS X it might be a copyright violation since you can't have a license for that copy.
It is possible, however, to buy a legitimate OS X and perform the same patches to get the install image they are using, in which case no copyright violation occurs. Installing shouldn't even be an EULA violation if you're doing it on an "Apple labeled" computer.. so just get an Apple sticker and label it.
It is possible, however, to buy a legitimate OS X and perform the same patches to get the install image they are using, in which case no copyright violation occurs. Installing shouldn't even be an EULA violation if you're doing it on an "Apple labeled" computer.. so just get an Apple sticker and label it.
I dont think sticking a sticker of an apple sticker on it makes it "Apple labeled" anymore then a tag saying "rolex" would make a fake rolex from the street a real rolex.
That's still a point of legal contention.
In any case, it's perfectly legal for you to buy a cheap watch and put a Rolex sticker on it as long as you don't sell it on as a "genuine" Rolex.
Something can be "Apple labeled" but not a genuine Apple product. "Apple manufactured" would have made more sense.
In any case, it's perfectly legal for you to buy a cheap watch and put a Rolex sticker on it as long as you don't sell it on as a "genuine" Rolex.
Something can be "Apple labeled" but not a genuine Apple product. "Apple manufactured" would have made more sense.
But of course Apple doesn't manufacture their own machines. They design them and label them, hence the odd wording in the EULA.
Just go the mall early with a brick, you know, when the walkers are getting their exercise. Throw the brick through the window of the Apple store and steal a mini. Its a better machine and Apple probably won't mind since they need to flush the inventory before next weeks announcements. Why, you are probably doing them a favor since they can write off the retail price as a loss from theft instead of flushing it at a reduced price. No one gets hurt, same as the original article.
(Ok, the mini isn't better if you want the two 3.5" SATA bays, in that case steal it the way the author documents.)
[Downvoted? At least I amused myself. Perhaps I should have added a smiley somewhere.]