generate iso from current filesystem

jjk · 2012-12-15 21:20:10

i installed grub and grub4dos am going to test iso booting tomorrow

kultex · 2012-12-17 09:46:06

sorry - a bit late, but research on Plop Boot Manager for another thread seems to be the possibility for Grub2

http://phanvinhthinh.blogspot.co.at/2010/08/boot-from-usb-flash-without-bios.html

its a pitty, that Elmar is not planing to add iso boot to plop boot manager - described here:

http://reboot.pro/topic/12781-plop-boot-manager-5011-released/

but maybe with syslinux installed on the disk, it should be possible

http://www.ultimatebootcd.com/forums/viewtopic.php?p=7356

http://www.rmprepusb.com/tutorials/chainload-syslinux

jjk · 2012-12-17 17:52:36

very nice, but im using grub4dos now smile

i tried this script:

title slitaz

find --set-root /boot/isos/slitaz.iso

map --mem /boot/isos/slitaz.iso (hd32)

map --hook

chainloader (hd32)

it gets stuck. I tried issuing the commands in the grub prompt, it gets stuck when i type te map --mem line. could the file be too big to get mapped to ram?

kultex · 2012-12-17 17:56:53

when it gets stuck, thats a sign, that it is to big

how much ram do you have?

jjk · 2012-12-17 17:58:17

512 Mb

the iso is 191 Mb

kultex · 2012-12-17 18:14:42

I think, that is to little, not very much, but to little.

to be on the secure side, you have to count x4 - I would say 756 MB would be enough

jjk · 2012-12-17 18:24:41

aha, anything i can do about this? i saw something about fake-write to harddrive, can I use that? or could i convert it to loram iso?

kultex · 2012-12-17 20:03:27

in your normal slitaz run

# tazlito build-loram slitaz.iso loram.iso

Creates an ISO image flavor for low ram systems from a SliTaz ISO image.

I have never tried it

jjk · 2012-12-20 18:43:03

ok i made a loram my menu.lst looks like this now:

title slitaz

find --set-root /boot/isos/slitaz-loram.iso

map --mem --heads=0 --sectors-per-track=0 /boot/isos/slitaz-loram.iso (hd32)

map --hook

chainloader (hd32)

it does map now but gives still kernel panic.

it succesfully chainloads to isolinux so i guess the problem is with isolinux

jjk · 2012-12-20 20:00:23

I am able to boot from the extracted iso file on my filesystem, could it be that there is too less ram to map the iso AND run it

Btw im content with this result

Thx a lot for your time and help kultex!!!!

kultex · 2012-12-21 18:59:17

what I would do:

boot from the cd, add some bigger apps like firefox gimp and abiword and run tazlito to make the iso and try this iso in your configuration, you have now - this should boot without any probs

when this works, then create a low ram iso from this new iso and look if this works too

maybe any problems with the menu.lst?

Here I found something for grub4dos:

title stilaz 4.0

map /boot/slitaz-4.0.iso (0xff) || map --mem /boot/slitaz-4.0.iso (0xff)

map --hook root (0xff)

chainloader (0xff)

and just here I found something for grub2 and booting 3.0 - so it should work also with bzimage in grub 2

menuentry "Slitaz 3.0" {

set isofile="/boot/slitaz-3.0.iso"

loopback loop $isofile

linux (loop)/boot/bzImage lang=en kmap=us autologin isofrom=$isofile boot=live noeject noprompt root=/dev/null

initrd (loop)/boot/rootfs.gz

}

and of course, grub legacy is also working with bzimage

so thats the question to the devs:

WHY we need bzImage and vmlinuz in the iso? - that would be 2.4 MB less !!

bellard · 2012-12-21 20:39:13

bzImage and vmlinuz-XXX are hard links. See http://hg.slitaz.org/tazlito/file/d5e9336b9867/tazlito#l240

The bzImage name is generic (for scripts)

The vmlinuz-VERSION is human readable information.

kultex · 2012-12-21 21:27:55

hi pascal,

the whole thread only exists, because tazlito is not coping vmlinuz from the iso - or CD to the new iso

is this a bug?

and about vmlinuz and bzImage - I just think, thats quite stupid to have 2 identical files in one CD quite bad invention....

bellard · 2012-12-22 09:13:35

What is stupid ?

- use the same scripts / boot config files for every kernel version (bzImage) ?

- show clearly the kernel version with ls (vmlinuz-*) ? Cost: 0 bytes (128 unused bytes - including rockridge attributes - in a iso9660 directory sector)

http://en.wikipedia.org/wiki/Hard_link

$ stat -m /media/cdrom/boot/vmlinuz-2.6.37-slitaz /media/cdrom/boot/bzImage | \

awk '{ if (prev + 1 != $1) printf("%d\n%d - ",prev,$1); prev=$1 } END { print prev }'

Only bzImage is necessary for scripts / boot config files.

kultex · 2012-12-25 15:48:03

thx pascal, I understood now Hard_link

but if I understand the tazlito receipt, bthere should be a hard link of vmlinuz lile in the normal slitaz iso, but it is not - see attachment

[attachment=19950,861] [attachment=19950,862]

SliTaz Forum

SliTaz Forum

#26 2012-12-15 21:20:10

Re: generate iso from current filesystem

#27 2012-12-17 09:46:06

Re: generate iso from current filesystem

#28 2012-12-17 17:52:36

Re: generate iso from current filesystem

#29 2012-12-17 17:56:53

Re: generate iso from current filesystem

#30 2012-12-17 17:58:17

Re: generate iso from current filesystem

#31 2012-12-17 18:14:42

Re: generate iso from current filesystem

#32 2012-12-17 18:24:41

Re: generate iso from current filesystem

#33 2012-12-17 20:03:27

Re: generate iso from current filesystem

#34 2012-12-20 18:43:03

Re: generate iso from current filesystem

#35 2012-12-20 20:00:23

Re: generate iso from current filesystem

#36 2012-12-21 18:59:17

Re: generate iso from current filesystem

#37 2012-12-21 20:39:13

Re: generate iso from current filesystem

#38 2012-12-21 21:27:55

Re: generate iso from current filesystem

#39 2012-12-22 09:13:35

Re: generate iso from current filesystem

#40 2012-12-25 15:48:03

Re: generate iso from current filesystem

Board footer