Slashdot Mirror


Debian win32-loader Goes Official

An anonymous reader writes "After a long process of review and polishing, the win32 loader from goodbye-microsoft.com has finally made its way to official Debian CDs. Latest daily builds of lenny (the development version) are including it, making starting Debian Installer as simple as just a few clicks (OGG). The win32-loader version, now based on GRUB 2, includes new features such as detection and pre-seeding of Windows settings, and is translated to 20 languages."

6 of 246 comments (clear)

  1. "apt-get hell" by Filter · · Score: 3, Interesting
    >>Who would want to install Debian anyway...? (Score:1)

    >> by aswalkeraus (563276) Alter Relationship on Thursday September 13, @11:07AM (#20588309)


    >>Seriously.... apt-get hell awaits, ... be afraid, very afraid!



    Thats the first time I heard that expression, not a total surprise I guess; google says:

    Results 1 - 10 of about 558 for "apt-get hell". (0.30 seconds)
    Results 1 - 10 of about 16,000 for "rpm hell". (0.12 seconds)
    Results 1 - 10 of about 208,000 for "dll hell". (0.07 seconds)

    btw. see how much longer it takes google to even come up with the list for apt-get, .30 seconds! That proves something for sure.

    --

    "better ways of doing things eventually just replace the inferior things" - Linus Torvalds 09-08-07

  2. Re:Huh? by joto · · Score: 5, Interesting

    And telling a newbie to go into BIOS setup to change settings is likely to scare the crap out of them.

    And the newbie would be right.

    Installing debian on a windows system should also scare the crap out of a newbie. He will loose all his old files (including family photos), even if this "win32-loader" allows him to keep his worthless bookmarks.

    While I have nothing against trying to convince people to try linux, I have something against the people who will try just about anything, including outright lying, in order to make people switch.

  3. bad feeling by d3ac0n · · Score: 3, Interesting

    What I find interesting is the potential for "Linux Phishing" or "Linux Greifing" that this creates. There are already plenty of problems with various viruses loading directly through the browser in Windows, can you imagine what would happen if a "religious Linux fanatic" were to take this, alter it to use a known but unpatched IE vulnerability to auto-install and reboot people's machines into Linux? What would happen if a "religious Microsoft fanatic" did the same thing to try and make Linux look bad?

    I've got a baaaad feeling about this...

    --
    Official Heretic from the "Church of Global Warming". Proven right thanks to whistle blowers. AGW = Flat Earth Theory
  4. Re: Huh? by dylan_- · · Score: 3, Interesting

    It should be included. See if /proc/sys/fs/binfmt_misc/ exists. If it doesn't, ask in your distro's forums. If it does, maybe just ask in your distro's forums if there's a gui for setting it up! :) But, if you really want to command-line it, next step is check if /proc/sys/fs/binfmt_misc/register exists. If not try:

    mount -t binfmt_misc none /proc/sys/fs/binfmt_misc

    and then check again if the "register" file exists. If it doesn't...something's wrong. If it does, then you can add entries like the wikipedia article says. So, you can "cd /proc/sys/fs/binfmt_misc" and then add a line to "register" of the form :name:type:offset:magic:mask:interpreter:

    Here's an example for Windows applications, using Wine.

    cd /proc/sys/fs/binfmt_misc
    echo ':Windows:M::MZ::/usr/bin/wine:' > register

    Which has:
    name = Windows
    type = M (use the magic number, rather than "E" which means use the extension)
    offset = just left blank
    magic = MZ (magic number for Windows executables, if you'd used "E" previous, you'd put "exe" here)
    mask = left blank
    interpreter = /usr/bin/wine (full path to wherever the "wine" program is)

    Now you can run Windows apps just by typing their name, like any Linux program. In fact, since we used the magic number rather than the extension, you could remove the .exe extension and it would still run fine.

    You'd probably want to put this in a startup script, or something :)

    --
    Igor Presnyakov stole my hat
  5. the Tux Virus by hawk · · Score: 4, Interesting

    This scenario was labeled the "Tux Virus" many years ago.

    Typically, the scenario involved a win95 themed wm and a far-fetched belief that wine or openoffice could allow the user to be fooled at least briefly.

    hawk

  6. Re:What? by cortana · · Score: 3, Interesting
    That's why it's best to have both testing and unstable in your sources.list; but to pin unstable to a lower priority than testing.

    $ apt-cache policy git-core
    git-core:
      Installed: 1:1.5.2.4-1 0
      Candidate: 1:1.5.2.4-1 0
      Version table:
        1:1.5.3.1-1 0
            520 http://ftp.uk.debian.org/ unstable/main Packages
      *** 1:1.5.2.4-1 0
            530 http://ftp.uk.debian.org/ lenny/main Packages
            100 /var/lib/dpkg/status
    In this case, if for some reason git-core was broken in testing, I could easily upgrade it to the version from unstable with a command such as aptitude install -t unstable git-core. But if I installed git-core without the -t argument, the version from testing would have been chosen.