[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: fedora 8 static ip not accepted

I posted a possible solution to redhat bugzilla

Install the anaconda source rpm and prepare the sources
with rpmbuild -bp <specfile> (in /usr/src/redhat/SPEC/)
They are in /usr/src/redhat/BUILD/anaconda.xxx

Enter the directory loader2 and edit file loader.c as explained on bugzilla.
Change directory to the anaconda root dir ( ../ ) and do make.

Now you have to copy loader2/loader inside the initrd.img of the
isolinux directory. It's a gzipped cpio archive

To open it copy it to a tmp dir then
mkdir initrd.dir
cd initrd.dir
zcat ../initrd.img | cpio -idv

Copy inside bin/ the previously compiled loader then recreate the
Inside initrd.dir do
find . -print | cpio -o -c --quiet | gzip -c9 > ../initrd.img.new

And finally copy the inird.img.new as initrd.img inside the isolinux/
directory, the one you use for creating kickstart cd's.

Matteo Faleschini

Edwind Richzendy Contreras Soto wrote:
> My kickstart file is:
> install
> network --device eth0 --bootproto static --noipv6 --ip 192.168.X.XXX--netmask
> --gateway 192.168.X.XXX --nameserver 192.168.X.XXX --hostname
> url --url http://192.168.X.XX/linux/f8/releases/Everything/i386/os
> keyboard la-latin1
> lang es_ES.UTF-8
> xconfig --startxonboot
> auth --useshadow  --enablemd5  --enableldap --enableldapauth --ldapserver=
> 192.168.X.XXX -ldapbasedn=ou=People,dc=XXXX,dc=XXX,dc=XX
> rootpw  --iscrypted $1$NxRxxxxvxNxvxSd$fboxXxwZxxcLSGxAx68xuxyxsxyxEx6xBu5/
> firewall --enabled --port=22:tcp
> authconfig --enableshadow --enablemd5
> selinux --enforcing
> timezone --utc America/Caracas
> bootloader --location=mbr --driveorder=sda --append="vga=791 rhgb quiet"
> --md5pass=$1$/v6xxNxxgx05A$BxFxxYxbxsxOxaxbx7xkxEBxUixuxBxlxdxxx1h0
> # The following is the partition information you requested
> # Note that any partitions you deleted are not expressed
> # here so unless you clear all partitions first, this is
> # not guaranteed to work
> clearpart --all --drives=sda
> part /boot --fstype ext3 --size=200 --ondisk=sda
> part pv.6 --size=0 --grow --ondisk=sda
> volgroup VolGroup00 --pesize=32768 pv.6
> logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=576
> logvol /home --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=60000
> logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=496
> --grow --maxsize=992
> logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=14496
> repo --name=XXXXX-Livna  --baseurl=http://192.168.X.XX/linux/f8/livna/i386/
> repo --name=XXXX-Update  --baseurl=http://192.168.X.XX/linux/f8/updates
> #reboot after install
> reboot --eject
> %post
> echo "session required        pam_mkhomedir.so skel=/etc/skel/ umask=0022"
>>> /etc/pam.d/gdm
> %packages
> packages
> ...
> ...
> ...
> i put a kickstart from http server and it's is my boot line:
> boot: linux ks=http://192.168.X.XX ip=192.168.x.xx netmask=
> 192.168.x.xx
> ip and gateway ips in boot line same equal to a ip and gateway ips to
> network line in kickstart file.
> but my instalation is frozen in a infinite loop searching a DHCP server
> after read and put kickstart file.
> What is wrong?
> 2007/12/15, Edwind Richzendy Contreras Soto <richzendy gmail com>:
>> 2007/12/15, Matteo Faleschini <matteo faleschini fisica unimi it>:
>>> I'm having problems to use this option inside the kickstart file
>>> network --bootproto=static --device=eth0 --gateway=
>>> --ip= --netmask= --onboot=on
>>> with a nfs or http installation.
>>> nfs --server ksbox.local.domain --dir /fedora/8.0/os
>>> In our departement we use a templating system that we wrote  since
>>> redhat 9 to fedora 6 (and scientific linux 4, a redhat derived) without
>>> problems.
>>> When I prepared the kickstart for the new fedora 8, I noticed that
>>> anaconda ( does not use the static ip information provided by
>>> the kickstart and chooses a dhcp configuration.
>>> To verify that it is not an error of our kickstart creator, I prepared a
>>> kickstart file on a fedora 8 machine with the system-config-kickstart
>>> script. But I found the same problem.
>>> I also switched the network and nfs lines but i found no difference.
>>> At first I thought about a new anaconda behaviour (nfs install uses only
>>> dynamic configuration) but having a look at the source code of the
>>> anaconda loader I have the impression that the network bootstrap follows
>>> the same principles.
>>> I searched through the mailing list for keywords bootproto and
>>> with no success. I also googled about but i did not find any hint. I
>>> don't know if it's a known anaconda issue or a syntax error of my
>>> kickstart.
>>> Matteo Faleschini
>> i have a same problem, it's a bug in anaconda for fedora 8?
>> _______________________________________________
>>> Kickstart-list mailing list
>>> Kickstart-list redhat com
>>> https://www.redhat.com/mailman/listinfo/kickstart-list
> ------------------------------------------------------------------------
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list redhat com
> https://www.redhat.com/mailman/listinfo/kickstart-list

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]