Of course it's *based* on a well-known distro. Actually it will almost *be* the original distro. The difference is that instead of installing rmps or debs, we install a snapshot of a healthy, tuned system.No clear indication how to update the system, security fixes, bug fixes etc. For that, you need to essentially base your distro on a well-known one - back to fights?
Minus answering a lot of questions ("Are we installing workstations? What security level?") and needing to install the patches individually. Taking away a lot of opportunities for human errors.Now, doesn't your process consist of essentially the same stages as the regular install: pop a disk in, partition the drive, transfer the packages to the disk in one form or another?
What probably would be useful is a post-install script or somethingWhy more useful? If we want a certain final result, why not go for it directly? Scripts are nice, but it takes time to write them, and sometimes we also write bugs.
that will add locally useful packages and configure a few things. And
maybe a CD with a full current set of updates.
As for the hardware setup that Ori mentioned, I believe that a single run of kudzu will do this as graceful as the installation script.
Eli
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
