How To: Remaster LiveCD from LiveCD without pain :-)

[gliezl]

WOW! Enormous amount of information. Thank you Henrique. I just used your custom made script for me just once. Yet I'm not successful with that. I tried your script (the one without SCSI Emul) that one worked. First I borrowed an empty hard drive and format it to EXT2. Then told script to put remaster files on that hard drive. All went well . I will be uploading a screeshot soon. My problem is that I already exceeded maximum requirement or Forum won't allow anymore.

Again, thanks Henrique!


P.S. Will this remaster able to install to hard-disk?

[gliezl]

On my first remaster, my error is that it stop at this message;
RAMDISK: Compressed image found at block 0
Then on my second remaster, my error message is;
No space left on device

I think the image.gz cannot fit to RAM.

This is the result df -m


I added Mozilla themes, wine, VNC, & Rox 2.3 & Yahoo Messenger clone. I moved the /root/my-applications directory to /usr and created a symlink to /root and I used your remaster script (no SCSI emul)

Any advice?

[gliezl]

This is how my Puppy remaster looks like...

[Alienx]

hehe, I can see me in the screenshot !

am I beautiful ?

[gliezl]

Just curious. How will I know what to put in the ramdisk_size parameter in isolinux.cfg after the image.gz compressed? Especially if I will not use PUP001 wherein you cannot save your settings...

What will I do?

[Alienx]

Just curious. How will I know what to put in the ramdisk_size parameter in isolinux.cfg after the image.gz compressed?

the script did it automatically for you

but you want to know how to it manually after the image.gz compressed ?

it's easy , do gunzip image.gz

the size of file image in kilobytes is what you will put in ramdisk_size=

[gliezl]

wow that's great!
thank you.

[gliezl]

Hi Henrique, why does my remaster display an error buring bootup something like this;

Cannot STAT /usr : No such file or directory



Then followed by this;



What's wrong with my remaster cd?

[Guest]

Bootscreen timeout seems to be missing after remaster?

[Alienx]

Bootscreen timeout seems to be missing after remaster?

yes, it was changed, there is no picture and text is other also

timeout is 600s but it can be easily changed

when paused, before creating final iso, you can edit file isolinux.cfg in the remaster folder

or before starting script edit it directly,it's easy

[PeterSieg]

Need overview of scripts - please...

Hi AlienX. Could you please be so kind and make some kind of overview
of the remaster scripts you have created, how to use them,
what they do and where should one select this or that script...

Thanks, PS

Idealy, would be some kind of a menu with these/all scripts together
with a help file explaining the differences etc.

[Alienx]

The most updated versions are:

1-remaster-livecd-0.0.4.tar.gz

http://www.murga.org/%7Epuppy/download.php?id=1121

2-remaster-livecd-fast.tar.gz

http://www.murga.org/%7Epuppy/download.php?id=1183

(experimental, not yet tested by me in real burning and booting, the main difference is that it doesnt touch usr_cram.fs, the changes to folder /usr goes to usr_more.sqs,very fast, the remaster is done in a minute or two)


How to use both of them:

1-Boot Puppy 1.05 or 1.06 live cd (dont use Puppy installled on hd)

2-install whatever you want: dotpups or pupgets

3-do some cleanup of your /root folder (dont let movies, mp3 or any big files on /root/my-docuyments and /root)

4-run the script

5-the main and first question the script do is where to create the remaster folder

dont choose any folder inside /root, it will not work

choose a folder on a ext2 or ext3 partition on hd with enough space (about 300 mb)

if you have a lot of ram (768 or more) you can accept the default (/mnt/remaster) and do all work in ramdisk

6-burn the iso that will be in the remaster folder you have choosed


The script do all for you, is fully automatic: creates a new image.gz, put the ramdisk_size= value in isolinux.cfg and creates a new usr_cramfs or usr-more.sqs and the final iso

TIP:

when we install a lot of dotpups, folder /root/my-applications becomes big and then file image.gz also

this is not good for low ram computers

so I suggest that before renning script user moves /root/my-applications to /usr and symlink it back to /root, file image.gz will be smaller

[Guest]

so I suggest that before renning script user moves /root/my-applications to /usr and symlink it back to /root, file image.gz will be smaller

Sorry to ask - how to do it ?

[Alienx]

so I suggest that before renning script user moves /root/my-applications to /usr and symlink it back to /root, file image.gz will be smaller

Sorry to ask - how to do it ?

you can do it with mc (midnight cmmander, a dotpup), rox or manually at console:

mv /root/my-applications/ /usr

ln -sf /usr/my-applications /root

[Guest]

Thank you - very much. And thank you for your nice work.

[PeterSieg]

Thanks AlienX. I have added your information on the wiki:

http://puppylinux.org/wikka/RemasterThings

I think your second script could also offer to only create the usr_more.sfs..?!
If you know, that the dotpups etc, that you are installed only under /root/.usr
than that should work... But probably, you never know...

Great work!

PS

[Alienx]

I think your second script could also offer to only create the usr_more.sfs..?!

or maybe

to create a separate script to do only this, a usr_more-maker

the main idea of script is to make the job the more simple as possible with so few questions "keep it simple, stupid"

the first version had not even that second question and pause, was just choose the folder and get the iso

I think that is good for newbies

[Alienx]

Thank you - very much. And thank you for your nice work.

I'm happy that people are happy with their remasters

and for contributing to our lovely Puppy

[zeke7237]

Trying to use AlienX's .4 script, and it seems that it's creating image-new too small (as I get out of space errors when it's getting loaded up). Anyone else run into this? It appears that the loop file size is set to the same size as the generated 'image' file, which seems like it should work .. but I get pages of these:

cp-FULL: cannot create directory `/mnt//remaster/image-new/root0/.tkdvd': No space left on device
cp-FULL: cannot create directory `/mnt//remaster/image-new/root0/archive': No space left on device
cp-FULL: cannot create directory `/mnt//remaster/image-new/root0/dotpups-downloads': No space left on device
cp-FULL: writing `/mnt//remaster/image-new/root0/.mailcap': No space left on device
cp-FULL: writing `/mnt//remaster/image-new/root0/.fonts.cache-1': No space left on device


zeke7237

[Alienx]

maybe the folder you have choosed for remaster (first question) isnt in a linux partition with enough free space (300-400 mb)