On Wed, 12 Aug 2009, nate wrote:
> James A. Peltier wrote:
>
>> window during installation? It poses a security risk for unattended
>> installs.
>
> Unattended? use serial console
>
> Even if you don't have one, doesn't matter since it's unattended!
>
> nate
noshell was just what I needed. The
James A. Peltier wrote:
> window during installation? It poses a security risk for unattended
> installs.
Unattended? use serial console
Even if you don't have one, doesn't matter since it's unattended!
nate
___
CentOS mailing list
CentOS@centos.or
On Wed, 12 Aug 2009, James Pearson wrote:
> James A. Peltier wrote:
>> Hi All,
>>
>> I'm trying to figure out where the inittab is for a pxeboot/kickstart
>> installation so that I can disable virtual terminals that allow for
>> interactive input such as CTRL+ALT+F2. I've looked in the /etc
>> di
James A. Peltier wrote:
> Hi All,
>
> I'm trying to figure out where the inittab is for a pxeboot/kickstart
> installation so that I can disable virtual terminals that allow for
> interactive input such as CTRL+ALT+F2. I've looked in the /etc
> directories for the pxeboot initrd as well as the
On Wed, 12 Aug 2009, Brian Mathis wrote:
> Those terminals are started in the inittab file. Looks for the
> "mingetty" lines.
Clicked send to quickly. I know that the file name that I am looking for
is inittab, however, none of the image files seem to contain it. In fact,
after the kickstart
On Wed, 12 Aug 2009, Brian Mathis wrote:
> Those terminals are started in the inittab file. Looks for the
> "mingetty" lines.
I know that much but I can't find the file that contains inittab
--
James A. Peltier
Systems Analyst (FASNet), VIVARIUM Technical Director
HPC Coordinator
Simon Fraser
Those terminals are started in the inittab file. Looks for the
"mingetty" lines.
On Wed, Aug 12, 2009 at 2:58 PM, James A. Peltier wrote:
> Hi All,
>
> I'm trying to figure out where the inittab is for a pxeboot/kickstart
> installation so that I can disable virtual terminals that allow for
> in
7 matches
Mail list logo
