We've been doing this for Linux installs for the last 2-3 years: - Install distro - install apps - customize everything - apps, configs, desktop, templates new kernel & modules... - boot into another OS or live cd - delete/rename fstab & hwconf (hardware info for that specific machine) & IP info - bzip the image to a CD and add a small script to install - add script to install grub reboot
rinse repeat support
Its not a bad way though it remains in the hack category in my opinion.
Grub does remove windows MBR BUT after it's installed it automatically offers windows boot option on every boot (apart from the linux that you installed). At least most distros during the last 2-3 years have been doing this.
AND to boot windows all you have to do is add an option "chainloader +1" to a new boot entry. BUT when windows removes the Linux MBR there is NO WAY to boot anything else without booting from some CD/floppy/usbdisk writing new MBR installing grub/lilo etc.
Slashdot Mirror
We've been doing this for Linux installs for the last 2-3 years:
- Install distro
- install apps
- customize everything - apps, configs, desktop, templates new kernel & modules...
- boot into another OS or live cd
- delete/rename fstab & hwconf (hardware info for that specific machine) & IP info
- bzip the image to a CD and add a small script to install
- add script to install grub
reboot
rinse
repeat
support
Its not a bad way though it remains in the hack category in my opinion.
2p
Grub does remove windows MBR BUT after it's installed it automatically offers windows boot option on every boot (apart from the linux that you installed). At least most distros during the last 2-3 years have been doing this. AND to boot windows all you have to do is add an option "chainloader +1" to a new boot entry. BUT when windows removes the Linux MBR there is NO WAY to boot anything else without booting from some CD/floppy/usbdisk writing new MBR installing grub/lilo etc.