Hi
On Wed, Feb 04, 2009 at 11:48:29AM +0100, Isaac Hailperin wrote:
> I don't have problems either. In fact, ksdevice=bootif does not work for
> me.
try ksdevice=link if you only have one interface plugged
Tru
--
Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance)
http://pgp.mit.edu:1
Isaac Hailperin wrote:
>>> I don't have problems either. In fact, ksdevice=bootif does not work for
>>> me.
>> How many NICs and connections do you have?
> Two. Both are connected, but on one network there is nothing happening
> at that stage, meaning no servers offering any services.
>
Mine us
> > I don't have problems either. In fact, ksdevice=bootif does not work for
> > me.
>
> How many NICs and connections do you have?
Two. Both are connected, but on one network there is nothing happening
at that stage, meaning no servers offering any services.
Isaac
___
Isaac Hailperin wrote:
>
>>
>>> The order of NIC detection/naming at bootup seems to be more or less
>>> random as of Centos 5.x. How do you know which name to choose here?
>> I find that I don't have any problems with this. I usually disable dhcp on
>> eth1 and have no cable in it during instal
On Wed, Feb 04, 2009 at 11:48:29AM +0100, Isaac Hailperin wrote:
...
> I don't have problems either. In fact, ksdevice=bootif does not work for
> me.
please trim your footer/disclaimer when sending to a public mailing list
or send from another email adress.
Thanks,
Tru
--
Tru Huynh (mirrors, Ce
On Wed, 2009-02-04 at 11:31 +0100, Kai Schaetzl wrote:
> Les Mikesell wrote on Tue, 03 Feb 2009 11:17:15 -0600:
>
> > The order of NIC detection/naming at bootup seems to be more or less
> > random as of Centos 5.x. How do you know which name to choose here?
>
> I find that I don't have any pro
On Tue, 2009-02-03 at 18:39 +0100, Ian Forde wrote:
> In order to avoid this, you can use the "ksdevice=bootif" to use the
> interface from which the system booted...
good to know, thank you.
Isaac
_
Vorstand: Ertu Uysal, Axel Qu
Les Mikesell wrote on Tue, 03 Feb 2009 11:17:15 -0600:
> The order of NIC detection/naming at bootup seems to be more or less
> random as of Centos 5.x. How do you know which name to choose here?
I find that I don't have any problems with this. I usually disable dhcp on
eth1 and have no cable
>-Original Message-
>From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of
>Isaac Hailperin
>Sent: Wednesday, February 04, 2009 11:13 AM
>To: CentOS mailing list
>Subject: Re: [CentOS] kickstart won't kick-off via network
>
>
>&g
> Especially since FDD aren't that common anymore... I'll see if I can't adapt
> my SOP:s to boot and install from network.
The set up is actually not too complicated. I really recommend it, you just
plug in
the computer and let it install.
There are various variants, you can either define what w
>-Original Message-
>From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of
>Isaac Hailperin
>Sent: Tuesday, February 03, 2009 4:56 PM
>To: CentOS mailing list
>Subject: Re: [CentOS] kickstart won't kick-off via network
>
>Now i
Ian Forde wrote:
>
> append initrd=distro/centos5.2/initrd.img ramdisk_size=7494
> ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic
to
use etc. I think there is a tutorial about doing PXE in
On Tue, Feb 03, 2009, Les Mikesell wrote:
>Isaac Hailperin wrote:
>> On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
>>> Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
>>>
append initrd=distro/centos5.2/initrd.img ramdisk_size=7494
ks=http://9.0.0.1/all/profiles/cluto_ce
On Tue, 2009-02-03 at 11:17 -0600, Les Mikesell wrote:
> Isaac Hailperin wrote:
> > On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
> >> Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
> >>
> >>> append initrd=distro/centos5.2/initrd.img ramdisk_size=7494
> >>> ks=http://9.0.0.1/al
Isaac Hailperin wrote:
> On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
>> Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
>>
>>> append initrd=distro/centos5.2/initrd.img ramdisk_size=7494
>>> ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
>> this is not enough, you
On Tue, 2009-02-03 at 15:42 +0100, Kai Schaetzl wrote:
> Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
>
> > append initrd=distro/centos5.2/initrd.img ramdisk_size=7494
> > ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
>
> this is not enough, you have to tell PXE about t
> >Now since I get asked all these questions at boot time, I suspect that
> >the kickstart file is not there to answer these questions.
>
> It does use it, it just doesn't find the network-block in ks.cfg. Does your
> ks.cfg contain some lines for the networking?
Yes:
# Kickstart file automatic
Isaac Hailperin wrote on Tue, 03 Feb 2009 14:45:44 +0100:
> append initrd=distro/centos5.2/initrd.img ramdisk_size=7494
> ks=http://9.0.0.1/all/profiles/cluto_centos5.2/cnode/ks.cfg
this is not enough, you have to tell PXE about the network, which nic to
use etc. I think there is a tutorial abou
>-Original Message-
>From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of
>Isaac Hailperin
>Sent: Tuesday, February 03, 2009 2:46 PM
>To: centos@centos.org
>Subject: [CentOS] kickstart won't kick-off via network
>
>What I did:
>Fi
Hello list,
I try to do an automated network installation of centos 5.2, following
the redat documentation at
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/pt-install-info.html
However, when installing I get promptet for various things, like which
network interface I w
20 matches
Mail list logo
