Lubi: Wubi for Linux: Install *ubuntu on any Linux, no partitioning needed

[tuxcantfly]

LUBI NOW HAS ITS OWN WEBSITE AND GUIDE AT http://lubi.sourceforge.net/lubi.html

Ever wanted to test the new K/X/Ubuntu 7.04 Feisty, but don't have a spare partition, and don't want to jeopardize your production environment by resizing partitions, dist-updating, or tinkering with its bootloader? Now you can leave your existing Linux distro (Ubuntu, Debian, Sabayon, Fedora, openSUSE, Gentoo, etc.) untouched, while being able to use Ubuntu 7.04 Feisty in a full-fledged install on a loopmounted partition, no partitioning required!

NOTE: Lubi can only install Ubuntu. If you want to install other distros without a CD such as Fedora, OpenSuse, Mandriva, Debian, or Arch Linux, use UNetbootin; site at http://lubi.sourceforge.net/unetbootin.html and forums at http://ubuntuforums.org/showthread.php?t=427540 Also, Lubi cannot run from Windows; if you want to do a no-CD install of Linux from Windows, use UNetbootin (for a full, standard, real-partition install) or Wubi (for a loopmounted install). Also, Lubi does not support installing Ubuntu versions other than 7.04; for these, use UNetbootin instead.

Credits

I wrote Lubi and this guide. Lupin http://launchpad.net/lupin is used as the codebase, see the Wubi forum at http://ubuntuforums.org/forumdisplay.php?f=234 and the site at http://cutlersoftware.com/ubuntusetu...-US/index.html for details.

Tested Versions

This has been tested on Sabayon 3.3 32-bit, PCLinuxOS 2007 32-bit, openSUSE 10.2 32-bit, Gentoo 2007.0 32-bit, Fedora Core 6 32-bit, Debian Sid 32-bit, Ubuntu 6.10 Edgy 32-bit, Ubuntu 7.04 Feisty 32-bit, and Xubuntu 7.04 Feisty 32-bit as the host systems. Kubuntu 7.04 Feisty 32-bit, Xubuntu 7.04 Feisty 32-bit, and Ubuntu 7.04 Feisty 32-bit were tested as guest systems. Other distros and versions, both 32-bit and 64-bit should work as the host system, just make sure you have the packages installed that are listed below. Distros and versions not based on Ubuntu 7.04 Feisty, and non-x86 architectures can also be used as the guest system, but these will require a custom build of lupin; see https://launchpad.net/lupin for details. Installations using LVM as the root filesystem are currently not supported. If this works/doesn't work for you please post the host/guest distro, version, and architecture.

What it does

Basically, it downloads a K/X/Ubuntu alternate i386 iso, creates loopmounted disk images so that they can be installed there, and adds an entry into /boot/grub/menu.lst which starts the d-i installer with that iso, and installs it into the loopmounted disk images. What thus results is a dual-boot system, in which K/X/Ubuntu are installed in loopmounted disk images in the folder /wubi/ on the filesystem, so that they can be installed without requiring any repartitioning, and they are booted using the system's GRUB, with the last menu entry, "Ubuntu", being added by the script to boot the loopmounted disk images.

Requirements/Dependencies

Before installing, please ensure that you have zenity (used for the GUI), and GRUB (used as the bootloader) installed. If not, install zenity and grub using emerge, apt-get, yum, yast2, or your distribution's equivalent. For Ubuntu and Debian, these should already have been installed.

Installing

You can either follow my step-by-step video tutorial at http://blip.tv/file/331040/ or follow the instructions below:

1. Download the latest lubi package (deb for ubuntu/debian-based, tar.bz2 for others) from: http://sourceforge.net/project/showf...roup_id=198821

2. Then, become root:

For openSUSE and other su-based distros, login as root, while in Ubuntu and other sudo-based distros, enter:

sudo -s

3. Then, if you are using the deb version, just install it, or if you are using the tar.bz2 version, extract it to the root filesystem

4. Then, either click Applications -> System Tools -> Lubi or enter the command "sudo lubi"

5. Answer the questions asked by the wizard, wait while the iso is downloaded, the disk images are created, and the grub entry is added, and you will then be prompted to reboot; reboot.

6. Upon rebooting, the GRUB menu should have a new line at the end, saying "Ubuntu". Select that one, and it will start the d-i installer in non-interactive mode, and will reboot again

7. Select "Ubuntu" in GRUB to boot your newly installed ubuntu, then upon booting, login with the username and password you supplied to the installer

Uninstalling/Removal/Undoing Changes

If using the deb version, enter this command to remove:

sudo dpkg --purge lubi

For the tar.bz2 version, these commands, entered in the terminal on the host system (NOT in the guest Ubuntu install), will remove your loopmounted Ubuntu install, and undo the changes to GRUB:

