Automate download, install, config of IE-only VM's with VirtualBox (Linux/OSX)
github.com
github.com
xdissent[1], the author of this package, is a HN user, but he has negative karma because his fourth comment was snarky and got heavily downvoted. Even though he's aware of the ban he clings to this handle and continues to post messages seen by almost no one (he posted twice on this comment page [2,3]). The rest of the messages eversince the incident have been fine (enable "showdead" in the user control pannel if you want to read them).
Since he seems attached to the handle, it would be nice if he could be upvoted back to the positive side so that he can once again participate.
He's got three upvotable posts in history (before the ban). His karma is currently at -32. This means that he needs 11 brave souls to break even. You know what to do :).
1. http://news.ycombinator.com/user?id=xdissent, comments: http://news.ycombinator.com/threads?id=xdissent
2. http://news.ycombinator.com/item?id=2955430
3. http://news.ycombinator.com/item?id=2955411
.
Edit: 58 minutes later: -10. Thanks to the upvoters.
I didn't even know karma worked this way on HN. Quite ridiculous, IMHO, to completely hide someone if their karma runs too low. Especially if it can happen by unfortunate accident and ends up hiding a positive contributor completely from view--basically means the system is broken.
This case is unfortunate, though, but I guess that's why the showdead option exists.
I don't know if a negative karma turns on an irreversible ban flag, or if going back to positive will alleviate the ban. If not, I'll write a mail to pg.
You may want to repost your earlier answers in this thread.
2011/9/3 Paul Graham <pg@ycombinator.com>
>
> fixed
>
> 2011/9/3 Pierre-Yves Gérardy <pygy79@gmail.com>:
> > Hello,
> > would it be possible to unban xdissent?
> > See http://news.ycombinator.com/item?id=2955023 for the details.
> > Kind regards,
> > -- Pierre-YvesBad trend in the open-source community. Please don't ask your users to install stuff this way. Not that you can't be trusted, it leads to people dropping their guard.
Projects like this are obviously targeted towards developers as they're hosted on github. If you really want to check out what the script is doing, just look at the file. Or better yet, clone the repo and use it/install however you want.
Unequivocally, it is dangerous to run random pieces of code from the internet, it just seems odd to me that if this same code was in a nice packaged install wizard nobody would say anything about it.
jargonjargon [*&*@![]2\3
if [[jargon -f "words!"]]
jargon # jargon jargon
jargon /&$_)(82
fi # jargon the jargon
jar(){
gon # yay pictures! #
∑´∞§∞¶•ø¨ˆ∆£˜¡–ª¢ø•ª¶π™˜£º¥µ # <(^.^)> #
˚∆∂¥•¡º™ª•¶ƒ˙¨ˆ # #
˙π¡˜ø£•¶√≠˚•™µº–£¨≤ # <= ˚∆˚! but it works #
}
and just go to the next step.edit: how about iOS? There have been news entries about them sending data where they shouldn't - that's a curated host. iOS is a lot more sandboxed, but that doesn't make the danger nonexistent.
When people are delivering software that isn't in the official repository, downloading a script and running it is no less secure than the alternatives.
And what will be the right way to do it? The way people don't drop their guard? `./configure && make && sudo make install`? Or `sudo apt-get install`? How are any of these or many other options seemingly better than this?
Rough VM size estimates:
IE7: 13GB IE8: 8.4GB IE9: 13GB Currently, the script will leave the compressed RAR files in place, which means you're looking at something like 45 freaking GB if you don't prune them manually (in ~/.ievms/vhd/). This wasn't a big deal for me on my company workstation, but kinda sucks on my Macbook Air, so I'll be adding a cleanup option shortly. You probably don't need to keep the compressed files around anyway since we take a snapshot like you mentioned.
What's weird is that there's a jump from 8.4 GB to 13 GB on Windows 7. What is on the IE9 vhd that isn't on the IE8 vhd?
Edit: Nevermind, from the official link the IE9 vm comes with additional tools.
For what it's worth, the DLLs in System32 are projected out of WinSxS with hardlinks, so they should not take up extra space. You still have the multiple version thing, however that can be somewhat mitigated by making service packs permanent[1].
[1] http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-...
IE 1.0 to IE 8.0 as standalone versions in a single installer.
Most importantly, why does my page not work in IE7, even though it works in IE7 mode in IE9?
http://stackoverflow.com/questions/5993222/why-does-my-page-...
IE9’s emulation of older IE document modes makes this easier but those emulations are not exact.
http://blogs.msdn.com/b/ie/archive/2011/02/04/testing-multip...
I was eager to see how the problem had been solved... but apparently Windows Vista and Windows 7 don't have that particular problem, and the IE6 VM (with Windows XP) just says "IE6 support is currently disabled".
That's kind of sad; at least for the light web-development I've done, IE7 and IE8 aren't nearly as fussy and hair-pulling as IE6.
Which is basically the only reason I do have an old Windows XP vm on my Mac.
This seems like a very reasonable decision on Microsoft's part: they make it easier / legal / quick to test on their platform and more people will support and develop on it.
You can just roll back to that snapshot at the end of your 30 days and everything will continue to be usable.
For example, I know a few online banking solutions that are IE-only. The most you need there might be a certificate, so resetting the vm every 30 days isn't such a big deal.
I try to keep the VMs as small as possible anyhow and if you need data, you keep it in a VM shared folder that you map in the Windows guest.
I mean, if you want a fully functional pirated version that doesn't expire every 30 days and you never have to activate you don't exactly have to look very hard, or far.
For example, qemu-img convert -O qcow2 Win7_IE8.vhd Win7_IE8.qcow2
W7 trial iso will work without a key, it will just shutdown every 30 minutes which is fine for testing purposes.
IEtester also has debugbar which sometimes is even better than some firefox tools I use.
I can't imagine what would one do with a ChromeOS VM when you have native Chrome builds available. Once the novelty factor wears out (and it does, pretty quickly), there is nothing to be done except delete the vm.
Otoh, I see the value in a secure device like the Chromebook and I think this is what ChromeOS is selling, not just the actual OS.
The automation might be mired in some obscure clause on either end, but it's just doing things you can legally do by hand.