Nik Clayton wrote:
On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote:
I'm wondering if there might not be a way to streamline this install
process, such that a boot floopy and script could be created to take a
minimum amount of information, and then "do the right thing" as
On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote:
I'm wondering if there might not be a way to streamline this install
process, such that a boot floopy and script could be created to take a
minimum amount of information, and then "do the right thing" as for the
install.
Perhaps this would be of interest in CURRENT issues:
We have several servers that we plan on deploying across the US. Their
purpose in life is network status and monitoring. The hardware profiles
are exactly the same...
Currently, we're using DD to mirror a disk image onto a new
In message [EMAIL PROTECTED], Forrest Aldrich writes
:
Perhaps this would be of interest in CURRENT issues:
We have several servers that we plan on deploying across the US. Their
purpose in life is network status and monitoring. The hardware profiles
are exactly the same...
Currently,
Perhaps this would be of interest in CURRENT issues:
We have several servers that we plan on deploying across the US. Their
purpose in life is network status and monitoring. The hardware profiles
are exactly the same...
Currently, we're using DD to mirror a disk image onto a new
In article [EMAIL PROTECTED], Rodney W. Grimes
[EMAIL PROTECTED] wrote:
A much faster way to do this is to just dd the first few megabytes
of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use
dump | restore to populate the disk.
Do you run newfs on the receiving disk before
In article [EMAIL PROTECTED], Rodney W. Grimes
[EMAIL PROTECTED] wrote:
A much faster way to do this is to just dd the first few megabytes
of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use
dump | restore to populate the disk.
Do you run newfs on the receiving disk