sudo rm -r /wubi
sudo rm /usr/share/applications/lubi.desktop
sudo rm /usr/share/menu/lubi
sudo mv /boot/grub/menu.lst.bak /boot/grub/menu.lst

Use this guide at your own risk, though if you encounter issues related to loopmounted installation, you should ask them in the Wubi forums at http://ubuntuforums.org/forumdisplay.php?f=234 as it is a generic Lupin/Wubi issue, not a Lubi problem. Post any issues related to Lubi here, and include the host and guest distro, architecture, and version. Also post results if installation succeeds on a host/guest distro/version/architecture combination that isn't listed above. The main lubi development page is at https://launchpad.net/lubi

[tuxcantfly]

After the latest slew of tests on a variety of distros, Lubi appears to be ready to go, I'm reopening this thread and stickying to bring this version to the users' attention...

[nu2this]

Not quite clear on somethings
1st

sudo rm -r /wubi
sudo mv /boot/grub/menu.lst.bak /boot/grub/menu.lst

if its lubi I'm removving would that /wubi be /lubi instead?
2nd in a dual boot set up this way as say MYLINUX & Ubuntu is the removal code put into Terminal in Ubuntu or in MYLINUX?

[tuxcantfly]

Not quite clear on somethings 1st Code: sudo rm -r /wubi sudo mv /boot/grub/menu.lst.bak /boot/grub/menu.lst if its lubi I'm removving would that /wubi be /lubi instead?

No, it's correct as stated in the instructions; it's because of a couple of issues with lupin that haven't been worked out that hardcode the directory to /wubi and prevent it from working properly with /lubi; it's /wubi.

2nd in a dual boot set up this way as say MYLINUX & Ubuntu is the removal code put into Terminal in Ubuntu or in MYLINUX?

In MYLINUX, I've clarified the instructions in my first post

[nu2this]

Thanks! Tuxcantfly I'm all clear now.

[tuxcantfly]

The new version (same download spot) can now work without zenity; simply give it the appropriate command line options from the terminal.
For details, enter:

sh lubi.sh -h all

[dragon_788]

Currently attempting to install this on Sabayon Linux 3.4 loop 2 32 bit. Thanks for the great work on Wubi/Lubi, I've installed Wubi at work where I don't have the time to mess with resizing partitions and reformatting and such.
Has moving a wubi loopback image between systems been tested? I realize that the bootloader would have to be updated but I'm thinking more in terms of moving it between a virtual machine and a physical machine (both running Windows).

[Lucho77]

I am trying to install 'Ubuntu 7.04' in a 'Dell inspiron 5000 laptop',
HD 9 GB Total (2 GB for Win98SE, 7 GB as logical so far, I want this one as Ubuntu 7.04)
RAM 64 MB
I downloaded the 'Wubi-7.04-test2.exe' runs good in 'low memory mode' until the the 'rezising partition time comes then sleeps forever in that screen, had to turn off the laptop by pushing the power button 5 secs. Any advice please. Thanks.

[tuxcantfly]

@Lucho77: this is a known issue, and we're in the process of solving it, go see http://ubuntuforums.org/showthread.php?t=441577 for advice on how to fix it. PS, I noticed that you were in the wubi-netboot thread, and it appears that your win9x bootloader was correctly configured this time; if so, just replace the standard wubi initrd and kernel with the ones from the wubi-netboot package, and that'll fix this issue (though it'll install to a dedicated partition, rather than a loopmounted file)

Has moving a wubi loopback image between systems been tested? I realize that the bootloader would have to be updated but I'm thinking more in terms of moving it between a virtual machine and a physical machine (both running Windows).

I wouldn't quite recommend trying to do that... virtual machines use a different set of hardware, you'll probably be left with a non-functional install if you try that, and you'll have to tinker with lots of hardware config files... it'll be easier simply to do an install from scratch.

PS, this is a thread specifically made for Lubi, if your issues are Wubi issues, ask them in the general Wubi forums http://ubuntuforums.org/forumdisplay.php?f=234

[dragon_788]

Thought I'd report on my progress (or lack thereof) with Lubi in Sabayon on my Gateway CX210X. I got it installed, but every time it tried booting the X server would crash and I was unable to resolve that with any of the methods I tried. I changed display devices, attempted to change drivers, but was unable to install new video drivers because for some reason the onboard NIC in my laptop was unable to properly get an IP, I got an IRQ error. The only way I got it to boot was in VGA mode, but no distro released recently is optimized for it and so I couldn't see half of the information that was trying to be displayed so I gave up. I've booted an Ubuntu LiveDVD on the laptop without any issues so I know the hardware support is there, not quite sure what the issue is.