| Autor |
Nachricht |
|
|
Titel: Loading Hellfire image from HD
 Verfasst am: 11.05.2011, 17:58 Uhr
|
|
Anmeldung: 09. Mai 2011
Beiträge: 74
|
|
There are two versions maybe both dated?
1. http://www.kanotix.com/index.php?module=pnWikka&tag=BootFromIso
Zitat:
Now what if you don't want to just copy it to KNOPPIX/KNOPPIX.ISO, well then you have choices in how to build up the path it will look for:
fromiso=path/to/KANO*.iso
Makes Kanotix look for path/to/KANO*.iso
then
Zitat:
knoppix_iso_dir=path/to/
Makes Kanotix look for path/to/KNOPPIX.ISO
knoppix_iso_name=KANO*.iso
Makes Kanotix look for KNOPPIX/KANO*.iso
which is confusing. And then
Zitat:
fromhd=/dev/hdXN?
Makes Kanotix only check the specified device. Unless you use this Kanotix will check your drives as it would when looking for the cd.
2. http://www.kanotix.com/FAQ-id_cat-62.html#q297
& http://kanotix.com/FAQ-id_cat-63.html#q298
Zitat:
With this cheatcode you can start from an iso out of a partition
Requirements:
- a functioning grub (on a floppy, a HD-Installation or from the Live-CD)
- a KANOTIX ISO Image e.g.: KANOTIX-2005-04.iso
First we choose a place for the iso and 2 files we need, so we get shorter names.
# mkdir /media/hda5/kanotix
# mv KANOTIX-2005-04.iso /media/hda5/kanotix
mount the iso image:
# mkdir -p /mnt/test
# mount -t iso9660 -o loop,ro /media/hda5/kanotix/KANOTIX-2005-04.iso /mnt/test
copy the files miniroot.gz and vmlinuz
# cp /mnt/test/boot/vmlinuz /media/hda5/kanotix/
# cp /mnt/test/boot/miniroot.gz /media/hda5/kanotix/
customize grub
### ISO boot
title Kanotix 32bit from ISO
kernel (hd0,4)/kanotix/vmlinuz ramdisk_size=100000 init=/etc/init fromiso=/kanotix/K*.iso noprompt noeject lang=en apm=power-off nomce quiet
initrd (hd0,4)/kanotix/miniroot.gz
Assume the second to be more appropriate. So, on my existing system I have created a top level directory '/Hellfire'
Code:
# mkdir /Hellfire
$ mv /kix/kanotix-2.6.38rc6.iso /Hellfire
$ ls -l /Hellfire
-rw-r--r-- 1 ik ik 1131413504 May 8 01:58 kanotix-2.6.38rc6.iso
# mkdir -p /mnt/test
# mount -t iso9660 -o loop,ro /Hellfire/kanotix-2.6.38rc6.iso /mnt/test
# ls -l /mnt/test/live
-r--r--r-- 1 root root 26399 Mar 2 04:47 filesystem.packages
-r--r--r-- 1 root root 1103929344 Mar 2 04:46 filesystem.squashfs
-r--r--r-- 1 root root 19970691 Mar 2 04:47 initrd.img
-r--r--r-- 1 root root 165084 Mar 2 04:47 memtest
-r--r--r-- 1 root root 4533424 Mar 2 04:47 vmlinuz
No 'miniroot.gz', so assume changed to be 'initrd.img'
Code:
# cp /mnt/test/live/vmlinuz /Hellfire
# cp /mnt/test/live/initrd.img /Hellfire
# ls -l /Hellfire
-r--r--r-- 1 root root 19970691 May 8 13:25 initrd.img
-rw-r--r-- 1 ik ik 1131413504 May 8 01:58 kanotix-2.6.38rc6.iso
-r--r--r-- 1 root root 4533424 May 8 13:24 vmlinuz
GRUB (Version 0.96) booting crashes!
Code:
# ISO boot
title Kanotix 32bit from ISO
kernel (hd0,0)/kanotix/vmlinuz ramdisk_size=100000 init=/etc/init fromiso=/Hellfire/k*.iso apm=power-off nomce quiet noprompt noeject
initrd (hd0,0)/kanotix/initrd.img
OR
Code:
# ISO boot
title Kanotix 32bit from ISO
kernel (hd0,0)/Hellfire/vmlinuz ramdisk_size=100000 init=/etc/init fromiso=/Hellfire/kanotix-2.6.38rc6.iso apm=power-off nomce quiet noprompt noeject
initrd (hd0,0)/Hellfire/initrd.img
OR Shorter Image Name
Code:
# mv /Hellfire/kanotix-2.6.38rc6.iso /Hellfire/hf.iso
# ISO boot
title Kanotix 32bit from ISO
kernel (hd0,0)/kanotix/vmlinuz ramdisk_size=100000 init=/etc/init fromiso=/Hellfire/hf.iso apm=power-off nomce quiet noprompt noeject
initrd (hd0,0)/kanotix/initrd.img
All give rise to the following output:
Code:
kernel (hd0,0)/kanotix/vmlinuz ramdisk_size=100000 init=/etc/init fromiso=/Hellfire/hf.iso apm=power-off nomce quiet noprompt noeject
[Linux-bzImage, setup=0x3a00, size=0x44f0b0]
initrd /Hellfire/initrd.img
[Linux-initrd @ 0x36bc4000, 0x130ba83 bytes]
boot
mdadm: No arrays found in config file or automatically
mount: can't read '/etc/fstab': No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /etc/init.
No init found. Try parameter init=bootarg.
BusyBox
Enter 'help'
/bin/sh: can't access tty; job control turned off
(initramfs)
(initramfs) find / -name linuxrc
(initramfs)
'linuxrc' not present!
Kernel 2.6.11.7 mit einigen Patches
KANOTIX 2005-02
P.S. Don't let me stop anyone from responding in German. It's just easie and quickerr for me to write in English.. |
|
|
| |
|
|
|
 |
