Slashdot Mirror


Boot Linux, BSD, and OS X from Vista

An anonymous reader writes, "NeoSmart Technologies has just released EasyBCD 1.5, complete with support for Vista, Windows NT/2k/XP, and Windows 9x/ME. EasyBCD 1.5 adds experimental support for dual-booting any of these along with Linux, Mac OS X, or BSD — straight from the Windows Vista bootloader without any additional configuration needed!" From the article: "Windows Vista's new bootmanager is a double-edged sword. It's one of the most powerful booting scripts in existence, and a far cry from the very limiting boot.ini of legacy Windows operating systems. But it overwrites the MBR without a second thought, and doesn't provide any means for users of alternate operating systems and boot managers to use their old system. That's where EasyBCD 1.5 comes in!" EasyBCD 1.5 is free.

8 of 225 comments (clear)

  1. Surprise, surprise. by Eideewt · · Score: 5, Funny

    "But it overwrites the MBR without a second thought...."

    Well, who would have expected Microsoft to do that?

    1. Re:Surprise, surprise. by HoboMaster · · Score: 5, Insightful

      I've had Red Hat (years ago) completely corrupt my HD while shutting down. Obviously I should never use any Linux distro ever again!

      --
      Remember kids, tin foil doesn't work, so use LeadHat.
    2. Re:Surprise, surprise. by sumdumass · · Score: 4, Interesting

      What if he is like me and already has a working, tweeked and otherwise perfected install of linux running. I'm sure there has to be an easier way then trashing that, installing windows first then rebuilding your linux install.

      Personaly, I choose to instal lilo onto a floppy (the boot code). Then go in later and move it to the hard drive. This allows me to boot to a boot disk and streight into linux if neccesary. Also it allows for a backup of lilo's config in case windows trashes the partition linux is on.

      Something i'm wondering is, Did microsoft do this in order to screw open source boot loaders and make the act of dual booting into a free operating system more dificult? It apears that the site is down for the EasyBCD loader. I cannot tell if it is free as in opensource free or just free as in no costs for now free. It could directly effect the way some distro's are compatible with VIsta.

      I'm also wondering if the "opensource" free version if any, would be GPLv3 compatible because microsoft will no doubtly have certain levels of pattents pertaining to the vista boot loader that the EasyBCD guys might not be able to control enough to be GPLv3 compliant. Not to mention that newer microsoft OS's typicly create a volume serial number that is tied into booting and operation of the OS. This is most evident when cloning drives and when it doesn't keep the corect serial you get errors on booting. How would this be effected by the ANTI-TIVO type wording in the GPLv3 when a GPLed product is working with the code or programs? I Think some clearification might be in order on this. I have raised simular questions before with products like Itunes and Hardware that locks certain performances out in cheaper versions and the answer is always, they shouldn't be doing that or the Closed app should be open. I'm sure booting to vista in a free way might be more important then forcing apple to opensource Itunes in order to keep a GPLv3 frontend compatible with the GPL.

      An no, I'm not trolling. These are legit concerns with the GPLv3 brought up by others too. I'm just putting them into relvent terms that can be related to in this context. It would suck donkey balls if GPLv3 licensed bootloaders are incompatible to dual booting with microsoft operating systems because of this. Especial when the entire idea behind the changes is to control the manufacturers hardware with previous versions of the GPL claims is outside the GPL's scope.

  2. Except for the fact that... by daveschroeder · · Score: 5, Informative

    ...you can't "boot OS X" on non-Apple hardware without:

    1. Breaking Apple's Mac OS X license agreement, which says that Mac OS X is to be run only on Apple-branded computers
    2. Pirating Mac OS X (Intel), since Mac OS X (Intel) is not available as a standalone OS at present
    3. Running a horribly hacked version of Mac OS X, with critical pieces of the system modified, including the kernel
    4. Running Mac OS X in an unupdateable state, since any official Apple software updates that overwrite modified pieces of the hacked version of Mac OS X will break it
    5. Running Mac OS X in a state completely unsupported by its vendor
    6. Possibly violating civil or criminal law in your jurisdiction

    I hope that most people can find at least *one* of the above items that would make them reconsider running Mac OS X (Intel) on a generic PC without paying for it (some will no doubt argue that they should be able to "reuse" PowerPC licenses for Mac OS X in spirit, but the fact is that it's not the same product - that's like saying that you at one time owned one software product from a company that's similar, so you should be able to use this other one/newer version/older version/different version for free). I'm sure others will come up with all sorts of justifications why it's okay.

    But isn't all of the billions of dollars or R&D and hundreds of thousands of manhours invested in Mac OS X worth something? What if their pricing is predicated on what is essentially a good faith agreement that you'll not hack it and run it on non-Apple hardware? Does Apple have ANY say in how they'd prefer it to be used?

    I could go on, of course, but just thought this was worth mentioning.

  3. License: Freeware by Benanov · · Score: 4, Informative

    Downloaded it just to check the license (yeah, I'm odd about this crap)

    It's freeware. Sorta looks like a Creative Commons license, but basically it's just plain old freeware.

    4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
    a. You may distribute the Work only under the terms of this License, and You must include a copy of, or the Uniform Resource Identifier (URI) to, this License with every copy of the Work You distribute, and only with the permission of the Licensor & Original Author. You may not offer or impose any terms on the Work that alter or restrict the terms of this License or the recipients' exercise of the rights granted hereunder. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties. You may not distribute the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement. The above applies to the Work as incorporated in a Collective Work, but this does not require the Collective Work apart from the Work itself to be made subject to the terms of this License. If You create a Collective Work, upon notice from any Licensor You must, to the extent practicable, remove from the Collective Work any credit as required by clause 4(c), as requested.
    b. You may not exercise any of the rights granted to You in Section 3 above in any manner that is primarily intended for or directed toward commercial advantage or private monetary compensation. The exchange of the Work for other copyrighted works by means of digital file-sharing or otherwise shall not be considered to be intended for or directed toward commercial advantage or private monetary compensation, provided there is no payment of any monetary compensation in connection with the exchange of copyrighted works.
    c. If you distribute the Work, You must obtain permission from and let the Original Author know, You must keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (and/or pseudonym, if applicable) if supplied, and/or (ii) if the Original Author and/or Licensor designate another party or parties (e.g. a sponsor institute, publishing entity, journal) for attribution in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; the title of the Work if supplied; and to the extent reasonably practicable, the Uniform Resource Identifier, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work. Such credit may be implemented in any reasonable manner.

  4. Tinfoil too tight? by Kadin2048 · · Score: 5, Funny

    Apple and the U.S. government established the anti-boot laws to keep people from booting OS X.

    I'm sorry ... what?

    Are you posting from the future, where the world has been decimated by killer iPods or something?

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  5. Re:Getting lots of OSes running by Shawn+is+an+Asshole · · Score: 4, Informative

    Grub isn't very difficult to adjust to. I also held out on learning it for a while, but it actually is kinda nice. The thing I really like about it is after making a change (new kernel, boot option, etc) it isn't necessary to reinstall it to the mbr. Just edit menu.lst and it's done.

    Take the 5 minutes to learn it.

    --
    "It ain't a war against drugs.it's a war against personal freedom" --Bill Hicks
  6. Re:Getting lots of OSes running by TeknoHog · · Score: 4, Informative

    When you "make install" a new Linux kernel, it makes a symlink /boot/vmlinuz to the new kernel. So you won't even have to edit menu.lst if the boot option is this symlink. Grub also has the nice feature of editing the kernel entry at bootup, so you can go back to the old kernel if necessary.

    --
    Escher was the first MC and Giger invented the HR department.