Last edited by Skeptical33; January 28th, 2008 at 07:26 AM.
That'll overwrite the disk's contents with zeros (you probably only have to do it for the first few megabytes or so). Then after that enter:Code:dd if=/dev/zero of=/dev/sda
fdisk will spew out errors and ask to initialize a new DOS disk label, enter the command "o" on the fdisk prompt (to create a new DOS disklabel), recreate your partitions, and hopefully it will work after that.Code:fdisk /dev/sda
Last edited by tuxcantfly; January 28th, 2008 at 07:17 AM.
In order to understand a bit better what can be done with UNetbootin, I'm interested in knowing a bit more about how it works. From what I can tell, it copies the kernel image and initrd image to the UNetbootin installation directory on the host (Windows or Linux). When you run UNetbootin from the host, it adds an entry in the bootloader that points to the kernel and initrd images in the UNetbootin installation directory on the host (which is on an NTFS or ext2/3, etc. partition). On reboot, the kernel and initrd images are loaded into RAM but none of the partitions on the hard drive are mounted. This way, the installer can blow away the partition containing the kernel and initrd images while its running (since they are loaded into memory and the partitions aren't mounted). Is this correct?
If so, I would pretty much understand how UNetbootin works. There's one more thing that I don't quite understand, though. How does UNetbootin remove itself from the bootloader menu after it's booted?
Thanks for all your work on UNetbootin and related projects. I think this project will start taking off as more and more machines start shipping without an optical drive (Asus' Eee PC, OLPC's XO, Apple's MacBook Air, etc.).
It seems to me that UNetbootin and related projects could benefit from moving to mailing lists instead of using forum threads as the primary means of communication. I find it easier to post to mailing lists since it is easier to send an e-mail than to login to a forum site and post a reply. Mailing lists also handle different threads of conversation more gracefully since most e-mail clients and archive tools (like pipermail, which most Mailman installs use) can group messages by thread. This makes it easier to find a topic that has been previously discussed.
I would suggest having Sourceforge host the mailing lists through the Lubi project page. This has worked well for me in projects that I have hosted.
I'd be happy to discuss this further. Let me know if you have any comments or questions.
It adds the uninstaller to the Windows autostart; that way it's removed (menu entry along with the files) next time the user boots WIndows. Theoretically, this can also be accomplished by loading a temporary kernel that removes the menu entry then chainloads the main kernel/initrd, but I stick with the Windows uninstaller approach because it's generally safer.If so, I would pretty much understand how UNetbootin works. There's one more thing that I don't quite understand, though. How does UNetbootin remove itself from the bootloader menu after it's booted?
Last edited by tuxcantfly; January 30th, 2008 at 05:07 AM.
Because of the large number of distributions that UNetbootin supports and since UNetbootin has separate releases for each distribution that contain that distributions kernel and initrd files (usually), there are a ton of released files to choose from when downloading. This could turn into quite a headache for the maintainer of UNetbootin as a change to the core of UNetbootin requires all of the packages to be re-made, for example.
I suggest that the core UNetbootin functionality be confined to a single package for each host distribution (so there would be one .deb, one .rpm, one .exe, etc.) that knows how to handle the installation of any target distribution (ie. FreeDOS, Ubuntu, etc.). This core package would know how to grab the necessary minimal ISO files from the web as needed (when the user selects which distro they want to install) and then take the necessary files from the ISO and stick them on the hard drive.
There could also be an option for the user to specify their own ISO to UNetbootin. This would allow users to test new distributions that UNetbootin doesn't know about yet. It may require UNetbootin to include a mechanism to search for the kernel and initrd image and prompt the user if it can't find them in the ISO.
Since I haven't really looked at the code, I'm not sure how feasible this would be, but it seems like the sort of thing that would be good to move toward.
From what I can tell, UNetbootin has not been tested on the Eee PC or OLPC XO and does not support Mac OS X. I'm guessing you're probably thinking about these, but in case you aren't, here's a nudge.
The Eee PC might work with the Debian package, but I'm not sure whether the file locations or bootloader configuration are sufficiently similar to most Debian installations to make it work. I may have access to an Eee PC for testing, but I'm not sure if I'd have a lot of time to test it.
The XO might work with the RPM, but it's less likely because it uses the Sugar interface by default. You could make a proper activity and use the Sugar interface, but it might be easier just to use a command-line app for starters. Also, the XO will not boot a standard kernel because it does not have the standard BIOS that most kernels assume. So one would have to replace the distribution-provided kernel from the minimal ISO with the kernel from the XO. This isn't too hard, but would require some special casing. It also means that UNetbootin would have to replace the installed kernel with the XO kernel, which is a little harder to do. Hopefully the mainline kernel will soon support the OLPC, but for now I don't think it does. I would be able to do some testing on the XO, but it probably won't be for a month or two. You could also emulate it yourself if you like (http://wiki.laptop.org/go/Emulating_the_XO).
Lastly, it would be nice to have Mac OS X support, especially now that the MacBook Air (sans optical drive) is released. This is probably a fair bit of work (at least to make it look nice), but perhaps you can find an OS X coder that's interested. You may want to include the automatic installation of rEFIt (http://refit.sourceforge.net/) to make things easier on the user.
I hope my comments are useful. I'd be happy to discuss them in more detail if you have questions.
I'd really like to see more resources behind this project (perhaps in the form of official Canonical support). I think that would really help with implementing some of these high-priority feature requests. Any tips on how to push for that would be appreciated.
https://help.ubuntu.com/community/EeePC. Similar methods should work for other distributions.
everything runs well,except i can't fling off the Linux boot loader,despite the fact I've already uninstall it when i log in my Windows XP Home.