Subject: | |
From: | |
Reply To: | Johnson, Kent A (GE Healthcare) |
Date: | Thu, 11 Aug 2011 10:23:42 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi Tom et.al.
It didn't complain and apparently ignored the ksdevice= then.
In any case, the problem has been worked around for now, simply by
adding the --activate option to the KS network line.
Now, instead of NM popping up an edit query after disk partitioning, it
posts a message only before disk partitioning saying "NM is activating
eth0" and everything proceeds to work fine completely unattended.
Thanks to you and the others for your help and suggestions. I'm really
impressed by everyone's willingness to help on the list!
Best Regards,
kent
-----Original Message-----
From: [log in to unmask]
[mailto:[log in to unmask]] On Behalf Of Tom
H
Sent: Thursday, August 11, 2011 9:00 AM
To: [log in to unmask]
Subject: Re: SL6.1 kickstart persistent networkmanager prevents
unattended install
On Thu, Aug 11, 2011 at 8:13 AM, Johnson, Kent A (GE Healthcare)
<[log in to unmask]> wrote:
>
> I tried adding ksdevice=sdb (my USB ks.cfg key) to the kernel boot
line
> during installer but it made no difference. Thanks anyway!
"ksdevice=" is to specify a NIC not storage device.
|
|
|