[sclug] Debian production release question

[Pieter Claassen]

This is a general question on how would you do it:

I am building two standard Debian systems that will always (hopefully) run
on the same hardware.
System 1:
Desktop system
2.4.x kernel
XWindows and KDE 2.0
OpenOffice
Printer support
Networking

System 2:
Security distro running of CDROM
Custom compiled kernel
Some security software such as Snort, Iptables
MySQL, Perl, PHP, ACID etc.

My idea until now has been:
1. Use my stable Debain development machine to download required sources
etc.
2. Create two custom installs on two separate partitions.
3. dd the relevant partitions to media of choice (new HD or CD) as required.
4. Make sure that the new systems are configured correctly (what needs to
change to make the CD version bootable?) and install a boot loader as
relevant. (how does one install a boot loader for a CD installation?)

Any suggestions and/or comments?
Thanks,
Pieter
-----------------------------
Pieter Claassen
pieter at openauth.co.uk
http://www.openauth.co.uk

OpenAuth
Tel: 01344 390530
DDI: 01344 390630/390631
Fax number: 01344 390700
Mobile:  0776 665 6924

Highview House
Charles Square
Bracknell
Berkshire
RG12 1DF

TERMS AND CONDITIONS
(i)The information contained in this email and attachments is only intended
for the addressed recipient(s) and may not be distributed or viewed by any
other party without the explicit consent of the sender. If you have received
this message by accident, please contact Pieter Claassen
(pieter at openauth.co.uk) and destroy any electronic or physical copies of the
information contained in it, immediately.
(ii)This email is not certified to be virus free and OpenAuth accepts no
liability for losses arising from you receiving this email.
(iii)Any digital signatures (if present) used to authenticate this email,
only serves to allow you to verify the originating email address of the
sender and should not be relied upon to prove identity or base financial
transactions on, unless the Certificate Practice Statement that the
signature references, explicitly states differently.
(iv)This email may be subjected to further terms and conditions as published
on the company website at http://www.openauth.co.uk. If you need to rely on
the information contained in this email in any way, then you should read
those terms and conditions to understand how much you can trust the
information in this email.