From mpjohnpaul at mail.com Tue Jun 1 05:56:07 2004 From: mpjohnpaul at mail.com (john paul) Date: Tue, 01 Jun 2004 00:56:07 -0500 Subject: Auto detection option question Message-ID: <20040601055607.42C614BDA3@ws1-1.us4.outblaze.com> An HTML attachment was scrubbed... URL: From jglass at liquidweb.com Tue Jun 1 13:30:06 2004 From: jglass at liquidweb.com (Joseph Glass) Date: Tue, 01 Jun 2004 09:30:06 -0400 Subject: Auto detection option question In-Reply-To: References: Message-ID: <1086096606.25824.6.camel@cipher.liquidweb.com> Hi David, I run a python script in the %pre section to detect what type/sizes of drives the machine has and create partitioning based on the results. A file with partitioning information is saved in the /tmp directory. This file is called from the ks.cfg from %include. If you'd like I can send you what I use and you can modify it to your needs. On Mon, 2004-05-31 at 06:53, Avrahami David wrote: > Hi , > > I am thinking of using kick start for installing the Linux(RHEL 3) on > either ide and scsii boxes. > I would like to use the same installation disk(ks.cfg) for both > installation. > I was wondering if kick start has an ability of ide/scsii auto > detection. > > Thanks in advance, > David Avrahami > Linux Platform > Tel: +972-3-6452374 > Mobile: +972-54-382374 > Email: David.Avrahami at Comverse.com > > > > ______________________________________________________________________ > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Joseph Glass Systems Administrator Liquid Web Inc. 800.580.4985 x227 From pantz at lqt.ca Tue Jun 1 14:12:08 2004 From: pantz at lqt.ca (Paul Pianta) Date: Tue, 01 Jun 2004 10:12:08 -0400 Subject: Auto detection option question In-Reply-To: <1086096606.25824.6.camel@cipher.liquidweb.com> References: <1086096606.25824.6.camel@cipher.liquidweb.com> Message-ID: <40BC8EB8.4070003@lqt.ca> Joseph Glass wrote: >Hi David, > >I run a python script in the %pre section to detect what type/sizes of >drives the machine has and create partitioning based on the results. > >A file with partitioning information is saved in the /tmp directory. >This file is called from the ks.cfg from %include. If you'd like I can >send you what I use and you can modify it to your needs. > > I would be interested in seeing it :) thanks pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From jglass at liquidweb.com Tue Jun 1 14:48:08 2004 From: jglass at liquidweb.com (Joseph Glass) Date: Tue, 01 Jun 2004 10:48:08 -0400 Subject: Disk configuration / auto detection script In-Reply-To: <1086096606.25824.6.camel@cipher.liquidweb.com> References: <1086096606.25824.6.camel@cipher.liquidweb.com> Message-ID: <1086101287.25823.58.camel@cipher.liquidweb.com> After a couple of requests I decided to post this. Attached is my whole kickstart file. Below are the sections that automatically configure the disks. The drives are configured like so: 100MB /boot on first disk 1GB / on first disk 1GB /tmp on first disk ($drive_size / 15) /usr on first disk ($drive_size / 15) /var on first disk Recommended swap size on first disk Anything left on first disk is configured as /home If there is a second disk, partition the whole thing as /backup If there is a scsi disk (/dev/sda exists): - use it as the first drive - if a second scsi disk exists use it as the second drive (/dev/sdb) - or if an ide disk exists, use it as the second drive If there are no scsi disks (/dev/sda is absent): - use /dev/hda as first drive - if /dev/hdb exists, use it as the second drive It is a somwhat static configuration, however this is our standard configuration for machines and it can be easily changed when needed. The script can't be 100% flexible without user intervention. Email me with any questions. Joe Glass ------- # I believe %include has to be before the %pre section # (Somewhat confusing in this context) %include /tmp/part-include %pre --interpreter /usr/bin/python import commands import os import string import sys import re script_name = sys.argv[0] output = commands.getoutput('fdisk -l') pattern = "sda" matchobj = re.search(pattern, output) if matchobj: scsi = "yes" else: scsi = "no" pattern = "sdb" matchobj = re.search(pattern, output) if matchobj: scsi2 = "yes" else: scsi2 = "no" pattern = "hda" matchobj = re.search(pattern, output) if matchobj: ide = "yes" else: ide = "no" pattern = "hdb" matchobj = re.search(pattern, output) if matchobj: ide2 = "yes" else: ide2 = "no" if scsi == "yes": drive1 = "sda" drive1_size = commands.getoutput('fdisk -l').strip() pattern = "sda: (\d+)" matchobj = re.search(pattern, drive1_size) if matchobj: drive1_size = matchobj.group(1) if scsi2 == "yes": drive2 = "sdb" elif ide == "yes": drive2 = "hda" if scsi == "no": if ide == "yes": drive1 = "hda" drive1_size = commands.getoutput('fdisk -l').strip() pattern = "hda: (\d+)" matchobj = re.search(pattern, drive1_size) if matchobj: drive1_size = matchobj.group(1) if ide2 == "yes": drive2 = "hdb" drive1_size = float(drive1_size) drive_size_m = int(drive1_size) * 1024 boot_size = 100; var_size = int(drive_size_m)/15 usr_size = int(drive_size_m)/15 root_size = 1024 tmp_size = 1024 f = open('/tmp/part-include', 'w') f.write("""# Drive partitioning information determined from %s clearpart --all --initlabel part /boot --fstype ext3 --size=%s --ondisk=%s --asprimary part /var --fstype ext3 --size=%s --ondisk=%s part /usr --fstype ext3 --size=%s --ondisk=%s --asprimary part / --fstype ext3 --size=%s --ondisk=%s part swap --recommended --ondisk=%s --asprimary part /tmp --fstype ext3 --size=%s --ondisk=%s part /home --fstype ext3 --size=1 --grow --ondisk=%s """ %(script_name, boot_size, drive1, var_size, drive1, usr_size, drive1, root_size, drive1, drive1, tmp_size, drive1, drive1) ) try: drive2 except NameError: f.write('# no backup selected\n') else: f.write('part /backup --fstype ext3 --size=1 --grow --ondisk=%s' % drive2) f.close() On Tue, 2004-06-01 at 09:30, Joseph Glass wrote: > Hi David, > > I run a python script in the %pre section to detect what type/sizes of > drives the machine has and create partitioning based on the results. > > A file with partitioning information is saved in the /tmp directory. > This file is called from the ks.cfg from %include. If you'd like I can > send you what I use and you can modify it to your needs. -- Joseph Glass Systems Administrator Liquid Web Inc. 800.580.4985 x227 -------------- next part -------------- # Next two lines must be consecutive install nfs --server 192.168.0.1 --dir /home/kickstart/FC1 lang en_US langsupport --default en_US.UTF-8 en_US.UTF-8 timezone America/Detroit keyboard us mouse none skipx text #reboot #reboot after install network --device eth0 --bootproto dhcp --hostname tempds1-1.liquidweb.com rootpw --iscrypted [ChangeThisHere} authconfig --enableshadow --enablemd5 bootloader --location=mbr # zerombr yes firewall --disabled %include /tmp/part-include %packages --resolvedeps @ Development Tools @ Editors @ Kernel Development @ System Tools @ Text-based Internet -irda-utils -network-server -gpm -gpm-devel %pre --interpreter /usr/bin/python import commands import os import string import sys import re script_name = sys.argv[0] output = commands.getoutput('fdisk -l') pattern = "sda" matchobj = re.search(pattern, output) if matchobj: scsi = "yes" else: scsi = "no" pattern = "sdb" matchobj = re.search(pattern, output) if matchobj: scsi2 = "yes" else: scsi2 = "no" pattern = "hda" matchobj = re.search(pattern, output) if matchobj: ide = "yes" else: ide = "no" pattern = "hdb" matchobj = re.search(pattern, output) if matchobj: ide2 = "yes" else: ide2 = "no" if scsi == "yes": drive1 = "sda" drive1_size = commands.getoutput('fdisk -l').strip() pattern = "sda: (\d+)" matchobj = re.search(pattern, drive1_size) if matchobj: drive1_size = matchobj.group(1) if scsi2 == "yes": drive2 = "sdb" elif ide == "yes": drive2 = "hda" if scsi == "no": if ide == "yes": drive1 = "hda" drive1_size = commands.getoutput('fdisk -l').strip() pattern = "hda: (\d+)" matchobj = re.search(pattern, drive1_size) if matchobj: drive1_size = matchobj.group(1) if ide2 == "yes": drive2 = "hdb" drive1_size = float(drive1_size) drive_size_m = int(drive1_size) * 1024 boot_size = 100; var_size = int(drive_size_m)/15 usr_size = int(drive_size_m)/15 root_size = 1024 tmp_size = 1024 f = open('/tmp/part-include', 'w') f.write("""# Drive partitioning information determined from %s clearpart --all --initlabel part /boot --fstype ext3 --size=%s --ondisk=%s --asprimary part /var --fstype ext3 --size=%s --ondisk=%s part /usr --fstype ext3 --size=%s --ondisk=%s --asprimary part / --fstype ext3 --size=%s --ondisk=%s part swap --recommended --ondisk=%s --asprimary part /tmp --fstype ext3 --size=%s --ondisk=%s part /home --fstype ext3 --size=1 --grow --ondisk=%s """ %(script_name, boot_size, drive1, var_size, drive1, usr_size, drive1, root_size, drive1, drive1, tmp_size, drive1, drive1) ) try: drive2 except NameError: f.write('# no backup selected\n') else: f.write('part /backup --fstype ext3 --size=1 --grow --ondisk=%s' % drive2) f.close() %post cat << EOF > /etc/resolv.conf domain liquidweb.com search liquidweb.com nameserver 198.172.239.5 nameserver 198.172.239.6 EOF /sbin/chkconfig portmap --level 345 off /sbin/chkconfig nfslock --level 345 off /sbin/chkconfig nfs --level 345 off /sbin/chkconfig isdn --level 345 off /sbin/chkconfig sendmail --level 345 off /sbin/chkconfig pcmcia --level 345 off rm -rf /root/anaconda-ks.cfg From pantz at lqt.ca Tue Jun 1 15:05:08 2004 From: pantz at lqt.ca (Paul Pianta) Date: Tue, 01 Jun 2004 11:05:08 -0400 Subject: Disk configuration / auto detection script In-Reply-To: <1086101287.25823.58.camel@cipher.liquidweb.com> References: <1086096606.25824.6.camel@cipher.liquidweb.com> <1086101287.25823.58.camel@cipher.liquidweb.com> Message-ID: <40BC9B24.8020700@lqt.ca> thanks for the script! (shame my thunderbird wasn't nice to the script tab settings :/) also ># I believe %include has to be before the %pre section > > snippet from rh73 manual --- You can add commands to run on the system immediately after the ks.cfg has been parsed. This section must be at the end of the kickstart file (after the commands) and must start with the %pre command. --- I have my %include before my %pre section too but only because my %pre section is the very last thing in my ks.cfg. Just a heads up for ya :) pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From forrestx.taylor at intel.com Tue Jun 1 16:38:31 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 01 Jun 2004 09:38:31 -0700 Subject: Fedora Kickstart In-Reply-To: <20040529090052.GA29598@ns.kevlo.org> References: <20040529090052.GA29598@ns.kevlo.org> Message-ID: <1086107911.20568.6.camel@bad.jf.intel.com> On Sat, 2004-05-29 at 02:00, Doug Lee wrote: > On Tue, May 18, 2004 at 10:55:47AM -0700, Taylor, ForrestX wrote: > > On Tue, 2004-05-18 at 10:31, mbox mbarsalou wrote: > > > There used be a wiki that had information on how to setup kickstart with > > > Fedora....anyone know where it went? I think the website was > > > rau.homedns.org. > > > > Yes, it is: > > http://rau.homedns.org/twiki/bin/view/Anaconda/AnacondaDocumentationProject > > > > Although it is mostly about anaconda and rebuilding a custom distro. > > The above url helps me a lot. But I have a question, I'm using Fedora Core 2, > it seems that comps.rpm should be rebuild on Fedora Core 2, otherwise, > I will get "cannot find CD" while booting the cdrom. > Did I miss something? thanks. Usually the 'cannot find CD' is a missing .discinfo. Did you copy/create that file on your CD? Forrest From lang at metsci.com Tue Jun 1 18:20:19 2004 From: lang at metsci.com (Lang, Clifford) Date: Tue, 1 Jun 2004 14:20:19 -0400 Subject: genhdlist problems solved under RHEL3 -- buildIso script enclosed(sorry, long) Message-ID: <9A2586DA53C29D44828E47CEFA9474D22DCC6B@mercury.metsci.com> I do not get a bootable ISO image out of this process. Has anyone else? Everything looks right, so I am not sure where to go from here. Any help would be greatly appreciated. Thanks - -cliff email: lang at metsci.com PH: 703-787-3649 -----Original Message----- From: Martin Robb [mailto:MartinRobb at ieee.org] Sent: Tuesday, May 25, 2004 5:48 PM To: kickstart-list at redhat.com Subject: genhdlist problems solved under RHEL3 -- buildIso script enclosed(sorry, long) Many thanks for the assistance from the list, especially Philip Rowlands and James Martin. My "buildIso" script is now working under both FC2 and RHEL3u2. It may even work to cross-target RHEL from an FC2 environment -- I don't have time left today to check, but since my problems were tracking 1 for 1 between targeting RHEL from RHEL and targeting RHEL from FC2, I think it's likely. For the record, using --withnumbers on the genhdlist command got me past the "/mnt/source" problem but ultimately grub failed at stage 1. Using the pkgorder command got me past the grub problem. I am enclosing the buildIso script for those interested. It is still a work in progress but is reasonably functional. It requires some supporting files which I will explain as I go. This would work a WHOLE lot better as an html message with attachments, but I don't know how well that would encapsulate in the digest or to all list members with plain mail clients. So let me apologize in advance for the lengthy plain text message. It seemed the most portable if not the most elegant. The heart of the script looks at the packages section of the ks.cfg file and expands it into a list of rpms, using the comps.xml file to expand package names into the corresponding rpms. It does NOT recursively find packages within packages. Along the way I found that both FC2 and RHEL3 have a sizeable list of rpms that are included "automagically" even in a minimal install -- even though they don't belong to any packages and aren't even listed in comps.xml. The script looks for the list of implicit rpms in the files "implicit.Fedora" and "implicit.RedHat" respectively. BTW, I obtained the list by doing a minimal install and running "rpm --query --all" and comparing the results to what I was extracting for the Base, Core and Dialup Networking Support packages. I don't know if there are other implicit RPMs for other packages. For my purposes I am always building off a minimal install. If anyone knows a more direct way to obtain this list I'd be interested in learning it. The rpms should be listed one per line, but I will join them together a bit here to save some space: The implicit.Fedora file contains: beecrypt bind-libs bzip2-libs chkconfig comps cracklib cracklib-dicts cyrus-sasl cyrus-sasl-md5 db4 dev device-mapper elfutils elfutils-libelf findutils gawk gdbm glib glib2 glibc-common gmp gnupg grep groff gzip hesiod hwdata info iptables isdn4k-utils kernel-smp krb5-libs krbafs less libacl libattr libselinux libstdc++ libuser libwvstreams libxml2 libxml2-python lockdev lrzsz lvm2 mailx make MAKEDEV mingetty mkinitrd mktemp modutils ncurses net-tools newt nscd openldap openssh openssl pam pcre perl perl-Filter popt portmap ppp procmail psmisc pyOpenSSL python python-optik pyxf86config rhnlib rhpl rmt rpm-python sed slang syslinux tar tzdata usbutils usermode which words yp-tools zlib The implicit.RedHat file contains: ash basesystem bash beecrypt binutils bzip2-libs chkconfig comps coreutils cpio cracklib cracklib-dicts cups cups-libs cyrus-sasl cyrus-sasl-md5 cyrus-sasl-plain db4 dev e2fsprogs ed elfutils elfutils-libelf ethtool expat file filesystem findutils fontconfig freetype gawk gdbm gettext glib glib2 glibc glibc-common gmp gnupg grep groff gzip hdparm hesiod hotplug htmlview hwdata info initscripts iproute iputils isdn4k-utils jfsutils jwhois kbd krb5-libs krbafs krbafs-utils less libacl libattr libgcc libgcj libjpeg libpng libstdc++ libtermcap libtiff libtool-libs libuser libwvstreams lockdev losetup lslk lsof lvm m4 mailx make MAKEDEV mingetty minicom mkinitrd mktemp modutils mount mt-st ncurses net-tools newt nscd openldap openssh openssh-server openssl pam passwd patch pcre perl perl-Filter popt portmap ppp procmail procps psmisc pspell pyOpenSSL python python-optik pyxf86config raidtools rdist readline redhat-config-mouse redhat-menus redhat-release rhnlib rhpl rmt rootfiles rpm rpm-python rp-pppoe sed sendmail setserial setup shadow-utils slang sudo sysklogd syslinux SysVinit tar tcpdump termcap traceroute tzdata up2date usbutils usermode utempter util-linux vim-minimal wget which wireless-tools words wvdial XFree86-libs XFree86-libs-data XFree86-Mesa-libGL xinetd yp-tools zlib Both FC2 and RHEL3 appear to have some "missing" files that are listed in the comps.xml file but don't exist on the disks. The installer doesn't complain but my buildIso script needs to know about them to know when to stop looking for RPMs. It looks for these in the files "missing.Fedora" and "missing.RedHat." The missing.Fedora file contains: efibootmgr elilo losetup openCryptoki ppc64-utils prctl run s390utils yaboot The missing.RedHat file contains: acpid efibootmgr elilo iprutils iscsi lrzsz openCryptoki ppc64-utils prctl reiserfs-utils s390utils statserial yaboot Finally, there may be some RPMs you want added in or left out depending on which target you've selected. These are in extra.Fedora and extra.RedHat. The extra.Fedora file contains: -at checkpolicy policy-sources The at rpm was not installing properly under FC2t3 and the -at leaves it out. This may be fixed under FC2 -- I haven't had time to check yet. The checkpolicy and policy-sources files are only of interest if you are using selinux. The extra.RedHat file contains: bridge-utils brltty I don't know that I really need either of these, but they are installed in a minimal install and they don't seem to be picked up implicitly like those listed in implicit.RedHat. So for the moment I'm including them explicitly. Before showing the buildIso script itself, I will also include an example ks.cfg file that seems to be working under both FC2 and RHEL3 and should work with this script. I've left off the %post commands and hashed out the rootpw. What's left of the ks.cfg file contains: install cdrom lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us mouse generic skipx rootpw --iscrypted ########################## firewall --disabled #selinux --disabled authconfig --enableshadow --enablemd5 timezone America/New_York bootloader --location=mbr --append hda=ide-scsi clearpart --all --initlabel part / --fstype ext3 --size 2048 part /sandbox --fstype ext3 --size 1 --grow part swap --size 1024 reboot %packages @ Core @ Dialup Networking Support @ Base # GENERIC ADDITIONS m4 libsafe tripwire # NEEDED FOR NTP libcap ntp tcl expect amhsfilter %post The buildIso script looks first for custom rpms in the CUSTOM_RPMS directory (default ../RPMs), then for replacement rpms in the PACKAGES directory (default ../Packages), and then for standard rpms on the install CDs. It lays out the ISO file directory structure under ROOTS (default ../Roots) is ${ROOTS}/IsoRoot. The script contains a lot of commented mutterings about where things resided under various RH versions. There are many apparent redundancies and out of desperation I tended to replace them all where possible. Much of this could/should be cleaned up -- but it works. The buildIso script contains: #! /bin/sh -- # # Interesting files and where they (should?) reside: # boot.iso: # images/boot.iso # (in 7.1 this was images/boot.img) # initrd.img: (first two are md5 identical in FC2t2) # isolinux/initrd.img # images/boot.iso[/isolinux/initrd.img] # images/pxeboot/initrd.img # (in 7.1 this was images/boot.img[initrd.img]) # isolinux.cfg: (identical) # isolinux/isolinux.cfg # images/boot.iso[isolinux/isolinux.cfg] # (in 7.1 this was images/boot.img[/syslinux.cfg] # ks.cfg: # /ks.cfg # isolinux/ks.cfg # isolinux/initrd.img[(gzipped)/isolinux/ks.cfg] # isolinux/initrd.img[(gzipped)/ks.cfg] # images/pxeboot/initrd.img[(gzipped)/isolinux/ks.cfg] # images/pxeboot/initrd.img[(gzipped)/ks.cfg] # (in 7.1 this was images/boot.img[(gzipped)/ks.cfg] # case `uname --kernel-release` in 2.4*) DEFAULT_TARGET=RedHat ;; 2.6*) DEFAULT_TARGET=Fedora ;; *) echo "Unrecognized kernel release `uname --kernel-release`" exit 1 ;; esac TARGET=${TARGET:-$DEFAULT_TARGET} ROOTS=${ROOTS:-`(cd ../Roots ; pwd)`} PACKAGES=${PACKAGES:-`(cd ../Packages ; pwd)`} CUSTOM_RPMS=${CUSTOM_RPMS:-`(cd ../RPMs ; pwd)`} ISO_LABEL=PinnacleCSIBastionInstall ISO_ROOT=${ROOTS}/IsoRoot ISO_NAME=${1:-BastionInstall.iso} RPMLIST_NAME=/tmp/rpmlist TMPLIST_NAME=/tmp/tmplist RPM_PATH=${TARGET}/RPMS COMPS_NAME=comps.xml COMPS_PATH=${TARGET}/base/${COMPS_NAME} HDLIST_NAME=hdlist HDLIST_PATH=${TARGET}/base/${HDLIST_NAME} # N.B. - the IsoRoot ks.cfg has extra rpm names not in the local ks.cfg KICKSTART_NAME=ks.cfg KICKSTART_PATH=${ISO_ROOT}/${KICKSTART_NAME} BOOTCAT_NAME=boot.cat BOOTCAT_PATH=isolinux/${BOOTCAT_NAME} CD_ROOT=/mnt/cdrom BOOTIMG_NAME=boot.iso BOOTIMG_PATH=images/${BOOTIMG_NAME} BOOTIMG_MOUNT=/mnt/bootimg BOOTIMG_ROOT=${ROOTS}/BootImage CONFIG_NAME=isolinux.cfg CONFIG_PATH=isolinux/${CONFIG_NAME} INITRD_NAME=initrd.img INITRD_PATH=isolinux/${INITRD_NAME} INITRD_MOUNT=/mnt/initrd Cleanup() { for FS_ROOT in ${ISO_ROOT} ${BOOTIMG_ROOT} do if [ -e ${FS_ROOT} ] then rm -rf ${FS_ROOT} fi mkdir ${FS_ROOT} done } ReplicateNonRpms() { if [ -e ${CD_ROOT} ] then sudo umount ${CD_ROOT} 2>/dev/null else sudo mkdir ${CD_ROOT} fi eject echo -n "Please insert ${TARGET} CD 1 and press ENTER: " read line sudo mount ${CD_ROOT} ( cd ${CD_ROOT} ; find . -print | grep -v RPMS | cpio -pdmvu ${ISO_ROOT} ) sudo umount ${CD_ROOT} eject chmod 644 ${ISO_ROOT}/${HDLIST_PATH} } UnpackBootIso() { if [ -e ${BOOTIMG_MOUNT} ] then sudo umount ${BOOTIMG_MOUNT} 2>/dev/null else sudo mkdir ${BOOTIMG_MOUNT} fi sudo mount -o loop -t iso9660 ${ISO_ROOT}/${BOOTIMG_PATH} ${BOOTIMG_MOUNT} mkdir ${BOOTIMG_ROOT} ( cd ${BOOTIMG_MOUNT} ; find . -print | cpio -pdmvu ${BOOTIMG_ROOT} ) sudo umount ${BOOTIMG_MOUNT} } RepackBootIso() { chmod 644 ${ISO_ROOT}/${BOOTIMG_PATH} sudo mkisofs -o ${ISO_ROOT}/${BOOTIMG_PATH} -V "${ISO_LABEL}" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -V -T ${BOOTIMG_ROOT} } # initrd.img: (first two are md5 identical in FC2t2) # isolinux/initrd.img # images/boot.iso[/isolinux/initrd.img] # images/pxeboot/initrd.img UnpackInitRd() { if [ -e ${INITRD_MOUNT} ] then sudo umount ${INITRD_MOUNT} 2>/dev/null else sudo mkdir ${INITRD_MOUNT} fi zcat ${ISO_ROOT}/${INITRD_PATH} >/tmp/${INITRD_NAME} sudo mount -o loop /tmp/${INITRD_NAME} ${INITRD_MOUNT} } RepackInitRd() { sudo umount ${INITRD_MOUNT} rm -f /tmp/${INITRD_NAME}.gz 2>/dev/null gzip /tmp/${INITRD_NAME} sudo cp /tmp/${INITRD_NAME}.gz ${ISO_ROOT}/${INITRD_PATH} sudo cp /tmp/${INITRD_NAME}.gz ${BOOTIMG_ROOT}/${INITRD_PATH} sudo cp /tmp/${INITRD_NAME}.gz ${ISO_ROOT}/images/pxeboot/${INITRD_NAME} } # isolinux.cfg: (they are identical) # isolinux/isolinux.cfg # images/boot.iso[isolinux/isolinux.cfg] # # allowcddma sometimes helps with CD problems - hasn't made a difference here # mem=exactmap mem=640k at 0m mem=1023M at 1M sometimes helps Proliant memory # recognition - hasn't made a difference here # UpdateLinuxConfig() { chmod 644 ${ISO_ROOT}/${CONFIG_PATH} ed - ${ISO_ROOT}/${CONFIG_PATH} << '!' H /default/s/linux/ks/p /append ks/s|ks|ks=cdrom:/ks.cfg|p w q ! chmod 644 ${BOOTIMG_ROOT}/${CONFIG_PATH} cp ${ISO_ROOT}/${CONFIG_PATH} ${BOOTIMG_ROOT}/${CONFIG_PATH} } # ks.cfg: # /ks.cfg # isolinux/ks.cfg # isolinux/initrd.img[(gzipped)/ks.cfg] # images/boot.iso[isolinux/initrd.img[(gzipped)/ks.cfg]] AddKickstartConfig() { cp -f ${KICKSTART_NAME} ${KICKSTART_PATH} ed - ${KICKSTART_PATH} < ${ISO_ROOT}/BOOTMSG.TXT <<'!' Test boot message ! } RpmsInPackage() { sed -n -e "/${1}<\/name>/,/<\/group>/p" <${ISO_ROOT}/${COMPS_PATH} | grep ']*[>]//g' | sed -e 's/ *//' } DetermineRpmList() { # These RPMS seem to be implied without explicit comps.xml entries cat implicit.${TARGET} > ${RPMLIST_NAME} sed -n -e '/%packages/,/%post/p' <${KICKSTART_PATH} | grep -v '^ *#' | grep -v '^%' | grep -v '^ *$' | while read LINE do case ${LINE} in [@]*) RpmsInPackage "`echo $LINE | sed -e 's/@ *//'`" >>${RPMLIST_NAME} ;; [-]*) ;; *) echo ${LINE} >>${RPMLIST_NAME} ;; esac done sort -u -o ${RPMLIST_NAME} ${RPMLIST_NAME} >${TMPLIST_NAME} while read PACKAGE do if ! grep -q '^ *'"${PACKAGE}"' *$' missing.${TARGET} then echo ${PACKAGE} >> ${TMPLIST_NAME} fi done < ${RPMLIST_NAME} mv ${TMPLIST_NAME} ${RPMLIST_NAME} } CopyRPMsFromDirectory() { DIRECTORY=${1:?"usage: $0 "} >${TMPLIST_NAME} while read PACKAGE do FILES=`ls ${DIRECTORY}/${PACKAGE}-*.rpm 2>/dev/null | grep ${PACKAGE}-[a-zA-Z0-9._]*-[a-zA-Z0-9._]*.rpm` if [ -n "${FILES}" ] then for FILE in ${FILES} do echo ${FILE} cp ${FILE} ${ISO_ROOT}/${RPM_PATH} done else echo ${PACKAGE} >> ${TMPLIST_NAME} fi done <${RPMLIST_NAME} mv ${TMPLIST_NAME} ${RPMLIST_NAME} } CopyRPMs() { if [ -e ${ISO_ROOT}/${RPM_PATH} ] then rm -rf ${ISO_ROOT}/${RPM_PATH} fi mkdir ${ISO_ROOT}/${RPM_PATH} CopyRPMsFromDirectory ${CUSTOM_RPMS} CopyRPMsFromDirectory ${PACKAGES} REMAINING_RPMS=`cat ${RPMLIST_NAME} | wc -l` DISK=1 while [ ${REMAINING_RPMS} -gt 0 ] do echo "${REMAINING_RPMS} RPMs remaining." eject echo -n "Please insert ${TARGET} Disk ${DISK} and press ENTER: " read line sudo mount ${CD_ROOT} CopyRPMsFromDirectory ${CD_ROOT}/${TARGET}/RPMS sudo umount ${CD_ROOT} eject REMAINING_RPMS=`cat ${RPMLIST_NAME} | wc -l` DISK=`expr ${DISK} + 1` done } MakeIsoFile() { ( cd ${ROOTS} ; find src -print | cpio -pdmvu ${ISO_ROOT} ) if [ "$TARGET" = RedHat ] then # RHEL3 genhdlist doesn't have --productpath /usr/lib/anaconda-runtime/genhdlist --withnumbers ${ISO_ROOT} PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder ${ISO_ROOT}/ '' rhe3qu2 >/tmp/pkgorder.txt /usr/lib/anaconda-runtime/genhdlist --withnumbers --fileorder /tmp/pkgorder.txt ${ISO_ROOT} else /usr/lib/anaconda-runtime/genhdlist --productpath ${TARGET} ${ISO_ROOT} fi sudo mkisofs -o ${ISO_NAME} -V "${ISO_LABEL}" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-info-table -J -r -nobak -T ${ISO_ROOT} } Cleanup ReplicateNonRpms UnpackBootIso #UnpackInitRd UpdateLinuxConfig AddKickstartConfig #AddBootMessage #RepackInitRd RepackBootIso DetermineRpmList CopyRPMs MakeIsoFile From JMAIER at de.ibm.com Wed Jun 2 09:36:57 2004 From: JMAIER at de.ibm.com (Joerg Maier) Date: Wed, 2 Jun 2004 11:36:57 +0200 Subject: netboot/install on power architecture Message-ID: He, i have a question regarding automated installation (without any interaction) and the location of the kickstart file. Pxeboot is not supported by architecture reason. dhcp-option filename is used to give redhat-netboot-image filename to the client. I did not find any possibility to tell the network-booting client where to get the ks.cfg file. Is it not possible to use kickstart in this specific environment? Then i have to write a expect script, maybe python with module pexpect, but this seems this is hard to maintain through different version. Best Regards, Joerg Maier JS20 Service Team IBM Deutschland Entwicklung GmbH - Lab Boeblingen phone: 49-7031-16-4762 (T/L: 120-4762) mail: jmaier at de.ibm.com http://www.de.ibm.com/entwicklung/ From chenwn at cn.ibm.com Wed Jun 2 09:54:29 2004 From: chenwn at cn.ibm.com (Wang Nan Chen) Date: Wed, 2 Jun 2004 17:54:29 +0800 Subject: netboot/install on power architecture Message-ID: Are you working with an power arch machine with an open firmware? If so, at open firmware prompt, you can trigger the noninteractive network installatin by running such a command: 0>boot /pci at 400000000211/pci at 2/ethernet at 1: ks=nfs:NFS_SERVER_IP:/PATH_TO_KSCFG/ks.cfg Here, "/pci at 400000000211/pci at 2/ethernet at 1" is device info of my working NIC. Please find your own exact string from SMS menu. After getting boot image by bootp, this client machine will launch that image. And, "ks=nfs:..." will be passed to that image as kernel parameter. Rgds, WangNan Joerg Maier To: kickstart-list at redhat.com Sent by: cc: kickstart-list-bounces Subject: netboot/install on power architecture @redhat.com 2004-06-02 17:36 Please respond to Discussion list about Kickstart He, i have a question regarding automated installation (without any interaction) and the location of the kickstart file. Pxeboot is not supported by architecture reason. dhcp-option filename is used to give redhat-netboot-image filename to the client. I did not find any possibility to tell the network-booting client where to get the ks.cfg file. Is it not possible to use kickstart in this specific environment? Then i have to write a expect script, maybe python with module pexpect, but this seems this is hard to maintain through different version. Best Regards, Joerg Maier JS20 Service Team IBM Deutschland Entwicklung GmbH - Lab Boeblingen phone: 49-7031-16-4762 (T/L: 120-4762) mail: jmaier at de.ibm.com http://www.de.ibm.com/entwicklung/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pic20695.gif Type: image/gif Size: 1255 bytes Desc: not available URL: From MartinRobb at ieee.org Wed Jun 2 13:17:57 2004 From: MartinRobb at ieee.org (Martin Robb) Date: Wed, 02 Jun 2004 09:17:57 -0400 Subject: genhdlist problems solved under RHEL3 -- buildIso script enclosed(sorry, long) In-Reply-To: <20040602095817.03AE073D16@hormel.redhat.com> References: <20040602095817.03AE073D16@hormel.redhat.com> Message-ID: <40BDD385.5010901@ieee.org> Cliff, Are you getting a mountable iso image that is just not bootable? Or is it corrupt altogether? Are you building the iso image under RHEL3 or FC2? The iso images are working for me under both RHEL3 and FC2, with HP Proliants and ASUS towers as the target systems. I have occasionally had problems in the past burning CDs that mount but don't boot, and got around the problem by switching from a generic CD to a name brand. Sounds weird, but it was quite consistent and reproducible. Beyond that, you might look at the mkisofs man page and try tinkering with the arguments. If you've had success in the past burning bootable CDs for your platform, try comparing the arguments with the mkisofs arguments I'm using in the script. Finally, FWIW, I'm using the following command line under FC2 to burn the cd: sudo cdrecord dev=/dev/cdrom driveropts=burnfree -v ${ISO_NAME} Hope that helps. Marty -----Original Message----- Subject: RE: genhdlist problems solved under RHEL3 -- buildIso script enclosed(sorry, long) From: "Lang, Clifford" Date: Tue, 1 Jun 2004 14:20:19 -0400 To: "Discussion list about Kickstart" I do not get a bootable ISO image out of this process. Has anyone else? Everything looks right, so I am not sure where to go from here. Any help would be greatly appreciated. Thanks - -cliff email: lang at metsci.com PH: 703-787-3649 From asim.zuberi.1993 at njit.edu Wed Jun 2 15:08:34 2004 From: asim.zuberi.1993 at njit.edu (Asim Zuberi) Date: Wed, 2 Jun 2004 10:08:34 -0500 Subject: tftp fails to proceed with KickStart installation! Message-ID: Hi there -- Okay, here's the situation. OS=RedHat 9.0 Hardware=Dell PE 750 NIC=Intel Giga bit card (integrated) PXE boot fails and the error I get in the /var/log/messages file is "tftp: client does not accept options". I can't KickStart the servers using PXE boot anymore. I need to get 30 servers setup before COB today. I read few email threads on the identical problem, I don't have time to compile the "initrd.msg" file. Can someone share the working "vmlinuz" and "initrd.img" files with me? Any help will greatly be appreciated. thanks --Asim; -------------- next part -------------- An HTML attachment was scrubbed... URL: From James_Martin at ao.uscourts.gov Wed Jun 2 19:58:03 2004 From: James_Martin at ao.uscourts.gov (James_Martin at ao.uscourts.gov) Date: Wed, 2 Jun 2004 15:58:03 -0400 Subject: tftp fails to proceed with KickStart installation! In-Reply-To: Message-ID: you sure like pushing deadlines. what tftp server are you using? The error you are showing has nothing to do with your initrd. James James S. Martin, RHCE Contractor Administrative Office of the United States Courts Washington, DC (202) 502-2394 kickstart-list-bounces at redhat.com wrote on 06/02/2004 11:08:34 AM: > Hi there -- > > Okay, here's the situation. > > OS=RedHat 9.0 > Hardware=Dell PE 750 > NIC=Intel Giga bit card (integrated) > > PXE boot fails and the error I get in the /var/log/messages file is > "tftp: client does not accept options". > I can't KickStart the servers using PXE boot anymore. I need to get > 30 servers setup before COB today. > I read few email threads on the identical problem, I don't have time > to compile the "initrd.msg" file. Can > someone share the working "vmlinuz" and "initrd.img" files with me? > > Any help will greatly be appreciated. > > thanks > --Asim; > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From timm at fnal.gov Wed Jun 2 20:31:25 2004 From: timm at fnal.gov (Steven Timm) Date: Wed, 2 Jun 2004 15:31:25 -0500 (CDT) Subject: tftp fails to proceed with KickStart installation! In-Reply-To: References: Message-ID: > > > > Okay, here's the situation. > > > > OS=RedHat 9.0 > > Hardware=Dell PE 750 > > NIC=Intel Giga bit card (integrated) > > > > PXE boot fails and the error I get in the /var/log/messages file is > > "tftp: client does not accept options". I have seen the above error message happen on all clients, even those that install successfully. So the tftp error may have no connection to what is really wrong. When you say PXE boot fails--at what stage does it fail. Also what type of nic is in the dell PE 750? Are you saying that the PXE just times out and you get nothing? Steve > > I can't KickStart the servers using PXE boot anymore. I need to get > > 30 servers setup before COB today. > > I read few email threads on the identical problem, I don't have time > > to compile the "initrd.msg" file. Can > > someone share the working "vmlinuz" and "initrd.img" files with me? > > > > Any help will greatly be appreciated. > > > > thanks > > --Asim; > > > > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From Piotr_Wolak at bose.com Thu Jun 3 18:50:57 2004 From: Piotr_Wolak at bose.com (Wolak, Piotr) Date: Thu, 3 Jun 2004 14:50:57 -0400 Subject: RH9 and missing proper e1000 network drivers Message-ID: <8BBA7B03263AD5118AE80003470D456D0BEE0C09@minerva.bose.com> Hello, I have a IBM x345 server which I want to kickstart with RH9 and do installation over HTTP/FTP. Unfortunately, the proper network drivers are not included on the original RH9 installation CD. I found a document which describes how to update the drivers and create a custom CD here http://www.puschitz.com/Kickstart.shtml but I can't use it in my case. My server will be using a public FTP/HTTP server for the installation data. I can modify the drivers on the CD (like update the kernel to 2.4.20-31.9 - the proper network drivers included) and make a custom CD but can't I update the stage2.img file which is on the public server. Do you know how can I build a driver under the standard RH9 BOOT kernel and transport it to a floppy and select it during the installation phase? I wish I could't go with Fedora but I can't at this time. Thanks for your help and best regards, Piotr From amul64 at yahoo.com Thu Jun 3 22:59:27 2004 From: amul64 at yahoo.com (Ajay Mulwani) Date: Thu, 3 Jun 2004 15:59:27 -0700 (PDT) Subject: buildinstall error on RHEL3.0 Message-ID: <20040603225927.87457.qmail@web50006.mail.yahoo.com> Hello List, While creating the customised CDs for RHEL3.0 the buildinstall is unable to finish cleanly and therefore I don't have a .discinfo file. Here is what happens: # /usr/lib/anaconda-runtime/buildinstall --comp RHEL-3.0 --pkgorder /redhat/pkgorder.txt --version 3.0 --product "Red Hat Enterprise Linux WS release 3 (Taroon Update 1)" --release "Red Hat Enterprise Linux WS release 3 (Taroon Update 1)" /redhat/i386/ warning: /export/home/EE3.0_32/i386/RedHat/RPMS/anaconda-runtime-9.1.1-7.RHEL.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e Running buildinstall... /export/home/EE3.0_32/i386/buildinstall.tree.6395 /redhat /redhat Going to run buildinstall again Usage: buildinstall [--comp ] [--pkgorder ] [--version ] [--product ] [--release ] Could anyone please suggest what is wrong here.. Regards, Ajay __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ From jim at rossberry.com Fri Jun 4 00:04:45 2004 From: jim at rossberry.com (Jim Wildman) Date: Thu, 3 Jun 2004 20:04:45 -0400 (EDT) Subject: buildinstall error on RHEL3.0 In-Reply-To: <20040603225927.87457.qmail@web50006.mail.yahoo.com> References: <20040603225927.87457.qmail@web50006.mail.yahoo.com> Message-ID: You need to copy all of mk-image.* and related scripts to the root of your build directory. ------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com From amul64 at yahoo.com Fri Jun 4 00:16:06 2004 From: amul64 at yahoo.com (Ajay Mulwani) Date: Thu, 3 Jun 2004 17:16:06 -0700 (PDT) Subject: buildinstall error on RHEL3.0 In-Reply-To: <1086307354.28931.11.camel@bad.jf.intel.com> Message-ID: <20040604001606.79671.qmail@web50001.mail.yahoo.com> Yes, Thanks. It seems that you have submited this already. I was going through this link: https://listman.redhat.com/archives/anaconda-devel-list/2003-October/msg00151.html This has worked for me. Thanks once again, Ajay --- "Taylor, ForrestX" wrote: > On Thu, 2004-06-03 at 16:32, Ajay Mulwani wrote: > > Hello List, > > > > While creating the customised CDs for RHEL3.0 the > > buildinstall is unable to finish cleanly and > therefore > > I don't have a .discinfo file. > > > > Here is what happens: > > > > # /usr/lib/anaconda-runtime/buildinstall --comp > > RHEL-3.0 --pkgorder /redhat/pkgorder.txt --version > 3.0 > > --product "Red Hat Enterprise Linux WS release 3 > > (Taroon Update 1)" --release "Red Hat Enterprise > Linux > > WS release 3 (Taroon Update 1)" /redhat/i386/ > > > > warning: > > > /export/home/EE3.0_32/i386/RedHat/RPMS/anaconda-runtime-9.1.1-7.RHEL.i386.rpm: > > V3 DSA signature: NOKEY, key ID db42a60e > > Running buildinstall... > > /export/home/EE3.0_32/i386/buildinstall.tree.6395 > > /redhat > > /redhat > > Going to run buildinstall again > > Usage: buildinstall [--comp ] > [--pkgorder > > ] [--version ] [--product > ] > > [--release ] > > Try rebuilding anaconda with this patch: > http://rau.homedns.org/twiki/pub/Anaconda/PatchesForAnaconda/buildinstall.patch > > More information can be had on that site. > > Forrest > __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ From stuart.grigg at baesystems.com Fri Jun 4 06:47:02 2004 From: stuart.grigg at baesystems.com (GRIGG, Stuart) Date: Fri, 4 Jun 2004 16:17:02 +0930 Subject: RH9 and missing proper e1000 network drivers Message-ID: I believe the driver will need to go into the initrd.img file (which for the CD boot is inside a file called cdboot.img). The page you have select has shown you how to add and upgrade your BOOT kernel, but I assume you only want to add a driver. The procedure would be (being that I am a bit fuzzy as I have not done it in a while on this but it should give you an idea on what to google) Install you BOOT kernel source set IS_BOOT_UP 0 and USE_BOOT 1 the /boot/kernel.h compile the drivers for the e1000 grab initrd.img from inside cdboot.img unzip and mount initrd add the compiles e1000.o to modules.cgz add the driver info to pcitable and module-info umount initrd and recompress. Set /boot/kernel.h back to normal Remove the BOOT kernel source Burn a new CD using the new cdboot.img and all should work. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Wolak, Piotr Sent: Friday, 4 June 2004 04:21 To: 'kickstart-list at redhat.com' Subject: RH9 and missing proper e1000 network drivers Hello, I have a IBM x345 server which I want to kickstart with RH9 and do installation over HTTP/FTP. Unfortunately, the proper network drivers are not included on the original RH9 installation CD. I found a document which describes how to update the drivers and create a custom CD here http://www.puschitz.com/Kickstart.shtml but I can't use it in my case. My server will be using a public FTP/HTTP server for the installation data. I can modify the drivers on the CD (like update the kernel to 2.4.20-31.9 - the proper network drivers included) and make a custom CD but can't I update the stage2.img file which is on the public server. Do you know how can I build a driver under the standard RH9 BOOT kernel and transport it to a floppy and select it during the installation phase? I wish I could't go with Fedora but I can't at this time. Thanks for your help and best regards, Piotr _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From brilong at cisco.com Fri Jun 4 12:43:13 2004 From: brilong at cisco.com (Brian Long) Date: Fri, 04 Jun 2004 08:43:13 -0400 Subject: RH9 and missing proper e1000 network drivers In-Reply-To: <8BBA7B03263AD5118AE80003470D456D0BEE0C09@minerva.bose.com> References: <8BBA7B03263AD5118AE80003470D456D0BEE0C09@minerva.bose.com> Message-ID: <1086352993.6250.43.camel@brilong-lnx.cisco.com> Use the "buildinstall" script which comes with anaconda-runtime to rebuild your installation floppies, stage2.img, etc. Check out the following for details: http://rau.homedns.org/twiki/bin/view/Anaconda/AnacondaDocumentationProject /Brian/ On Thu, 2004-06-03 at 14:50, Wolak, Piotr wrote: > Hello, > > I have a IBM x345 server which I want to kickstart with RH9 and do > installation over HTTP/FTP. Unfortunately, the proper network drivers are > not included on the original RH9 installation CD. I found a document which > describes how to update the drivers and create a custom CD here > http://www.puschitz.com/Kickstart.shtml but I can't use it in my case. > > My server will be using a public FTP/HTTP server for the installation data. > I can modify the drivers on the CD (like update the kernel to 2.4.20-31.9 - > the proper network drivers included) and make a custom CD but can't I update > the stage2.img file which is on the public server. > > Do you know how can I build a driver under the standard RH9 BOOT kernel and > transport it to a floppy and select it during the installation phase? > > I wish I could't go with Fedora but I can't at this time. > > Thanks for your help and best regards, > Piotr > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s From martinr at hotkey.net.au Mon Jun 7 09:04:42 2004 From: martinr at hotkey.net.au (Martin Rheumer) Date: Mon, 07 Jun 2004 09:04:42 Subject: Redhat ES2.1 and Poweredge 1750 Perc 4/Di In-Reply-To: <3.0.5.32.20040603105517.0102f068@pop.hotkey.net.au> Message-ID: <3.0.5.32.20040607090442.01fb26b0@pop.mogwai.net.au> Gday again, Has anybody actually achieved a kickstart with Enterprise 2.0 Redhat, and a cdrom install ( ks=cdrom ) and would like to comment on the isolinux.cfg they created or the line they typed at the boot: prompt ? My install keeps complaining about cant find ks.cfg in the /tmp directory ? Thanks again Martin At 10:55 AM 6/3/2004, Martin Rheumer wrote: >List.. > > >Have changed the lines in isolinux.cfg > >default ks >prompt 1 >timeout 600 >display boot.msg >F1 boot.msg >F2 general.msg >F3 expert.msg >F4 param.msg >F5 rescue.msg >label linux > kernel vmlinuz > append initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 >label text > kernel vmlinuz > append initrd=initrd.img lang= text devfs=nomount ramdisk_size=7168 >label expert > kernel vmlinuz > append expert initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 >label ks > kernel vmlinuz > append expert noprobe ks=cdrom initrd=initrd.img lang= devfs=nomount >ramdisk_size=7168 >label nofb > kernel vmlinuz > append initrd=initrd.img lang= devfs=nomount nofb ramdisk_size=7168 >label lowres > kernel vmlinuz > append initrd=initrd.img lang= lowres devfs=nomount ramdisk_size=7168 > >So that the ks config now has expert noprobe in them. > >And then added the device lines to the ks.cfg > >install >lang en_US >langsupport --default en_AU en_AU en_US >keyboard us >mouse none --device null >skipx >network --device eth0 --bootproto dhcp >text >rootpw --iscrypted $1$16??H??O$lTPsWNVVICEM4bM.NOHY31 >firewall --disabled >authconfig --enableshadow --enablemd5 >timezone Australia/Sydney >device net tg3 >device scsi megaraid2 >bootloader > >It now prompts me at the boot: menu, I press enter, then for a driver disk, >I say no, then the language and keyboard and finally says >the only choice to install is from cd. > >I think I have done something wrong. > >Anymore ideas ? > >Martin > > > > > > >Date: Thu, 03 Jun 2004 08:23:34 >To: martinr at hotkey.net.au >Subject: Re: Redhat ES2.1 and Poweredge 1750 Perc 4/Di > >On Wed, Jun 02, 2004 at 08:01:31PM +0000, Martin Rheumer wrote: >> >> Peeps, >> >> Have been wanting to rebuild my kickstart routine on >> the Dell 1750 and Perc 4/Di controllers which I >> thought was going to be fixed with Redhat ES2.1 >> and Update 4.. But alas it works fine with drivers >> for the Network Card the Broadcom is now supported >> but the Megaraid controller fails to install and run >> and so the machine cannot install via kickstart. > >You need to do an 'expert noprobe' install and specify "device scsi >megaraid2", "device net tg3" in your kickstart. That'll force it to >use megaraid2 and tg3, which is what you want. > From JMAIER at de.ibm.com Mon Jun 7 06:41:28 2004 From: JMAIER at de.ibm.com (Joerg Maier) Date: Mon, 7 Jun 2004 08:41:28 +0200 Subject: netboot/install on power architecture In-Reply-To: Message-ID: Thank you very much, that solved the problem. Now i still have the problem that anaconda does not accept partition parameters in the ks.cfg. I took them from anaconda-ks.cfg which was created during a manual installation. the chrp boot partition is missing. i will try with newer versions of rhelas3. Newertheless, the hint that of can pass parameters to the netboot-image is a big help. Best Regards, Joerg Maier JS20 Service Team IBM Deutschland Entwicklung GmbH - Lab Boeblingen phone: 49-7031-16-4762 (T/L: 120-4762) mail: jmaier at de.ibm.com http://www.de.ibm.com/entwicklung/ Wang Nan Chen Sent by: kickstart-list-bounces at redhat.com 02.06.2004 11:54 Please respond to Discussion list about Kickstart To Discussion list about Kickstart cc Subject Re: netboot/install on power architecture Are you working with an power arch machine with an open firmware? If so, at open firmware prompt, you can trigger the noninteractive network installatin by running such a command: 0>boot /pci at 400000000211/pci at 2/ethernet at 1: ks=nfs:NFS_SERVER_IP:/PATH_TO_KSCFG/ks.cfg Here, "/pci at 400000000211/pci at 2/ethernet at 1" is device info of my working NIC. Please find your own exact string from SMS menu. After getting boot image by bootp, this client machine will launch that image. And, "ks=nfs:..." will be passed to that image as kernel parameter. Rgds, WangNan Joerg Maier Joerg Maier Sent by: kickstart-list-bounces at redhat.com 2004-06-02 17:36 Please respond to Discussion list about Kickstart To: kickstart-list at redhat.com cc: Subject: netboot/install on power architecture He, i have a question regarding automated installation (without any interaction) and the location of the kickstart file. Pxeboot is not supported by architecture reason. dhcp-option filename is used to give redhat-netboot-image filename to the client. I did not find any possibility to tell the network-booting client where to get the ks.cfg file. Is it not possible to use kickstart in this specific environment? Then i have to write a expect script, maybe python with module pexpect, but this seems this is hard to maintain through different version. Best Regards, Joerg Maier JS20 Service Team IBM Deutschland Entwicklung GmbH - Lab Boeblingen phone: 49-7031-16-4762 (T/L: 120-4762) mail: jmaier at de.ibm.com http://www.de.ibm.com/entwicklung/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From chenwn at cn.ibm.com Mon Jun 7 06:54:37 2004 From: chenwn at cn.ibm.com (Wang Nan Chen) Date: Mon, 7 Jun 2004 14:54:37 +0800 Subject: netboot/install on power architecture Message-ID: Hi, I got the solution to PReP boot partition from this maillist about one year before. You can try this: Add such a line in your kickstart configuration file: part None --fstype "PPC PReP Boot" --size 8 This PReP boot partition problem has nothing with the versions of rhelas3. Good luck! Rgds, WangNan Joerg Maier To: Discussion list about Kickstart Sent by: cc: kickstart-list-bounces Subject: Re: netboot/install on power architecture @redhat.com 2004-06-07 14:41 Please respond to Discussion list about Kickstart Thank you very much, that solved the problem. Now i still have the problem that anaconda does not accept partition parameters in the ks.cfg. I took them from anaconda-ks.cfg which was created during a manual installation. the chrp boot partition is missing. i will try with newer versions of rhelas3. Newertheless, the hint that of can pass parameters to the netboot-image is a big help. Best Regards, Joerg Maier JS20 Service Team IBM Deutschland Entwicklung GmbH - Lab Boeblingen phone: 49-7031-16-4762 (T/L: 120-4762) mail: jmaier at de.ibm.com http://www.de.ibm.com/entwicklung/ Wang Nan Chen Sent by: kickstart-list-bounces at redhat.com 02.06.2004 11:54 Please respond to Discussion list about Kickstart To Discussion list about Kickstart cc Subject Re: netboot/install on power architecture Are you working with an power arch machine with an open firmware? If so, at open firmware prompt, you can trigger the noninteractive network installatin by running such a command: 0>boot /pci at 400000000211/pci at 2/ethernet at 1: ks=nfs:NFS_SERVER_IP:/PATH_TO_KSCFG/ks.cfg Here, "/pci at 400000000211/pci at 2/ethernet at 1" is device info of my working NIC. Please find your own exact string from SMS menu. After getting boot image by bootp, this client machine will launch that image. And, "ks=nfs:..." will be passed to that image as kernel parameter. Rgds, WangNan Joerg Maier Joerg Maier Sent by: kickstart-list-bounces at redhat.com 2004-06-02 17:36 Please respond to Discussion list about Kickstart To: kickstart-list at redhat.com cc: Subject: netboot/install on power architecture He, i have a question regarding automated installation (without any interaction) and the location of the kickstart file. Pxeboot is not supported by architecture reason. dhcp-option filename is used to give redhat-netboot-image filename to the client. I did not find any possibility to tell the network-booting client where to get the ks.cfg file. Is it not possible to use kickstart in this specific environment? Then i have to write a expect script, maybe python with module pexpect, but this seems this is hard to maintain through different version. Best Regards, Joerg Maier JS20 Service Team IBM Deutschland Entwicklung GmbH - Lab Boeblingen phone: 49-7031-16-4762 (T/L: 120-4762) mail: jmaier at de.ibm.com http://www.de.ibm.com/entwicklung/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pic15655.gif Type: image/gif Size: 1255 bytes Desc: not available URL: From andy.ciordia at pgdc.com Mon Jun 7 16:12:36 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Mon, 07 Jun 2004 12:12:36 -0400 Subject: Issue with Aquiring DHCP Message-ID: <40C493F4.3090902@pgdc.com> Ethernet Card: eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Problem: Installing from PXE fails to aquire DHCP address as Kickstart begins. Summary: PXE-Booting aquires DHCP w/ MAC matching Kernel is passed over and Boots Kickstart engages and knows to boot over HTTP, its first job is to aquire its address through DHCP. The first broadcast is never handled and times out, thus causing a stop point for the user asking methodology for aquiring an address. When you select OK to try DHCP again, it aquires, and the installation continues as it should. I've seen this problem reported before, but never really seen an applicable solution. In the DHCP logs I see a broadcast coming over the lines but I don't know why its not getting a response at this time and why it gets it on the second trial. The Console logs: Sending DHCP request through device eth0 Waiting for link 5 seconds . . . Pump told us: no DHCP reply recieved. Gut check says DHCP server is being pinged too fast by an address that was just allocated but I'm not sure where to head next.. might be way off base but if anyone has some guesses, I'd like to hear them. Install is 100% right on after this, but w/o this fixed I can't have a person-less-install. If there is no direct solution, is there a way to get it to just try again if it fails? Thanks, -a -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- (are you a bot that sends mal-mail? Try webfaux at pgdc.com its just for you!) From brilong at cisco.com Mon Jun 7 16:44:57 2004 From: brilong at cisco.com (Brian Long) Date: Mon, 07 Jun 2004 12:44:57 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: <40C493F4.3090902@pgdc.com> References: <40C493F4.3090902@pgdc.com> Message-ID: <1086626696.21267.158.camel@brilong-lnx.cisco.com> Does your switch have spanning tree port-fast enabled? This tells the switch to disable spanning tree calculations for that port. If not configured and spanning tree is enabled on your network, the time it takes your link to come up could be 30+ seconds and that's too long for "loader" to acquire an IP. /Brian/ On Mon, 2004-06-07 at 12:12, Andy Ciordia wrote: > Ethernet Card: > eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] > (PCIX:133MHz:64-bit) 10/100/1000BaseT > > Problem: Installing from PXE fails to aquire DHCP address as Kickstart > begins. > > Summary: > PXE-Booting aquires DHCP w/ MAC matching > Kernel is passed over and Boots > Kickstart engages and knows to boot over HTTP, its first job is to > aquire its address through DHCP. The first broadcast is never handled > and times out, thus causing a stop point for the user asking methodology > for aquiring an address. > When you select OK to try DHCP again, it aquires, and the installation > continues as it should. > > I've seen this problem reported before, but never really seen an > applicable solution. In the DHCP logs I see a broadcast coming over the > lines but I don't know why its not getting a response at this time and > why it gets it on the second trial. The Console logs: > > Sending DHCP request through device eth0 > Waiting for link > 5 seconds . . . > Pump told us: no DHCP reply recieved. > > Gut check says DHCP server is being pinged too fast by an address that > was just allocated but I'm not sure where to head next.. might be way > off base but if anyone has some guesses, I'd like to hear them. Install > is 100% right on after this, but w/o this fixed I can't have a > person-less-install. > > If there is no direct solution, is there a way to get it to just try > again if it fails? > > Thanks, > -a > > -- > Andy Ciordia, Network Engineer > Planned Giving Design Center (www.pgdc.com) > 10800-D Independence Pointe Pkwy, Matthews, NC 28105 > Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s From andy.ciordia at pgdc.com Mon Jun 7 17:41:21 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Mon, 07 Jun 2004 13:41:21 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: <1086626696.21267.158.camel@brilong-lnx.cisco.com> References: <40C493F4.3090902@pgdc.com> <1086626696.21267.158.camel@brilong-lnx.cisco.com> Message-ID: <40C4A8C1.4070209@pgdc.com> Brian Long wrote: > Does your switch have spanning tree port-fast enabled? This tells the > switch to disable spanning tree calculations for that port. If not > configured and spanning tree is enabled on your network, the time it > takes your link to come up could be 30+ seconds and that's too long for > "loader" to acquire an IP. > Sorry for being a bit dense atm, are you saying spanning tree port-fast should be enabled? As well, it does aquire the first pass, through PXE's asking DHCP for an address, that is resolved immediatly. Its the second DHCP request which is when the install engages that stalls. Currently on out Catalyst 5000: ! #spantree #uplinkfast groups set spantree uplinkfast disable #backbonefast set spantree backbonefast disable #vlan 208 set spantree enable 208 set spantree fwddelay 15 208 set spantree hello 2 208 set spantree maxage 20 208 set spantree priority 32768 208 -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- From jeremy at broadware.com Mon Jun 7 17:50:50 2004 From: jeremy at broadware.com (Jeremy Silver) Date: Mon, 7 Jun 2004 10:50:50 -0700 Subject: Issue with Aquiring DHCP In-Reply-To: <40C4A8C1.4070209@pgdc.com> Message-ID: <004801c44cb7$fb69d640$a13c0a0a@slaptop> Do you have multiple ethernet interfaces? Linux and the BIOS do not always agree on which is the 'first' ethernet port(and therefore eth0) in the system. On some systems I have to use the second (as labeled on the server chassis) ethernet port for kickstart as Linux see it as eth0, or specify eth1 as the ksdevice to use the first ethernet port. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Andy Ciordia Sent: Monday, June 07, 2004 10:41 AM To: Discussion list about Kickstart Subject: Re: Issue with Aquiring DHCP Brian Long wrote: > Does your switch have spanning tree port-fast enabled? This tells the > switch to disable spanning tree calculations for that port. If not > configured and spanning tree is enabled on your network, the time it > takes your link to come up could be 30+ seconds and that's too long > for "loader" to acquire an IP. > Sorry for being a bit dense atm, are you saying spanning tree port-fast should be enabled? As well, it does aquire the first pass, through PXE's asking DHCP for an address, that is resolved immediatly. Its the second DHCP request which is when the install engages that stalls. Currently on out Catalyst 5000: ! #spantree #uplinkfast groups set spantree uplinkfast disable #backbonefast set spantree backbonefast disable #vlan 208 set spantree enable 208 set spantree fwddelay 15 208 set spantree hello 2 208 set spantree maxage 20 208 set spantree priority 32768 208 -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From brilong at cisco.com Mon Jun 7 17:51:56 2004 From: brilong at cisco.com (Brian Long) Date: Mon, 07 Jun 2004 13:51:56 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: <40C4A8C1.4070209@pgdc.com> References: <40C493F4.3090902@pgdc.com> <1086626696.21267.158.camel@brilong-lnx.cisco.com> <40C4A8C1.4070209@pgdc.com> Message-ID: <1086630716.18593.9.camel@brilong-lnx2.cisco.com> On Mon, 2004-06-07 at 13:41, Andy Ciordia wrote: > Brian Long wrote: > > Does your switch have spanning tree port-fast enabled? This tells the > > switch to disable spanning tree calculations for that port. If not > > configured and spanning tree is enabled on your network, the time it > > takes your link to come up could be 30+ seconds and that's too long for > > "loader" to acquire an IP. > > > > Sorry for being a bit dense atm, are you saying spanning tree port-fast > should be enabled? Yes. Usually, the first PXE/DHCP would fail as well if port-fast was disabled. I just wanted you to verify port-fast was enabled. /Brian/ -- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s From andy.ciordia at pgdc.com Mon Jun 7 20:11:32 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Mon, 07 Jun 2004 16:11:32 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: <004801c44cb7$fb69d640$a13c0a0a@slaptop> References: <004801c44cb7$fb69d640$a13c0a0a@slaptop> Message-ID: <40C4CBF4.7070401@pgdc.com> Jeremy Silver wrote: > Do you have multiple ethernet interfaces? Linux and the BIOS do not always > agree on which is the 'first' ethernet port(and therefore eth0) in the > system. On some systems I have to use the second (as labeled on the server > chassis) ethernet port for kickstart as Linux see it as eth0, or specify > eth1 as the ksdevice to use the first ethernet port. > This is a dual onboard machine however only one nic is jacked in atm. Through PXE we recieve address, through second trial DHCP on same eth0 it is aquired. I don't change anything, I just wait for it to fail, then hit OK and it catches it. Just strange that it aquires it the first time, but when it asks for the same information 10 seconds later, it gets no response. Does DHCP have an idea of flood protection? -a -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- From jrobertson at convera.com Mon Jun 7 21:07:16 2004 From: jrobertson at convera.com (Joe Robertson) Date: Mon, 7 Jun 2004 14:07:16 -0700 Subject: Issue with Aquiring DHCP Message-ID: Andy, What kind of ethernet NIC do you have? (e1000 driver?) I've been fighting this problem for quite some time - trying to get kickstart via NFS to work. I finally found a solution!!!! It requires changing anaconda and rebuilding the entire distribution. I'll be reporting on this as soon as I am confident in the accuracy of the method. Basically it requires checking for failures in such things as attempting an NFS mount (or in your example getting a DHCP lease) and trying again (perhaps multiple times) if the initial attempts fail. Granted, this seems like a patch but I'm not sure what the 'correct' solution should be. It does seem that this is going to work for me - at least to get kickstart going. Having said that, there are still failures obtaining the IP address via PXE during boots subsequent to the install. I haven't determined what to do to resolve this yet. Thanks, Joe From jeremy at broadware.com Mon Jun 7 21:19:37 2004 From: jeremy at broadware.com (Jeremy Silver) Date: Mon, 7 Jun 2004 14:19:37 -0700 Subject: Issue with Aquiring DHCP In-Reply-To: Message-ID: <007c01c44cd5$267cbab0$a13c0a0a@slaptop> Joe, Which version of Red Hat are you using? I have been kickstarting RH8 systems using e1000 from an RH9 server since last year without going near anaconda code. Maybe it's the network I am using, there is just a Netgear hub between my kickstart/dhcp/tftp server and the servers I am building. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Joe Robertson Sent: Monday, June 07, 2004 02:07 PM To: Discussion list about Kickstart Subject: RE: Issue with Aquiring DHCP Andy, What kind of ethernet NIC do you have? (e1000 driver?) I've been fighting this problem for quite some time - trying to get kickstart via NFS to work. I finally found a solution!!!! It requires changing anaconda and rebuilding the entire distribution. I'll be reporting on this as soon as I am confident in the accuracy of the method. Basically it requires checking for failures in such things as attempting an NFS mount (or in your example getting a DHCP lease) and trying again (perhaps multiple times) if the initial attempts fail. Granted, this seems like a patch but I'm not sure what the 'correct' solution should be. It does seem that this is going to work for me - at least to get kickstart going. Having said that, there are still failures obtaining the IP address via PXE during boots subsequent to the install. I haven't determined what to do to resolve this yet. Thanks, Joe _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From tdiehl at rogueind.com Mon Jun 7 21:20:33 2004 From: tdiehl at rogueind.com (Tom Diehl) Date: Mon, 7 Jun 2004 17:20:33 -0400 (EDT) Subject: Issue with Aquiring DHCP In-Reply-To: References: Message-ID: Is this your problem: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114092 Tom On Mon, 7 Jun 2004, Joe Robertson wrote: > Andy, > > What kind of ethernet NIC do you have? (e1000 driver?) > > I've been fighting this problem for quite some time - trying > to get kickstart via NFS to work. > > I finally found a solution!!!! > > It requires changing anaconda and rebuilding the entire > distribution. I'll be reporting on this as soon as I > am confident in the accuracy of the method. > > Basically it requires checking for failures in such things > as attempting an NFS mount (or in your example getting > a DHCP lease) and trying again (perhaps multiple times) if > the initial attempts fail. > > Granted, this seems like a patch but I'm not sure what the > 'correct' solution should be. It does seem that this is > going to work for me - at least to get kickstart going. > > Having said that, there are still failures obtaining the > IP address via PXE during boots subsequent to the install. > I haven't determined what to do to resolve this yet. From jrobertson at convera.com Mon Jun 7 21:34:34 2004 From: jrobertson at convera.com (Joe Robertson) Date: Mon, 7 Jun 2004 14:34:34 -0700 Subject: Issue with Aquiring DHCP Message-ID: > From: Jeremy Silver [mailto:jeremy at broadware.com] > > Which version of Red Hat are you using? I have been > kickstarting RH8 systems using e1000 from an RH9 server since > last year without going near anaconda code. Maybe it's the > network I am using, there is just a Netgear hub between my > kickstart/dhcp/tftp server and the servers I am building. > Jeremy, I'm using Fedora Core 2. I have also tried most versions of Redhat from 8.0 up to and including RHAS-3.0 Update 2. None of the versions would run kickstart unless I connected to a specific switch configuration. See https://www.redhat.com/archives/kickstart-list/2004-May/msg00017.html for the beginning of quite a long thread on this topic. If you are using a 100 MB switch or hub that is not managed, chances are you don't see this problem. However, the minute I connect the GB nic to a managed switch - or apparently any GB switch, I could not run kickstart. You are connected to the Netgear hub which is probably the reason you don't have a problem. I connected to a Netgear 100 MB switch and everything was OK. When I connected to a Netgear GB switch, I couldn't kickstart. By the way... the solution I used is based on a previously submitted patch to Bugzilla which was obviously never included in the code for Fedora or AS. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110036 I removed the logMessage statements included in the patch since they broke the build/package process in Fedora Core 2 and I haven't yet tried to determine why. Joe > From andy.ciordia at pgdc.com Mon Jun 7 21:52:57 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Mon, 07 Jun 2004 17:52:57 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: References: Message-ID: <40C4E3B9.7090909@pgdc.com> Tom Diehl wrote: >Is this your problem: >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114092 > >Tom > > > No sir, not quite. The bail point is the same but the error is different. Ethernet Card: eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Problem: Installing from PXE, fails to aquire DHCP address as Kickstart begins. Summary: 1. PXE-Booting aquires DHCP w/ MAC matching 2. Kernel is passed over and Boots 3. Kickstart engages and knows to boot over HTTP, its first job is to aquire its address through DHCP. The first broadcast is never handled and times out, thus causing a stop point for the user asking methodology for aquiring an address. 4. When you select OK to try DHCP again, it aquires, and the installation continues as it should. I've seen this problem reported before, but never really seen an applicable solution. In the DHCP logs I see a broadcast coming over the lines but I don't know why its not getting a response at this time and why it gets it on the second trial. The Console logs: Sending DHCP request through device eth0 Waiting for link 5 seconds . . . Pump told us: no DHCP reply recieved. From jrobertson at convera.com Mon Jun 7 22:13:31 2004 From: jrobertson at convera.com (Joe Robertson) Date: Mon, 7 Jun 2004 15:13:31 -0700 Subject: Issue with Aquiring DHCP Message-ID: > -----Original Message----- > From: Tom Diehl [mailto:tdiehl at rogueind.com] > Is this your problem: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114092 > > Tom > No, I've not received those messages. It does seem that there are several similar problems that might all be related in some way to a timing issue. I'm not sure how it is determined that a device driver has been loaded and is ready for use. It appears that in many cases some code makes an assumption that the driver is ready when it is not. This becomes more of a problem when a component is of the GB persuasion... > On Mon, 7 Jun 2004, Joe Robertson wrote: > > > > Having said that, there are still failures obtaining the > > IP address via PXE during boots subsequent to the install. > > I haven't determined what to do to resolve this yet. > > I failed to say that my IP address failures are not consistent. I get perhaps 1 failure in 10 reboots - on different machines. I almost never see the IP address failure when I'm trying to do an install. Joe From David.Avrahami at comverse.com Tue Jun 8 10:50:39 2004 From: David.Avrahami at comverse.com (Avrahami David) Date: Tue, 8 Jun 2004 13:50:39 +0300 Subject: Question on making the partitions Message-ID: Hi, I would like the default partitions to be defined as follows: / - 2GB /usr - 4GB /opt - 2GB The remaining FSs should be a percent of the remaining free space (after allocating the above): /home - 50% /var - 30% /tmp - 20% Any clue how should be my ks.cfg? David -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott at telesoft.com Tue Jun 8 16:17:08 2004 From: scott at telesoft.com (Scott Dudley) Date: Tue, 08 Jun 2004 09:17:08 -0700 Subject: RH9 Upgrade: Automate Swap File Creation in ks.cfg? Message-ID: <40C5E684.8050305@telesoft.com> I've created a kickstart FTP config that I'm using to perform remote, unattended upgrades of some of my >= 6.1 systems to 9. Has worked flawlessly except on those systems for which their was insufficient swap space allocated. Anaconda pops up with the nice little UI prompting for swap file creation. If one responds affirmatively, the upgrade continues and completes successfully. How can I automate the check of this swap file creation? Is there a "standard" way of doing so? I was just toying with the following idea. To be added to the %pre stanza: %pre # get size of ram and swap mem=$(grep ^MemTotal: /proc/meminfo | awk '{print $2}') swap=$(grep ^SwapTotal: /proc/meminfo | awk '{print $2}') check=$((mem*2)) # create additional swap file, if required [ $swap -lt $check ] && { size=$((check-$swap) disk=$(df -t ext2 -t ext3 | sort -k 4n,5 | tail -1) part=$(echo $disk | awk '{print $6}') avail=$(echo $disk | awk '{print $4}') echo "Creating swap file ${part}/swapfile of size $size" # insufficient disk space on partition with most space to create swap file of required size [ $avail -lt $size ] && { echo "Insufficient free space ($avail) on $part to create swap file of size $size" exit 1 } dd if=/dev/zero of=${part}/swapfile bs=1024 count=$size chmod 600 ${part}/swapfile mkswap ${part}/swapfile # find /etc/fstab and add swap file to same - where mounted for install? } -- Regards, Scott Dudley From mark_denni at agilent.com Tue Jun 8 16:44:51 2004 From: mark_denni at agilent.com (Mark Denni) Date: Tue, 08 Jun 2004 09:44:51 -0700 Subject: Redhat 7.3 kicstart on Dell PowerEdge 1750 In-Reply-To: <9153F74610B7D311B83900902771C87113C6DAB6@axcs07.cos.agilent.com> References: <9153F74610B7D311B83900902771C87113C6DAB6@axcs07.cos.agilent.com> Message-ID: <40C5ED03.8020507@agilent.com> Has anyone managed to get a RedHat 7.3 kickstart install working on a Dell PowerEdge 1750? It uses an LSI Fusion MPT SCSI RAID controller (Dell calls it Perc 4/Di ) drivers are available at: http://www.snc.com.tr/ftp/PXBWS/SCSI/UTILITY/CIM/install.htm It also uses a Broadcom 5704 gigabit ethernet controller. -- Mark A. Denni Engineering Support Agilent Technologies, I/O Solutions Division From andy.ciordia at pgdc.com Tue Jun 8 19:13:55 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Tue, 08 Jun 2004 15:13:55 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: References: Message-ID: <40C60FF3.8090609@pgdc.com> Joe Robertson wrote: > No, I've not received those messages. It does seem that there > are several similar problems that might all be related in some > way to a timing issue. > > I'm not sure how it is determined that a device driver has been > loaded and is ready for use. It appears that in many cases > some code makes an assumption that the driver is ready when > it is not. This becomes more of a problem when a component > is of the GB persuasion... > Deffinitly deserves a bit of looking into.. Your patch sounds like a good idea I just don't want to go back through and repackage all the distros, yet again I don't know another way around it. I've got another 4 machines to work Kickstarts through it'll be interesting to see which of those cause (or lack there of) problems. Since no one really had a good clue I'll report my findings on the rest of the machines and what occurs as I get to it. -a -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- From Eric.Lambert at citadelgroup.com Wed Jun 9 17:55:28 2004 From: Eric.Lambert at citadelgroup.com (Lambert, Eric) Date: Wed, 9 Jun 2004 12:55:28 -0500 Subject: Issue with Aquiring DHCP Message-ID: I've had this same problem for this reason. i.e. PXE booting a dell 1750 over the on-board gig-1 (chosing between gig-1 and gig-2) with an additional e1000 card in the box will boot PXE over the gig-1 then fail on the anaconda DHCP with this error. When I modify the ks.cfg to use eth1 instead of eth0 it works. As Jeremy stated below, I think it's because the BIOS and linux differ on which interface is eth0 once the OS starts to load. -Eric -----Original Message----- From: Jeremy Silver [mailto:jeremy at broadware.com] Sent: Monday, June 07, 2004 12:51 PM To: 'Discussion list about Kickstart' Subject: RE: Issue with Aquiring DHCP Do you have multiple ethernet interfaces? Linux and the BIOS do not always agree on which is the 'first' ethernet port(and therefore eth0) in the system. On some systems I have to use the second (as labeled on the server chassis) ethernet port for kickstart as Linux see it as eth0, or specify eth1 as the ksdevice to use the first ethernet port. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Andy Ciordia Sent: Monday, June 07, 2004 10:41 AM To: Discussion list about Kickstart Subject: Re: Issue with Aquiring DHCP Brian Long wrote: > Does your switch have spanning tree port-fast enabled? This tells the > switch to disable spanning tree calculations for that port. If not > configured and spanning tree is enabled on your network, the time it > takes your link to come up could be 30+ seconds and that's too long > for "loader" to acquire an IP. > Sorry for being a bit dense atm, are you saying spanning tree port-fast should be enabled? As well, it does aquire the first pass, through PXE's asking DHCP for an address, that is resolved immediatly. Its the second DHCP request which is when the install engages that stalls. Currently on out Catalyst 5000: ! #spantree #uplinkfast groups set spantree uplinkfast disable #backbonefast set spantree backbonefast disable #vlan 208 set spantree enable 208 set spantree fwddelay 15 208 set spantree hello 2 208 set spantree maxage 20 208 set spantree priority 32768 208 -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ------------------------------------------------------------------------------------------------- ------------------------- CONFIDENTIALITY AND SECURITY NOTICE This e-mail contains information that may be confidential and proprietary. It is to be read and used solely by the intended recipient(s). Citadel and its affiliates retain all proprietary rights they may have in the information. If you are not an intended recipient, please notify us immediately either by reply e-mail or by telephone at 312-395-2100 and delete this e-mail (including any attachments hereto) immediately without reading, disseminating, distributing or copying. We cannot give any assurances that this e-mail and any attachments are free of viruses and other harmful code. Citadel reserves the right to monitor, intercept and block all communications involving its computer systems. From andy.ciordia at pgdc.com Wed Jun 9 18:12:13 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Wed, 09 Jun 2004 14:12:13 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: References: Message-ID: <40C752FD.1040107@pgdc.com> Since you mentioned this adding weight I went and adjusted my ksdevice from eth0 to eth1 and PXE still loads the kernel right but then I can't get passed the dhcp allocation screen. Its waiting for a link which is not hot. So I think the kernel and pxe understand that eth0 is eth0 it just for some reason fires off too early, or needs to understand failure/latency and retry some set number of times or have fallback mechanism. It needs to get a bit smarter, one point of failure cannot be an acceptable option. -a Lambert, Eric wrote: > I've had this same problem for this reason. i.e. PXE booting a dell > 1750 over the on-board gig-1 (chosing between gig-1 and gig-2) with an > additional e1000 card in the box will boot PXE over the gig-1 then fail > on the anaconda DHCP with this error. When I modify the ks.cfg to use > eth1 instead of eth0 it works. As Jeremy stated below, I think it's > because the BIOS and linux differ on which interface is eth0 once the OS > starts to load. > > -Eric > > -----Original Message----- > From: Jeremy Silver [mailto:jeremy at broadware.com] > Sent: Monday, June 07, 2004 12:51 PM > To: 'Discussion list about Kickstart' > Subject: RE: Issue with Aquiring DHCP > > Do you have multiple ethernet interfaces? Linux and the BIOS do not > always agree on which is the 'first' ethernet port(and therefore eth0) > in the system. On some systems I have to use the second (as labeled on > the server > chassis) ethernet port for kickstart as Linux see it as eth0, or > specify > eth1 as the ksdevice to use the first ethernet port. > -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- From Eric.Lambert at citadelgroup.com Wed Jun 9 18:54:20 2004 From: Eric.Lambert at citadelgroup.com (Lambert, Eric) Date: Wed, 9 Jun 2004 13:54:20 -0500 Subject: Issue with Aquiring DHCP Message-ID: ...and just in case, if you're using a kickstart file with something like this: network --device eth0 --bootproto dhcp Be sure you change that device eth0 to eth1 as well. -Eric -----Original Message----- From: Andy Ciordia [mailto:andy.ciordia at pgdc.com] Sent: Wednesday, June 09, 2004 1:12 PM To: Discussion list about Kickstart Subject: Re: Issue with Aquiring DHCP Since you mentioned this adding weight I went and adjusted my ksdevice from eth0 to eth1 and PXE still loads the kernel right but then I can't get passed the dhcp allocation screen. Its waiting for a link which is not hot. So I think the kernel and pxe understand that eth0 is eth0 it just for some reason fires off too early, or needs to understand failure/latency and retry some set number of times or have fallback mechanism. It needs to get a bit smarter, one point of failure cannot be an acceptable option. -a Lambert, Eric wrote: > I've had this same problem for this reason. i.e. PXE booting a dell > 1750 over the on-board gig-1 (chosing between gig-1 and gig-2) with an > additional e1000 card in the box will boot PXE over the gig-1 then > fail on the anaconda DHCP with this error. When I modify the ks.cfg > to use > eth1 instead of eth0 it works. As Jeremy stated below, I think it's > because the BIOS and linux differ on which interface is eth0 once the > OS starts to load. > > -Eric > > -----Original Message----- > From: Jeremy Silver [mailto:jeremy at broadware.com] > Sent: Monday, June 07, 2004 12:51 PM > To: 'Discussion list about Kickstart' > Subject: RE: Issue with Aquiring DHCP > > Do you have multiple ethernet interfaces? Linux and the BIOS do not > always agree on which is the 'first' ethernet port(and therefore eth0) > in the system. On some systems I have to use the second (as labeled > on the server > chassis) ethernet port for kickstart as Linux see it as eth0, or > specify > eth1 as the ksdevice to use the first ethernet port. > -- Andy Ciordia, Network Engineer Planned Giving Design Center (www.pgdc.com) 10800-D Independence Pointe Pkwy, Matthews, NC 28105 Ph: (704)849-0731 x106 | Fax: (770)456-5239 -- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ------------------------------------------------------------------------------------------------- ------------------------- CONFIDENTIALITY AND SECURITY NOTICE This e-mail contains information that may be confidential and proprietary. It is to be read and used solely by the intended recipient(s). Citadel and its affiliates retain all proprietary rights they may have in the information. If you are not an intended recipient, please notify us immediately either by reply e-mail or by telephone at 312-395-2100 and delete this e-mail (including any attachments hereto) immediately without reading, disseminating, distributing or copying. We cannot give any assurances that this e-mail and any attachments are free of viruses and other harmful code. Citadel reserves the right to monitor, intercept and block all communications involving its computer systems. From jrobertson at convera.com Wed Jun 9 22:01:43 2004 From: jrobertson at convera.com (Joe Robertson) Date: Wed, 9 Jun 2004 15:01:43 -0700 Subject: Issue with Aquiring DHCP Message-ID: This sounds like it is the same issue I've been having with GB ethernet (i.e. e1000 drivers) on kickstart. In my case I get past the DHCP only to fail when I tried to use NFS to access the kickstart file. I've finally resolved that particular issue by creating a loop in anaconda to attempt multiple NFS mounts if the first one fails. However there are still other cases - like when I reboot after an install - that I randomly fail to get a DHCP lease. I think all of this is caused by the GB nic taking longer to initialize than 100 MB nics. You should try connecting your GB nic to an unmanaged 100 MB switch and see if that removes the problem. I did that and my kickstart would run just fine. Joe > > From phr at doc.ic.ac.uk Wed Jun 9 22:48:31 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Wed, 9 Jun 2004 23:48:31 +0100 (BST) Subject: Issue with Aquiring DHCP In-Reply-To: References: Message-ID: I posted this on May 12th, but here it is again: https://rhn.redhat.com/errata/RHBA-2004-195.html " Bug fixes include: - Increase amount of time we wait for network controllers to establish a link " The exact patch to do this is below. In short, the default time to wait for a link was 5 seconds, is now 15, and can be set via the "linksleep=" command line parameter. Note: this feature was introduced in 9.1.2, so is present only in RHEL3U2, not even Fedora Core 2 (anaconda v10) from checking... diff -rc -C 1 anaconda-9.1/loader2/loader.c anaconda-9.1.2/loader2/loader.c *** anaconda-9.1/loader2/loader.c Fri Sep 26 22:38:41 2003 --- anaconda-9.1.2/loader2/loader.c Tue Apr 13 21:14:10 2004 *************** *** 88,89 **** --- 88,90 ---- + int num_link_checks = 15; *************** *** 528,529 **** --- 528,531 ---- loaderData->ethtool = strdup(argv[i] + 8); + else if (!strncasecmp(argv[i], "linksleep=", 10)) + num_link_checks = atoi(argv[i] + 10); else if (numExtraArgs < (MAX_EXTRA_ARGS - 1)) { diff -rc -C 1 anaconda-9.1/loader2/loader.h anaconda-9.1.2/loader2/loader.h *** anaconda-9.1/loader2/loader.h Mon Jul 7 23:50:55 2003 --- anaconda-9.1.2/loader2/loader.h Tue Apr 13 21:14:10 2004 *************** *** 94,95 **** --- 94,97 ---- + extern int num_link_checks; + /* 64 bit platforms, definitions courtesy of glib */ diff -rc -C 1 anaconda-9.1/loader2/net.c anaconda-9.1.2/loader2/net.c *** anaconda-9.1/loader2/net.c Thu Sep 4 20:57:24 2003 --- anaconda-9.1.2/loader2/net.c Tue Apr 13 20:57:37 2004 *************** *** 125,127 **** logMessage("waiting for link..."); ! while (tries < 5) { if (get_link_status(dev) != 0) --- 125,127 ---- logMessage("waiting for link..."); ! while (tries < num_link_checks) { if (get_link_status(dev) != 0) Cheers, Phil From mewett at cisco.com Thu Jun 10 00:18:42 2004 From: mewett at cisco.com (Scott Mewett) Date: Wed, 09 Jun 2004 17:18:42 -0700 Subject: Issue with Aquiring DHCP In-Reply-To: <40C4E3B9.7090909@pgdc.com> References: <40C4E3B9.7090909@pgdc.com> Message-ID: <1086826722.29359.236.camel@mewett-tp> Brians on the right track with regard to port-fast. What you want to enable there is on a per port basis. It's not a general spanning tree config. I mention this because your earlier mail only showed some general spanning tree settings. I have seen what you describe. It will work for the pxe dhcp request but fail on the kickstart dhcp request. It depends on how fast your machine boots and if the interface gets reset right before pxe dhcp. Spanning tree can take up to 50 seconds to go through the cycle of blocking, listening, learning, before it starts forwarding on that port again. Your looking at at least 30 seconds. Kickstart then resets the interface, which make the interface leave the bridge, and thus when it reconnects the switch port goes back to blocking mode and goes through the cycle again. Here what you'd change: cat5k> (enable) show port spantree 2/3 Port(s) Vlan Port-State Cost Priority Portfast Channel_id ------------------------ ---- ------------- ----- -------- ---------- ---------- 2/3 1 forwarding 19 32 disabled 0 cat5k> (enable) set spantree portfast 2/3 enable Warning: Spantree port fast start should only be enabled on ports connected to a single host. Connecting hubs, concentrators, switches, bridges, etc. to a fast start port can cause temporary spanning tree loops. Use with caution. Spantree port 2/3 fast start enabled. cat5k> (enable) show port spantree 2/3 Port(s) Vlan Port-State Cost Priority Portfast Channel_id ------------------------ ---- ------------- ----- -------- ---------- ---------- 2/3 1 forwarding 19 32 enabled 0 cat5k> (enable) Enabling Port fast on all ports that are only going to be connected to hosts is a good practice. One example of why you would want do do this is NTP would have problems setting it's initial time on boot up since on a fast machine NTP may start before the switch port is in forwarding mode. Also notice the warning it gave. So you don't want to plug in a switch to that port or it could cause problems. To protect against that versions of CatOS 5.4.1 have a feature called BPDU Guard. If you enable this then the port will get disabled if it detects the device being connected is running spanning tree. You can control how long it will disable for as well. cat5k> (enable) set spantree portfast bpdu-guard enable Spantree portfast bpdu-guard enabled on this switch. cat5k> (enable) See http://www.cisco.com/warp/public/473/65.html for more information. Thanks Scott On Mon, 2004-06-07 at 14:52, Andy Ciordia wrote: > Tom Diehl wrote: > > >Is this your problem: > >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114092 > > > >Tom > > > > > > > No sir, not quite. The bail point is the same but the error is different. > > > Ethernet Card: > eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] > (PCIX:133MHz:64-bit) 10/100/1000BaseT > > Problem: Installing from PXE, fails to aquire DHCP address as Kickstart > begins. > > Summary: > 1. PXE-Booting aquires DHCP w/ MAC matching > 2. Kernel is passed over and Boots > 3. Kickstart engages and knows to boot over HTTP, its first job is to > aquire its address through DHCP. The first broadcast is never handled > and times out, thus causing a stop point for the user asking methodology > for aquiring an address. > 4. When you select OK to try DHCP again, it aquires, and the > installation continues as it should. > > I've seen this problem reported before, but never really seen an > applicable solution. In the DHCP logs I see a broadcast coming over the > lines but I don't know why its not getting a response at this time and > why it gets it on the second trial. The Console logs: > > Sending DHCP request through device eth0 > Waiting for link > 5 seconds . . . > Pump told us: no DHCP reply recieved. > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From andy.ciordia at pgdc.com Thu Jun 10 14:06:29 2004 From: andy.ciordia at pgdc.com (Andy Ciordia) Date: Thu, 10 Jun 2004 10:06:29 -0400 Subject: Issue with Aquiring DHCP In-Reply-To: <1086826722.29359.236.camel@mewett-tp> References: <40C4E3B9.7090909@pgdc.com> <1086826722.29359.236.camel@mewett-tp> Message-ID: <40C86AE5.3040509@pgdc.com> Scott Mewett wrote: > Brians on the right track with regard to port-fast. > What you want to enable there is on a per port basis. > It's not a general spanning tree config. > I mention this because your earlier mail only showed some general > spanning tree settings. > Kickstart then resets the interface, which make the interface leave the > bridge, and thus when it reconnects the switch port goes back to > blocking mode and goes through the cycle again. You know I hadn't thought of that and I'll have to go back and look but you're probably right. If its flushing that port its going to take a chunk of seconds before it accepts that link again. > Also notice the warning it gave. So you don't want to plug in a switch > to that port or it could cause problems. To protect against that > versions of CatOS 5.4.1 have a feature called BPDU Guard. If you enable > this then the port will get disabled if it detects the device being > connected is running spanning tree. You can control how long it will > disable for as well. Right now the machine thats being tested is hooked into the Cat5k but the array I'm will be pushing the work to has 100unmanaged switch connect into the 5k.. I'm curious if there will be a problem there.. Since the Cat5k isn't opening a new port it might just breeze on through. That'd be refreshing ;) I need to develop my other KS's for the other roles in that rack and see what happens. And thanks go to Philip Rowlands as well. Nice to see that patch got wrapped already into U2, I don't have an install tree for that atm but I might consider it. :) -a From jeroen at science.uva.nl Thu Jun 10 16:30:46 2004 From: jeroen at science.uva.nl (Jeroen Roodhart) Date: Thu, 10 Jun 2004 18:30:46 +0200 Subject: Issue with Aquiring DHCP Message-ID: <40C88CB6.4070300@science.uva.nl> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! |Brians on the right track with regard to port-fast. Maybe so, but we tried a lot of different settings over here and it didn't work at all. What works over here is to apply a small patch to the anaconda nfsmount (isys/nfsmount.c) code. This uses NFS over UDP but doesn't do any error recovery. Turns out that it only once tries to do a pmap_getmaps, when that fails this results in the visible error of not being able to get the kickstart configuration file. Just retrying for a maximum number of retries fixes things for us... (This is not my idea, I saw a patch for this in the kicktstart list...) With kind regards, Jeroen *** nfsmount.c 2004-05-06 23:40:21.000000000 +0200 - --- /scratch/nfsmount.c 2004-06-10 12:55:56.600409365 +0200 *************** *** 198,209 **** ~ { ~ struct pmaplist *pmap; ~ static struct pmap p = {0, 0, 0, 0}; ~ server_addr->sin_port = PMAPPORT; ~ pmap = pmap_getmaps(server_addr); ! if (!pmap) ! return NULL; ~ if (version > MAX_NFSPROT) ~ version = MAX_NFSPROT; - --- 198,218 ---- ~ { ~ struct pmaplist *pmap; ~ static struct pmap p = {0, 0, 0, 0}; + int retries = 0; ~ server_addr->sin_port = PMAPPORT; ~ pmap = pmap_getmaps(server_addr); ! if (!pmap) { ! while (!pmap && (retries < 30)) { ! sleep(1); ! pmap = pmap_getmaps(server_addr); ! retries++; ! } ! if (!pmap) ! return NULL; ! } ! ~ if (version > MAX_NFSPROT) ~ version = MAX_NFSPROT; - -- Jeroen Roodhart University of Amsterdam jeroen at science.uva.nl Faculty of Science / ICT-Group Systeem- en netwerkbeheer Tel. 020 525 7203 / 06 51338165 - -- See http://www.science.uva.nl/~jeroen for openPGP public key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAyIy237AP1zFtDU0RAsAJAKDEdfUHqnQSlFcIuvtg9SvboPyQegCdGMR4 VXFB4O8OqAjDPxH+If7Yia8= =N2W2 -----END PGP SIGNATURE----- From mewett at cisco.com Fri Jun 11 04:13:30 2004 From: mewett at cisco.com (Scott Mewett) Date: Thu, 10 Jun 2004 21:13:30 -0700 Subject: Issue with Aquiring DHCP In-Reply-To: <40C86AE5.3040509@pgdc.com> References: <40C4E3B9.7090909@pgdc.com> <1086826722.29359.236.camel@mewett-tp> <40C86AE5.3040509@pgdc.com> Message-ID: <1086927210.25469.1.camel@mewett-tp> On Thu, 2004-06-10 at 07:06, Andy Ciordia wrote: > Scott Mewett wrote: > > Brians on the right track with regard to port-fast. > > What you want to enable there is on a per port basis. > > It's not a general spanning tree config. > > I mention this because your earlier mail only showed some general > > spanning tree settings. > > > Kickstart then resets the interface, which make the interface leave the > > bridge, and thus when it reconnects the switch port goes back to > > blocking mode and goes through the cycle again. > > You know I hadn't thought of that and I'll have to go back and look but > you're probably right. If its flushing that port its going to take a > chunk of seconds before it accepts that link again. > > > Also notice the warning it gave. So you don't want to plug in a switch > > to that port or it could cause problems. To protect against that > > versions of CatOS 5.4.1 have a feature called BPDU Guard. If you enable > > this then the port will get disabled if it detects the device being > > connected is running spanning tree. You can control how long it will > > disable for as well. > > Right now the machine thats being tested is hooked into the Cat5k but > the array I'm will be pushing the work to has 100unmanaged switch > connect into the 5k.. I'm curious if there will be a problem there.. > Since the Cat5k isn't opening a new port it might just breeze on > through. That'd be refreshing ;) That's what would happen. Since the uplink port on your unmanaged switch does change state, the port wouldn't get shut down. As a result the your kickstart should proceed along without stopping. Scott > > I need to develop my other KS's for the other roles in that rack and see > what happens. > > And thanks go to Philip Rowlands as well. Nice to see that patch got > wrapped already into U2, I don't have an install tree for that atm but I > might consider it. :) > > -a > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From bernard.mcauley at phyworks-ic.com Wed Jun 16 10:57:22 2004 From: bernard.mcauley at phyworks-ic.com (Bernard McAuley) Date: Wed, 16 Jun 2004 11:57:22 +0100 Subject: Kickstart NFS fails to find a DHCP address Message-ID: <000401c45390$b38b3fa0$06b5a8c0@ANALAPBERN> Hi, After trawling through the e-mail archives, I've found several users with a similar problem, but I haven't found a 'good' solution - so I'm hoping that somebody can help me. I have a PC attached via a cisco switch (and yet port fast is enabled!) to a DHCP server, from which I'm trying to kickstart (via NFS but that isn't particularly relevant) using a redhat 8.0 boot disk. When the boot starts the machine looks for a DHCP address, fails to get one and so the boot stops there. (PUMP returns the messages: No DHCP reply received) However, if I boot into a full linux installation (Red Hat 7.2 in this case) and run pump I obtain an IP address without problems. Looking at the DHCP server is it responding to the DHCPDISCOVER requrest and offering out an IP addres but the machine refuses to pick up the IP address. I've put a hub between the switch and the client and used Ethereal to monitor the traffic to and from the machine and with an installation these are the first 2 transactions that I get:- Frame 12 (342 bytes on wire, 342 bytes captured) Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Frame 15 (357 bytes on wire, 357 bytes captured) Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: physerv1.phyworks-ic.com (192.168.181.200), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68) Bootstrap Protocol Frame 17 (342 bytes on wire, 342 bytes captured) Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Frame 18 (357 bytes on wire, 357 bytes captured) Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: physerv1.phyworks-ic.com (192.168.181.200), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68) Bootstrap Protocol The frames continue for a short while, but the PC never picks up on the returning DHCPOFFER packets (which aren't delayed by a long period). Compare this to the transaction whilst using PUMP:- Frame 5 (357 bytes on wire, 357 bytes captured) Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: physerv1.phyworks-ic.com (192.168.181.200), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68) Bootstrap Protocol Frame 6 (590 bytes on wire, 590 bytes captured) Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Frame 7 (342 bytes on wire, 342 bytes captured) Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: physerv1.phyworks-ic.com (192.168.181.200), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68) Bootstrap Protocol Frame 8 (590 bytes on wire, 590 bytes captured) Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Frame 9 (342 bytes on wire, 342 bytes captured) Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff Internet Protocol, Src Addr: physerv1.phyworks-ic.com (192.168.181.200), Dst Addr: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68) Bootstrap Protocol Can anybody suggest whats going on here? Earlier posts have suggested that the DHCP request is timed out too soon, but the time stamps on the install and the pump run are roughly the same (just under 1 second). I'm digging into the sources now, but I really don't want to be rebuilding anaconda if I can help it! Regards, Bernard McAuley From bernard.mcauley at phyworks-ic.com Wed Jun 16 14:01:40 2004 From: bernard.mcauley at phyworks-ic.com (Bernard McAuley) Date: Wed, 16 Jun 2004 15:01:40 +0100 Subject: Kickstart NFS fails to find a DHCP address In-Reply-To: Message-ID: <002401c453aa$72ade040$06b5a8c0@ANALAPBERN> I'm afraid that this doesn't appear to have any effect, I still get the same startup error. Regards, Bernard McAuley > -----Original Message----- > From: Asim Zuberi [mailto:Asim.Zuberi.1993 at njit.edu] > Sent: 16 June 2004 14:41 > To: 'Bernard McAuley' > Subject: RE: Kickstart NFS fails to find a DHCP address > > try these settings at your boot prompt.... > > ksdevice=eth0 lang=en devfs=nomount ramdisk_size=9216 > ks=nfs:135.1.45.11:/local/RedHat/ks.cfg nofb console=tty1 > > --Asim; > > > > > =] -----Original Message----- > =] From: kickstart-list-bounces at redhat.com > =] [mailto:kickstart-list-bounces at redhat.com] On Behalf Of > =] Bernard McAuley > =] Sent: Wednesday, June 16, 2004 5:57 AM > =] To: kickstart-list at redhat.com > =] Subject: Kickstart NFS fails to find a DHCP address > =] > =] > =] Hi, > =] > =] After trawling through the e-mail archives, I've found > =] several users with a similar problem, but I haven't found a > =] 'good' solution - so I'm hoping that somebody can help me. > =] > =] I have a PC attached via a cisco switch (and yet port fast > =] is enabled!) to a DHCP server, from which I'm trying to > =] kickstart (via NFS but that isn't particularly relevant) > =] using a redhat 8.0 boot disk. When the boot starts the > =] machine looks for a DHCP address, fails to get one and so > =] the boot stops there. (PUMP returns the messages: No DHCP reply > =] received) > =] > =] However, if I boot into a full linux installation (Red Hat > =] 7.2 in this > =] case) and run pump I obtain an IP address without problems. > =] > =] Looking at the DHCP server is it responding to the > =] DHCPDISCOVER requrest and offering out an IP addres but the > =] machine refuses to pick up the IP address. > =] > =] I've put a hub between the switch and the client and used > =] Ethereal to monitor the traffic to and from the machine and > =] with an installation these are the first 2 transactions that I get:- > =] > =] Frame 12 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 15 (357 bytes on wire, 357 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Frame 17 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 18 (357 bytes on wire, 357 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] The frames continue for a short while, but the PC never > =] picks up on the returning DHCPOFFER packets (which aren't > =] delayed by a long period). > =] > =] Compare this to the transaction whilst using PUMP:- > =] > =] Frame 5 (357 bytes on wire, 357 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Frame 6 (590 bytes on wire, 590 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 7 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Frame 8 (590 bytes on wire, 590 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 9 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Can anybody suggest whats going on here? Earlier posts > =] have suggested that the DHCP request is timed out too soon, > =] but the time stamps on the install and the pump run are > =] roughly the same (just under 1 second). I'm digging into > =] the sources now, but I really don't want to be rebuilding > =] anaconda if I can help it! > =] > =] Regards, > =] > =] > =] Bernard McAuley > =] > =] > =] > =] > =] > =] _______________________________________________ > =] Kickstart-list mailing list > =] Kickstart-list at redhat.com > =] https://www.redhat.com/mailman/listinfo/kickstart-list > =] From bernard.mcauley at phyworks-ic.com Wed Jun 16 14:29:23 2004 From: bernard.mcauley at phyworks-ic.com (Bernard McAuley) Date: Wed, 16 Jun 2004 15:29:23 +0100 Subject: Kickstart NFS fails to find a DHCP address In-Reply-To: Message-ID: <002d01c453ae$5455f1b0$06b5a8c0@ANALAPBERN> I'm afraid that I don't have the necessary setups on the server to run PXE (i.e. no bootp or tftp server - only DHCP). Regards, Bernard McAuley > -----Original Message----- > From: Asim Zuberi [mailto:Asim.Zuberi.1993 at njit.edu] > Sent: 16 June 2004 15:16 > To: 'Bernard McAuley' > Subject: RE: Kickstart NFS fails to find a DHCP address > > > Could you try using PXE boot.... > > =] -----Original Message----- > =] From: kickstart-list-bounces at redhat.com > =] [mailto:kickstart-list-bounces at redhat.com] On Behalf Of > =] Bernard McAuley > =] Sent: Wednesday, June 16, 2004 9:02 AM > =] To: kickstart-list at redhat.com > =] Subject: RE: Kickstart NFS fails to find a DHCP address > =] > =] > =] I'm afraid that this doesn't appear to have any effect, I > =] still get the same startup error. > =] > =] Regards, > =] > =] Bernard McAuley > =] > =] > -----Original Message----- > =] > From: Asim Zuberi [mailto:Asim.Zuberi.1993 at njit.edu] > =] > Sent: 16 June 2004 14:41 > =] > To: 'Bernard McAuley' > =] > Subject: RE: Kickstart NFS fails to find a DHCP address > =] > > =] > try these settings at your boot prompt.... > =] > > =] > ksdevice=eth0 lang=en devfs=nomount ramdisk_size=9216 > =] > ks=nfs:135.1.45.11:/local/RedHat/ks.cfg nofb console=tty1 > =] > > =] > --Asim; > =] > > =] > > =] > > =] > > =] > =] -----Original Message----- > =] > =] From: kickstart-list-bounces at redhat.com > =] > =] [mailto:kickstart-list-bounces at redhat.com] On Behalf Of =] > =] > Bernard McAuley =] Sent: Wednesday, June 16, 2004 5:57 AM > =] > =] To: kickstart-list at redhat.com > =] > =] Subject: Kickstart NFS fails to find a DHCP address > =] > =] > =] > =] > =] > =] Hi, > =] > =] > =] > =] After trawling through the e-mail archives, I've found > =] > =] several users with a similar problem, but I haven't found a > =] > =] 'good' solution - so I'm hoping that somebody can help me. > =] > =] > =] > =] I have a PC attached via a cisco switch (and yet port fast > =] > =] is enabled!) to a DHCP server, from which I'm trying to > =] > =] kickstart (via NFS but that isn't particularly relevant) > =] > =] using a redhat 8.0 boot disk. When the boot starts the > =] > =] machine looks for a DHCP address, fails to get one and so > =] > =] the boot stops there. (PUMP returns the messages: No > =] DHCP reply > =] > =] received) > =] > =] > =] > =] However, if I boot into a full linux installation (Red Hat > =] > =] 7.2 in this > =] > =] case) and run pump I obtain an IP address without problems. > =] > =] > =] > =] Looking at the DHCP server is it responding to the > =] > =] DHCPDISCOVER requrest and offering out an IP addres but the > =] > =] machine refuses to pick up the IP address. > =] > =] > =] > =] I've put a hub between the switch and the client and used > =] > =] Ethereal to monitor the traffic to and from the machine and > =] > =] with an installation these are the first 2 transactions that I > =] get:- > =] > =] > =] > =] Frame 12 (342 bytes on wire, 342 bytes captured) > =] > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: > =] ff:ff:ff:ff:ff:ff =] > =] > Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: =] > =] > 255.255.255.255 (255.255.255.255) User Datagram Protocol, =] Src > =] > Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol =] > =] > =] Frame 15 (357 bytes on wire, 357 bytes captured) > =] > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] > =] > =] Frame 17 (342 bytes on wire, 342 bytes captured) > =] > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] > =] Src Port: bootpc (68), Dst Port: bootps (67) > =] Bootstrap Protocol > =] > =] > =] > =] Frame 18 (357 bytes on wire, 357 bytes captured) > =] > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] > =] > =] The frames continue for a short while, but the PC never > =] > =] picks up on the returning DHCPOFFER packets (which aren't > =] > =] delayed by a long period). > =] > =] > =] > =] Compare this to the transaction whilst using PUMP:- > =] > =] > =] > =] Frame 5 (357 bytes on wire, 357 bytes captured) > =] > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] > =] > =] Frame 6 (590 bytes on wire, 590 bytes captured) > =] > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] > =] Src Port: bootpc (68), Dst Port: bootps (67) > =] Bootstrap Protocol > =] > =] > =] > =] Frame 7 (342 bytes on wire, 342 bytes captured) > =] > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] > =] > =] Frame 8 (590 bytes on wire, 590 bytes captured) > =] > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] > =] Src Port: bootpc (68), Dst Port: bootps (67) > =] Bootstrap Protocol > =] > =] > =] > =] Frame 9 (342 bytes on wire, 342 bytes captured) > =] > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] > =] > =] Can anybody suggest whats going on here? Earlier posts > =] > =] have suggested that the DHCP request is timed out too soon, > =] > =] but the time stamps on the install and the pump run are > =] > =] roughly the same (just under 1 second). I'm digging into > =] > =] the sources now, but I really don't want to be rebuilding > =] > =] anaconda if I can help it! > =] > =] > =] > =] Regards, > =] > =] > =] > =] > =] > =] Bernard McAuley > =] > =] > =] > =] > =] > =] > =] > =] > =] > =] > =] > =] _______________________________________________ > =] > =] Kickstart-list mailing list > =] > =] Kickstart-list at redhat.com > =] > =] https://www.redhat.com/mailman/listinfo/kickstart-list > =] > =] > =] > =] > =] > =] _______________________________________________ > =] Kickstart-list mailing list > =] Kickstart-list at redhat.com > =] https://www.redhat.com/mailman/listinfo/kickstart-list > =] From golharam at umdnj.edu Wed Jun 16 15:50:47 2004 From: golharam at umdnj.edu (Ryan Golhar) Date: Wed, 16 Jun 2004 11:50:47 -0400 Subject: Kickstart NFS fails to find a DHCP address In-Reply-To: <002401c453aa$72ade040$06b5a8c0@ANALAPBERN> Message-ID: <00b301c453b9$b3bb2ca0$f900a8c0@GOLHARMOBILE1> If you press Ctrl-Alt-F2 or F3, you'll get a log console, what does it say? ----- Ryan Golhar Computational Biologist The Informatics Institute at The University of Medicine & Dentistry of NJ Phone: 973-972-5034 Fax: 973-972-7412 Email: golharam at umdnj.edu -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Bernard McAuley Sent: Wednesday, June 16, 2004 10:02 AM To: kickstart-list at redhat.com Subject: RE: Kickstart NFS fails to find a DHCP address I'm afraid that this doesn't appear to have any effect, I still get the same startup error. Regards, Bernard McAuley > -----Original Message----- > From: Asim Zuberi [mailto:Asim.Zuberi.1993 at njit.edu] > Sent: 16 June 2004 14:41 > To: 'Bernard McAuley' > Subject: RE: Kickstart NFS fails to find a DHCP address > > try these settings at your boot prompt.... > > ksdevice=eth0 lang=en devfs=nomount ramdisk_size=9216 > ks=nfs:135.1.45.11:/local/RedHat/ks.cfg nofb console=tty1 > > --Asim; > > > > > =] -----Original Message----- > =] From: kickstart-list-bounces at redhat.com > =] [mailto:kickstart-list-bounces at redhat.com] On Behalf Of =] > Bernard McAuley =] Sent: Wednesday, June 16, 2004 5:57 AM > =] To: kickstart-list at redhat.com > =] Subject: Kickstart NFS fails to find a DHCP address > =] > =] > =] Hi, > =] > =] After trawling through the e-mail archives, I've found > =] several users with a similar problem, but I haven't found a > =] 'good' solution - so I'm hoping that somebody can help me. > =] > =] I have a PC attached via a cisco switch (and yet port fast > =] is enabled!) to a DHCP server, from which I'm trying to > =] kickstart (via NFS but that isn't particularly relevant) > =] using a redhat 8.0 boot disk. When the boot starts the > =] machine looks for a DHCP address, fails to get one and so > =] the boot stops there. (PUMP returns the messages: No DHCP reply > =] received) > =] > =] However, if I boot into a full linux installation (Red Hat > =] 7.2 in this > =] case) and run pump I obtain an IP address without problems. > =] > =] Looking at the DHCP server is it responding to the > =] DHCPDISCOVER requrest and offering out an IP addres but the > =] machine refuses to pick up the IP address. > =] > =] I've put a hub between the switch and the client and used > =] Ethereal to monitor the traffic to and from the machine and > =] with an installation these are the first 2 transactions that I get:- > =] > =] Frame 12 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff =] > Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: =] > 255.255.255.255 (255.255.255.255) User Datagram Protocol, =] Src > Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol =] > =] Frame 15 (357 bytes on wire, 357 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Frame 17 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 18 (357 bytes on wire, 357 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] The frames continue for a short while, but the PC never > =] picks up on the returning DHCPOFFER packets (which aren't > =] delayed by a long period). > =] > =] Compare this to the transaction whilst using PUMP:- > =] > =] Frame 5 (357 bytes on wire, 357 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Frame 6 (590 bytes on wire, 590 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 7 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Frame 8 (590 bytes on wire, 590 bytes captured) > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > =] > =] Frame 9 (342 bytes on wire, 342 bytes captured) > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > =] (192.168.181.200), Dst Addr: 255.255.255.255 > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > =] > =] Can anybody suggest whats going on here? Earlier posts > =] have suggested that the DHCP request is timed out too soon, > =] but the time stamps on the install and the pump run are > =] roughly the same (just under 1 second). I'm digging into > =] the sources now, but I really don't want to be rebuilding > =] anaconda if I can help it! > =] > =] Regards, > =] > =] > =] Bernard McAuley > =] > =] > =] > =] > =] > =] _______________________________________________ > =] Kickstart-list mailing list > =] Kickstart-list at redhat.com > =] https://www.redhat.com/mailman/listinfo/kickstart-list > =] _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From bernard.mcauley at phyworks-ic.com Thu Jun 17 09:05:18 2004 From: bernard.mcauley at phyworks-ic.com (Bernard McAuley) Date: Thu, 17 Jun 2004 10:05:18 +0100 Subject: Kickstart NFS fails to find a DHCP address In-Reply-To: <00b301c453b9$b3bb2ca0$f900a8c0@GOLHARMOBILE1> Message-ID: <008601c4544a$374fb460$06b5a8c0@ANALAPBERN> Hi, What is visible on the screen is as follows:- *modules to inset hid key keybdev usb-storage * module(s) hid keybdev not found * inserted /tmp/usb-storage.0 * load module set done * no firewaire controller found * probing for floppy devices * first non-detatched floppy is fd0 * system floppy device is fd0 * in startPcmcia() * pcmcia probe returned: | PCI bridge probe: not found. Intel PCIC probe: not found. Databook TCIC-2 probe : not found. | * no pcic controller found * probing buses * finished bus probing * modules to inset natsemi usb-ohci * module(s) usb-ohci.o found * inserted /tmp/natsemi.o * load module set done * sending dhcp request through device eth0 * pump told us: No DHCP reply received * no dhcp response received Regards, Bernard McAuley bernard.mcauley at phyworks-ic.com > -----Original Message----- > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list- > bounces at redhat.com] On Behalf Of Ryan Golhar > Sent: 16 June 2004 16:51 > To: 'Discussion list about Kickstart' > Subject: RE: Kickstart NFS fails to find a DHCP address > > If you press Ctrl-Alt-F2 or F3, you'll get a log console, what does it > say? > > ----- > Ryan Golhar > Computational Biologist > The Informatics Institute at > The University of Medicine & Dentistry of NJ > > Phone: 973-972-5034 > Fax: 973-972-7412 > Email: golharam at umdnj.edu > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Bernard McAuley > Sent: Wednesday, June 16, 2004 10:02 AM > To: kickstart-list at redhat.com > Subject: RE: Kickstart NFS fails to find a DHCP address > > > I'm afraid that this doesn't appear to have any effect, I still get the > same startup error. > > Regards, > > Bernard McAuley > > > -----Original Message----- > > From: Asim Zuberi [mailto:Asim.Zuberi.1993 at njit.edu] > > Sent: 16 June 2004 14:41 > > To: 'Bernard McAuley' > > Subject: RE: Kickstart NFS fails to find a DHCP address > > > > try these settings at your boot prompt.... > > > > ksdevice=eth0 lang=en devfs=nomount ramdisk_size=9216 > > ks=nfs:135.1.45.11:/local/RedHat/ks.cfg nofb console=tty1 > > > > --Asim; > > > > > > > > > > =] -----Original Message----- > > =] From: kickstart-list-bounces at redhat.com > > =] [mailto:kickstart-list-bounces at redhat.com] On Behalf Of =] > > Bernard McAuley =] Sent: Wednesday, June 16, 2004 5:57 AM > > =] To: kickstart-list at redhat.com > > =] Subject: Kickstart NFS fails to find a DHCP address > > =] > > =] > > =] Hi, > > =] > > =] After trawling through the e-mail archives, I've found > > =] several users with a similar problem, but I haven't found a > > =] 'good' solution - so I'm hoping that somebody can help me. > > =] > > =] I have a PC attached via a cisco switch (and yet port fast > > =] is enabled!) to a DHCP server, from which I'm trying to > > =] kickstart (via NFS but that isn't particularly relevant) > > =] using a redhat 8.0 boot disk. When the boot starts the > > =] machine looks for a DHCP address, fails to get one and so > > =] the boot stops there. (PUMP returns the messages: No DHCP reply > > =] received) > > =] > > =] However, if I boot into a full linux installation (Red Hat > > =] 7.2 in this > > =] case) and run pump I obtain an IP address without problems. > > =] > > =] Looking at the DHCP server is it responding to the > > =] DHCPDISCOVER requrest and offering out an IP addres but the > > =] machine refuses to pick up the IP address. > > =] > > =] I've put a hub between the switch and the client and used > > =] Ethereal to monitor the traffic to and from the machine and > > =] with an installation these are the first 2 transactions that I > get:- > > =] > > =] Frame 12 (342 bytes on wire, 342 bytes captured) > > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff =] > > Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: =] > > 255.255.255.255 (255.255.255.255) User Datagram Protocol, =] Src > > Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol =] > > =] Frame 15 (357 bytes on wire, 357 bytes captured) > > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > > =] (192.168.181.200), Dst Addr: 255.255.255.255 > > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > > =] > > =] Frame 17 (342 bytes on wire, 342 bytes captured) > > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > > =] > > =] Frame 18 (357 bytes on wire, 357 bytes captured) > > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > > =] (192.168.181.200), Dst Addr: 255.255.255.255 > > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > > =] > > =] The frames continue for a short while, but the PC never > > =] picks up on the returning DHCPOFFER packets (which aren't > > =] delayed by a long period). > > =] > > =] Compare this to the transaction whilst using PUMP:- > > =] > > =] Frame 5 (357 bytes on wire, 357 bytes captured) > > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > > =] (192.168.181.200), Dst Addr: 255.255.255.255 > > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > > =] > > =] Frame 6 (590 bytes on wire, 590 bytes captured) > > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > > =] > > =] Frame 7 (342 bytes on wire, 342 bytes captured) > > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > > =] (192.168.181.200), Dst Addr: 255.255.255.255 > > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > > =] > > =] Frame 8 (590 bytes on wire, 590 bytes captured) > > =] Ethernet II, Src: 00:09:5b:61:38:5a, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: 0.0.0.0 (0.0.0.0), Dst Addr: > > =] 255.255.255.255 (255.255.255.255) User Datagram Protocol, > > =] Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol > > =] > > =] Frame 9 (342 bytes on wire, 342 bytes captured) > > =] Ethernet II, Src: 00:02:55:aa:7e:3d, Dst: ff:ff:ff:ff:ff:ff > > =] Internet Protocol, Src Addr: physerv1.phyworks-ic.com > > =] (192.168.181.200), Dst Addr: 255.255.255.255 > > =] (255.255.255.255) User Datagram Protocol, Src Port: bootps > > =] (67), Dst Port: bootpc (68) Bootstrap Protocol > > =] > > =] Can anybody suggest whats going on here? Earlier posts > > =] have suggested that the DHCP request is timed out too soon, > > =] but the time stamps on the install and the pump run are > > =] roughly the same (just under 1 second). I'm digging into > > =] the sources now, but I really don't want to be rebuilding > > =] anaconda if I can help it! > > =] > > =] Regards, > > =] > > =] > > =] Bernard McAuley > > =] > > =] > > =] > > =] > > =] > > =] _______________________________________________ > > =] Kickstart-list mailing list > > =] Kickstart-list at redhat.com > > =] https://www.redhat.com/mailman/listinfo/kickstart-list > > =] > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From bakins at web.turner.com Fri Jun 18 14:21:10 2004 From: bakins at web.turner.com (Brian Akins) Date: Fri, 18 Jun 2004 10:21:10 -0400 Subject: Specify just the first disk In-Reply-To: <200404271346.38613.jkeating@j2solutions.net> References: <40882A33.1090901@web.turner.com> <1082681667.40886943ece83@trmail.triumf.ca> <408EC417.7090809@web.turner.com> <200404271346.38613.jkeating@j2solutions.net> Message-ID: <40D2FA56.2000007@web.turner.com> Jesse Keating wrote: > >In the %pre section, use fdisk (or something like that) to probe which >disks are present, awk out the actual disk > >fdisk -l |awk '/^Disk/ {print $2}' |awk -F "/" '{print $3}' |sed -e >'s/://' > >Something similar to that. Then use this value (in a variable) for your >--ondisk=${firstdisk} > > Cool this works on FC2. Thanks. -- Brian Akins Senior Systems Engineer CNN Internet Technologies From bakins at web.turner.com Fri Jun 18 14:23:51 2004 From: bakins at web.turner.com (Brian Akins) Date: Fri, 18 Jun 2004 10:23:51 -0400 Subject: Good way to figure out arch Message-ID: <40D2FAF7.4060209@web.turner.com> I have two arch's (i386 and x86_64) and each needs a different url. I can't do any thing with the %pre, because this is after the url is used. Anyone know a good way to determine the architecture and use it in url? -- Brian Akins Senior Systems Engineer CNN Internet Technologies From phr at doc.ic.ac.uk Fri Jun 18 14:48:29 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Fri, 18 Jun 2004 15:48:29 +0100 (BST) Subject: Good way to figure out arch In-Reply-To: <40D2FAF7.4060209@web.turner.com> References: <40D2FAF7.4060209@web.turner.com> Message-ID: On Fri, 18 Jun 2004, Brian Akins wrote: >I have two arch's (i386 and x86_64) and each needs a different url. I >can't do any thing with the %pre, because this is after the url is >used. Anyone know a good way to determine the architecture and use it >in url? I assume you mean for the kickstart file? Which bootloader are you using (isolinux, syslinux, pxelinux, LILO, GRUB, other)? I don't believe you can influence the requested URL from within anaconda, so you might have to set it dynamically from the bootloader. Sounds like this would be easiest with PXE, although I don't know where you'd switch between i386/x86_64 versions... Cheers, Phil From bakins at web.turner.com Fri Jun 18 16:30:55 2004 From: bakins at web.turner.com (Brian Akins) Date: Fri, 18 Jun 2004 12:30:55 -0400 Subject: Fedora core 2 and hostname Message-ID: <40D318BF.2030702@web.turner.com> Is there an easy way to get the hostname in post in FC2. hostname just returns localhost I'm using dhcp. -- Brian Akins Senior Systems Engineer CNN Internet Technologies From cegeddin at gmail.com Fri Jun 18 16:43:35 2004 From: cegeddin at gmail.com (Chris Geddings) Date: Fri, 18 Jun 2004 12:43:35 -0400 Subject: Fedora core 2 and hostname In-Reply-To: <40D318BF.2030702@web.turner.com> References: <40D318BF.2030702@web.turner.com> Message-ID: <4dd9d616040618094351544769@mail.gmail.com> Assuming the machine gets proper hostname information, it may be in the /etc/sysconfig/network file... grep HOSTNAME /etc/sysconfig/network That may or may not work :) I can't quite recall how the entry is obtained by the system though, so it may require some combination of the hostname being known by the dns servers and the dhcp options handing out the proper hostname. And it may be indicative that those settings are not working since your machine is returning localhost as the hostname at that point. (Or, that may mean nothing, depending on how the configuration of that environment is happening, I'm simply not sure.) --Chris On Fri, 18 Jun 2004 12:30:55 -0400, Brian Akins > Is there an easy way to get the hostname in post in FC2. hostname just > returns localhost > I'm using dhcp. > > From festifn at rupert.informatik.uni-stuttgart.de Fri Jun 18 16:48:40 2004 From: festifn at rupert.informatik.uni-stuttgart.de (Florian Festi) Date: Fri, 18 Jun 2004 18:48:40 +0200 (METDST) Subject: Fedora core 2 and hostname In-Reply-To: <4dd9d616040618094351544769@mail.gmail.com> Message-ID: > Assuming the machine gets proper hostname information, it may be in > the /etc/sysconfig/network file... > grep HOSTNAME /etc/sysconfig/network We are using the following lines on Fedora Core 1: #!/bin/bash source /etc/sysconfig/network hostname $HOSTNAME cu Florian Festi From lccha-rhlist at naos.org Fri Jun 18 16:42:37 2004 From: lccha-rhlist at naos.org (lccha-rhlist at naos.org) Date: Fri, 18 Jun 2004 09:42:37 -0700 Subject: Fedora core 2 and hostname In-Reply-To: <4dd9d616040618094351544769@mail.gmail.com> References: <40D318BF.2030702@web.turner.com> <4dd9d616040618094351544769@mail.gmail.com> Message-ID: <20040618164237.GA32070@turtleville.lccha.org> Once upon a time (like on Jun 18, 2004), Chris Geddings wrote: > I can't quite recall how the entry is obtained by the system though, > so it may require some combination of the hostname being known by the > dns servers and the dhcp options handing out the proper hostname. And You probably need: use-host-decl-names on; # give the host its hostname in the appropriate scope of your dhcpd.conf file (assuming you're using the ISC dhcp server). I can't tell from the original message if this is the only thing that is missing though ... -L From mcotton at aptas.com Fri Jun 18 18:07:17 2004 From: mcotton at aptas.com (Mike Cotton) Date: Fri, 18 Jun 2004 12:07:17 -0600 Subject: Need help with PXE/NFS install Message-ID: <200406181807.i5II7Ha05829@vhost6.atomicservers.com> Hello All, I need some assistance with finishing a PXE NFS install. I have reviewed the archives and the information there has helped me to get this far. I have a DHCP server and a separate file server running the TFTP and NFS services. I have figured out the DHCP settings to pass on the hostname, the IP, and the NextServer to push the installation over to the TFTP server. At the TFTP server, the pxeboot hex file points to the nfs share and anaconda finds the vmlinuz and initrd.img files and starts the interactive installation. Here is the part I am stuck on - whenever I try to add kickstart information into the hex file (ksdevice=eth0 ks=nfs:/{fileserver IP}/path to the ks file), the vmlinuz and initrd.img file are found and the initial install begins. As the install is checking for hardware it kernel panics with a VFS error when attempting to locate the hard drive. It seems that the megaraid driver we need is not getting installed, and it gacks at that point. To be clear - the nfs portion is operational and will lead to an interactive install, but when the kickstart information for an unattended installation, the install kernel panics with a VFS error. What did I break? :-) Thank you very much for any assistance - it is greatly appreciated. Mike Cotton -------------- next part -------------- An HTML attachment was scrubbed... URL: From amul64 at yahoo.com Fri Jun 18 23:15:15 2004 From: amul64 at yahoo.com (Ajay Mulwani) Date: Fri, 18 Jun 2004 16:15:15 -0700 (PDT) Subject: problem integrating ks.cfg with RHEL WS 2.1 ISOs Message-ID: <20040618231515.66715.qmail@web50004.mail.yahoo.com> Hello, I have created the two sets of customized ISOs of RHEL WS 2.1 by doing genhdlist, buildinstall, pkgorder (optional), splitdistro, genhdlist and mkisofs. 1) The first set has integrated ks.cfg file within isolinux/initrd.img and also updated isolinux/isolinux.cfg so that this ks.cfg is called by default even if just the "Enter" key is pressed at the "boot:" prompt. The ks.cfg file has ONLY the %post section which calls a script. With this set the problem that I am facing is the linux installer does not gives me an option to select packages and starts the "minimal" installation always. The installer tries to perform post-install but the script is not successfull since "Everything" is not installed. I don't want to include the %packages section and specify "@Everything" in the ks.cfg. 2) To avoid the situation in (1) I created the second set. Here, I restored the original initrd.img and isolinux.cfg and now kept ks.cfg at the top level and at isolinux directory. Now if at the "boot:" prompt I give "linux ks=cdrom:/ks.cfg" I am getting the following error: "I could not find a Red Hat Enterprise Linux WS CDROM in any of your CDROM drives. Please insert the Red Hat CD and press "OK" to retry" At this point I am not able to even eject this CD. If ks.cfg is not specified in the command; the installation goes absolutely fine but ofcourse the script which I want to will not execute. Could any one please suggest what could be wrong here so that the script should execute once the manual installation is over. Regards, Ajay __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From vikassep1984 at hotmail.com Sat Jun 19 05:31:47 2004 From: vikassep1984 at hotmail.com (VIKAS B) Date: Sat, 19 Jun 2004 11:01:47 +0530 Subject: Fedora core 2 and hostname Message-ID: Hi Brian, Yes there's an easy way of changing the hostname in FC2. after Login just at command line enter 'hostname' to see what is the hostname seted there, if returns localhost then you have to change this in 1. '/etc/sysconfig/network' edit this file and give hostname whatever you like in the line "hostname=" and then save this file and at the command line give the hostname command but now also you will get the same old host name as 'localhost' so set the hostname using command hostname (for eg: hostname vikas -- here hostname command will set the hostname as vikas, pls note that the name you are giving for the host name must be same as the hostname you have specified in '/etc/sysconfig/network' file. 2. '/etc/hosts' edit this file and this file would look like " IPAddress hostname localhost.localdomain localhost" in the place of hostname give the name as you wish(in the example same as hostname given in /etc/sysconfig/network file and hostname setted at command line), and save this file 3. Now restart the NFS and Network service by using the command 'service nfs restart' and 'service network restart' 4. Restart your computer inorder to take effect the changes you have done. now onwards your hostname will be setted as you had given in the above steps. (Be careful in following the above steps, because if you do the single mistake also it may cause your system problem in booting or functioning) if further doubts send an email to me. all the best. regards vikas >From: Brian Akins >Reply-To: Discussion list about Kickstart >To: Discussion list about Kickstart >Subject: Fedora core 2 and hostname >Date: Fri, 18 Jun 2004 12:30:55 -0400 > >Is there an easy way to get the hostname in post in FC2. hostname just >returns localhost > >I'm using dhcp. > >-- >Brian Akins >Senior Systems Engineer >CNN Internet Technologies > > >_______________________________________________ >Kickstart-list mailing list >Kickstart-list at redhat.com >https://www.redhat.com/mailman/listinfo/kickstart-list _________________________________________________________________ Catch up with old friends. Bring back the good times. http://www.batchmates.com/msn.asp Reconnect with the past. From vikassep1984 at hotmail.com Sat Jun 19 05:32:16 2004 From: vikassep1984 at hotmail.com (VIKAS B) Date: Sat, 19 Jun 2004 11:02:16 +0530 Subject: Fedora core 2 and hostname Message-ID: Hi Brian, Yes there's an easy way of changing the hostname in FC2. after Login just at command line enter 'hostname' to see what is the hostname seted there, if returns localhost then you have to change this in 1. '/etc/sysconfig/network' edit this file and give hostname whatever you like in the line "hostname=" and then save this file and at the command line give the hostname command but now also you will get the same old host name as 'localhost' so set the hostname using command hostname (for eg: hostname vikas -- here hostname command will set the hostname as vikas, pls note that the name you are giving for the host name must be same as the hostname you have specified in '/etc/sysconfig/network' file. 2. '/etc/hosts' edit this file and this file would look like " IPAddress hostname localhost.localdomain localhost" in the place of hostname give the name as you wish(in the example same as hostname given in /etc/sysconfig/network file and hostname setted at command line), and save this file 3. Now restart the NFS and Network service by using the command 'service nfs restart' and 'service network restart' 4. Restart your computer inorder to take effect the changes you have done. now onwards your hostname will be setted as you had given in the above steps. (Be careful in following the above steps, because if you do the single mistake also it may cause your system problem in booting or functioning) if further doubts send an email to me. all the best. regards vikas >From: Brian Akins >Reply-To: Discussion list about Kickstart >To: Discussion list about Kickstart >Subject: Fedora core 2 and hostname >Date: Fri, 18 Jun 2004 12:30:55 -0400 > >Is there an easy way to get the hostname in post in FC2. hostname just >returns localhost > >I'm using dhcp. > >-- >Brian Akins >Senior Systems Engineer >CNN Internet Technologies > > >_______________________________________________ >Kickstart-list mailing list >Kickstart-list at redhat.com >https://www.redhat.com/mailman/listinfo/kickstart-list _________________________________________________________________ Marriage? http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74 Join BharatMatrimony.com for free. From phr at doc.ic.ac.uk Sat Jun 19 11:13:11 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Sat, 19 Jun 2004 12:13:11 +0100 (BST) Subject: Need help with PXE/NFS install In-Reply-To: <200406181807.i5II7Ha05829@vhost6.atomicservers.com> References: <200406181807.i5II7Ha05829@vhost6.atomicservers.com> Message-ID: On Fri, 18 Jun 2004, Mike Cotton wrote: >I need some assistance with finishing a PXE NFS install. I have >reviewed the archives and the information there has helped me to get >this far. SQ1 [Standard Question #1]: Which version of Redhat/Fedora/Anaconda? >Here is the part I am stuck on - whenever I try to add kickstart >information into the hex file (ksdevice=eth0 ks=nfs:/{fileserver >IP}/path to the ks file), the vmlinuz and initrd.img file are found and >the initial install begins. As the install is checking for hardware it >kernel panics with a VFS error when attempting to locate the hard >drive. It seems that the megaraid driver we need is not getting >installed, and it gacks at that point. The megaraid support in the installation kernel has evolved over the last few distros; this page has a good summary: http://linux.dell.com/storage.shtml#megaraid >To be clear - the nfs portion is operational and will lead to an >interactive install, but when the kickstart information for an >unattended installation, the install kernel panics with a VFS error. I might be wrong then - either the driver support is there, or it isn't. Kickstart oughtn't make any difference. You're using initrd-everything.img, aka pxeboot/initrd.img in recent releases, right? Cheers, Phil From tdiehl at rogueind.com Sat Jun 19 16:30:06 2004 From: tdiehl at rogueind.com (Tom Diehl) Date: Sat, 19 Jun 2004 12:30:06 -0400 (EDT) Subject: Fedora core 2 and hostname In-Reply-To: References: Message-ID: On Sat, 19 Jun 2004, VIKAS B wrote: > Hi Brian, > Yes there's an easy way of changing the hostname in FC2. > after Login just at command line enter 'hostname' to see what is the > hostname seted there, if returns localhost then you have to change this in > > 1. '/etc/sysconfig/network' edit this file and give hostname whatever you > like in the line "hostname=" and then save this file and at the command line > give the hostname command but now also you will get the same old host name > as 'localhost' so set the hostname using command hostname (for eg: hostname > vikas -- here hostname command will set the hostname as vikas, pls note > that the name you are giving for the host name must be same as the hostname > you have specified in '/etc/sysconfig/network' file. No, it does not have to be the same. It is just that if it is different, then what is in /etc/sysconfig/network will be the hostname when you reboot. The hostname you set on the command line will be gone. If you are going to reboot then messing with the hostname command is a waste of time. At boot time the initscripts read the hostname from /etc/sysconfig/network and set it to whatever the HOSTNAME variable is set to. Note the HOSTNAME= line in the above file must be uppercase. ie: HOSTNAME=foo will set the hostname to foo. hostname=foo will not. > 2. '/etc/hosts' edit this file and this file would look like > " IPAddress hostname localhost.localdomain localhost" > in the place of hostname give the name as you wish(in the example same as > hostname given in /etc/sysconfig/network file and hostname setted at command > line), and save this file If you have a working dns on the network and the new name resolves you do not need to mess with /etc/hosts. If you are going to mess with /etc/hosts leave the line with the localhost stuff in it and add another line with the new info. That way localhost will always resolve no matter what. Not having localhost resolve can cause problems sometimes. > 3. Now restart the NFS and Network service by using the command 'service nfs > restart' and > 'service network restart' Why? This is not necessary, especially if you are going to reboot. What is the point of restarting a service and then rebooting the machine to restart the service again. It appears to me you are giving advice on a subject you know little about. > 4. Restart your computer inorder to take effect the changes you have done. Not necessary. Pick one way or the other. If you are going to restart the machine simply edit /etc/sysconfig/network and /etc/hosts if necessary, then reboot. If you do not want to reboot, then do the above plus "hostname new_hostname" and "service syslog restart" so that syslog rereads the hostname and labels the log files correctly. The OP wanted a simple way to change the hostname. Your way while it will not hurt is unnecessarily complex and as you described it above will not work (hostname= != HOSTNAME=). HTH, Tom From phr at doc.ic.ac.uk Sun Jun 20 00:17:56 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Sun, 20 Jun 2004 01:17:56 +0100 (BST) Subject: problem integrating ks.cfg with RHEL WS 2.1 ISOs In-Reply-To: <20040618231515.66715.qmail@web50004.mail.yahoo.com> References: <20040618231515.66715.qmail@web50004.mail.yahoo.com> Message-ID: On Fri, 18 Jun 2004, Ajay Mulwani wrote: >1) The first set has integrated ks.cfg file within isolinux/initrd.img >and also updated isolinux/isolinux.cfg so that this ks.cfg is called by >default even if just the "Enter" key is pressed at the "boot:" prompt. >The ks.cfg file has ONLY the %post section which calls a script. With >this set the problem that I am facing is the linux installer does not >gives me an option to select packages and starts the "minimal" >installation always. Sounds like you want the "interactive" option in the kickstart file: interactive (optional) Uses the information provided in the kickstart file during the installation, but allow for inspection and modification of the values given. You will be presented with each screen of the installation program with the values from the kickstart file. Either accept the values by clicking Next or change the values and click Next to continue. See also [50]the Section called autostep. >2) To avoid the situation in (1) I created the second set. Here, I >restored the original initrd.img and isolinux.cfg and now kept ks.cfg >at the top level and at isolinux directory. Now if at the "boot:" >prompt I give "linux ks=cdrom:/ks.cfg" Is that a valid argument? command-line.txt has: ks=cdrom: Kickstart from CDROM ks=file: Kickstart from a file (path = 'fd0/ks.cfg') (observe no file specified for cdrom, perhaps file would work) Cheers, Phil From amul64 at yahoo.com Sun Jun 20 06:48:41 2004 From: amul64 at yahoo.com (Ajay Mulwani) Date: Sat, 19 Jun 2004 23:48:41 -0700 (PDT) Subject: problem integrating ks.cfg with RHEL WS 2.1 ISOs In-Reply-To: Message-ID: <20040620064841.33018.qmail@web50009.mail.yahoo.com> Hello Philip, Sincere thanks for your inputs. I am aware of the interactive option but just missed to try it and will give it a shot... However the question is: why just the package selection screen is skipped despite no %packages section specified (as I have mentioned there is only %post section in my ks.cfg).. Anyway this option definately needs an attempt. Thanks. "linux ks=cdrom:/ks.cfg" is a valid syntax. "file" argument is used if ks.cfg is to be integrated with initrd.img which is what I have done while creating the first set. Regards, Ajay --- Philip Rowlands wrote: > On Fri, 18 Jun 2004, Ajay Mulwani wrote: > > >1) The first set has integrated ks.cfg file within > isolinux/initrd.img > >and also updated isolinux/isolinux.cfg so that this > ks.cfg is called by > >default even if just the "Enter" key is pressed at > the "boot:" prompt. > >The ks.cfg file has ONLY the %post section which > calls a script. With > >this set the problem that I am facing is the linux > installer does not > >gives me an option to select packages and starts > the "minimal" > >installation always. > > Sounds like you want the "interactive" option in the > kickstart file: > > interactive (optional) > > Uses the information provided in the kickstart > file during the > installation, but allow for inspection and > modification of the > values given. You will be presented with each > screen of the > installation program with the values from the > kickstart file. > Either accept the values by clicking Next or > change the values > and click Next to continue. See also [50]the > Section called > autostep. > > >2) To avoid the situation in (1) I created the > second set. Here, I > >restored the original initrd.img and isolinux.cfg > and now kept ks.cfg > >at the top level and at isolinux directory. Now if > at the "boot:" > >prompt I give "linux ks=cdrom:/ks.cfg" > > Is that a valid argument? command-line.txt has: > > ks=cdrom: Kickstart from CDROM > ks=file: Kickstart from a file (path = > 'fd0/ks.cfg') > > (observe no file specified for cdrom, perhaps file > would work) > > > Cheers, > Phil > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From phr at doc.ic.ac.uk Sun Jun 20 09:13:21 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Sun, 20 Jun 2004 10:13:21 +0100 (BST) Subject: problem integrating ks.cfg with RHEL WS 2.1 ISOs In-Reply-To: <20040620064841.33018.qmail@web50009.mail.yahoo.com> References: <20040620064841.33018.qmail@web50009.mail.yahoo.com> Message-ID: On Sat, 19 Jun 2004, Ajay Mulwani wrote: >I am aware of the interactive option but just missed to try it and will >give it a shot... However the question is: why just the package >selection screen is skipped despite no %packages section specified (as >I have mentioned there is only %post section in my ks.cfg).. Without "interactive", a kickstart file is intended for an unattended install. On a strict reading of the docs, the kickstart file has a number of mandatory settings (auth, bootloader, keyboard, lang, mouse, rootpw etc.). I've not tried deliberate omission, but my guess is that %packages, if not given, defaults to "@ Base" only, i.e. it *does* have a package list to work with, and therefore doesn't need to ask. Cheers, Phil From mcotton at aptas.com Mon Jun 21 18:12:32 2004 From: mcotton at aptas.com (Mike Cotton) Date: Mon, 21 Jun 2004 12:12:32 -0600 Subject: Need help with PXE/NFS install In-Reply-To: Message-ID: <200406211812.i5LICcZ07959@vhost6.atomicservers.com> Phil, < SQ1 [Standard Question #1]: References: <200406211812.i5LICcZ07959@vhost6.atomicservers.com> Message-ID: On Mon, 21 Jun 2004, Mike Cotton wrote: >So - I believe that I am using the correct pxeboot initrd.img file. >Should I need to create the file tree, or can I use the iso's? I think >that may be where the problem lies? You can do either, but if you "explode" the install tree ensure that you follow the directions in README-en, specifically: If you are setting up an installation tree for NFS, FTP, or HTTP installations, you must copy the RELEASE-NOTES files and all files from the RedHat directory on all Installation CD-ROMs. On Linux and UNIX systems, the following process will properly configure the /target/directory on your server (repeat for each disc): 1. Insert CD-ROM 2. mount /mnt/cdrom 3. cp -a /mnt/cdrom/RedHat /target/directory 4. cp /mnt/cdrom/RELEASE-NOTES* /target/directory (Installation CD 1 only) 5. umount /mnt/cdrom I don't think this is causing the kernel panic though - if anaconda can't find any storage it should just complain and prompt for more drivers, rather than fall over. Cheers, Phil From mcotton at aptas.com Mon Jun 21 23:06:46 2004 From: mcotton at aptas.com (Mike Cotton) Date: Mon, 21 Jun 2004 17:06:46 -0600 Subject: Need help with PXE/NFS install In-Reply-To: Message-ID: <200406212306.i5LN6lZ10256@vhost6.atomicservers.com> Phil, I may have a badly configured but operational environment - would you mind taking a look here and offering some input? There are 2 servers - 1 running DHCP and the other is a file server running TFTP and NFS. Server 1 has the DHCP config (10.0.0.1 for example sake.)- # Kickstart test area host testpc { hardware ethernet XX:XX:XX:XX:XX:XX; fixed-address 10.0.0.162; next-server 10.0.0.2; } The MAC is installed and the handoff works. Server 2 has the TFTP and NFS (10.0.0.2) The /tftpboot/linux-install/pxelinux.cfg directory has the hex file for the appropriate client IP 0A0000A2 (10.0.0.162) and reads - default test label test kernel test/vmlinuz append initrd=test/initrd.img ramdisk_size=10000 append ksdevice=eth0 ks=nfs:10.0.0.2/export2/ESv.3/10.0.0.162-kickstart Where test in the kernel and initrd reference is 10.0.0.2/share/ESv.3. The 10.0.0.162-kickstart file also lives in that directory. The 10.0.0.162- Kickstart file reads - # Kickstart file automatically generated by anaconda. install lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us mouse genericwheelps/2 --device psaux xconfig --card "ATI Rage XL" --videoram 8192 --hsync 31.5-35.1 --vsync 50-61 --resolution 800x600 --depth 24 --startxonboot --defaultdesktop gnome network --device eth0 --bootproto dhcp --hostname testpc network --device eth1 --bootproto dhcp --hostname testpc network --device eth2 --bootproto dhcp --hostname testpc rootpw --iscrypted $1$8VTcjY4h$w2clTqskNPhE6hMiSVM.I/ firewall --disabled authconfig --enableshadow --enablemd5 timezone America/Denver bootloader --location=mbr # 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 part /boot --fstype ext3 --start=260 --end=271 --ondisk=sda part swap --start=1 --end=259 --ondisk=sda part / --fstype ext3 --start=272 --end=1037 --ondisk=sda part /usr --fstype ext3 --start=1038 --end=2057 --ondisk=sda part /var --fstype ext3 --start=2058 --end=2568 --ondisk=sda part /export --fstype ext3 --start=2569 --end=9727 --ondisk=sda %packages @ engineering-and-scientific @ legacy-software-development @ editors @ system-tools @ base-x @ development-tools @ printing @ text-internet @ kde-desktop @ x-software-development @ server-cfg @ dialup @ admin-tools @ authoring-and-publishing @ gnome-desktop @ kernel-development @ graphical-internet @ compat-arch-support -ant -gcc-g77-ssa -ant -gcc-java-ssa -gcc-g77 ethereal-gnome kernel-smp kernel -gcc-g77 grub -nedit -gcc-java -gcc-gnat ethereal-gnome -gcc-gnat -nmap -gcc-java %post -------------------- The NFS share is /share/ESv.3 and has the 4 .iso's in it and also has each of the 4 disks uncompressed as folders called disk1, disk2, etc... It also has the 10.0.0.162-kickstart file in it. I also copied the images folder off disk1 into the root of the /share/ESv.3 folder for the pxeboot images for booting. ---------------------------------- Ok - the strange part is that if I remove the append ksdevice.... line out of the 0A0000A2 file - anaconda will start the installer and load the megaraid driver and drop me at the interactive start screen. Can you see if I have created a loop or some other issue? Thanks again for all of your assistance!!! Mike From phr at doc.ic.ac.uk Tue Jun 22 06:32:58 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Tue, 22 Jun 2004 07:32:58 +0100 (BST) Subject: Need help with PXE/NFS install In-Reply-To: <200406212306.i5LN6lZ10256@vhost6.atomicservers.com> References: <200406212306.i5LN6lZ10256@vhost6.atomicservers.com> Message-ID: On Mon, 21 Jun 2004, Mike Cotton wrote: >label test > kernel test/vmlinuz > append initrd=test/initrd.img ramdisk_size=10000 > append ksdevice=eth0 ks=nfs:10.0.0.2/export2/ESv.3/10.0.0.162-kickstart That might not work - try putting all the "append ..." items on a single line. Where did "ramdisk_size=10000" come from? Try taking it out. For comparison: $ cat pxelinux.cfg/default label ks kernel vmlinuz append ks=nfs:10.10.10.10:/export/redhat/rhel3/kickstart/mdb/ initrd=initrd.img which works for me. >The NFS share is /share/ESv.3 and has the 4 .iso's in it and also has each >of the 4 disks uncompressed as folders called disk1, disk2, etc... As per previous mail, there's a certain way the "exploded" file tree has to be constructed. I suspect the disk{1,2,3,4} directories are being ignored. >Ok - the strange part is that if I remove the append ksdevice.... line >out of the 0A0000A2 file - anaconda will start the installer and load >the megaraid driver and drop me at the interactive start screen. (BTW, suggest fetching latest syslinux package - it doesn't require the 16-bit packed filenames ("0A0000A2"), but permits more human-readable alternatives.) I wouldn't conclude anything from landing at the options screens - typically anaconda, in the absence of a kickstart file, will throw you to the interactive menus without a whisper. Check the other VTs (Alt+F2, Alt+F3 etc.) for interesting-looking error messages. Cheers, Phil From johnpaulmp at amiindia.co.in Tue Jun 22 06:51:59 2004 From: johnpaulmp at amiindia.co.in (johnpaul) Date: Tue, 22 Jun 2004 12:21:59 +0530 Subject: please help needed References: <200406212306.i5LN6lZ10256@vhost6.atomicservers.com> Message-ID: <014b01c45825$72aea960$8300000a@johnpaul> hai everybody I am customizing the 2.4.20 kernel and I am changing the installer Slightly. I am creating the hdlists with only the anaconda RPMS and I am building the installer with all the RPMS in the RedHat/RPMS again I am creating the hdlist with the resulting package order But while Installing i am getting an error saying that " You dont have enough space in / directory and you need 10MB more " how to proceed along this thanx & Regards John paul From forrestx.taylor at intel.com Tue Jun 22 16:01:00 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 22 Jun 2004 09:01:00 -0700 Subject: please help needed In-Reply-To: <014b01c45825$72aea960$8300000a@johnpaul> References: <200406212306.i5LN6lZ10256@vhost6.atomicservers.com> <014b01c45825$72aea960$8300000a@johnpaul> Message-ID: <1087920060.30368.17.camel@bad.jf.intel.com> On Mon, 2004-06-21 at 23:51, johnpaul wrote: > hai everybody > > I am customizing the 2.4.20 kernel and I am changing the installer > Slightly. I am creating the hdlists with only the anaconda RPMS and I am > building the installer with all the RPMS in the RedHat/RPMS again I am > creating the hdlist with the resulting package order > But while Installing i am getting an error saying that " You dont > have enough space in / directory and you need 10MB more " > how to proceed along this What does `df -h` show? This looks like you do not have enough space in / to install anaconda(?). Forrest From mcotton at aptas.com Tue Jun 22 17:21:09 2004 From: mcotton at aptas.com (Mike Cotton) Date: Tue, 22 Jun 2004 11:21:09 -0600 Subject: Need help with PXE/NFS install In-Reply-To: Message-ID: <200406221721.i5MHL9Z21257@vhost6.atomicservers.com> Phil, Thank you very much for your assistance!! The single append line did indeed resolve the kernel panic. I was also missing the colon for the nfs path and after resolving that one Kickstart is working!! I will tinker with the Kickstart script and the post options to get to the next step. Many Thanks Again!!!!! Mike From phr at doc.ic.ac.uk Tue Jun 22 17:32:03 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Tue, 22 Jun 2004 18:32:03 +0100 (BST) Subject: Need help with PXE/NFS install In-Reply-To: <200406221721.i5MHL9Z21257@vhost6.atomicservers.com> References: <200406221721.i5MHL9Z21257@vhost6.atomicservers.com> Message-ID: On Tue, 22 Jun 2004, Mike Cotton wrote: >Thank you very much for your assistance!! The single append line did >indeed resolve the kernel panic. I was also missing the colon for the >nfs path and after resolving that one Kickstart is working!! Pleased to hear it. Perhaps a bug report (or at least warning) for Syslinux is in order - which version do you have? ("strings pxelinux.0 |grep PXELINUX" will confess) Cheers, Phil From mcotton at aptas.com Tue Jun 22 17:38:02 2004 From: mcotton at aptas.com (Mike Cotton) Date: Tue, 22 Jun 2004 11:38:02 -0600 Subject: Need help with PXE/NFS install In-Reply-To: Message-ID: <200406221738.i5MHc2Z26872@vhost6.atomicservers.com> Phil, We are running PXELINUX 2.06 2003-08-22 on the server with the tftp/nfs setup. Thank you for looking out for others coming down the same path. Mike From johnpaulmp at amiindia.co.in Wed Jun 23 04:42:32 2004 From: johnpaulmp at amiindia.co.in (johnpaul) Date: Wed, 23 Jun 2004 10:12:32 +0530 Subject: please help needed References: <200406212306.i5LN6lZ10256@vhost6.atomicservers.com><014b01c45825$72aea960$8300000a@johnpaul> <1087920060.30368.17.camel@bad.jf.intel.com> Message-ID: <019e01c458dc$82e2d650$8300000a@johnpaul> thanx for your intrest Actually df at that stage shows only 215MB but i have partitioned / for 512 MB ie still I have more than 200MB free I hope creating hd list and building Installer may be the problem . can you please tell me the steps to build the Installer again thanx in advance John paul ----- Original Message ----- From: "Taylor, ForrestX" To: "Discussion list about Kickstart" Sent: Tuesday, June 22, 2004 9:31 PM Subject: Re: please help needed > On Mon, 2004-06-21 at 23:51, johnpaul wrote: > > hai everybody > > > > I am customizing the 2.4.20 kernel and I am changing the installer > > Slightly. I am creating the hdlists with only the anaconda RPMS and I am > > building the installer with all the RPMS in the RedHat/RPMS again I am > > creating the hdlist with the resulting package order > > But while Installing i am getting an error saying that " You dont > > have enough space in / directory and you need 10MB more " > > how to proceed along this > > What does `df -h` show? This looks like you do not have enough space in > / to install anaconda(?). > > Forrest > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From crow69dude at hotmail.com Thu Jun 24 15:42:49 2004 From: crow69dude at hotmail.com (Crow69 aka thedude) Date: Thu, 24 Jun 2004 10:42:49 -0500 Subject: two kickstart problems i'm having Message-ID: Hi, First question (how do I avoid probing for monitor?): When I am doing a kickstart over NFS using Fedora Core 2 to a PC that does not have a monitor hooked up, it doesn't kickstart and I notice (when I hook up a monitor) that it is asking for my monitor type. Is there something I need to put in the kickstart file to tell it not to look for a monitor or to use a default basic monitor? Second question (what causes 3 minute delay during kickstart "Determining host name and domain" section of the kickstart with Fedora Core 2?): With Fedora Core 2, I have noticed a kickstarting delay at the point when the PC being NFS kickstarted is at the "Determining host name and domain" point in the kickstart. I notice a delay of about 3 minutes or so at this point. Can someone help me determine what is causing this delay? What on the dhcpd config file could I do to speed up this delay? (The kickstart does work, but there seems to be some kind of 3 minute timeout at the "Determining host name and domain" point in the kickstart. I'd like to get rid of that timeout.) Thanks in advance for any help! Jeff _________________________________________________________________ MSN Toolbar provides one-click access to Hotmail from any Web page ? FREE download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/ From phr at doc.ic.ac.uk Thu Jun 24 15:48:32 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Thu, 24 Jun 2004 16:48:32 +0100 (BST) Subject: two kickstart problems i'm having In-Reply-To: References: Message-ID: On Thu, 24 Jun 2004, Crow69 aka thedude wrote: >When I am doing a kickstart over NFS using Fedora Core 2 to a PC that does >not have a monitor hooked up, it doesn't kickstart and I notice (when I hook >up a monitor) that it is asking for my monitor type. Is there something I >need to put in the kickstart file to tell it not to look for a monitor or to >use a default basic monitor? Either "skipx" or "xconfig --noprobe". Both described in kickstart-docs.txt from the anaconda package. Not sure on the other one - consider DNS lookup timeouts?? Cheers, Phil From dwaquilina at gmail.com Fri Jun 25 13:39:11 2004 From: dwaquilina at gmail.com (David Aquilina) Date: Fri, 25 Jun 2004 09:39:11 -0400 Subject: two kickstart problems i'm having In-Reply-To: References: Message-ID: On Thu, 24 Jun 2004 10:42:49 -0500, Crow69 aka thedude wrote: > > Second question (what causes 3 minute delay during kickstart "Determining > host name and domain" section of the kickstart with Fedora Core 2?): I'm not sure about Fedora Core 2 specifically, but in RHL (and RHEL, iirc) it will try and find a DHCP server to fetch network information from even if you've told it to use a static IP address. -- David Aquilina dwaquilina at gmail.com From jason.ctr.alburger at faa.gov Tue Jun 29 13:50:11 2004 From: jason.ctr.alburger at faa.gov (jason.ctr.alburger at faa.gov) Date: Tue, 29 Jun 2004 09:50:11 -0400 Subject: check-repository problems Message-ID: RH 7.2 I'm attempting for the 1st time to build a customized kickstart installation. I've trimmed down the RPMs and have edited the comps file to get rid of references to the packages I don't want. I've seen from several sources that I should comment out the "import todo" in the check-repository.py script, which I have done. When I run the script, I get the message: Traceback (innermost last): File "/usr/lib/anaconda-runtime/check-repository.py", line 34, in ? from comps import ComponentSet, HeaderList File "/usr/lib/anaconda/comps.py", line 17, in ? import rpm ImportError: librpm-4.0.3.so: cannot open shared object file: No such file or directory Is this a problem with my comps file or my version of librpm? A search for librpm on my system shows: /usr/lib/librpmbuild.a /usr/lib/librpm.a /usr/lib/librpm.la /usr/lib/librpm.so /usr/lib/librpmbuild.la /usr/lib/librpmbuild.so /usr/lib/librpmdb.a /usr/lib/librpmdb.la /usr/lib/librpmdb.so /usr/lib/librpmio.a /usr/lib/librpmio.la /usr/lib/librpmio.so /usr/lib/librpmbuild-4.0.4.so /usr/lib/librpm-4.0.4.so /usr/lib/librpmdb-4.0.4.so /usr/lib/librpmio-4.0.4.so Thanks in advance! Jason Alburger 609-485-7225 CPDLC Engineer Joseph Sheairs Associates, Inc. FAA/AOS-330 From forrestx.taylor at intel.com Tue Jun 29 16:36:15 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 29 Jun 2004 09:36:15 -0700 Subject: check-repository problems In-Reply-To: References: Message-ID: <1088526975.6382.36.camel@bad.jf.intel.com> On Tue, 2004-06-29 at 06:50, jason.ctr.alburger at faa.gov wrote: > > > RH 7.2 > > I'm attempting for the 1st time to build a customized kickstart > installation. I've trimmed down the RPMs and have edited the comps file to > get rid of references to the packages I don't want. I've seen from several > sources that I should comment out the "import todo" in the > check-repository.py script, which I have done. When I run the script, I > get the message: > > Traceback (innermost last): > File "/usr/lib/anaconda-runtime/check-repository.py", line 34, in ? > from comps import ComponentSet, HeaderList > File "/usr/lib/anaconda/comps.py", line 17, in ? > import rpm > ImportError: librpm-4.0.3.so: cannot open shared object file: No such file > or directory > > > Is this a problem with my comps file or my version of librpm? A search for > librpm on my system shows: > > /usr/lib/librpmbuild.a > /usr/lib/librpm.a > /usr/lib/librpm.la > /usr/lib/librpm.so > /usr/lib/librpmbuild.la > /usr/lib/librpmbuild.so > /usr/lib/librpmdb.a > /usr/lib/librpmdb.la > /usr/lib/librpmdb.so > /usr/lib/librpmio.a > /usr/lib/librpmio.la > /usr/lib/librpmio.so > /usr/lib/librpmbuild-4.0.4.so > /usr/lib/librpm-4.0.4.so > /usr/lib/librpmdb-4.0.4.so > /usr/lib/librpmio-4.0.4.so It is trying to import librpm-4.0.3.so, where you have librpm-4.0.4.so. Do you have different versions of rpm in your build? Forrest From jason.ctr.alburger at faa.gov Tue Jun 29 16:52:50 2004 From: jason.ctr.alburger at faa.gov (jason.ctr.alburger at faa.gov) Date: Tue, 29 Jun 2004 12:52:50 -0400 Subject: check-repository problems Message-ID: Looks like I have rpm-4.0.3-1.03.i386.rpm in the build directory but librpm-4.0.4.so is installed on the box. I'll install 4.0.3 and see if that helps me out. Jason Alburger 609-485-7225 CPDLC Engineer Joseph Sheairs Associates, Inc. FAA/AOS-330 "Taylor, ForrestX" .com> cc: Sent by: Subject: Re: check-repository problems kickstart-list-bounces @redhat.com 06/29/2004 12:36 PM Please respond to Discussion list about Kickstart On Tue, 2004-06-29 at 06:50, jason.ctr.alburger at faa.gov wrote: > > > RH 7.2 > > I'm attempting for the 1st time to build a customized kickstart > installation. I've trimmed down the RPMs and have edited the comps file to > get rid of references to the packages I don't want. I've seen from several > sources that I should comment out the "import todo" in the > check-repository.py script, which I have done. When I run the script, I > get the message: > > Traceback (innermost last): > File "/usr/lib/anaconda-runtime/check-repository.py", line 34, in ? > from comps import ComponentSet, HeaderList > File "/usr/lib/anaconda/comps.py", line 17, in ? > import rpm > ImportError: librpm-4.0.3.so: cannot open shared object file: No such file > or directory > > > Is this a problem with my comps file or my version of librpm? A search for > librpm on my system shows: > > /usr/lib/librpmbuild.a > /usr/lib/librpm.a > /usr/lib/librpm.la > /usr/lib/librpm.so > /usr/lib/librpmbuild.la > /usr/lib/librpmbuild.so > /usr/lib/librpmdb.a > /usr/lib/librpmdb.la > /usr/lib/librpmdb.so > /usr/lib/librpmio.a > /usr/lib/librpmio.la > /usr/lib/librpmio.so > /usr/lib/librpmbuild-4.0.4.so > /usr/lib/librpm-4.0.4.so > /usr/lib/librpmdb-4.0.4.so > /usr/lib/librpmio-4.0.4.so It is trying to import librpm-4.0.3.so, where you have librpm-4.0.4.so. Do you have different versions of rpm in your build? Forrest _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From jason.ctr.alburger at faa.gov Tue Jun 29 20:08:31 2004 From: jason.ctr.alburger at faa.gov (jason.ctr.alburger at faa.gov) Date: Tue, 29 Jun 2004 16:08:31 -0400 Subject: check-repository.py questions Message-ID: RH 7.2 Still trying to build a kickstart installation & I'm having troubles with check-repository.py. I ran the script a few times & it told me there was a problem with some things, at which time I replaced the rpms I needed back into my build directory, and it looks like those problems were being fixed one by one. Then, I ran the script again & got the following message: # check-repository.py . Traceback (innermost last): File "/usr/lib/anaconda-runtime/check-repository.py", line 97, in ? CheckRepository(sys.argv[1]) File "/usr/lib/anaconda-runtime/check-repository.py", line 93, in __init__ self.getCompsList () File "/usr/lib/anaconda-runtime/check-repository.py", line 56, in getCompsList self.comps = self.readComps(self.hdList) File "/usr/lib/anaconda-runtime/check-repository.py", line 64, in readComps '/RedHat/base/comps', hdlist) File "/usr/lib/anaconda/comps.py", line 795, in __init__ self.readCompsFile(file, self.packages) File "/usr/lib/anaconda/comps.py", line 581, in readCompsFile comp.setDefaultSelection() File "/usr/lib/anaconda/comps.py", line 322, in setDefaultSelection self.select() File "/usr/lib/anaconda/comps.py", line 257, in select "included by component %s", name, self.name) File "/usr/lib/anaconda/log.py", line 38, in __call__ raise RuntimeError, "log file not open yet" RuntimeError: log file not open yet Can anybody help? Thanks!! Jason Alburger 609-485-7225 CPDLC Engineer Joseph Sheairs Associates, Inc. FAA/AOS-330 From forrestx.taylor at intel.com Tue Jun 29 20:17:21 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 29 Jun 2004 13:17:21 -0700 Subject: check-repository.py questions In-Reply-To: References: Message-ID: <1088540241.6382.236.camel@bad.jf.intel.com> On Tue, 2004-06-29 at 13:08, jason.ctr.alburger at faa.gov wrote: > > > RH 7.2 > > Still trying to build a kickstart installation & I'm having troubles with > check-repository.py. I ran the script a few times & it told me there was a > problem with some things, at which time I replaced the rpms I needed back > into my build directory, and it looks like those problems were being fixed > one by one. Then, I ran the script again & got the following message: > File "/usr/lib/anaconda/comps.py", line 257, in select > "included by component %s", name, self.name) > File "/usr/lib/anaconda/log.py", line 38, in __call__ > raise RuntimeError, "log file not open yet" > RuntimeError: log file not open yet Here is something that Alain came up with a while ago: https://listman.redhat.com/archives/anaconda-devel-list/2003-March/msg00048.html Forrest From kfir at aduva.com Wed Jun 30 06:39:13 2004 From: kfir at aduva.com (Kfir Lavi) Date: Wed, 30 Jun 2004 09:39:13 +0300 Subject: default packages Message-ID: <40E26011.2060406@aduva.com> Hi, I would like to have kickstart file for the default (ie: next, next...), and for the Base category. How do i know in advance what is the default packages or packages groups of distribution? Thanks, Kfir From phr at doc.ic.ac.uk Wed Jun 30 06:44:01 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Wed, 30 Jun 2004 07:44:01 +0100 (BST) Subject: default packages In-Reply-To: <40E26011.2060406@aduva.com> References: <40E26011.2060406@aduva.com> Message-ID: On Wed, 30 Jun 2004, Kfir Lavi wrote: >I would like to have kickstart file for the default (ie: next, next...), >and for the Base category. >How do i know in advance what is the default packages or packages groups >of distribution? One of: RedHat/base/comps RedHat/base/comps.xml Fedora/base/comps.xml depending which version you're using. Cheers, Phil From kfir at aduva.com Wed Jun 30 06:55:38 2004 From: kfir at aduva.com (Kfir Lavi) Date: Wed, 30 Jun 2004 09:55:38 +0300 Subject: default packages In-Reply-To: References: <40E26011.2060406@aduva.com> Message-ID: <40E263EA.4040704@aduva.com> Philip Rowlands wrote: > On Wed, 30 Jun 2004, Kfir Lavi wrote: > > >>I would like to have kickstart file for the default (ie: next, next...), >>and for the Base category. >>How do i know in advance what is the default packages or packages groups >>of distribution? > > > One of: > RedHat/base/comps > RedHat/base/comps.xml > Fedora/base/comps.xml > > depending which version you're using. > > > Cheers, > Phil > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list Thanks for the quick replay. I know about comps.xml, but i don't find in this file the group of the default installation. Example: minimal installation is Core or Base? default installation uses kde or gnome? if i do interactive kickstart, when %packages is empty, i get a minimal intallation, but what is it Core or Base? I want to have a way befor installing, to know what are the default groups. Thanks From phr at doc.ic.ac.uk Wed Jun 30 07:29:46 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Wed, 30 Jun 2004 08:29:46 +0100 (BST) Subject: default packages In-Reply-To: <40E263EA.4040704@aduva.com> References: <40E26011.2060406@aduva.com> <40E263EA.4040704@aduva.com> Message-ID: On Wed, 30 Jun 2004, Kfir Lavi wrote: >I know about comps.xml, but i don't find in this file the group of the >default installation. >Example: minimal installation is Core or Base? >default installation uses kde or gnome? > >if i do interactive kickstart, when %packages is empty, i get a minimal >intallation, but what is it Core or Base? The default groups are specified by the true markup. Both Core and Base appear to have this set. Check the comps.xml documentation here: http://rhlinux.redhat.com/anaconda/comps.html Cheers, Phil From kfir at aduva.com Wed Jun 30 07:50:16 2004 From: kfir at aduva.com (Kfir Lavi) Date: Wed, 30 Jun 2004 10:50:16 +0300 Subject: default packages In-Reply-To: References: <40E26011.2060406@aduva.com> <40E263EA.4040704@aduva.com> Message-ID: <40E270B8.6080406@aduva.com> Philip Rowlands wrote: > On Wed, 30 Jun 2004, Kfir Lavi wrote: > > >>I know about comps.xml, but i don't find in this file the group of the >>default installation. >>Example: minimal installation is Core or Base? >>default installation uses kde or gnome? >> >>if i do interactive kickstart, when %packages is empty, i get a minimal >>intallation, but what is it Core or Base? > > > The default groups are specified by the true markup. > Both Core and Base appear to have this set. > > Check the comps.xml documentation here: > http://rhlinux.redhat.com/anaconda/comps.html > > > Cheers, > Phil I understand now the default group. Is there a way to know what groups are selected when i choose minimal in the installation? From thomas at polichromo.gr Wed Jun 30 09:33:33 2004 From: thomas at polichromo.gr (Thomas Bellos) Date: Wed, 30 Jun 2004 12:33:33 +0300 Subject: Fedora core 1 kickstart Message-ID: <003001c45e85$67c48450$25bec0c2@THOMASPC> Hello I have created a kickstart file and placed it into the top dir of the cdrom. Also I have changed the ks sction of the isolinux/isolinux.cfg file, to read .. append ks=cdrom:/ks.cfg ... but when I boot from the cd I don't see the kickstart working, during the various phases of installation. I used interactive mode for the kickstart How can I be sure that the kickstart is read? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From martinr at hotkey.net.au Wed Jun 30 19:46:34 2004 From: martinr at hotkey.net.au (Martin Rheumer) Date: Wed, 30 Jun 2004 19:46:34 Subject: Fedora core 1 kickstart In-Reply-To: <003001c45e85$67c48450$25bec0c2@THOMASPC> Message-ID: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 724 bytes Desc: not available URL: From thomas at polichromo.gr Wed Jun 30 10:10:52 2004 From: thomas at polichromo.gr (Thomas Bellos) Date: Wed, 30 Jun 2004 13:10:52 +0300 Subject: Fedora core 1 kickstart References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> Message-ID: <006501c45e8a$9b405980$25bec0c2@THOMASPC> Thanks for the reply When the cdrom boots do I need to type anything special or just hit enter? ----- Original Message ----- From: Martin Rheumer To: Discussion list about Kickstart ; kickstart-list at redhat.com Sent: Wednesday, June 30, 2004 7:46 PM Subject: Re: Fedora core 1 kickstart ks=cdrom is all you need. Martin At 12:33 PM 6/30/2004 +0300, Thomas Bellos wrote: >>>> Hello I have created a kickstart file and placed it into the top dir of the cdrom. Also I have changed the ks sction of the isolinux/isolinux.cfg file, to read .. append ks=cdrom:/ks.cfg ... but when I boot from the cd I don't see the kickstart working, during the various phases of installation. I used interactive mode for the kickstart How can I be sure that the kickstart is read? Thanks _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list <<<< ------------------------------------------------------------------------------ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From martinr at hotkey.net.au Wed Jun 30 20:15:26 2004 From: martinr at hotkey.net.au (Martin Rheumer) Date: Wed, 30 Jun 2004 20:15:26 Subject: Fedora core 1 kickstart In-Reply-To: <006501c45e8a$9b405980$25bec0c2@THOMASPC> References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> Message-ID: <3.0.5.32.20040630201526.00e5aba0@pop.mogwai.net.au> A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 2363 bytes Desc: not available URL: From thomas at polichromo.gr Wed Jun 30 10:36:11 2004 From: thomas at polichromo.gr (Thomas Bellos) Date: Wed, 30 Jun 2004 13:36:11 +0300 Subject: Fedora core 1 kickstart References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> <3.0.5.32.20040630201526.00e5aba0@pop.mogwai.net.au> Message-ID: <008701c45e8e$25097400$25bec0c2@THOMASPC> Thanks I will give it a go ----- Original Message ----- From: Martin Rheumer To: Discussion list about Kickstart Sent: Wednesday, June 30, 2004 8:15 PM Subject: Re: Fedora core 1 kickstart edit your isolinux.cfg to something like this.. And it will do it all itself. default ks prompt 1 timeout 60 display boot.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 snake.msg label linux kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 label text kernel vmlinuz append initrd=initrd.img text ramdisk_size=8192 label expert kernel vmlinuz append expert initrd=initrd.img ramdisk_size=8192 label ks kernel vmlinuz append ks=cdrom initrd=initrd.img ramdisk_size=8192 label lowres kernel vmlinuz append initrd=initrd.img lowres ramdisk_size=8192 label selinux kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 selinux label memtest86 kernel memtest append - At 01:10 PM 6/30/2004 +0300, you wrote: >>>> Thanks for the reply When the cdrom boots do I need to type anything special or just hit enter? ----- Original Message ----- From: Martin Rheumer To: Discussion list about Kickstart ; kickstart-list at redhat.com Sent: Wednesday, June 30, 2004 7:46 PM Subject: Re: Fedora core 1 kickstart ks=cdrom is all you need. Martin At 12:33 PM 6/30/2004 +0300, Thomas Bellos wrote: >>>> Hello I have created a kickstart file and placed it into the top dir of the cdrom. Also I have changed the ks sction of the isolinux/isolinux.cfg file, to read .. append ks=cdrom:/ks.cfg ... but when I boot from the cd I don't see the kickstart working, during the various phases of installation. I used interactive mode for the kickstart How can I be sure that the kickstart is read? Thanks _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list <<<< ---------- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list <<<< ------------------------------------------------------------------------------ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas at polichromo.gr Wed Jun 30 12:24:34 2004 From: thomas at polichromo.gr (Thomas Bellos) Date: Wed, 30 Jun 2004 15:24:34 +0300 Subject: Fedora core 1 kickstart References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> <3.0.5.32.20040630201526.00e5aba0@pop.mogwai.net.au> Message-ID: <002e01c45e9d$46be2780$25bec0c2@THOMASPC> unfortunately it didn't work once again I can't figure out what is wrong ----- Original Message ----- From: Martin Rheumer To: Discussion list about Kickstart Sent: Wednesday, June 30, 2004 8:15 PM Subject: Re: Fedora core 1 kickstart edit your isolinux.cfg to something like this.. And it will do it all itself. default ks prompt 1 timeout 60 display boot.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 snake.msg label linux kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 label text kernel vmlinuz append initrd=initrd.img text ramdisk_size=8192 label expert kernel vmlinuz append expert initrd=initrd.img ramdisk_size=8192 label ks kernel vmlinuz append ks=cdrom initrd=initrd.img ramdisk_size=8192 label lowres kernel vmlinuz append initrd=initrd.img lowres ramdisk_size=8192 label selinux kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 selinux label memtest86 kernel memtest append - At 01:10 PM 6/30/2004 +0300, you wrote: >>>> Thanks for the reply When the cdrom boots do I need to type anything special or just hit enter? ----- Original Message ----- From: Martin Rheumer To: Discussion list about Kickstart ; kickstart-list at redhat.com Sent: Wednesday, June 30, 2004 7:46 PM Subject: Re: Fedora core 1 kickstart ks=cdrom is all you need. Martin At 12:33 PM 6/30/2004 +0300, Thomas Bellos wrote: >>>> Hello I have created a kickstart file and placed it into the top dir of the cdrom. Also I have changed the ks sction of the isolinux/isolinux.cfg file, to read .. append ks=cdrom:/ks.cfg ... but when I boot from the cd I don't see the kickstart working, during the various phases of installation. I used interactive mode for the kickstart How can I be sure that the kickstart is read? Thanks _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list <<<< ---------- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list <<<< ------------------------------------------------------------------------------ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From pantz at lqt.ca Wed Jun 30 13:41:09 2004 From: pantz at lqt.ca (Paul Pianta) Date: Wed, 30 Jun 2004 09:41:09 -0400 Subject: default packages In-Reply-To: <40E26011.2060406@aduva.com> References: <40E26011.2060406@aduva.com> Message-ID: <40E2C2F5.6050401@lqt.ca> Kfir Lavi wrote: > Hi, > I would like to have kickstart file for the default (ie: next, > next...), and for the Base category. > How do i know in advance what is the default packages or packages > groups of distribution? > > Thanks, > Kfir You could always go through a manual installation yourself - choosing the install options that you wish to test (eg. default install, minimal install, etc.) and then check the %packages section in the /root/anaconda-ks.cfg which will be on your newly installed system. This file is a kickstart summary of the install that you just completed. pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From pantz at lqt.ca Wed Jun 30 14:09:31 2004 From: pantz at lqt.ca (Paul Pianta) Date: Wed, 30 Jun 2004 10:09:31 -0400 Subject: Fedora core 1 kickstart In-Reply-To: <002e01c45e9d$46be2780$25bec0c2@THOMASPC> References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> <3.0.5.32.20040630201526.00e5aba0@pop.mogwai.net.au> <002e01c45e9d$46be2780$25bec0c2@THOMASPC> Message-ID: <40E2C99B.2020600@lqt.ca> Thomas Bellos wrote: > label ks > kernel vmlinuz > append ks=cdrom initrd=initrd.img ramdisk_size=8192 > If you have a 'label' like this in your isolinux.cfg file - you will need to type 'ks' at the boot prompt. Also your ks=cdrom:/ks.cfg should be ok too - both methods should work ok. If typing your isolinux 'label' at the boot prompt doesn't work ... include your complete isolinux.cfg and ks.cfg files in your next email and we will check out what's going on. pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From thomas at polichromo.gr Wed Jun 30 14:18:40 2004 From: thomas at polichromo.gr (Thomas Bellos) Date: Wed, 30 Jun 2004 17:18:40 +0300 Subject: Fedora core 1 kickstart References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> <3.0.5.32.20040630201526.00e5aba0@pop.mogwai.net.au><002e01c45e9d$46be2780$25bec0c2@THOMASPC> <40E2C99B.2020600@lqt.ca> Message-ID: <001101c45ead$3c68a2a0$25bec0c2@THOMASPC> I finally figured it At the prompt I typed linux ks=cdrom:/ks.cfg ----- Original Message ----- From: "Paul Pianta" To: "Discussion list about Kickstart" Sent: Wednesday, June 30, 2004 5:09 PM Subject: Re: Fedora core 1 kickstart > Thomas Bellos wrote: > > > label ks > > kernel vmlinuz > > append ks=cdrom initrd=initrd.img ramdisk_size=8192 > > > If you have a 'label' like this in your isolinux.cfg file - you will > need to type 'ks' at the boot prompt. > Also your ks=cdrom:/ks.cfg should be ok too - both methods should work ok. > > If typing your isolinux 'label' at the boot prompt doesn't work ... > include your complete isolinux.cfg and ks.cfg files in your next email > and we will check out what's going on. > > pantz > > -- > Before you criticize someone, walk a mile in their shoes ... > That way when you do criticize them, you're a mile away and you have their shoes! > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From pantz at lqt.ca Wed Jun 30 15:55:52 2004 From: pantz at lqt.ca (Paul Pianta) Date: Wed, 30 Jun 2004 11:55:52 -0400 Subject: Fedora core 1 kickstart In-Reply-To: <001101c45ead$3c68a2a0$25bec0c2@THOMASPC> References: <3.0.5.32.20040630194634.00e5aba0@pop.mogwai.net.au> <3.0.5.32.20040630201526.00e5aba0@pop.mogwai.net.au><002e01c45e9d$46be2780$25bec0c2@THOMASPC> <40E2C99B.2020600@lqt.ca> <001101c45ead$3c68a2a0$25bec0c2@THOMASPC> Message-ID: <40E2E288.8090102@lqt.ca> Thomas Bellos wrote: >I finally figured it >At the prompt I typed linux ks=cdrom:/ks.cfg > > By typing this - you are not using your custom line in isolinux.cfg. You are actually using the default label 'linux' in the isolinux.cfg file and then manually appending 'ks=cdrom:/ks.cfg'. If you want to use your customised line in isolinux.cfg - just type your custom label name - eg. 'ks' pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From forrestx.taylor at intel.com Wed Jun 30 16:04:30 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Wed, 30 Jun 2004 09:04:30 -0700 Subject: Fedora core 1 kickstart In-Reply-To: <003001c45e85$67c48450$25bec0c2@THOMASPC> References: <003001c45e85$67c48450$25bec0c2@THOMASPC> Message-ID: <1088611470.23242.5.camel@bad.jf.intel.com> On Wed, 2004-06-30 at 02:33, Thomas Bellos wrote: > Hello > I have created a kickstart file and placed it into the top dir of the > cdrom. > Also I have changed the ks sction of the isolinux/isolinux.cfg file, > to read > .. > append ks=cdrom:/ks.cfg ... > but when I boot from the cd I don't see the kickstart working, during > the various phases of installation. > I used interactive mode for the kickstart > How can I be sure that the kickstart is read? > Thanks Remove the interactive mode and you will see if it works. Forrest From kfir at aduva.com Wed Jun 30 16:42:57 2004 From: kfir at aduva.com (Kfir Lavi) Date: Wed, 30 Jun 2004 19:42:57 +0300 Subject: default packages In-Reply-To: <40E2C2F5.6050401@lqt.ca> References: <40E26011.2060406@aduva.com> <40E2C2F5.6050401@lqt.ca> Message-ID: <40E2ED91.4090903@aduva.com> Paul Pianta wrote: > Kfir Lavi wrote: > >> Hi, >> I would like to have kickstart file for the default (ie: next, >> next...), and for the Base category. >> How do i know in advance what is the default packages or packages >> groups of distribution? >> >> Thanks, >> Kfir > > > You could always go through a manual installation yourself - choosing > the install options that you wish to test (eg. default install, minimal > install, etc.) and then check the %packages section in the > /root/anaconda-ks.cfg which will be on your newly installed system. > > This file is a kickstart summary of the install that you just completed. > > pantz > Thanks, This helps alot, but i need a tool that will let me know in advance what will be the default categories in minimal, and server etc... From jacksoto at ameritech.net Wed Jun 30 21:24:00 2004 From: jacksoto at ameritech.net (T. Jackson) Date: Wed, 30 Jun 2004 14:24:00 -0700 (PDT) Subject: default packages In-Reply-To: <40E2ED91.4090903@aduva.com> Message-ID: <20040630212400.64306.qmail@web81305.mail.yahoo.com> you can always look in the comps.xml file. Here is a link to get you started http://rhlinux.redhat.com/anaconda/comps.html --- Kfir Lavi wrote: > Paul Pianta wrote: > > Kfir Lavi wrote: > > > >> Hi, > >> I would like to have kickstart file for the > default (ie: next, > >> next...), and for the Base category. > >> How do i know in advance what is the default > packages or packages > >> groups of distribution? > >> > >> Thanks, > >> Kfir > > > > > > You could always go through a manual installation > yourself - choosing > > the install options that you wish to test (eg. > default install, minimal > > install, etc.) and then check the %packages > section in the > > /root/anaconda-ks.cfg which will be on your newly > installed system. > > > > This file is a kickstart summary of the install > that you just com pleted. > > > > pantz > > > Thanks, > This helps alot, but i need a tool that will let me > know in advance what > will be the default categories in minimal, and > server etc... > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > ===== --------------------------------------------------------------------------------------- What a world this would be if people learn the concept of Responsibility