Other Help Topics :: Booting, Backup, My DSL on CDRW?



This is how its worked so far.  I checked mkmydsl and basicly shredded it.  I broke it into is parts.  It was only needed to copy KNOPPIX and the boot image once (and there was no chance of running toram with all the extensions).  Then I copied extensions to the directory in mydsl and optional.  Added whatever I wanted to the backup but excluded the backup device file. Backed up to a hard drive partition then copied the backup to the directory.  Then edited the boot cheat codes by hand.  now reboot with dsl base norestore toram, mounted the partition with this directory and my changed version of the script which from here just creates the iso and burns it.  (remembering of course to change the cd).  I did add a line that quick blanks the cd-rw before burning.  very convenient for experimenting.

mkisofs and cdrecord are surprisingly easy to use from the command line.

I used the cheat codes mydsl=scd0 restore=scd0.  which seems to be bring back any custom configurations so far.  The only thing I noticed is mydsl is now mounted read only so optionals can't put  anything there.  But thats not a problem because they can go some place else handy   And I would more then likely want to do a short script that would load the extension and any dependencies then restore configurations from a different backup and start it.  As far as backing up files (documents etc...), I noticed some time back, but didn't pay much attention at the time, tar has a progressive backup for tape drives.  Crosses my mind that that might work for multisession.  Also noticed that cdrecord has options to unclose or blank the last session.  As long as the drive can boot, and my ancient TDK burner and my Toshiba 520 CDT have no problem booting multisession.

Thanks, I'm having more fun with this than could possibly be legal.

p.s. I have run into one other thing.  Some newer computers no longer come with a restore CD or anything and are factory set in bios to boot from hard drive first.
Quote
I did add a line that quick blanks the cd-rw before burning.  very convenient for experimenting.
Afaik you don't need to quick blank the whole cd, as using newer tracks that have files of the same name will be seen instead.

Quote
mydsl=scd0 restore=scd0
iirc, the cd is also autosearched for those, but this may be handy if the cd isn't necessarily the first device looked at.

Quote
p.s. I have run into one other thing.  Some newer computers no longer come with a restore CD or anything and are factory set in bios to boot from hard drive first.
I'm guessing restore CD's depends on your system builder...  Having the bios boot from hdd first could be for boot speed or perhaps a security measure.
Quote
Quote
mydsl=scd0 restore=scd0
iirc, the cd is also autosearched for those, but this may be handy if the cd isn't necessarily the first device looked at.
Exactly.  Otherwise it restores from hard drive.
Quote
Quote
I did add a line that quick blanks the cd-rw before burning.  very convenient for experimenting.
Afaik you don't need to quick blank the whole cd, as using newer tracks that have files of the same name will be seen instead.
I was using just what is in mkmydsl to burn the iso.  If I don't blank first the burn fails.  I will play some more with the command line options for cdrecord.
I am continuing this at
http://damnsmalllinux.org/cgi-bin....981&st=
I think that is where this realy belongs after reading the hacking DSL page.
thanks so much everyone
Quote (spark-o-matic @ April 06 2008,16:46)
Quote
Quote
I did add a line that quick blanks the cd-rw before burning.  very convenient for experimenting.
Afaik you don't need to quick blank the whole cd, as using newer tracks that have files of the same name will be seen instead.
I was using just what is in mkmydsl to burn the iso.  If I don't blank first the burn fails.  I will play some more with the command line options for cdrecord.

To add new tracks is a bit different.  You wouldn't burn an entire .iso but just the tracks that contain the updated files.  This way the burn process is much faster.  I haven't done this at the command line before though.
Next Page...
original here.