ow you can sometimes miss error mesages if you don't
look for them. Perhaps it's luck that it succeeds? I still believe
this is an inconsistency that needs to be fixed for all.
-mark
Message: 4
Date: Thu, 10 Jun 2004 14:39:29 +0100
From: Graham Purcocks <[EMAIL PROTECTED]>
Organiz
I used SI on a Redhat ES 3.0 system with grub and it installed the
system fine but wouldn't boot as it couldn't find the SCSI controller
which was different from the Gold. I used the original ES discs to do a
minimum intstall to get the correct SCSI driver and it was fine after that.
So does th
I used SI on a Redhat ES 3.0 system with grub and it installed the
system fine but wouldn't boot as it couldn't find the SCSI controller
which was different from the Gold. I used the original ES discs to do a
minimum intstall to get the correct SCSI driver and it was fine after that.
So does th
autoinstall script and have it take affect for all the clients with soft
links pointing to it.
If you need a customized script for an individual client, you can break
the link, and make that client's hostname.sh script different.
Cheers, -Brian
Thus spake Graham Purcocks ([EMAIL PROTECTED]):
Thank
I tried the archives but didn't see anything relevant.
Basically I have a hand crafted autoinstall script and using local.cfg
to define IP address, etc. But when it gets to loading the script it
attempts to pull .master rather than the .sh which
I expected.
What is the correct way to solve thi
I tried the archives but didn't see anything relevant.
Basically I have a hand crafted script and using local.cfg to define IP
address, etc. But when it gets to loading the script it attempts to pull
.master rather than the .sh which I expected.
What is the correct way to solve this?
Thanks
Gr
