- Ubuntu v8.04 install from iso-image on HD w/o CD ! ========================================= copy ISO-Image to root of ext3/3 partition, e.g. /media/sda8/ extract vmlinuz to e.g. /media/sda8/boot/vmlinuz extract initrd.gz to e.g. /media/sda8/boot/initrd.gz change menu.list of grub accordingly, e.g.: title ubuntu 8.04 kernel (hd1,7)/boot/isolinux/vmlinuz root=/dev/hdb8 initrd (hd1,7)/boot/isolinux/initrd.gz - SliTaz ======= copy content of iso-image to /media/sda14/boot invoke in menu.list as follows: # linux live-cd SliTaz on /dev/hda14. title SliTaz v2.0, k 2.6.22.9, (on /dev/sda14) from iso root (hd0,13) kernel /boot/bzImage home=hda14 initrd /boot/rootfs.gz - qemu ======= Code: # qemu -cdrom cdimage.iso -boot d - grub ====== - debian mit debootstrap in chroot-Umgebung installieren ============================================= ( http://www.kai-hildebrandt.de/linux/debian_chroot.html ) - direct ISO install ? ================= ( http://www.linuxforums.org/forum/installation/48138-direct-iso-install.html ) If you want boot a live on cd from a partition, and NOT installing it like the installer does, follow the steps below (using syslinux (isolinux) as bootloader). You can have goblix and any other live cd running from hd, just the same way it is running from cdrom, improving performance quite a lot. it is definitively slower than really installing the unpacked goblix (like using goinstall...) but lot quicker than from cd. furthermore you can take advantage of automatically mounted swap partition etc. etc. only thing to be done is to replace isolinux with extlinux from syslinux, because isolinux can only boot from isos and there are quite some differences for the bios to boot from cdrom than from hd. little howto: create datapartition - size is rather unimportant: goblix mini fits within 200MB create swappartition copy content of cdrom to data partition download extlinux from syslinux homepage copy isolinux.cfg to extlinux.conf run command "extlinux /mnt/hda1" (if hda1 is mounted to /mnt/hda1 and is datapartition run command "cat mbr.bin > /dev/hda" make sure /dev/hda1 has boot flag activated - Booting the ISO from a hard disk partition ================================== ( http://wiki.lunar-linux.org/index.php/Installation:No_CD ) contents: # 1 Booting the ISO from a hard disk partition # 2 Chrooting into the ISO * 2.1 Installing from 2.4 kernels with devfs support * 2.2 Installing from 2.6 kernels with udev support * 2.3 This is something different * 2.4 Usb bootable lunar # 1) Booting the ISO from a hard disk partition ? =============================== requires: * Enough free disk space plus partition big enough for the iso image * Any installed operating system and tools that allow directly to write to a partition * A working boot loader like windows' bootloader, lilo or grub Your best bet is to free some space at the end of your disk. Make sure this is larger than the lunar iso (somewhere around 350mb). Create a partition and copy the contents of the iso to that partition: cat lunar-1.5.1-i686.iso > /dev/hda15 Once done, you should edit your bootloader (be it windows or grub or lilo) and make it boot the boot sector of the iso. Here's the lilo entry you would need: other = /dev/hda15 label = lunar-1.5.1 That's it! reboot and select the iso entry, and you're ready to go! The lunar installer should start and everything should work just as good as from a CD! # 2) Chrooting into the ISO ? ================ Installing from 2.4 kernels with devfs support If the above method fails, you can always manually chroot into the ISO and start the installer manually too. requires: * A running linux installation with relatively new 2.4 kernel that has devfs support and allows chroot usage (must be root) This method is a bit trickier since you will be repartitioning your hard disk from which you just have booted, so you should actually install a small linux installation somewhere near the end of your disk, losetup/loopmount the iso on there, and then install to partitions that are NOT active/mounted. This might even fail since the kernel doesn't like changing partitions when it's running. So, start out by getting your 'tiny' linux running anf booting. Preferably install it at the end of your hard disk and re-partition the beginning of your hard disk already for the lunar installation. Reboot your system so the partitions are known by the kernel, and prepare to mount the ISO over loop: losetup /dev/loop0 lunar-1.5.1-i686.iso mount /dev/loop0 /mnt -o ro chroot /mnt /sbin/lunar-install that's it! The installer should run and you can perform all steps necessary for installing lunar on the remaining partitions. At the end, make sure you don't accidentally overwrite your bootstrap linux installation so you can fallback to it. Beware that you might want to add the bootstrap bootloader info too, in case you want to boot that installation if something goes wrong. Once lunar installs succesfully, you can remove this partition of course. - Howto: Vector Linux No-CD Install using UNetbootin ? =========================================== ( http://ubuntuforums.org/showthread.php?p=4062492 ) ( http://unetbootin.sourceforge.net/ ) It's an installer for Windows or Linux users that lets you install Vector Linux without a CD. The way it works is that a small (6 MB) installer places the Vector Linux installer on your hard drive, and configures your boot loader, either NTLDR if using Windows, or GRUB if using Linux, to boot from the installer, which uses the packages from an iso file to install Vector Linux to your hard drive. - CD-Image von HDD booten (Inhalt auf HD kopieren) ? ======================== http://board.gulli.com/thread/368120-cd-image-von-hdd-booten/ zumindest bei Kanotix geht das sehr einfach , andere habe ich noch nicht probiert. iso mounten, Eine kleine Partition 800MB erstellen ISO-Inhalt reinkopieren grub anpassen booten fertsch Ja und es funktioniert und ist innerhalb weniger Minuten erledigt ohne Zusatztools. In die gleiche Partition kannst du dann jeweils dein ISO reinpacken was du gerade testen willst. - Booten vom iso-Image ==================== http://www.pclinuxos.de/smf/index.php?topic=960.15 ikerekes, Administrator, Hero Member View Profile Personal Message (Online) Re: booting from iso - saving settings « Reply #3 on: Today at 10:23:21 AM » Reply with quote The grub entry what you're using should be: title pclinuxos squashfs kernel (hd1,7)/boot/isolinux/vmlinuz bootfrom=/dev/hdb8/ changes=/dev/hda8 root=/dev/hdb8 vga=788 splash=silent initrd (hd1,7)/boot/isolinux/initrd.gz i.e the livecd.sqfs not needed in the bootfrom= and the changes=/dev/hda8 will make all the changes you'r making after boot, persistent. The only requirement for the partition used for changes it has to be linux type (i.e. ext2,3 reiserfs). the livecd will automatically allocate a /changes directory if it doesn't exist and mount it over the memory. If it exist, it will use it. If the /changes directory exists, (meaning persistent changes) the poor man install will suspect no rerun of detection required. If you want to use on some other machine (like putting the changes on a usb stick partition) you have to instruct the livecd to rerun the hardware detection with hwdetect=yes cheatcode not to take the hardware config info from the persistent /changes directory. The changes= cheatcode takes only the partition number as a parameter, not the full path, it expects the /changes directory at the root of the partition. --------------------------------------------------------------- Das bedeutet: - man kann alle veränderten Einstellungen und auch Daten auf einem USB-Stick speichern. Der muß (!) aber ext2, ext3 oder reiserfs-formatiert sein. Sonst, z.B. mit vfat, geht das nicht. War bei mir so. - man muß wol den /changes - Ordner auf einer anderen Partition einrichten als der, auf der man das live-cd.sqs-Datei gespeichert hat. (Ich rate: immer mal wieder den Inhalt von /changes durchsehen. Da sammeln sich, jedenfalls bei SLAX, mit der Zeit jede Menge unbenötigter .wh-Dateien an, log-Files usw., so daß dieser Ordner immer größer wird). Vorgehen eines poormans install mit PCLinuxOS: - wie oben beschrieben (also ähnlich Knoppix, nicht wie bei SLAX, wo man vom .iso-Image booten kann) - die GRUB-menu.lst-Zeilen so anpassen wie ikerekes schreibt. Statt /dev/hda8 kann man jede andere Partition nehmen, die Platz hat, und die ext2, ext3 oder reiserfs formatiert ist. Vermutlich, aber nicht ausprobiert, könnte man den Ordner /boot/isolinux und die livecd.sqs-Datei auch auf eine vfat- oder gar ntfs-Platte speichern. Der /changes-Ordner muß dann aber woanders sein! Macht man das hat man (falls man viel RAM hat!!!) eine blitzschnell agierende Installation, die man auch leicht mit Software erweitern kann (neu installierte rpms wären dann in /changes!). Statt später neu zu installieren löscht man die alte livecd.sqs-Datei und speichert die neue dorthin. Das ist aber vermutlich für Anfänger nicht gut geeignet. Ich rate zur Vorsicht! Es ist eine Art "3. Weg" zwischen Live-CD und Festinstallation, der wieder einmal zeigt, wie man mit Linux zaubern kann. Die armen Windozer können von so etwas nicht einmal träumen, weil sie so etwas nicht denken können. die Einzelheiten! Sperrig sind sie aber auch: die Datei isolinux ist ein Ordner, keine Datei. Du solltest haben auf Deiner Partition: /boot /isolinux livecd.sqfs Dann in der GRUB-menu.lst Deiner Hauptinstallation: title pclinuxos 2007 neu kernel (hd1,7)/isolinux/vmlinuz bootfrom=/dev/hdb8 root=/dev/hdb8 vga=788 keyb=de_nodeadkeys hwdetect=yes changes=/dev/hdb8 initrd (hd1,7)//isolinux/initrd.gz Immer auch an die Mitleser denken, damit die Menschen draußen im Lande, die diese Live-CD auf diese Weise booten wollen, keine Mißerfolge einfahren, die sie dann der unschuldigen Software zuschieben! ;-) Michael Bischof - How To Install Ubuntu Locally Over The Network ========================================= http://ubuntu-tutorials.com/2007/10/08/how-to-install-ubuntu-locally-over-the-network/ http://www.addhen.org/blog/2007/10/30/installing-gutsy-over-the-lan/ I spent some time this week figuring out the requirements for installing Ubuntu locally over the network. Ubuntu has netboot installers which are more than happy to go find a public repository mirror for you, but how about installing over the LAN using the contents of the CD as the repository? Well, if you’re interested in fast installations and no longer burning CDs this tutorial is for you. You should note that this tutorial is considered intermediate to advanced so please read through the entire contents before you continue and research any steps you’re not familiar with before diving in. Requirements This tutorial does not outline PXE boot based installation information. That is for an upcoming tutorial. This simply outlines installing the contents of the CD over the network. In order to do this we’ll need a few basic things: 1. CD image 2. Apache 3. netboot installer The way that each of these requirements will be used is that we’ll copy the contents of the CD to a web-accessible share on Apache and then boot the machine-to-be-installed via the netboot installer (CD or USB based options available here). 1. Download the .iso image for the ubuntu version and variant that you want, saving it to disk (alternate, not desktop!). 2. Install apache “sudo aptitude install apache2” * 3. netboot installer image i386 64bit (compatible for use with any alternate install image in step #1) * The configuration of apache is beyond the scope of this tutorial but a basic installation should provide enough core functionality to allow us to continue with the installation. Preparing the CD for installation We’ll need to unpack the contents of the downloaded CD .iso file. The way I generally do this is using these commands: sudo mkdir /var/www/ubuntu/ sudo mount -o loop /path/to/.iso /mnt sudo cp -a /mnt/* /var/www/ubuntu/ If you’re not familiar with the above commands we’re first creating a directory called ubuntu within our apache web-accessible directory. We’re then locally “loop” mounting the CD image to the location /mnt. Finally we’re copying the contents of the CD to our new directory. Preparing the Installer We’ll now need a netboot installer created. This is a very minimal installation CD that can be used to install any other Ubuntu image. For example one copy of this netboot installer will allow you to install previous, current and (most likely) future releases of Ubuntu as long as you have access to the web-accessible CD image or public repository. So, although above I promised no more burning CDs you will actually need to burn just *one* more. Also, this netboot installer image is available for CD or USB image if you prefer one over the other (I prefer USB). Hopefully you’ve already followed step #3 of the Requirements section and you have either the mini.iso or the boot.img.gz file downloaded. To prepare either of those for use do follow these steps: mini.iso (CD) * (gnome) insert a writable disk into your machine, right-click mini.iso and select “Write to disk”. * (KDE) insert a writable disk into your machine, right-click mini.iso and select “Actions > Write CD image with K3B” boot.img.gz (USB) You’ll first need to uncompress this file before you can write the image to disk: gunzip boot.img.gz insert a USB device that you’ll use as your boot device. ALL DATA WILL BE WIPED TO MAKE IT BOOTABLE. You can use the ‘dmesg’ command to see what device your USB was detected as (sdb, sdc, etc). We’ll then write the contents of the image to the device using dd: dd if=boot.img of=/dev/sdX (where X is the device detected with dmesg, sdb, etc) Starting The Installer You should now be ready to install your machine by booting either the CD or via the USB you’ve created. If you have trouble booting to either of those devices you might check your BIOS settings to see that one of them takes priority over the main hard drive. If you are using the boot.img on a USB you will want to remove this device when you are prompted with the language selection menu. This will help avoid conflicts with drives-to-be-installed, where to install the Boot Loader, etc. You’ll be presented with a very basic menu when the netboot installer loads. To install only the base system type 'server', then ENTER. For the default installation, press ENTER. The default installation is suitable for most desktop or laptop systems. Navigate through the installer as normal but watch for the step entitled: Choose a mirror of the Ubuntu archive At this step we will tell the installer to use a custom repository, in this case being the locally shared CD contents we set up previously. Instead of selecting your country in this step go up to the first option listed: (pg-up to the top) enter information manually I don’t think the option of entering custom information is very intuitive so I missed this the first few times through. Watch for this step. If you are given a prompt offering us.archive.ubuntu.com or CC.archive.ubuntu.com you’ve gone too far! The next step will prompt you for the hostname or IP address of the server you will be installing from. This is the IP address of the server you copied the CD contents and installed Apache to. After the hostname or IP is entered the installer will prompt you for the path to the publicly shared contents. If you closely followed these steps the default entry of /ubuntu/ should work. If you copied your CD contents into a folder other than /ubuntu/ you’ll need to update this accordingly. At this point navigate through the installer as normal and enjoy what should be faster installation speeds as network-based is usually faster than CD-based. As usual if you have any questions feel free to leave a comment. It should be noted, again, that this tutorial is probably considered intermediate to advanced so you may not want to undertake this if you’re a n00b. * gabriel hello, thanks for this helpfull tutorial. I have follow all steps but error like “no kernel modules were found…” show me another ways. 1. u don’t need apache Server and cd !! 2. just take the version of mini.iso u need 3. follow this tutorial until the point where u have to give the host-name. type us.archive.ubuntu.com or XX.archive.ubuntu.com where XX are the land initial . note u don’t have to type “http://” !! 4. the path is /ubuntu/ it’s ALL Posted on 28-Jan-09 at 5:31 pm | Permalink