|
|
|
Titel: Loading Hellfire image from HD
Verfasst am: 11.05.2011, 19:17 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16790
|
|
|
|
|
|
|
|
|
Titel: Loading Hellfire image from HD
Verfasst am: 12.05.2011, 00:57 Uhr
|
|
Anmeldung: 15. Mar 2008
Beiträge: 610
|
|
Well you see not every part on the Wiki is up-to-date. There is a lack of men power to hold the Wiki in a good shape. Feel free to help and fix it. I like to see that the people take a lot at it, most people know that it is not in the best shape and ignore it completely. That's the wrong attitude to change the situation. So you are really welcome to help.
Thanks, TheOne |
_________________
Lenovo ThinkPad X220 | Core i7-2640M 16GB | Hellfire 3.6
FSC Tablet T4220 | Core2 Duo T7250 2GHz 3GB | Intel GMA X3100 | Hellfire 3.6
Clevo M570U | Core2 T7200 2GHz 2GB | Geforce Go 7950gtx | Hellfire 3.2
|
| |
|
|
|
|
|
|
|
Titel: Re: Loading Hellfire image from HD
Verfasst am: 12.05.2011, 12:57 Uhr
|
|
Anmeldung: 09. Mai 2011
Beiträge: 74
|
|
|
Kano hat folgendes geschrieben::
The Hellfire 2011-05 way
which doesn't work cos I need to get Grub2 
btw couldn't help noticing that the '666..' script
Code:
set isopart=/dev/sda1
set isopath=/Hellfire
set isoname=hf.iso
...
menuentry "Kanotix Live - EN" {
search -sf /${isopath}/${isoname}
loopback iso /${isopath}/${isoname}
linux (iso)/live/vmlinuz fromiso=${isopart}/${isopath}/${isoname} boot=live config utc=yes locales=us quiet
initrd (iso)/live/initrd.img
}
...
woud give rise to double // slashes,
Code:
search -sf //Hellfire/${isoname}
loopback iso //Hellfire/${isoname}
linux (iso)/live/vmlinuz fromiso=${isopart}//Hellfire/${isoname} boot=live config
and would it matter? |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: Loading Hellfire image from HD
Verfasst am: 13.05.2011, 02:42 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16790
|
|
| i see no reason for //, can you tell me which bootloader you use? grub2 is really common. |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: Loading Hellfire image from HD
Verfasst am: 13.05.2011, 20:39 Uhr
|
|
Anmeldung: 09. Mai 2011
Beiträge: 74
|
|
|
|
|
|
|
|
|
Titel: Re: Loading Hellfire image from HD
Verfasst am: 14.05.2011, 01:10 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16790
|
|
| Grub 1 can not be used that way, there is no loopback support. In that case you extract the live dir - best rename it to kanotix and use live-media-path=kanotix as extra option to the default options - but WITHOUT fromiso option - or extract just kernel + initrd and use fromiso. |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: Loading Hellfire image from HD using GRUB (Version 0.96)
Verfasst am: 15.05.2011, 01:19 Uhr
|
|
Anmeldung: 09. Mai 2011
Beiträge: 74
|
|
|
Kano hat folgendes geschrieben::
Grub 1 can not be used that way, there is no loopback support. In that case you extract the live dir - best rename it to kanotix and use live-media-path=kanotix as extra option to the default options - but WITHOUT fromiso option
Thanx. 
TheOne hat folgendes geschrieben::
Well you see not every part on the Wiki is up-to-date. There is a lack of men power to hold the Wiki in a good shape. Feel free to help and fix it. ... So you are really welcome to help.
Thanks, TheOne
For the Record:
Code:
# mkdir /mnt/kix
# mkdir /kanotix
# mount -t iso9660 -o loop,ro /Hellfire/hf.iso /mnt/kix
# cp -a /mnt/kix/live/* /kanotix
# ls -l /kanotix
-r--r--r-- 1 root root 26399 Mar 2 04:47 filesystem.packages
-r--r--r-- 1 root root 1103929344 Mar 2 04:46 filesystem.squashfs
-r--r--r-- 1 root root 19970691 Mar 2 04:47 initrd.img
-r--r--r-- 1 root root 165084 Mar 2 04:47 memtest
-r--r--r-- 1 root root 4533424 Mar 2 04:47 vmlinuz
Edit: menu.lst
Code:
title Hellfire Live - GFX - EN
root (hd0,0)
kernel /kanotix/vmlinuz live-media-path=kanotix boot=live config utc=yes locales=us quiet gfx=on
initrd /kanotix/initrd.img
|
|
|
| |
|
|
|
|
|
|
|
Titel: Loading Hellfire image from HD using GRUB (Version 0.96)
Verfasst am: 16.05.2011, 22:47 Uhr
|
|
Anmeldung: 09. Mai 2011
Beiträge: 74
|
|
There is a rider to be appended here.
If there is a top level directory of the same name, as that given in 'live-media-pathh=' , in another partiition as well, then that directory could be used resulting in a crash thru picking up the wrong version. |
|
|
| |
|
|
|
|
|
|
|
Titel: Loading Hellfire image from HD using GRUB (Version 0.96)
Verfasst am: 17.05.2011, 08:35 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16790
|
|
Thats correct, you can specify
live-media=/dev/sdx |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 18.05.2011, 07:05 Uhr
|
|
Anmeldung: 02. Mai 2004
Beiträge: 471
Wohnort: Portland, OR, USA
|
|
This would be a good time to link to the Debian Live wiki on how to add a "persistent home" to your "poor man's installation".
The short version:
- Create and format a loopback file named "live-rw"
- Put it at the root of a formatted partition (I'd guess it has to be a different partition than the one you have the kernel, initrd, and sqashfs images saved to)
- Put the cheatcode "persistent" in your kernel line
So your GRUB1 (not GRUB2) entry might look like this. (In this example the kernel, initrd.img, and squashfs image are saved at /dev/sda3/mnt/kanotix and the loopback image is at the root of another partition, both ext3-formatted.)
Code:
title Kanotix PMI
root (hd0,2)
kernel /mnt/kanotix/vmlinuz \
live-media-path=mnt/kanotix \
boot=live \
config \
utc=no \
locales=en_US \
timezone=America/Los_Angeles \
quiet \
persistent
initrd /mnt/kanotix/initrd.img
boot
|
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 18.05.2011, 07:58 Uhr
|
|
Anmeldung: 06. Jan 2005
Beiträge: 638
|
|
for persistence I use a separate partition rather than a loopback file. I give a label to this (ext3-formated) partition: live-rw.
The entry "persistent" in Grub will then cause all changes made to the live system to be put into this live-rw-partition. Upon reboot these changes are loaded into the live system. They also can easily be inspected there....... |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 18.05.2011, 11:53 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16790
|
|
@eco2geek
The "/mnt" looks weird in your example. Also the last "boot" is not needed. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 19.05.2011, 02:39 Uhr
|
|
Anmeldung: 02. Mai 2004
Beiträge: 471
Wohnort: Portland, OR, USA
|
|
You're right, it works equally well without "boot" at the end and with "live-media-path=/mnt/kanotix".
Is there a replacement for the "noeject" cheatcode, which no longer works? |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 19.05.2011, 17:26 Uhr
|
|
Anmeldung: 09. Mai 2011
Beiträge: 74
|
|
|
eco2geek hat folgendes geschrieben::
This would be a good time to link to the Debian Live wiki on how to add a "persistent home" to your "poor man's installation".
The short version:
- Create and format a loopback file named "live-rw"
- Put it at the root of a formatted partition (I'd guess it has to be a different partition than the one you have the kernel, initrd, and sqashfs images saved to)
Code:
# Create an empty ramdisk image
$ dd if=/dev/null of=live-rw bs=1G seek=1 # for a 1GB sized image file
# Make it an ext2 mountable file system
$ /sbin/mkfs.ext2 -F live-rw
Seems to me to be more flexible to have a file which one can move around, rather than to be bound to a particular partition. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 20.05.2011, 09:52 Uhr
|
|
Anmeldung: 02. Mai 2004
Beiträge: 471
Wohnort: Portland, OR, USA
|
|
|
Tejas hat folgendes geschrieben::
Seems to me to be more flexible to have a file which one can move around, rather than to be bound to a particular partition.
Why? Are you planning on moving around the 1.1 GB squashfs file between partitions, too? 
Seriously, those instructions say the "live-rw" file just has to be at the root of a partition that can be found and read. It's not tied to any particular partition. |
|
|
| |
|
|
|
|
|
|
