From don.carlton at citadel.edu Mon Jan 9 16:04:04 2012 From: don.carlton at citadel.edu (Don Carlton) Date: Mon, 9 Jan 2012 11:04:04 -0500 Subject: listing packages under group Message-ID: Is there a way to list what packages are contained within a group? For example what packages are installed when you chose the "Core" group? -------------- next part -------------- An HTML attachment was scrubbed... URL: From skvidal at fedoraproject.org Mon Jan 9 16:08:30 2012 From: skvidal at fedoraproject.org (seth vidal) Date: Mon, 9 Jan 2012 11:08:30 -0500 Subject: listing packages under group In-Reply-To: References: Message-ID: <20120109110830.1efcaa39@opus> On Mon, 9 Jan 2012 11:04:04 -0500 "Don Carlton" wrote: > Is there a way to list what packages are contained within a group? For > example what packages are installed when you chose the "Core" group? > repoquery -g -l core -sv From don.carlton at citadel.edu Mon Jan 9 18:06:55 2012 From: don.carlton at citadel.edu (Don Carlton) Date: Mon, 9 Jan 2012 13:06:55 -0500 Subject: listing packages under group In-Reply-To: <20120109110830.1efcaa39@opus> References: <20120109110830.1efcaa39@opus> Message-ID: This doesn't list the packages in the kickstart group? -----Original Message----- From: seth vidal [mailto:skvidal at fedoraproject.org] Sent: Monday, January 09, 2012 11:08 AM To: Discussion list about Kickstart Cc: Don Carlton Subject: Re: listing packages under group On Mon, 9 Jan 2012 11:04:04 -0500 "Don Carlton" wrote: > Is there a way to list what packages are contained within a group? For > example what packages are installed when you chose the "Core" group? > repoquery -g -l core -sv From skvidal at fedoraproject.org Mon Jan 9 18:23:10 2012 From: skvidal at fedoraproject.org (seth vidal) Date: Mon, 9 Jan 2012 13:23:10 -0500 Subject: listing packages under group In-Reply-To: References: <20120109110830.1efcaa39@opus> Message-ID: <20120109132310.38b14b91@opus> On Mon, 9 Jan 2012 13:06:55 -0500 "Don Carlton" wrote: > This doesn't list the packages in the kickstart group? > > - the kickstart groups come from comps file - the groups/groups_gz metadata types in the repodata. that's what repoquery -g -l looks at. -sv From stan.hearn at nscorp.com Mon Jan 9 18:43:00 2012 From: stan.hearn at nscorp.com (Hearn, Stan J.) Date: Mon, 9 Jan 2012 13:43:00 -0500 Subject: listing packages under group In-Reply-To: <20120109132310.38b14b91@opus> References: <20120109110830.1efcaa39@opus> <20120109132310.38b14b91@opus> Message-ID: >> This doesn't list the packages in the kickstart group? >> >> - > the kickstart groups come from comps file - the groups/groups_gz > metadata types in the repodata. > > that's what repoquery -g -l looks at. With RHEL 5 I get an error using this command. # lsb_release -a LSB Version: :core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 5.6 (Tikanga) Release: 5.6 Codename: Tikanga # rhn-channel --list rhel-i386-server-5-u6-2011_04_03 rhel-i386-server-5-u6-2011_04_03-rhn_tools rhel-i386-server-5-u6-2011_04_03-supplementary # repoquery -g -l core Traceback (most recent call last): File "/usr/bin/repoquery", line 850, in ? main(sys.argv) File "/usr/bin/repoquery", line 841, in main repoq.doGroupSetup() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 590, in doGroupSetup return self._getGroups() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 652, in _getGroups raise Errors.GroupsError, _('No Groups Available in any repository') yum.Errors.GroupsError: No Groups Available in any repository Thanks, Stan From skvidal at fedoraproject.org Mon Jan 9 21:40:23 2012 From: skvidal at fedoraproject.org (seth vidal) Date: Mon, 9 Jan 2012 16:40:23 -0500 Subject: listing packages under group In-Reply-To: References: <20120109110830.1efcaa39@opus> <20120109132310.38b14b91@opus> Message-ID: <20120109164023.28f0ac23@opus> On Mon, 9 Jan 2012 13:43:00 -0500 "Hearn, Stan J." wrote: > >> This doesn't list the packages in the kickstart group? > >> > >> - > > > the kickstart groups come from comps file - the groups/groups_gz > > metadata types in the repodata. > > > > that's what repoquery -g -l looks at. > > > With RHEL 5 I get an error using this command. > > # lsb_release -a > LSB > Version: :core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch > Distributor ID: RedHatEnterpriseServer Description: Red Hat > Enterprise Linux Server release 5.6 (Tikanga) Release: 5.6 > Codename: Tikanga > # rhn-channel --list > rhel-i386-server-5-u6-2011_04_03 > rhel-i386-server-5-u6-2011_04_03-rhn_tools > rhel-i386-server-5-u6-2011_04_03-supplementary > # repoquery -g -l core > Traceback (most recent call last): > File "/usr/bin/repoquery", line 850, in ? > main(sys.argv) > File "/usr/bin/repoquery", line 841, in main > repoq.doGroupSetup() > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 590, > in doGroupSetup return self._getGroups() > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 652, > in _getGroups raise Errors.GroupsError, _('No Groups Available in any > repository') yum.Errors.GroupsError: No Groups Available in any > repository > then none of the repositories you have access to from rhn appear to be offering groups. -sv From inode0 at gmail.com Mon Jan 9 22:01:17 2012 From: inode0 at gmail.com (inode0) Date: Mon, 9 Jan 2012 16:01:17 -0600 Subject: listing packages under group In-Reply-To: <20120109164023.28f0ac23@opus> References: <20120109110830.1efcaa39@opus> <20120109132310.38b14b91@opus> <20120109164023.28f0ac23@opus> Message-ID: On Mon, Jan 9, 2012 at 3:40 PM, seth vidal wrote: > On Mon, 9 Jan 2012 13:43:00 -0500 > "Hearn, Stan J." wrote: > >> >> This doesn't list the packages in the kickstart group? >> >> >> >> - >> >> > the kickstart groups come from comps file - the groups/groups_gz >> > metadata types in the repodata. >> > >> > that's what repoquery -g -l looks at. >> >> >> With RHEL 5 I get an error using this command. >> >> # lsb_release -a >> LSB >> Version: ? ?:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch >> Distributor ID: RedHatEnterpriseServer Description: ? ?Red Hat >> Enterprise Linux Server release 5.6 (Tikanga) Release: ? ? ? ?5.6 >> Codename: ? ? ? Tikanga >> # rhn-channel --list >> rhel-i386-server-5-u6-2011_04_03 >> rhel-i386-server-5-u6-2011_04_03-rhn_tools >> rhel-i386-server-5-u6-2011_04_03-supplementary >> # repoquery -g -l core >> Traceback (most recent call last): >> ? File "/usr/bin/repoquery", line 850, in ? >> ? ? main(sys.argv) >> ? File "/usr/bin/repoquery", line 841, in main >> ? ? repoq.doGroupSetup() >> ? File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 590, >> in doGroupSetup return self._getGroups() >> ? File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 652, >> in _getGroups raise Errors.GroupsError, _('No Groups Available in any >> repository') yum.Errors.GroupsError: No Groups Available in any >> repository >> > > then none of the repositories you have access to from rhn appear to be > offering groups. You might need to add --plugins to repoquery on RHEL5 iirc. John From skvidal at fedoraproject.org Mon Jan 9 22:02:25 2012 From: skvidal at fedoraproject.org (seth vidal) Date: Mon, 9 Jan 2012 17:02:25 -0500 Subject: listing packages under group In-Reply-To: References: <20120109110830.1efcaa39@opus> <20120109132310.38b14b91@opus> <20120109164023.28f0ac23@opus> Message-ID: <20120109170225.785b91dc@opus> On Mon, 9 Jan 2012 16:01:17 -0600 inode0 wrote: > On Mon, Jan 9, 2012 at 3:40 PM, seth vidal > wrote: > > On Mon, 9 Jan 2012 13:43:00 -0500 > > "Hearn, Stan J." wrote: > > > >> >> This doesn't list the packages in the kickstart group? > >> >> > >> >> - > >> > >> > the kickstart groups come from comps file - the groups/groups_gz > >> > metadata types in the repodata. > >> > > >> > that's what repoquery -g -l looks at. > >> > >> > >> With RHEL 5 I get an error using this command. > >> > >> # lsb_release -a > >> LSB > >> Version: > >> ?:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch > >> Distributor ID: RedHatEnterpriseServer Description: ? ?Red Hat > >> Enterprise Linux Server release 5.6 (Tikanga) Release: ? ? ? ?5.6 > >> Codename: ? ? ? Tikanga # rhn-channel --list > >> rhel-i386-server-5-u6-2011_04_03 > >> rhel-i386-server-5-u6-2011_04_03-rhn_tools > >> rhel-i386-server-5-u6-2011_04_03-supplementary > >> # repoquery -g -l core > >> Traceback (most recent call last): > >> ? File "/usr/bin/repoquery", line 850, in ? > >> ? ? main(sys.argv) > >> ? File "/usr/bin/repoquery", line 841, in main > >> ? ? repoq.doGroupSetup() > >> ? File "/usr/lib/python2.4/site-packages/yum/__init__.py", line > >> 590, in doGroupSetup return self._getGroups() > >> ? File "/usr/lib/python2.4/site-packages/yum/__init__.py", line > >> 652, in _getGroups raise Errors.GroupsError, _('No Groups > >> Available in any repository') yum.Errors.GroupsError: No Groups > >> Available in any repository > >> > > > > then none of the repositories you have access to from rhn appear to > > be offering groups. > > You might need to add --plugins to repoquery on RHEL5 iirc. > That's a good point. Depending on the version of rhel5 that will matter. -sv From Moray.Henderson at ict-software.org Thu Jan 12 11:28:51 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 12 Jan 2012 11:28:51 +0000 Subject: Adding drivers In-Reply-To: <1324389259.5505.112.camel@vpodzime.brq.redhat.com> References: <000001ccbf15$ec771f70$c5655e50$@Henderson@ict-software.org> <1324389259.5505.112.camel@vpodzime.brq.redhat.com> Message-ID: <000001ccd11d$5d548a20$17fd9e60$@Henderson@ict-software.org> > From: Vratislav Podzimek [mailto:vpodzime at redhat.com] > Sent: 20 December 2011 13:54 > On Tue, 2011-12-20 at 12:50 +0000, Moray Henderson wrote: > > On the point of releasing the CentOS 5-based system I've spent the > last 8 > > months developing, I find the manufacturers of the hardware it was > designed > > for have changed their specs and it won't install any more. Grrr. > > > > I now have kernel modules for the relevant hardware - does anyone > know how > > to build a driverdisk? So far everything I've tried results in > Anaconda > > complaining "can't find either driver disk identifier, bad driver > disk". > For RHEL5, there is the ddiskit tool which could help you. See > http://dup.et.redhat.com/ddiskit/ for more details. Thanks for that pointer - exactly what I need. I did notice a few things, though: The "latest version", ddiskit-0.9.9, provides "kernel-modules = ${verrel}${variant}" in the rpms it builds. The el5 driver builds from elrepo.org seem to be built from a different ddiskit which provides "kabi-modules" instead. Is there documentation to say which is correct for which distro release? ddiskit-0.9.9 supports the new rpm form of driver disk, and the release notes for RHEL 5.1 say Anaconda supports it - but looking at the source for anaconda-11.1.2.224 (CentOS 5.6) and anaconda-11.1.2.242 (CentOS 5.7) I don't see any of the code for it. Is that an RHEL-only feature? The docs/anaconda-release-notes.txt file for both releases states you can use a supplemental driver disk image called drvnet.img to supply extra network device drivers. Again, the only occurrences of "drvnet" anywhere in the source are anaconda-release-notes.txt and ChangeLog. Are you still supposed to be able to include supplemental drivers with your install media? Moray. ?To err is human; to purr, feline.? From Moray.Henderson at ict-software.org Thu Jan 12 15:29:36 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 12 Jan 2012 15:29:36 +0000 Subject: Adding drivers In-Reply-To: <4F0EC77C.8020007@avaya.com> References: <000001ccbf15$ec771f70$c5655e50$@Henderson@ict-software.org> <1324389259.5505.112.camel@vpodzime.brq.redhat.com> <000001ccd11d$5d548a20$17fd9e60$@Henderson@ict-software.org> <4F0EC77C.8020007@avaya.com> Message-ID: <000101ccd13e$fef3cd70$fcdb6850$@Henderson@ict-software.org> > From: Adrian Cruceru [mailto:crucerua at avaya.com] > Sent: 12 January 2012 11:44 > Why not put them directly in your initrd/stage2 images? Initrd gets rebuilt when I run Anaconda's buildinstall; I was hoping for a solution that I wouldn't have to repeat (and remember I had to repeat) each time I rebuild the installer. fine mess of postings! That's another Moray. ?To err is human; to purr, feline.? > On 01/12/2012 01:28 PM, Moray Henderson wrote: > >> From: Vratislav Podzimek [mailto:vpodzime at redhat.com] > >> Sent: 20 December 2011 13:54 > >> On Tue, 2011-12-20 at 12:50 +0000, Moray Henderson wrote: > >>> On the point of releasing the CentOS 5-based system I've spent the > >> last 8 > >>> months developing, I find the manufacturers of the hardware it was > >> designed > >>> for have changed their specs and it won't install any more. Grrr. > >>> > >>> I now have kernel modules for the relevant hardware - does anyone > >> know how > >>> to build a driverdisk? So far everything I've tried results in > >> Anaconda > >>> complaining "can't find either driver disk identifier, bad driver > >> disk". > >> For RHEL5, there is the ddiskit tool which could help you. See > >> http://dup.et.redhat.com/ddiskit/ for more details. > > Thanks for that pointer - exactly what I need. I did notice a few > things, though: > > > > The "latest version", ddiskit-0.9.9, provides "kernel-modules = > ${verrel}${variant}" in the rpms it builds. The el5 driver builds from > elrepo.org seem to be built from a different ddiskit which provides > "kabi-modules" instead. Is there documentation to say which is correct > for which distro release? > > > > ddiskit-0.9.9 supports the new rpm form of driver disk, and the > release notes for RHEL 5.1 say Anaconda supports it - but looking at > the source for anaconda-11.1.2.224 (CentOS 5.6) and anaconda-11.1.2.242 > (CentOS 5.7) I don't see any of the code for it. Is that an RHEL-only > feature? > > > > The docs/anaconda-release-notes.txt file for both releases states you > can use a supplemental driver disk image called drvnet.img to supply > extra network device drivers. Again, the only occurrences of "drvnet" > anywhere in the source are anaconda-release-notes.txt and ChangeLog. > Are you still supposed to be able to include supplemental drivers with > your install media? > > > > > > Moray. > > ?To err is human; to purr, feline.? > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list From Jim.Cole at mckesson.com Wed Jan 18 20:11:42 2012 From: Jim.Cole at mckesson.com (Cole, Jim) Date: Wed, 18 Jan 2012 15:11:42 -0500 Subject: Kickstarting RHEL 6.2 issues Message-ID: <815F317B2BC9C84C920132D40978647E16EEEBEE@NDHV3000.na.corp.mckesson.com> I'm having issues creating a kickstart for RHEL 6.2 so I just walked through the installer, used the kickstart file generated into /root and tried to incorporate that into the isolinux.cfg file. The error I'm getting is "unable to read package metadata. This may be due to a missing repodata directory" Can not retrieve repository meadata (repomd.xml) for repository: Red Hat Enterprise Linux. Please verify its path and try again. Can someone please help? Thanks! -Jim The anaconda-ks.cfg was renamed to jim.ks and placed into the isolinux dir on a 6.2 DVD. Here is my isolinux.cfg: menu color title 0 #ffffffff #00000000 menu color tabmsg 0 #ffffffff #00000000 menu color unsel 0 #ffffffff #00000000 menu color hotsel 0 #ff000000 #ffffffff menu color hotkey 7 #ffffffff #ff000000 menu color scrollbar 0 #ffffffff #00000000 label linux menu label ^Install or upgrade an existing system menu default kernel vmlinuz append initrd=initrd.img label vesa menu label Install system with ^basic video driver kernel vmlinuz append initrd=initrd.img xdriver=vesa nomodeset label rescue menu label ^Rescue installed system kernel vmlinuz append initrd=initrd.img rescue label local menu label Boot from ^local drive localboot 0xffff label memtest86 menu label ^Memory test kernel memtest append - label jim menu label jim kernel vmlinuz append append ks=cdrom://isolinux/jim.ks initrd=initrd.img ramdisk_size=8192 Here is the jim.ks: # Kickstart file automatically generated by anaconda. #version=DEVEL install cdrom lang en_US.UTF-8 keyboard us network --onboot no --device eth0 --noipv4 --noipv6 rootpw --iscrypted $6$g9mqaBzA12oOR8LU$28Dj4b08Mv4VL5ToT0VVf7cIoTwwDywgsOieFyO1R9JdXkWoqYumMgHSRo4Q7ZZgtJc0JkrXmZmqzD4pDwRAC1 firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --enforcing timezone --utc America/Chicago bootloader --location=mbr --driveorder=sda --append=" rhgb crashkernel=auto quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #clearpart --all --drives=sda #part /boot --fstype=ext4 --size=500 #part pv.008002 --grow --size=1 #volgroup vg_hpm --pesize=4096 pv.008002 #logvol /home --fstype=ext4 --name=lv_home --vgname=vg_hpm --grow --size=100 #logvol / --fstype=ext4 --name=lv_root --vgname=vg_hpm --grow --size=1024 --maxsize=51200 #logvol swap --name=lv_swap --vgname=vg_hpm --grow --size=2016 --maxsize=4032 repo --name="Red Hat Enterprise Linux" --baseurl=cdrom:sr0 --cost=100 %packages @additional-devel @base @client-mgmt-tools @core @debugging @basic-desktop @desktop-debugging @desktop-platform @desktop-platform-devel @development @directory-client @eclipse @emacs @fonts @general-desktop @graphical-admin-tools @graphics @input-methods @internet-browser @java-platform @legacy-x @network-file-system-client @performance @perl-runtime @print-client @remote-desktop-clients @server-platform @server-platform-devel @server-policy @tex @technical-writing @virtualization @virtualization-client @virtualization-platform @x11 libXinerama-devel openmotif-devel libXmu-devel xorg-x11-proto-devel startup-notification-devel libgnomeui-devel libbonobo-devel junit libXau-devel libgcrypt-devel popt-devel libdrm-devel libXrandr-devel libxslt-devel libglade2-devel gnutls-devel mtools pax python-dmidecode oddjob sgpio genisoimage wodim abrt-gui desktop-file-utils ant rpmdevtools jpackage-utils rpmlint certmonger pam_krb5 krb5-workstation netpbm-progs openmotif libXmu libXp perl-DBD-SQLite libvirt-java %end From Jim.Cole at mckesson.com Wed Jan 18 21:35:42 2012 From: Jim.Cole at mckesson.com (Cole, Jim) Date: Wed, 18 Jan 2012 16:35:42 -0500 Subject: Kickstarting RHEL 6.2 issues Message-ID: <815F317B2BC9C84C920132D40978647E16EEEED3@NDHV3000.na.corp.mckesson.com> I resolved my issue..it was a bad ISO :) Thanks! -Jim -----Original Message----- From: Cole, Jim Sent: Wednesday, January 18, 2012 2:12 PM To: Discussion list about Kickstart Subject: Kickstarting RHEL 6.2 issues I'm having issues creating a kickstart for RHEL 6.2 so I just walked through the installer, used the kickstart file generated into /root and tried to incorporate that into the isolinux.cfg file. The error I'm getting is "unable to read package metadata. This may be due to a missing repodata directory" Can not retrieve repository meadata (repomd.xml) for repository: Red Hat Enterprise Linux. Please verify its path and try again. Can someone please help? Thanks! -Jim The anaconda-ks.cfg was renamed to jim.ks and placed into the isolinux dir on a 6.2 DVD. Here is my isolinux.cfg: menu color title 0 #ffffffff #00000000 menu color tabmsg 0 #ffffffff #00000000 menu color unsel 0 #ffffffff #00000000 menu color hotsel 0 #ff000000 #ffffffff menu color hotkey 7 #ffffffff #ff000000 menu color scrollbar 0 #ffffffff #00000000 label linux menu label ^Install or upgrade an existing system menu default kernel vmlinuz append initrd=initrd.img label vesa menu label Install system with ^basic video driver kernel vmlinuz append initrd=initrd.img xdriver=vesa nomodeset label rescue menu label ^Rescue installed system kernel vmlinuz append initrd=initrd.img rescue label local menu label Boot from ^local drive localboot 0xffff label memtest86 menu label ^Memory test kernel memtest append - label jim menu label jim kernel vmlinuz append append ks=cdrom://isolinux/jim.ks initrd=initrd.img ramdisk_size=8192 Here is the jim.ks: # Kickstart file automatically generated by anaconda. #version=DEVEL install cdrom lang en_US.UTF-8 keyboard us network --onboot no --device eth0 --noipv4 --noipv6 rootpw --iscrypted $6$g9mqaBzA12oOR8LU$28Dj4b08Mv4VL5ToT0VVf7cIoTwwDywgsOieFyO1R9JdXkWoqYumMgHSRo4Q7ZZgtJc0JkrXmZmqzD4pDwRAC1 firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --enforcing timezone --utc America/Chicago bootloader --location=mbr --driveorder=sda --append=" rhgb crashkernel=auto quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #clearpart --all --drives=sda #part /boot --fstype=ext4 --size=500 #part pv.008002 --grow --size=1 #volgroup vg_hpm --pesize=4096 pv.008002 #logvol /home --fstype=ext4 --name=lv_home --vgname=vg_hpm --grow --size=100 #logvol / --fstype=ext4 --name=lv_root --vgname=vg_hpm --grow --size=1024 --maxsize=51200 #logvol swap --name=lv_swap --vgname=vg_hpm --grow --size=2016 --maxsize=4032 repo --name="Red Hat Enterprise Linux" --baseurl=cdrom:sr0 --cost=100 %packages @additional-devel @base @client-mgmt-tools @core @debugging @basic-desktop @desktop-debugging @desktop-platform @desktop-platform-devel @development @directory-client @eclipse @emacs @fonts @general-desktop @graphical-admin-tools @graphics @input-methods @internet-browser @java-platform @legacy-x @network-file-system-client @performance @perl-runtime @print-client @remote-desktop-clients @server-platform @server-platform-devel @server-policy @tex @technical-writing @virtualization @virtualization-client @virtualization-platform @x11 libXinerama-devel openmotif-devel libXmu-devel xorg-x11-proto-devel startup-notification-devel libgnomeui-devel libbonobo-devel junit libXau-devel libgcrypt-devel popt-devel libdrm-devel libXrandr-devel libxslt-devel libglade2-devel gnutls-devel mtools pax python-dmidecode oddjob sgpio genisoimage wodim abrt-gui desktop-file-utils ant rpmdevtools jpackage-utils rpmlint certmonger pam_krb5 krb5-workstation netpbm-progs openmotif libXmu libXp perl-DBD-SQLite libvirt-java %end From hennebry at web.cs.ndsu.nodak.edu Wed Jan 25 04:19:55 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Tue, 24 Jan 2012 22:19:55 -0600 (CST) Subject: kickstart vs. /etc/login.defs Message-ID: I've encountered two problems: How to specify the kickstart file. How, in the kickstart file does one affect /etc/login.defs . According to fedora, a kickstart file is the right way to do what I want. There is no specific command to affect /etc/login.defs . >From what I have read, %post runs too late: Fake users have already been assigned in the range 500..999 . It seems to me that %pre runs too soon, before partitions are even assigned. The %pre example has me really confused. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-kic kstart2-preinstallconfig.html The example writes out a partioning scheme, but to work / , /bin and /tmp must already exist. What is going on? How do I specify the kickstart file? I plan to use a minimal bootable CD and a DVD image on a hard drive. One technique mentioned was to put ks.cfg in a correct directory and let anaconda find it. That technique would seem to require inserting it into an iso file. I must be missing something. The other technique involves editing a boot command. I've seen two syntaxes: linux ks=hd:/device/dir/ks.cfg linux ks=hd:partition/path/ks.cfg If I do it that way, which boot sequence do I interrupt? As I understand it, two boot sequences, one to the CD and the other to the DVD iso file. Is that correct? -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From root at nachtmaus.us Wed Jan 25 04:32:33 2012 From: root at nachtmaus.us (root at nachtmaus.us) Date: Wed, 25 Jan 2012 04:32:33 +0000 Subject: kickstart vs. /etc/login.defs In-Reply-To: References: Message-ID: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Firstly, for where to put the ks file, it would be easiest for you to remaster the boot CD, and put the ks file into the root directory of the CD, update the configuration for the CD's boot-loader to add something like "ks=cdrom:/fc14.ks", and then burn the resulting (modified) file-tree to a new CD disk To get around the too early/to late of %pre and %post, you may want to add a custom RPM archive file to the CD, have it dump the files into the being-created system, and run a command as part of its installation procedure that causes the newly added files to be read. Then reference the new RPM archive in the packages section of your ks file. HTH -DTK Sent via BlackBerry from T-Mobile -----Original Message----- From: Michael Hennebry Sender: kickstart-list-bounces at redhat.com Date: Tue, 24 Jan 2012 22:19:55 To: Reply-To: Discussion list about Kickstart Subject: kickstart vs. /etc/login.defs I've encountered two problems: How to specify the kickstart file. How, in the kickstart file does one affect /etc/login.defs . According to fedora, a kickstart file is the right way to do what I want. There is no specific command to affect /etc/login.defs . >From what I have read, %post runs too late: Fake users have already been assigned in the range 500..999 . It seems to me that %pre runs too soon, before partitions are even assigned. The %pre example has me really confused. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-kic kstart2-preinstallconfig.html The example writes out a partioning scheme, but to work / , /bin and /tmp must already exist. What is going on? How do I specify the kickstart file? I plan to use a minimal bootable CD and a DVD image on a hard drive. One technique mentioned was to put ks.cfg in a correct directory and let anaconda find it. That technique would seem to require inserting it into an iso file. I must be missing something. The other technique involves editing a boot command. I've seen two syntaxes: linux ks=hd:/device/dir/ks.cfg linux ks=hd:partition/path/ks.cfg If I do it that way, which boot sequence do I interrupt? As I understand it, two boot sequences, one to the CD and the other to the DVD iso file. Is that correct? -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From hennebry at web.cs.ndsu.nodak.edu Wed Jan 25 16:35:33 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Wed, 25 Jan 2012 10:35:33 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: On Wed, 25 Jan 2012, root at nachtmaus.us wrote: > Firstly, for where to put the ks file, it would be easiest for you to remaster the boot CD, and put the ks file into the root directory of the CD, update the configuration for the CD's boot-loader to add something like "ks=cdrom:/fc14.ks", and then burn the resulting (modified) file-tree to a new CD disk Wow. The possibility that I might have to edit the CD had occurred to me, but I had assumed my reasoning was wrong. >From here: http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-kickstart2-startinginstall.html it seems like I could use a kickstart file in lots of places if I knew the magic formula. Also if the instructions there apply when one is using a minimal CD and a DVD image. Also, I would need to know how to refer to a partition or a device. It's my understanding that beginning with F15 or F16, names like sdb2 are not reliable anymore. > To get around the too early/to late of %pre and %post, you may want to add a custom RPM archive file to the CD, have it dump the files into the being-created system, and run a command as part of its installation procedure that causes the newly added files to be read. Then reference the new RPM archive in the packages section of your ks file. If that is really necessary, I might have to give up. It might be easy if one knows how, but I don't. I've never made an RPM before. I've never used kickstart before. For me, installing is something I've always approached with fear and trepidation. Something always goes wrong. Also, that prescription seems rather a lot to be inferred from just "use a kickstart file". Assuming that I edit my CD image, is making it bootable just a matter of ticking the right flag on the burner program? I'd always sort of expected that installer CDs were special. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From amm at lanl.gov Wed Jan 25 16:57:04 2012 From: amm at lanl.gov (Aaron Morrison) Date: Wed, 25 Jan 2012 09:57:04 -0700 Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: <4F203460.2020209@lanl.gov> Are you limited to using CD/DVDs? You can put a custom ks file on other media types or make it available via the network(via ftp, nfs, http, etc) amm On 01/25/2012 09:35 AM, Michael Hennebry wrote: > On Wed, 25 Jan 2012, root at nachtmaus.us wrote: > >> Firstly, for where to put the ks file, it would be easiest for you to >> remaster the boot CD, and put the ks file into the root directory of >> the CD, update the configuration for the CD's boot-loader to add >> something like "ks=cdrom:/fc14.ks", and then burn the resulting >> (modified) file-tree to a new CD disk > > Wow. > The possibility that I might have to edit the CD had occurred to me, > but I had assumed my reasoning was wrong. >> From here: > http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-kickstart2-startinginstall.html > > it seems like I could use a kickstart file in > lots of places if I knew the magic formula. > Also if the instructions there apply when > one is using a minimal CD and a DVD image. > Also, I would need to know how to refer to a partition or a device. > It's my understanding that beginning with F15 or F16, > names like sdb2 are not reliable anymore. > >> To get around the too early/to late of %pre and %post, you may want >> to add a custom RPM archive file to the CD, have it dump the files >> into the being-created system, and run a command as part of its >> installation procedure that causes the newly added files to be read. >> Then reference the new RPM archive in the packages section of your ks >> file. > > If that is really necessary, I might have to give up. > It might be easy if one knows how, but I don't. > I've never made an RPM before. > I've never used kickstart before. > For me, installing is something I've always > approached with fear and trepidation. > Something always goes wrong. > Also, that prescription seems rather a lot to > be inferred from just "use a kickstart file". > > Assuming that I edit my CD image, > is making it bootable just a matter of ticking > the right flag on the burner program? > I'd always sort of expected that installer CDs were special. > From Moray.Henderson at ict-software.org Wed Jan 25 17:43:43 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Wed, 25 Jan 2012 17:43:43 +0000 Subject: kickstart vs. /etc/login.defs In-Reply-To: References: Message-ID: <000001ccdb88$e3335890$a99a09b0$@Henderson@ict-software.org> > From: Michael Hennebry [mailto:hennebry at web.cs.ndsu.nodak.edu] > Sent: 25 January 2012 04:20 > > I've encountered two problems: > How to specify the kickstart file. > How, in the kickstart file does one affect /etc/login.defs . > According to fedora, a kickstart file is the right way to do what I > want. > There is no specific command to affect /etc/login.defs . > >From what I have read, %post runs too late: > Fake users have already been assigned in the range 500..999 . > It seems to me that %pre runs too soon, before partitions are even > assigned. > The %pre example has me really confused. > http://docs.fedoraproject.org/en- > US/Fedora/16/html/Installation_Guide/s1-kic > kstart2-preinstallconfig.html > The example writes out a partioning scheme, > but to work / , /bin and /tmp must already exist. > What is going on? > > How do I specify the kickstart file? > I plan to use a minimal bootable CD and a DVD image on a hard drive. > One technique mentioned was to put ks.cfg in a > correct directory and let anaconda find it. > That technique would seem to require inserting it into an iso file. > I must be missing something. > The other technique involves editing a boot command. > I've seen two syntaxes: > linux ks=hd:/device/dir/ks.cfg > linux ks=hd:partition/path/ks.cfg > If I do it that way, which boot sequence do I interrupt? > As I understand it, two boot sequences, > one to the CD and the other to the DVD iso file. > Is that correct? When you boot the installer, it creates a running system with / and /tmp directories in a RAM-disk. That's a part of memory that has been configured to look like a disk with filesystems. That is what the %pre example you quoted is using. Your real disk partitions have not been created yet. The usual use of %pre is to work out how the real disk should be partitioned. After the installer creates the real partitions, it mounts them under /mnt/sysimage from its RAM-disk, in order to write files to them. When the system boots the new operating system, the real disk partitions get mounted in their proper places and the RAM-disk contents are lost. "Two boot sequences" doesn't look right - although I've never tried what you're describing. I would imagine that it _boots_ from the minimal bootable CD and then loads stuff from the DVD image. In that case, where you would just press or type linux text to start the installer, you would type linux ks= with whatever the path to your kickstart file is. If you have a floppy disk, that's still the easiest way to specify a kickstart file; a USB floppy is the next easiest. I'm sure there has been advice on working out the correct device path for USB kickstart on on this list before - have a look through the archives. An ordinary USB stick is possible, but you do need to be careful that it doesn't get incorporated into the filesystems for the installed system and reformatted. Let's step back a bit, though. What do you need to change in login.defs, and what "fake users" are being assigned? There may be a better way to fix this. Moray. "To err is human; to purr, feline." From hennebry at web.cs.ndsu.nodak.edu Wed Jan 25 17:44:38 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Wed, 25 Jan 2012 11:44:38 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: <4F203460.2020209@lanl.gov> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <4F203460.2020209@lanl.gov> Message-ID: On Wed, 25 Jan 2012, Aaron Morrison wrote: > Are you limited to using CD/DVDs? > You can put a custom ks file on other media types or make it available > via the network(via ftp, nfs, http, etc) The plan is to use a minimal CD boot disk and a DVD image on hard disk. I've tried to use just a DVD image, but could never get it to work. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-kickstart2-startinginstall.html seems to suggest that I don't need to edit the boot disk to use a kickstart file on hard disk, but I would need to know how to refer to a partition. It's my understanding that since F15 or F16, names like sdb2 are no longer reliable. Also, changing /etc/login.defs would seem to be a lot harder than just figuring out where to put the kickstart file. > On 01/25/2012 09:35 AM, Michael Hennebry wrote: >> On Wed, 25 Jan 2012, root at nachtmaus.us wrote: >>> To get around the too early/to late of %pre and %post, you may want >>> to add a custom RPM archive file to the CD, have it dump the files >>> into the being-created system, and run a command as part of its >>> installation procedure that causes the newly added files to be read. >>> Then reference the new RPM archive in the packages section of your ks >>> file. >> >> If that is really necessary, I might have to give up. >> It might be easy if one knows how, but I don't. >> I've never made an RPM before. >> I've never used kickstart before. >> For me, installing is something I've always >> approached with fear and trepidation. >> Something always goes wrong. >> Also, that prescription seems rather a lot to >> be inferred from just "use a kickstart file". -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From tytus64 at gmail.com Wed Jan 25 19:09:06 2012 From: tytus64 at gmail.com (Piotr R) Date: Wed, 25 Jan 2012 14:09:06 -0500 Subject: installing onto a loopback device Message-ID: I am trying to create a disk image with a customized version of Cento6 installation on my Centos6 machine. I am planning to dump this image to a disk of an embedded device. I thought I could use a loopback device as the installation destination instead of a real disk but when I put "loop0" in kickstart file I am getting the following error: The following error was found while parsing the kickstart configuration file: The following problem occurred on line 36 of the kickstart file: Specified nonexistent disk loop0 in partition command Here is my kickstart file: #platform=x86, AMD64, or Intel EM64T #version=DEVEL # Firewall configuration firewall --disabled # Install OS instead of upgrade install # Use hard drive installation media repo --name=centos6 --baseurl=file://my/repo/path/centos6_repo/os/x86_64 # Root password rootpw --iscrypted $1$2ThvVzg7$PCHK8TnCECOjzbRV4VPzo1 # Network information #network --onboot yes --device eth1 --bootproto dhcp --noipv6 #network --bootproto=dhcp --device=eth1 --onboot=on # System authorization information auth --useshadow --passalgo=sha512 # Use graphical install #graphical # System keyboard keyboard us # System language lang en_US # SELinux configuration selinux --disabled # Do not configure the X Window System skipx # Installation logging level logging --level=debug # System timezone timezone America/New_York # System bootloader configuration bootloader --location=mbr --driveorder=loop0 # Partition clearing information #clearpart --all --drives=loop0 --initlabel # Disk partitioning information part / --fstype="ext4" --grow --ondisk=loop0 --size=1 %packages --excludedocs --nobase @core --nodefaults #anaconda -ipw2100-firmware -ipw2200-firmware -ivtv-firmware -iwl100-firmware -iwl1000-firmware -iwl3945-firmware -iwl4965-firmware -iwl5000-firmware -iwl5150-firmware -iwl6000-firmware -iwl6000g2a-firmware -iwl6000g2b-firmware -iwl6050-firmware #-kernel-firmware -libertas-usb8388-firmware -ql2100-firmware -ql2200-firmware -ql23xx-firmware -ql2400-firmware -ql2500-firmware -rt61pci-firmware -rt73usb-firmware -xorg-x11-drv-ati-firmware -zd1211-firmware %end %post --erroronfail #!/bin/bash umount /proc/bus/usb umount /proc umount /sys umount /selinux umount /dev/pts umount /dev/shm umount /dev %end reboot The empty image fle was created in the following way: # qemu-img create -f raw /my/path/cie.img 1G and then attached to /dev/loop0 (before running anaconda): # losetup -v -f /my/path/cie.img Loop device is /dev/loop0 Any help greatly appreciated, Piotr -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Mooney at ndsu.edu Thu Jan 26 00:32:10 2012 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Wed, 25 Jan 2012 18:32:10 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: In regard to: Re: kickstart vs. /etc/login.defs, Michael Hennebry said (at...: > On Wed, 25 Jan 2012, root at nachtmaus.us wrote: > >> Firstly, for where to put the ks file, it would be easiest for you to >> remaster the boot CD, and put the ks file into the root directory of the CD, >> update the configuration for the CD's boot-loader to add something like >> "ks=cdrom:/fc14.ks", and then burn the resulting (modified) file-tree to a >> new CD disk For a one-off install, in the absence of a provisioning environment like cobbler, I personally think it's a lot easier to load the kickstart file over the network. Just do something like - place your ks.cfg in a directory that is accessible via a URL - tell anaconda to load the ks.cfg from the URL ks=http://your.web.host.here/url/path/to/ks.cfg This assumes that the client you're kickstarting can get a DHCP address. If not, assuming you have an IP reserved for it, you can kickstart it so DHCP is not required: ks=http://your.web.host.here/url/path/to/ks.cfg \ ksdevice=eth0 ip= \ netmask= \ gateway= \ dns=dns_server1,dns_server2 Other useful parameters to anaconda include debug text noipv6 syslog= loglevel=debug vnc vncconnect=host:port vncpassword= >> To get around the too early/to late of %pre and %post, you may want to add a >> custom RPM archive file to the CD, have it dump the files into the >> being-created system, and run a command as part of its installation >> procedure that causes the newly added files to be read. Then reference the >> new RPM archive in the packages section of your ks file. I don't understand from the initial post what the actual goal is, so it's hard to know what to suggest here. Unless I missed it, the original issue has something to do with uids in the 101-499 range, but I have no idea what the actual problem is. I will say that you can do a lot in %post using things like "wget" to fetch a remote tarball or zip and then using the contents of that archive to perform further actions. Tim -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242, IACC Building North Dakota State University, Fargo, ND 58105-5164 From hennebry at web.cs.ndsu.nodak.edu Thu Jan 26 00:56:05 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Wed, 25 Jan 2012 18:56:05 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: On Wed, 25 Jan 2012, Tim Mooney wrote: > In regard to: Re: kickstart vs. /etc/login.defs, Michael Hennebry said > (at...: > >> On Wed, 25 Jan 2012, root at nachtmaus.us wrote: >> >>> Firstly, for where to put the ks file, it would be easiest for you to >>> remaster the boot CD, and put the ks file into the root directory of the >>> CD, update the configuration for the CD's boot-loader to add something >>> like "ks=cdrom:/fc14.ks", and then burn the resulting (modified) file-tree >>> to a new CD disk > > For a one-off install, in the absence of a provisioning environment like > cobbler, I personally think it's a lot easier to load the kickstart file > over the network. Just do something like > > - place your ks.cfg in a directory that is accessible via a URL > - tell anaconda to load the ks.cfg from the URL > > ks=http://your.web.host.here/url/path/to/ks.cfg I think I can do that. I'm pretty sure that I can use my web site for it. Right, Tim? >>> To get around the too early/to late of %pre and %post, you may want to add >>> a custom RPM archive file to the CD, have it dump the files into the >>> being-created system, and run a command as part of its installation >>> procedure that causes the newly added files to be read. Then reference the >>> new RPM archive in the packages section of your ks file. > > I don't understand from the initial post what the actual goal is, so it's > hard to know what to suggest here. Unless I missed it, the original issue > has something to do with uids in the 101-499 range, but I have no idea > what the actual problem is. By default, Fedora 16 has UID_MIN=GID_MIN=1000. My Fedora 14 (EOL) has UID_MIN=GID=500. These values are stored in /etc/login.defs . I want to install (not uppgrade) Fedora 16 and retain the 500. I have considered alternatives. During %pre /etc does not yet exist, so %pre is too early. During %post there will already be fake users in the range 500..999, so %post is too late. Fedora claims that a kickstart file is the way to keep the 500. Fedora was stingy with details. > I will say that you can do a lot in %post using things like "wget" to > fetch a remote tarball or zip and then using the contents of that archive > to perform further actions. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From Tim.Mooney at ndsu.edu Thu Jan 26 01:54:50 2012 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Wed, 25 Jan 2012 19:54:50 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: In regard to: Re: kickstart vs. /etc/login.defs, Michael Hennebry said (at...: >> ks=http://your.web.host.here/url/path/to/ks.cfg > > I think I can do that. I'm pretty sure that I can use my web site for it. > Right, Tim? Yes, you should be able to just drop it into your personal web space and have anaconda read it, providing you give it the correct URL to the file. > By default, Fedora 16 has UID_MIN=GID_MIN=1000. > My Fedora 14 (EOL) has UID_MIN=GID=500. > These values are stored in /etc/login.defs . > I want to install (not uppgrade) Fedora 16 and retain the 500. So, in your %post - use whatever tool you want to modify /etc/login.defs, changing the values. - find all the system accounts that have already been created with uids in the 500-999 range, and modify them to be in whatever range you want them to be in. If you use shell for %post, something like for u in `cut -d : -f 3 /etc/passwd` do if test $u -ge 500 && test $u -le 999 ; then user=`grep "^[^:]*:[^:]*:$u:" /etc/passwd | cut -d : -f 1` new_uid=`expr $u + 1000` # remove the echo when you're satisfied the code is correct echo usermod -u $new_uid $user fi done If you know perl or python better, the same can be coded for the post, you just need to tell %post to use a different interpreter. Note: usermod only fixes file ownership of stuff in their home dir, if these system users already own files outside of their home, you'll need to find them and modify them too. - proceed with whatever other post tasks you need You're already talking about installing FC16 in a way that's not recommended, so modifying the accounts is no worse. You should think carefully before you proceed down this path. It may not be worth the effort. > Fedora claims that a kickstart file is the way to keep the 500. I'm not following how using *just* a kickstart file allows you to avoid the issue, but perhaps there's some clever bit I'm not seeing. Making a re-spin of FC16 with your own custom version of the package that owns /etc/login.defs (probably shadow-utils) would. Tim -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From rocha at abracops.info Thu Jan 26 02:34:37 2012 From: rocha at abracops.info (Sebastiao Rocha) Date: Thu, 26 Jan 2012 00:34:37 -0200 Subject: How to start MySql on %post install and insert data In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: Hi guys, i nee ome help. im using kickstart from fedora 7 to fedora 13, now im trying to use it on fedora 16 with no success my trouble is how to start mysqld on post install i have tried this code... systemctl enable mysqld.service systemctl start mysqld.service but it gave me a error message: "Running in chroot, ignoring request" and mysqld does not start to allow data insertion with mysql << anyone know hot to do this on fc15+ with systemd ? thanks... Rocha From hennebry at web.cs.ndsu.nodak.edu Thu Jan 26 03:15:37 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Wed, 25 Jan 2012 21:15:37 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: On Wed, 25 Jan 2012, Tim Mooney wrote: > In regard to: Re: kickstart vs. /etc/login.defs, Michael Hennebry said >> By default, Fedora 16 has UID_MIN=GID_MIN=1000. >> My Fedora 14 (EOL) has UID_MIN=GID=500. >> These values are stored in /etc/login.defs . >> I want to install (not uppgrade) Fedora 16 and retain the 500. > If you know perl or python better, the same can be coded for the post, > you just need to tell %post to use a different interpreter. I'd use python. > Note: usermod only fixes file ownership of stuff in their home dir, if > these system users already own files outside of their home, you'll need > to find them and modify them too. Another reason to get the job done before %post . > - proceed with whatever other post tasks you need > > You're already talking about installing FC16 in a way that's not > recommended, so modifying the accounts is no worse. Strickly speaking, that is not true. anaconda would happily let me keep my 500 if I were upgrading. > You should think carefully before you proceed down this path. It may > not be worth the effort. I've come to the conclusion that it is not. It's not so much the effort as the likelihood that I would mess it up in some horrible way. Finding an owned-by-user-500 file occasionally is less likely to less of a nuisance than screwing up a system user. I think the fedora folks were just teasing me when they said to use a kickstart file. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From hbrown at divms.uiowa.edu Thu Jan 26 04:20:03 2012 From: hbrown at divms.uiowa.edu (Hugh Brown) Date: Wed, 25 Jan 2012 22:20:03 -0600 Subject: How to start MySql on %post install and insert data In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: <585F927D-02C1-4479-9A57-3B49DFDA5252@divms.uiowa.edu> On Jan 25, 2012, at 20:34, Sebastiao Rocha wrote: > > Hi guys, i nee ome help. > > im using kickstart from fedora 7 to fedora 13, now im trying to use it on > fedora 16 with no success > > my trouble is how to start mysqld on post install > > i have tried this code... > systemctl enable mysqld.service > systemctl start mysqld.service > > but it gave me a error message: "Running in chroot, ignoring request" > and mysqld does not start to allow data insertion with mysql << > > anyone know hot to do this on fc15+ with systemd ? > > thanks... > > Rocha > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list I had the same problem with cups, so I just started cupsd directly and then terminated it when I was done. I'd call whatever the mysql.service file is calling. Hugh From Moray.Henderson at ict-software.org Thu Jan 26 10:01:44 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 26 Jan 2012 10:01:44 +0000 Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> > From: Michael Hennebry [mailto:hennebry at web.cs.ndsu.nodak.edu] > Sent: 26 January 2012 00:56 > On Wed, 25 Jan 2012, Tim Mooney wrote: > > > In regard to: Re: kickstart vs. /etc/login.defs, Michael Hennebry > said > > (at...: > > > >> On Wed, 25 Jan 2012, root at nachtmaus.us wrote: > >> > >>> Firstly, for where to put the ks file, it would be easiest for you > to > >>> remaster the boot CD, and put the ks file into the root directory > of the > >>> CD, update the configuration for the CD's boot-loader to add > something > >>> like "ks=cdrom:/fc14.ks", and then burn the resulting (modified) > file-tree > >>> to a new CD disk > > > > For a one-off install, in the absence of a provisioning environment > like > > cobbler, I personally think it's a lot easier to load the kickstart > file > > over the network. Just do something like > > > > - place your ks.cfg in a directory that is accessible via a URL > > - tell anaconda to load the ks.cfg from the URL > > > > ks=http://your.web.host.here/url/path/to/ks.cfg > > I think I can do that. I'm pretty sure that I can use my web site for > it. > Right, Tim? > > >>> To get around the too early/to late of %pre and %post, you may want > to add > >>> a custom RPM archive file to the CD, have it dump the files into > the > >>> being-created system, and run a command as part of its installation > >>> procedure that causes the newly added files to be read. Then > reference the > >>> new RPM archive in the packages section of your ks file. > > > > I don't understand from the initial post what the actual goal is, so > it's > > hard to know what to suggest here. Unless I missed it, the original > issue > > has something to do with uids in the 101-499 range, but I have no > idea > > what the actual problem is. > > By default, Fedora 16 has UID_MIN=GID_MIN=1000. > My Fedora 14 (EOL) has UID_MIN=GID=500. > These values are stored in /etc/login.defs . > I want to install (not uppgrade) Fedora 16 and retain the 500. > I have considered alternatives. > During %pre /etc does not yet exist, > so %pre is too early. > During %post there will already be fake users in the range 500..999, > so %post is too late. > Fedora claims that a kickstart file is the way to keep the 500. > Fedora was stingy with details. > > > I will say that you can do a lot in %post using things like "wget" to > > fetch a remote tarball or zip and then using the contents of that > archive > > to perform further actions. Ah, so I was right to have some of my own programs check login.defs rather than relying on a hard-wired 500 everywhere! That's useful to know. What fake users are created by the install? I would expect only system accounts to be created at that point, which are supposed to have uid's outside the range of normal users. Oh, amandabackup (in CentOS 5, anyway) is a "normal" user. That could be considered a bug in the amanda-backup_client package. Other than that, the only user I see on my CentOS servers that does not use an explicitly defined uid is openvpn, and that is created as a system user. It would be tricky to do what you want. /etc/login.defs is part of the shadow-utils package. You would need to create an rpm that would be installed onto the system after shadow-utils and before whichever packages create the users you are concerned about. In %post, though, you could modify the login.defs file - it will be /mnt/sysimage/etc/login.defs while the %post script is running, and use usermod to change the uid of any user you are particularly concerned about. Note: users with explicitly-assigned uids should not be changed. The --uid option of usermod will change a uid and "Any files which the user owns and which are located in the directory tree rooted at the user's home directory will have the file user ID changed automatically. Files outside of the user's home directory must be altered manually." If you're freshly installing a system though, I would really recommend leaving the defaults the way they are. Moray. "To err is human; to purr, feline." From hennebry at web.cs.ndsu.nodak.edu Thu Jan 26 14:12:36 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Thu, 26 Jan 2012 08:12:36 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> Message-ID: On Thu, 26 Jan 2012, Moray Henderson wrote: > Ah, so I was right to have some of my own programs check login.defs rather > than relying on a hard-wired 500 everywhere! That's useful to know. > > What fake users are created by the install? I would expect only system > accounts to be created at that point, which are supposed to have uid's > outside the range of normal users. I don't know. My current install has 38 fake users, including 0..8, 493..499 and 65534. With UID_MIN=1000, I'd expect to get some in the range 500..999. Just changing UID_MIN in %post would put them in the normal user range. As noted, getting the fixup right would be tricky. > It would be tricky to do what you want. /etc/login.defs is part of the > shadow-utils package. You would need to create an rpm that would be > installed onto the system after shadow-utils and before whichever packages > create the users you are concerned about. Nyet. I can barely use an rpm, much less write one. > In %post, though, you could modify the login.defs file - it will be > /mnt/sysimage/etc/login.defs while the %post script is running, and use Something else I didn't know and would have tripped over. > usermod to change the uid of any user you are particularly concerned about. > Note: users with explicitly-assigned uids should not be changed. The --uid Also, not all fake users have groups IDs the same as the UIDs. Hard as it would be to get it all right, knowing that I got it right would be even harder. > If you're freshly installing a system though, I would really recommend > leaving the defaults the way they are. It's looking like I won't have much choice. There would be too many hills to climb at once. >From http://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html#id3021598 "If you need to install a new system from scratch, while starting user accounts from 500 (to connect the system to a network with globally-defined UIDs), install using a kickstart script that places /etc/login.defs on the file system before package installation starts." Yeah right. BTW hennebry at web.cs.ndsu.NoDak.edu (not my computer) is user 362. UID_MIN is 1000. GID_MIN is 100. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From Moray.Henderson at ict-software.org Thu Jan 26 14:52:37 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 26 Jan 2012 14:52:37 +0000 Subject: kickstart vs. /etc/login.defs In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> Message-ID: <000c01ccdc3a$25cc6d70$71654850$@Henderson@ict-software.org> > From: Michael Hennebry [mailto:hennebry at web.cs.ndsu.nodak.edu] > Sent: 26 January 2012 14:13 > > >From http://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/sect-Releas e_Notes-Changes_for_Sysadmin.html#id3021598 > "If you need to install a new system from scratch, while starting user > accounts from 500 (to connect the system to a network with > globally-defined UIDs), install using a kickstart script that places > /etc/login.defs on the file system before package installation starts." Any Fedora developers care to comment here? Although documentation is a major source of frustration in the Open Source world, the other guys aren't really any better. I just got a great pop-up on Win 7 today: "A program running on this computer is trying to display a message." It gave 2 options: "View the message" and "Ask me later". I mean: WHAT?? Moray. "To err is human; to purr, feline." From rocha at abracops.info Thu Jan 26 15:35:19 2012 From: rocha at abracops.info (Sebastiao Rocha) Date: Thu, 26 Jan 2012 13:35:19 -0200 Subject: How to start MySql on %post install and insert data In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> Message-ID: <550a0cfc46abab41ffb1ea01104382f6@localhost> I already try your sugeestion, mysqld start, but without bind socket, so mysqld start but mysql and mysqladmin does not connect to him. any other sugestions ? On Thu, 26 Jan 2012 00:34:37 -0200, Sebastiao Rocha wrote: > Hi guys, i nee ome help. > > im using kickstart from fedora 7 to fedora 13, now im trying to use it on > fedora 16 with no success > > my trouble is how to start mysqld on post install > > i have tried this code... > systemctl enable mysqld.service > systemctl start mysqld.service > > but it gave me a error message: "Running in chroot, ignoring request" > and mysqld does not start to allow data insertion with mysql << > > anyone know hot to do this on fc15+ with systemd ? > > thanks... > > Rocha > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Atensiosamente Sebasti?o Rocha Interlink Sistemas Ltda. Fixo: (34) 3212-7512 Claro: (34) 8805-7512 TIM: (34) 8855-7512 From crucerua at avaya.com Thu Jan 26 16:03:03 2012 From: crucerua at avaya.com (Adrian Cruceru) Date: Thu, 26 Jan 2012 18:03:03 +0200 Subject: How to start MySql on %post install and insert data In-Reply-To: <550a0cfc46abab41ffb1ea01104382f6@localhost> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <550a0cfc46abab41ffb1ea01104382f6@localhost> Message-ID: <4F217937.4020509@avaya.com> Hi Rocha, You will probably need to do this in "%post --nochroot" section Mount stuff to your chroot: mount -o bind /dev /mnt/sysimage/dev mount -o bind /sys /mnt/sysimage/sys mount -o bind /proc /mnt/sysimage/proc Raise a network interface: /sbin/ifconfig lo up After which, your %post should probably work. You will be able to run mysqld from installer context. I'm not sure if that is really a good idea though, it might be better to have a simple script that does this at first boot. Regards, Adrian Cruceru On 01/26/2012 05:35 PM, Sebastiao Rocha wrote: > I already try your sugeestion, mysqld start, but without bind socket, so > mysqld start but mysql and mysqladmin does not connect to him. > > any other sugestions ? > > On Thu, 26 Jan 2012 00:34:37 -0200, Sebastiao Rocha > wrote: >> Hi guys, i nee ome help. >> >> im using kickstart from fedora 7 to fedora 13, now im trying to use it > on >> fedora 16 with no success >> >> my trouble is how to start mysqld on post install >> >> i have tried this code... >> systemctl enable mysqld.service >> systemctl start mysqld.service >> >> but it gave me a error message: "Running in chroot, ignoring request" >> and mysqld does not start to allow data insertion with mysql<< >> >> anyone know hot to do this on fc15+ with systemd ? >> >> thanks... >> >> Rocha >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list From sir_june at yahoo.com Sat Jan 28 19:30:35 2012 From: sir_june at yahoo.com (Sir June) Date: Sat, 28 Jan 2012 11:30:35 -0800 (PST) Subject: kickstart dhcp issues In-Reply-To: <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> Message-ID: <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> Hi, I am using a Poweredge R710 with 4 embedded NICs.? I have a kickstart procedure using? http. So i boot from my USB, type in: linux ks=http://x.x.x.x./path/ks.cfg Anaconda prompts me then which eth to use, i selected eth0 (which is connected to the network). But the sending request for IP information is taking forever. I them timesout, asks to select? ipv4/ipv6 options.? And back to "sending request for ip info...."? I am also using a cisco switch on the other end and changes in the switch config is not an option.This issue defeats auto install of Redhat. IF i connect the server into a normal switch (not Cisco), kickstart works fine., How to set something that anaconda will continue to request & wait for DHCP ip. thanks, sirjun -------------- next part -------------- An HTML attachment was scrubbed... URL: From kajtzu at a51.org Sat Jan 28 20:15:56 2012 From: kajtzu at a51.org (Kaj Niemi) Date: Sat, 28 Jan 2012 20:15:56 +0000 Subject: kickstart dhcp issues In-Reply-To: <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> Message-ID: Try enabling portfast (rstp edge) the ports on your Cisco switch? It'll transition the port to forwarding directly without going through blocking, listening or learning state. Kaj On Jan 28, 2012, at 19:30, Sir June wrote: > > Hi, > > I am using a Poweredge R710 with 4 embedded NICs. I have a kickstart procedure using http. So i boot from my USB, type in: > linux ks=http://x.x.x.x./path/ks.cfg > > Anaconda prompts me then which eth to use, i selected eth0 (which is connected to the network). But the sending request for IP information is taking forever. I them timesout, asks to select ipv4/ipv6 options. And back to "sending request for ip info...." I am also using a cisco switch on the other end and changes in the switch config is not an option.This issue defeats auto install of Redhat. IF i connect the server into a normal switch (not Cisco), kickstart works fine., > > How to set something that anaconda will continue to request & wait for DHCP ip. > > thanks, > sirjun > > _______________________________________________ > 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: smime.p7s Type: application/pkcs7-signature Size: 4383 bytes Desc: not available URL: From sir_june at yahoo.com Sat Jan 28 22:54:21 2012 From: sir_june at yahoo.com (Sir June) Date: Sat, 28 Jan 2012 14:54:21 -0800 (PST) Subject: kickstart dhcp issues In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> Message-ID: <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com> re-configuring the Cisco switch is not an option. i can't seem to find the right combination for? dhcptimeout, nicdelay, linksleep options.? ksdevice=eth0 seems not to take effect also.? it keeps on asking me to select which eth to use -sirjune ? ________________________________ From: Kaj Niemi To: Sir June ; Discussion list about Kickstart Sent: Saturday, January 28, 2012 3:15 PM Subject: Re: kickstart dhcp issues Try enabling portfast (rstp edge) the ports on your Cisco switch? It'll transition the port to forwarding directly without going through blocking, listening or learning state. Kaj On Jan 28, 2012, at 19:30, Sir June wrote: > >Hi, > >I am using a Poweredge R710 with 4 embedded NICs.? I have a kickstart procedure using? http. So i boot from my USB, type in: >linux ks=http://x.x.x.x./path/ks.cfg > >Anaconda prompts me then which eth to use, i selected eth0 (which is connected to the network). But the sending request for IP information is taking forever. I them timesout, asks to select? ipv4/ipv6 options.? And back to "sending request for ip info...."? I am also using a cisco switch on the other end and changes in the switch config is not an option.This issue defeats auto install of Redhat. IF i connect the server into a normal switch (not Cisco), kickstart works fine., > >How to set something that anaconda will continue to request & wait for DHCP ip. > >thanks, >sirjun > >_______________________________________________ >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 hennebry at web.cs.ndsu.nodak.edu Sun Jan 29 00:11:12 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Sat, 28 Jan 2012 18:11:12 -0600 (CST) Subject: kickstart packages Message-ID: One of the things I would like to do with kickstart is to get aproximately the same set of packages I have installed now. I always forget something that I have to install later, so just using the anaconda-generated kickstart file would not do the trick. I've looked at the kickstart file, I've read about its format and I've looked at package lists from yum and rpm. The correspondence is not obvious to me. Assuming that the kickstart file is correct, how do I add a package to it? How do I figure out what name to give in the kickstart file? I'm pretty sure that I didn't add tex after install, but look here: [root at localhost ~]# yum provides '*/tex' ... texlive-2007-56.fc14.i686 : Binaries for the TeX formatting system Repo : installed Matched from: Filename : /usr/bin/tex [root at localhost ~]# rpm -q --all | grep tex texlive-texmf-2007-36.fc14.noarch texlive-texmf-fonts-2007-36.fc14.noarch texlive-utils-2007-56.fc14.i686 tex-preview-11.86-6.fc14.noarch gettext-0.18.1.1-5.fc14.i686 texlive-2007-56.fc14.i686 texlive-texmf-latex-2007-36.fc14.noarch texlive-texmf-dvips-2007-36.fc14.noarch texlive-dvips-2007-56.fc14.i686 texlive-latex-2007-56.fc14.i686 gettext-libs-0.18.1.1-5.fc14.i686 libtextcat-2.2-11.fc13.i686 [root at localhost ~]# grep tex anaconda-ks.cfg @text-internet Also, anaconda-ks.cfg was generated by a F14 install. I'll be installing F16. How badly will that bite me? -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From kajtzu at a51.org Sun Jan 29 01:39:30 2012 From: kajtzu at a51.org (Kaj Niemi) Date: Sun, 29 Jan 2012 01:39:30 +0000 Subject: kickstart dhcp issues In-Reply-To: <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> , <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com> Message-ID: Without portfast it will take 50 seconds for the port to transition to forwarding. Your delay will need to be longer than that. You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs. Personally I would add one line per port on the switches ;-) Kaj Sent from my iPhone On 28 Jan 2012, at 22:54, "Sir June" > wrote: re-configuring the Cisco switch is not an option. i can't seem to find the right combination for dhcptimeout, nicdelay, linksleep options. ksdevice=eth0 seems not to take effect also. it keeps on asking me to select which eth to use -sirjune ________________________________ From: Kaj Niemi > To: Sir June >; Discussion list about Kickstart > Sent: Saturday, January 28, 2012 3:15 PM Subject: Re: kickstart dhcp issues Try enabling portfast (rstp edge) the ports on your Cisco switch? It'll transition the port to forwarding directly without going through blocking, listening or learning state. Kaj On Jan 28, 2012, at 19:30, Sir June wrote: Hi, I am using a Poweredge R710 with 4 embedded NICs. I have a kickstart procedure using http. So i boot from my USB, type in: linux ks=http://x.x.x.x./path/ks.cfg Anaconda prompts me then which eth to use, i selected eth0 (which is connected to the network). But the sending request for IP information is taking forever. I them timesout, asks to select ipv4/ipv6 options. And back to "sending request for ip info...." I am also using a cisco switch on the other end and changes in the switch config is not an option.This issue defeats auto install of Redhat. IF i connect the server into a normal switch (not Cisco), kickstart works fine., How to set something that anaconda will continue to request & wait for DHCP ip. thanks, sirjun _______________________________________________ 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 petro at cpetro.us Sun Jan 29 05:43:24 2012 From: petro at cpetro.us (Petro) Date: Sun, 29 Jan 2012 15:13:24 +0930 Subject: kickstart dhcp issues In-Reply-To: References: Message-ID: <4F24DC7C.2060607@cpetro.us> On 1/29/12 08:24 AM, kickstart-list-request at redhat.com wrote: > > re-configuring the Cisco switch is not an option. i can't seem to find > the right combination for dhcptimeout, nicdelay, linksleep options. > ksdevice=eth0 seems not to take effect also. it keeps on asking me to > select which eth to use If you can't effect a change in the cisco switch, then it just may not work. It's not just a matter of portfast, if you're using vlans (I'm probably going to screw this up, I'm not as deeply versed in networks as I'd like) you need to have some sort of dhcp helper line. Cisco's documentation says: """ To forward the BootP/DHCP request from the client to the DHCP server, the ip helper-address interface command is used. The IP helper-address can be configured to forward any UDP broadcast based on UDP port number. By default, the IP helper-address will forward the following UDP broadcasts: * Trivial File Transfer Protocol (TFTP) (port 69) * DNS (port 53), time service (port 37) * NetBIOS name server (port 137) * NetBIOS datagram server (port 138) * Boot Protocol (DHCP/BootP) client and server datagrams (ports 67 and 68) * Terminal Access Control Access Control System (TACACS) service (port 49) * IEN-116 name service (port 42) """ You would need a line like "ip helper-address 172.30.23.34". I suspect that if you can't modify the switch config at all then you're hosed. From Moray.Henderson at ict-software.org Mon Jan 30 10:37:41 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Mon, 30 Jan 2012 10:37:41 +0000 Subject: Keeping up with the changes In-Reply-To: References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> , <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com> Message-ID: <000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> From: Kaj Niemi [mailto:kajtzu at a51.org] Sent: 29 January 2012 01:40 You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs. Pretty soon I'm going to have to start updating the software I develop and maintain for RHEL 6. Apparently, I'm going to have to rewrite the entire set of perfectly-working network code because many (but not all) of my customers use Dells. What's the best place to keep up with changes like this - to learn not just what they are, but the reasons for them and the lists of exactly what hardware combinations produce which responses in the OS? Moray. "To err is human; to purr, feline." -------------- next part -------------- An HTML attachment was scrubbed... URL: From hellstrom.mattias at gmail.com Mon Jan 30 10:52:55 2012 From: hellstrom.mattias at gmail.com (=?ISO-8859-1?Q?Mattias_Hellstr=F6m?=) Date: Mon, 30 Jan 2012 11:52:55 +0100 Subject: kickstart vs. /etc/login.defs In-Reply-To: References: Message-ID: On Wed, Jan 25, 2012 at 5:19 AM, Michael Hennebry wrote: > I've encountered two problems: > How to specify the kickstart file. > How, in the kickstart file does one affect /etc/login.defs . > According to fedora, a kickstart file is the right way to do what I want. > There is no specific command to affect /etc/login.defs . >> >> From what I have read, %post runs too late: > I solved this problem by remaking shadow-utils.src.rpm by changing the login.defs it provieds. Then create a repo and reference it in kickstart.cfg: repo --name=usr500 --baseurl=http://mywebserver/yum/arch/f16-i386 --cost=1 --includepkgs=shadow-utils More retails, it all took only half a day: Patching an rpm means installing it, editing the spec and the contents (or adding a patchfile) then repacking the src.rpm then rpmrebuild --rebuild it. Repo are just the files on a webserver and then run createrepo. A better solution would be to implement a kickstart %mid section where you can run a script on the install just before any packages are installed, after filesystems are created and mounted are mounted etc. /Mattias From ks-list at puzzled.xs4all.nl Mon Jan 30 14:12:13 2012 From: ks-list at puzzled.xs4all.nl (Patrick Lists) Date: Mon, 30 Jan 2012 15:12:13 +0100 Subject: Keeping up with the changes In-Reply-To: <000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> , <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com> <000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> Message-ID: <4F26A53D.7050400@puzzled.xs4all.nl> On 30-01-12 11:37, Moray Henderson wrote: > *From:*Kaj Niemi [mailto:kajtzu at a51.org] > *Sent:* 29 January 2012 01:40 > > You did not mention which rhel version you are using but interfaces on > dells in rhel 6.1 will show up as em1, em2, etc. by default instead of > eth0, eth1. Both dell and redhat mention it in their docs. > > Pretty soon I?m going to have to start updating the software I develop > and maintain for RHEL 6. Apparently, I?m going to have to rewrite the > entire set of perfectly-working network code because many (but not all) > of my customers use Dells. What?s the best place to keep up with changes > like this - to learn not just what they are, but the reasons for them > and the lists of exactly what hardware combinations produce which > responses in the OS? Read Linux related news sites :) Iirc there were quite a few reports about biosdevname. See Matt Domsch's blog: http://domsch.com/blog/?p=455 Matt works at Dell which explains the Dell focus. A good way of keeping up is by tracking Fedora's New Features page of the upcoming Fedora release on Fedora's wiki. Fedora is usually the first to pick up new stuff which can/will end up in RHEL (CentOS) as was the case for biosdevname. Just run Fedora on your desktop and test your RPMs on your desktop too. If your software uses SysVinit: on Fedora it has already been replaced by systemd which probably will find its way to RHEL at some point since it was developed by a Red Hat employee (Lennart Poettering). A 12 part systemd admin guide: http://0pointer.de/blog/projects/systemd-for-admins-1.html Regards, Patrick From chip.shabazian at bankofamerica.com Mon Jan 30 15:33:34 2012 From: chip.shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 30 Jan 2012 15:33:34 +0000 Subject: kickstart dhcp issues In-Reply-To: <4F24DC7C.2060607@cpetro.us> References: <4F24DC7C.2060607@cpetro.us> Message-ID: <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> This has been covered many times if you search through the archive, or Google for the presentations I've given at Linuxworld and Red Hat Summit years ago. You need to force the NIC to speed/duplex. Chip -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Petro Sent: Saturday, January 28, 2012 9:43 PM To: kickstart-list at redhat.com Subject: Re: kickstart dhcp issues On 1/29/12 08:24 AM, kickstart-list-request at redhat.com wrote: > > re-configuring the Cisco switch is not an option. i can't seem to find > the right combination for dhcptimeout, nicdelay, linksleep options. > ksdevice=eth0 seems not to take effect also. it keeps on asking me to > select which eth to use If you can't effect a change in the cisco switch, then it just may not work. It's not just a matter of portfast, if you're using vlans (I'm probably going to screw this up, I'm not as deeply versed in networks as I'd like) you need to have some sort of dhcp helper line. Cisco's documentation says: """ To forward the BootP/DHCP request from the client to the DHCP server, the ip helper-address interface command is used. The IP helper-address can be configured to forward any UDP broadcast based on UDP port number. By default, the IP helper-address will forward the following UDP broadcasts: * Trivial File Transfer Protocol (TFTP) (port 69) * DNS (port 53), time service (port 37) * NetBIOS name server (port 137) * NetBIOS datagram server (port 138) * Boot Protocol (DHCP/BootP) client and server datagrams (ports 67 and 68) * Terminal Access Control Access Control System (TACACS) service (port 49) * IEN-116 name service (port 42) """ You would need a line like "ip helper-address 172.30.23.34". I suspect that if you can't modify the switch config at all then you're hosed. _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. From kajtzu at a51.org Mon Jan 30 16:27:26 2012 From: kajtzu at a51.org (Kaj Niemi) Date: Mon, 30 Jan 2012 16:27:26 +0000 Subject: Keeping up with the changes In-Reply-To: <000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry> <000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org> <1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com> , <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com> <000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> Message-ID: <85FA8C10-5F8E-4787-9EAE-71B838C6369F@a51.org> I believe this is mentioned at least by: - Dell in their release notes for each platform - Dell PowerEdge blogs, Meaningful names for network devices in RHEL 6.1 on Dell systems ... - Dell OS And Application notes, http://en.community.dell.com/techcenter/os-applications/w/wiki/red-hat.aspx - Dell whitepapers, http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf - RedHat in their technical notes for RHEL 6u1 and 6u2 (pages 7, 189) etc. From my POV there wasn't much to change and now the name of the interface (em1) corresponds to interface labeled Gb1 on the back of the server. Kaj On Jan 30, 2012, at 10:37, Moray Henderson wrote: > From: Kaj Niemi [mailto:kajtzu at a51.org] > Sent: 29 January 2012 01:40 > > You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs. > > Pretty soon I?m going to have to start updating the software I develop and maintain for RHEL 6. Apparently, I?m going to have to rewrite the entire set of perfectly-working network code because many (but not all) of my customers use Dells. What?s the best place to keep up with changes like this - to learn not just what they are, but the reasons for them and the lists of exactly what hardware combinations produce which responses in the OS? > > > Moray. > ?To err is human; to purr, feline.? > _______________________________________________ > 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: smime.p7s Type: application/pkcs7-signature Size: 4383 bytes Desc: not available URL: From kajtzu at a51.org Mon Jan 30 16:28:44 2012 From: kajtzu at a51.org (Kaj Niemi) Date: Mon, 30 Jan 2012 16:28:44 +0000 Subject: kickstart dhcp issues In-Reply-To: <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> References: <4F24DC7C.2060607@cpetro.us> <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> Message-ID: <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> There should be no need to force speed/duplex in 2012. Kaj On Jan 30, 2012, at 15:33, Shabazian, Chip wrote: > This has been covered many times if you search through the archive, or Google for the presentations I've given at Linuxworld and Red Hat Summit years ago. You need to force the NIC to speed/duplex. > > Chip > > -----Original Message----- > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Petro > Sent: Saturday, January 28, 2012 9:43 PM > To: kickstart-list at redhat.com > Subject: Re: kickstart dhcp issues > > On 1/29/12 08:24 AM, kickstart-list-request at redhat.com wrote: >> >> re-configuring the Cisco switch is not an option. i can't seem to find >> the right combination for dhcptimeout, nicdelay, linksleep options. >> ksdevice=eth0 seems not to take effect also. it keeps on asking me to >> select which eth to use > If you can't effect a change in the cisco switch, then it just may not work. > > It's not just a matter of portfast, if you're using vlans (I'm probably going to screw this up, I'm not as deeply versed in networks as I'd > like) you need to have some sort of dhcp helper line. Cisco's documentation says: > > """ > To forward the BootP/DHCP request from the client to the DHCP server, the ip helper-address interface command is used. The IP helper-address can be configured to forward any UDP broadcast based on UDP port number. > By default, the IP helper-address will forward the following UDP broadcasts: > > * Trivial File Transfer Protocol (TFTP) (port 69) > * DNS (port 53), time service (port 37) > * NetBIOS name server (port 137) > * NetBIOS datagram server (port 138) > * Boot Protocol (DHCP/BootP) client and server datagrams (ports 67 and 68) > * Terminal Access Control Access Control System (TACACS) service (port 49) > * IEN-116 name service (port 42) > """ > > You would need a line like "ip helper-address 172.30.23.34". > > I suspect that if you can't modify the switch config at all then you're hosed. > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: > http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4383 bytes Desc: not available URL: From Jim.Cole at mckesson.com Mon Jan 30 16:46:09 2012 From: Jim.Cole at mckesson.com (Cole, Jim) Date: Mon, 30 Jan 2012 11:46:09 -0500 Subject: Keeping up with the changes In-Reply-To: <85FA8C10-5F8E-4787-9EAE-71B838C6369F@a51.org> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry><000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org><1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com>, <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com><000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> <85FA8C10-5F8E-4787-9EAE-71B838C6369F@a51.org> Message-ID: <815F317B2BC9C84C920132D40978647E17182F3E@NDHV3000.na.corp.mckesson.com> Is this applicable for all HW vendors with RHEL 6u2 or just Dell? If you work with a variety of vendors like I do..thats a concern. I don't want to try to deal with determining the vendor during the kickstart. Thanks! Jim Cole Senior Technical Engineer McKesson Provider Technologies jim.cole at mckesson.com Office: (515) 619-9820 Live Meeting URL: Here Conference #: (877) 684-9625 Participant code: 732158 From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Kaj Niemi Sent: Monday, January 30, 2012 10:27 AM To: Discussion list about Kickstart Subject: Re: Keeping up with the changes I believe this is mentioned at least by: - Dell in their release notes for each platform - Dell PowerEdge blogs, Meaningful names for network devices in RHEL 6.1 on Dell systems ... - Dell OS And Application notes, http://en.community.dell.com/techcenter/os-applications/w/wiki/red-hat.a spx - Dell whitepapers, http://linux.dell.com/files/whitepapers/consistent_network_device_naming _in_linux.pdf - RedHat in their technical notes for RHEL 6u1 and 6u2 (pages 7, 189) etc. >From my POV there wasn't much to change and now the name of the interface (em1) corresponds to interface labeled Gb1 on the back of the server. Kaj On Jan 30, 2012, at 10:37, Moray Henderson wrote: From: Kaj Niemi [mailto:kajtzu at a51.org] Sent: 29 January 2012 01:40 You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs. Pretty soon I'm going to have to start updating the software I develop and maintain for RHEL 6. Apparently, I'm going to have to rewrite the entire set of perfectly-working network code because many (but not all) of my customers use Dells. What's the best place to keep up with changes like this - to learn not just what they are, but the reasons for them and the lists of exactly what hardware combinations produce which responses in the OS? Moray. "To err is human; to purr, feline." _______________________________________________ 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 hennebry at web.cs.ndsu.nodak.edu Mon Jan 30 17:59:24 2012 From: hennebry at web.cs.ndsu.nodak.edu (Michael Hennebry) Date: Mon, 30 Jan 2012 11:59:24 -0600 (CST) Subject: kickstart vs. /etc/login.defs In-Reply-To: References: Message-ID: On Mon, 30 Jan 2012, Mattias Hellstr?m wrote: > On Wed, Jan 25, 2012 at 5:19 AM, Michael Hennebry > wrote: >> I've encountered two problems: >> How to specify the kickstart file. >> How, in the kickstart file does one affect /etc/login.defs . >> According to fedora, a kickstart file is the right way to do what I want. >> There is no specific command to affect /etc/login.defs . >>> >>> From what I have read, %post runs too late: >> > > I solved this problem by remaking shadow-utils.src.rpm by changing the > login.defs it provieds. As noted earlier, I can barely use an rpm, much less edit one. Too many hills to climb at once. > Then create a repo and reference it in kickstart.cfg: > repo --name=usr500 --baseurl=http://mywebserver/yum/arch/f16-i386 > --cost=1 --includepkgs=shadow-utils You might want to consider contributing this to a repository. It's a bit late for me, but there are others who might not switch until F15 is EOL. > More retails, it all took only half a day: > Patching an rpm means installing it, editing the spec and the contents > (or adding a patchfile) then repacking the src.rpm then rpmrebuild > --rebuild it. > Repo are just the files on a webserver and then run createrepo. > > A better solution would be to implement a kickstart %mid section where > you can run a script on the install just before any packages are > installed, after filesystems are created and mounted are mounted etc. Yup. BTW is there anything that can be done in %post that root cannot do later? -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily From kajtzu at a51.org Mon Jan 30 18:12:45 2012 From: kajtzu at a51.org (Kaj Niemi) Date: Mon, 30 Jan 2012 18:12:45 +0000 Subject: Keeping up with the changes In-Reply-To: <815F317B2BC9C84C920132D40978647E17182F3E@NDHV3000.na.corp.mckesson.com> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry><000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org><1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com>, <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com><000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> <85FA8C10-5F8E-4787-9EAE-71B838C6369F@a51.org> <815F317B2BC9C84C920132D40978647E17182F3E@NDHV3000.na.corp.mckesson.com> Message-ID: Using ksdevice=bootif or ksdevice=link when kickstarting makes one not care about interface naming. The link parameter is problematic if you have a crapload of interfaces connected and need to make sure a specific card is the one that is booted from while bootif uses whatever interface you have defined as the PXE interface. Works well in my experience. As for other vendors I'm not sure. I deal with vendor specific things (hp asm, dell omsa, etc.) only after kickstart has finished in a firstboot -type installation script where the vendor is determinted by using dmidecode. :-) Kaj On Jan 30, 2012, at 16:46, Cole, Jim wrote: > Is this applicable for all HW vendors with RHEL 6u2 or just Dell? If you work with a variety of vendors like I do..thats a concern. I don?t want to try to deal with determining the vendor during the kickstart. > > Thanks! > Jim Cole > Senior Technical Engineer > McKesson Provider Technologies > jim.cole at mckesson.com > Office: (515) 619-9820 > Live Meeting URL: Here > Conference #: (877) 684-9625 Participant code: 732158 > > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Kaj Niemi > Sent: Monday, January 30, 2012 10:27 AM > To: Discussion list about Kickstart > Subject: Re: Keeping up with the changes > > I believe this is mentioned at least by: > > - Dell in their release notes for each platform > - Dell PowerEdge blogs, Meaningful names for network devices in RHEL 6.1 on Dell systems ... > - Dell OS And Application notes, http://en.community.dell.com/techcenter/os-applications/w/wiki/red-hat.aspx > - Dell whitepapers, http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf > - RedHat in their technical notes for RHEL 6u1 and 6u2 (pages 7, 189) > > etc. > > From my POV there wasn't much to change and now the name of the interface (em1) corresponds to interface labeled Gb1 on the back of the server. > > > > > Kaj > > On Jan 30, 2012, at 10:37, Moray Henderson wrote: > > > From: Kaj Niemi [mailto:kajtzu at a51.org] > Sent: 29 January 2012 01:40 > > > You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs. > > Pretty soon I?m going to have to start updating the software I develop and maintain for RHEL 6. Apparently, I?m going to have to rewrite the entire set of perfectly-working network code because many (but not all) of my customers use Dells. What?s the best place to keep up with changes like this - to learn not just what they are, but the reasons for them and the lists of exactly what hardware combinations produce which responses in the OS? > > > Moray. > ?To err is human; to purr, feline.? > _______________________________________________ > 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: smime.p7s Type: application/pkcs7-signature Size: 4383 bytes Desc: not available URL: From angus.clarke at gmail.com Mon Jan 30 18:36:37 2012 From: angus.clarke at gmail.com (Angus Clarke) Date: Mon, 30 Jan 2012 19:36:37 +0100 Subject: kickstart dhcp issues In-Reply-To: <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> References: <4F24DC7C.2060607@cpetro.us> <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> Message-ID: I find specifying the device MAC address in the ifcfg-eth? config file is enough to bond the configuration to a particular physical interface. I suppose your modules configuration would need some consideration for interfaces that use different modules. In my setup however, eth0 through to eth3 (onboard) and eth4 through to eth7 (PCIe which might be added much later after initial RHEL install) all use bnx2. I notice that without specifying the device MAC address in the config files you are concerned with, and then later adding additional NICs on the PCIe bus - results in the PCIe NICs preceding the onboard NICs (eth0 changes to represent the NIC on the lowest PCIe bus.) HP DL380 G7 and RHEL5.2 x86_64 On 30 January 2012 17:28, Kaj Niemi wrote: > There should be no need to force speed/duplex in 2012. > > > > Kaj > > On Jan 30, 2012, at 15:33, Shabazian, Chip wrote: > > > This has been covered many times if you search through the archive, or > Google for the presentations I've given at Linuxworld and Red Hat Summit > years ago. You need to force the NIC to speed/duplex. > > > > Chip > > > > -----Original Message----- > > From: kickstart-list-bounces at redhat.com [mailto: > kickstart-list-bounces at redhat.com] On Behalf Of Petro > > Sent: Saturday, January 28, 2012 9:43 PM > > To: kickstart-list at redhat.com > > Subject: Re: kickstart dhcp issues > > > > On 1/29/12 08:24 AM, kickstart-list-request at redhat.com wrote: > >> > >> re-configuring the Cisco switch is not an option. i can't seem to find > >> the right combination for dhcptimeout, nicdelay, linksleep options. > >> ksdevice=eth0 seems not to take effect also. it keeps on asking me to > >> select which eth to use > > If you can't effect a change in the cisco switch, then it just may not > work. > > > > It's not just a matter of portfast, if you're using vlans (I'm probably > going to screw this up, I'm not as deeply versed in networks as I'd > > like) you need to have some sort of dhcp helper line. Cisco's > documentation says: > > > > """ > > To forward the BootP/DHCP request from the client to the DHCP server, > the ip helper-address interface command is used. The IP helper-address can > be configured to forward any UDP broadcast based on UDP port number. > > By default, the IP helper-address will forward the following UDP > broadcasts: > > > > * Trivial File Transfer Protocol (TFTP) (port 69) > > * DNS (port 53), time service (port 37) > > * NetBIOS name server (port 137) > > * NetBIOS datagram server (port 138) > > * Boot Protocol (DHCP/BootP) client and server datagrams (ports 67 and > 68) > > * Terminal Access Control Access Control System (TACACS) service (port > 49) > > * IEN-116 name service (port 42) > > """ > > > > You would need a line like "ip helper-address 172.30.23.34". > > > > I suspect that if you can't modify the switch config at all then you're > hosed. > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > ---------------------------------------------------------------------- > > This message w/attachments (message) is intended solely for the use of > the intended recipient(s) and may contain information that is privileged, > confidential or proprietary. If you are not an intended recipient, please > notify the sender, and then please delete and destroy all copies and > attachments, and be advised that any review or dissemination of, or the > taking of any action in reliance on, the information contained in or > attached to this message is prohibited. > > Unless specifically indicated, this message is not an offer to sell or a > solicitation of any investment products or other financial product or > service, an official confirmation of any transaction, or an official > statement of Sender. Subject to applicable law, Sender may intercept, > monitor, review and retain e-communications (EC) traveling through its > networks/systems and may produce any such EC to regulators, law > enforcement, in litigation and as required by law. > > The laws of the country of each sender/recipient may impact the handling > of EC, and EC may be archived, supervised and produced in countries other > than the country in which you are located. This message cannot be > guaranteed to be secure or free of errors or viruses. > > > > References to "Sender" are references to any subsidiary of Bank of > America Corporation. Securities and Insurance Products: * Are Not FDIC > Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit > * Are Not a Condition to Any Banking Service or Activity * Are Not Insured > by Any Federal Government Agency. Attachments that are part of this EC may > have additional important disclosures and disclaimers, which you should > read. This message is subject to terms available at the following link: > > http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender > you consent to the foregoing. > > > > _______________________________________________ > > 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 kajtzu at a51.org Mon Jan 30 19:06:28 2012 From: kajtzu at a51.org (Kaj Niemi) Date: Mon, 30 Jan 2012 19:06:28 +0000 Subject: kickstart dhcp issues In-Reply-To: References: <4F24DC7C.2060607@cpetro.us> <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> Message-ID: <617EF12B-7DAE-4101-822C-D95E7B161FBA@a51.org> I think this is what the dell naming scheme was designed to prevent? :-) Kaj On Jan 30, 2012, at 18:36, Angus Clarke wrote: > I notice that without specifying the device MAC address in the config files you are concerned with, and then later adding additional NICs on the PCIe bus - results in the PCIe NICs preceding the onboard NICs (eth0 changes to represent the NIC on the lowest PCIe bus.) > > HP DL380 G7 and RHEL5.2 x86_64 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4383 bytes Desc: not available URL: From angus.clarke at gmail.com Mon Jan 30 20:13:56 2012 From: angus.clarke at gmail.com (Angus Clarke) Date: Mon, 30 Jan 2012 21:13:56 +0100 Subject: kickstart dhcp issues In-Reply-To: <617EF12B-7DAE-4101-822C-D95E7B161FBA@a51.org> References: <4F24DC7C.2060607@cpetro.us> <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> <617EF12B-7DAE-4101-822C-D95E7B161FBA@a51.org> Message-ID: Perhaps - I didn't read the Dell solution as specifying MAC addresses is sufficient and already available, at least for my requirements (Ethernet interfaces) All the best ~Angus On 30 January 2012 20:06, Kaj Niemi wrote: > I think this is what the dell naming scheme was designed to prevent? :-) > > > > > Kaj > > On Jan 30, 2012, at 18:36, Angus Clarke wrote: > > I notice that without specifying the device MAC address in the config > files you are concerned with, and then later adding additional NICs on the > PCIe bus - results in the PCIe NICs preceding the onboard NICs (eth0 > changes to represent the NIC on the lowest PCIe bus.) > > HP DL380 G7 and RHEL5.2 x86_64 > > > > _______________________________________________ > 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 Moray.Henderson at om.org Tue Jan 31 14:35:02 2012 From: Moray.Henderson at om.org (Moray Henderson (ICT)) Date: Tue, 31 Jan 2012 14:35:02 +0000 Subject: Keeping up with the changes In-Reply-To: <815F317B2BC9C84C920132D40978647E17182F3E@NDHV3000.na.corp.mckesson.com> References: <1581250944-1327465954-cardhu_decombobulator_blackberry.rim.net-1077717564-@b26.c5.bise6.blackberry><000b01ccdc11$8383a7e0$8a8af7a0$@Henderson@ict-software.org><1327779035.9283.YahooMailNeo@web65708.mail.ac4.yahoo.com>, <1327791261.7925.YahooMailNeo@web65709.mail.ac4.yahoo.com><000c01ccdf3b$32b1cf40$98156dc0$@Henderson@ict-software.org> <85FA8C10-5F8E-4787-9EAE-71B838C6369F@a51.org> <815F317B2BC9C84C920132D40978647E17182F3E@NDHV3000.na.corp.mckesson.com> Message-ID: Oh, it's not hardware vendor you would need to detect: it's the individual hardware Model! You should be able to get that sort of stuff with dmidecode though. http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf lists the models and also tells you how to turn it off, which will be helpful in the short term. Is there a Thing like list-harddrives available yet to help kickstarters work out what their network card is called - or which is the Ethernet and which the Wireless? Or any tips for people wanting to do it the New Way? Moray. "To err is human; to purr, feline." From: Cole, Jim [mailto:Jim.Cole at mckesson.com] Sent: 30 January 2012 16:46 To: Discussion list about Kickstart Subject: RE: Keeping up with the changes Is this applicable for all HW vendors with RHEL 6u2 or just Dell? If you work with a variety of vendors like I do..thats a concern. I don't want to try to deal with determining the vendor during the kickstart. Thanks! Jim Cole Senior Technical Engineer McKesson Provider Technologies jim.cole at mckesson.com Office: (515) 619-9820 Live Meeting URL: Here Conference #: (877) 684-9625 Participant code: 732158 From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Kaj Niemi Sent: Monday, January 30, 2012 10:27 AM To: Discussion list about Kickstart Subject: Re: Keeping up with the changes I believe this is mentioned at least by: - Dell in their release notes for each platform - Dell PowerEdge blogs, Meaningful names for network devices in RHEL 6.1 on Dell systems ... - Dell OS And Application notes, http://en.community.dell.com/techcenter/os-applications/w/wiki/red-hat.aspx - Dell whitepapers, http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf - RedHat in their technical notes for RHEL 6u1 and 6u2 (pages 7, 189) etc. >From my POV there wasn't much to change and now the name of the interface (em1) corresponds to interface labeled Gb1 on the back of the server. Kaj On Jan 30, 2012, at 10:37, Moray Henderson wrote: From: Kaj Niemi [mailto:kajtzu at a51.org] Sent: 29 January 2012 01:40 You did not mention which rhel version you are using but interfaces on dells in rhel 6.1 will show up as em1, em2, etc. by default instead of eth0, eth1. Both dell and redhat mention it in their docs. Pretty soon I'm going to have to start updating the software I develop and maintain for RHEL 6. Apparently, I'm going to have to rewrite the entire set of perfectly-working network code because many (but not all) of my customers use Dells. What's the best place to keep up with changes like this - to learn not just what they are, but the reasons for them and the lists of exactly what hardware combinations produce which responses in the OS? Moray. "To err is human; to purr, feline." _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ________________________________ OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 0JG - United Kingdom A company limited by guarantee - Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sir_june at yahoo.com Tue Jan 31 15:16:36 2012 From: sir_june at yahoo.com (Sir June) Date: Tue, 31 Jan 2012 07:16:36 -0800 (PST) Subject: kickstart dhcp issues In-Reply-To: References: <4F24DC7C.2060607@cpetro.us> <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> <617EF12B-7DAE-4101-822C-D95E7B161FBA@a51.org> Message-ID: <1328022996.62675.YahooMailNeo@web65702.mail.ac4.yahoo.com> I thank you all for the comments, solutions and suggestions. as of yesterday,? I was able to install? RHEL5.5 via kickstart using? linux ks=http://192.168xxx.xxx/redhat/ks.cfg? dhcptimeout=500 although it still asks me as to which ethernet to use, (eth0..eth5). it continues afterwards.? I tried specifying ksdevice=eth0 and noipv6? but the installation wont proceed and keeps on coming back to the ipv4 and ipv6 selections. I will try all the suggestions & options mentioned here. thanks, Sirjune ? ________________________________ From: Angus Clarke To: Discussion list about Kickstart Sent: Monday, January 30, 2012 3:13 PM Subject: Re: kickstart dhcp issues Perhaps - I didn't read the Dell solution as specifying MAC addresses is sufficient and already available, at least for my requirements (Ethernet interfaces) All the best ~Angus On 30 January 2012 20:06, Kaj Niemi wrote: I think this is what the dell naming scheme was designed to prevent? :-) > > > > > > > > >Kaj > >On Jan 30, 2012, at 18:36, Angus Clarke wrote: > >I notice that without specifying the device MAC address in the config files you are concerned with, and then later adding additional NICs on the PCIe bus - results in the PCIe NICs preceding the onboard NICs (eth0 changes to represent the NIC on the lowest PCIe bus.) >> >>HP DL380 G7 and RHEL5.2 x86_64 > >_______________________________________________ >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 listsarnau at gmail.com Tue Jan 31 15:32:19 2012 From: listsarnau at gmail.com (Arnau Bria) Date: Tue, 31 Jan 2012 16:32:19 +0100 Subject: vnc + rescue Message-ID: <20120131163219.1be500a4@amarrosa.pic.es> Hi all, I'm trying to run rescue + vnc options on same kickstart installation file. The vnc does not work, it only starts the rescue mode. Did anyone ran both options at once? are they mutual exclusive? (Rh5 and Rh6) TIA, Arnau From jlaska at redhat.com Tue Jan 31 15:46:54 2012 From: jlaska at redhat.com (James Laska) Date: Tue, 31 Jan 2012 10:46:54 -0500 Subject: vnc + rescue In-Reply-To: <20120131163219.1be500a4@amarrosa.pic.es> References: <20120131163219.1be500a4@amarrosa.pic.es> Message-ID: <1328024814.6611.187.camel@flatline.usersys.redhat.com> On Tue, 2012-01-31 at 16:32 +0100, Arnau Bria wrote: > Hi all, > > I'm trying to run rescue + vnc options on same kickstart installation > file. The vnc does not work, it only starts the rescue mode. > > Did anyone ran both options at once? are they mutual exclusive? > > (Rh5 and Rh6) Rescue mode is a text-only utility. Unlike the traditional installer, there is no graphical component. Thanks, James -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From listsarnau at gmail.com Tue Jan 31 16:00:36 2012 From: listsarnau at gmail.com (Arnau Bria) Date: Tue, 31 Jan 2012 17:00:36 +0100 Subject: vnc + rescue In-Reply-To: <1328024814.6611.187.camel@flatline.usersys.redhat.com> References: <20120131163219.1be500a4@amarrosa.pic.es> <1328024814.6611.187.camel@flatline.usersys.redhat.com> Message-ID: <20120131170036.4098bb1a@amarrosa.pic.es> On Tue, 31 Jan 2012 10:46:54 -0500 James Laska wrote: [...] > Rescue mode is a text-only utility. Unlike the traditional installer, > there is no graphical component. Ok :-( > Thanks, > James Cheers, Arnau From Moray.Henderson at ict-software.org Tue Jan 31 17:06:49 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Tue, 31 Jan 2012 17:06:49 +0000 Subject: vnc + rescue In-Reply-To: <20120131170036.4098bb1a@amarrosa.pic.es> References: <20120131163219.1be500a4@amarrosa.pic.es> <1328024814.6611.187.camel@flatline.usersys.redhat.com> <20120131170036.4098bb1a@amarrosa.pic.es> Message-ID: <003b01cce03a$b91ef300$2b5cd900$@Henderson@ict-software.org> > -----Original Message----- > From: Arnau Bria [mailto:listsarnau at gmail.com] > Sent: 31 January 2012 16:01 > > On Tue, 31 Jan 2012 10:46:54 -0500 > James Laska wrote: > > [...] > > Rescue mode is a text-only utility. Unlike the traditional > installer, > > there is no graphical component. > > Ok :-( > > > Thanks, > > James > Cheers, > Arnau If you're able to build a custom initrd file and repackage the install media, you can include dropbear, the busybox ssh daemon. That can give you remote command-line access in rescue mode. Moray. "To err is human; to purr, feline." From hbrown at divms.uiowa.edu Tue Jan 31 17:55:28 2012 From: hbrown at divms.uiowa.edu (Hugh Brown) Date: Tue, 31 Jan 2012 11:55:28 -0600 Subject: kickstart packages In-Reply-To: References: Message-ID: <4F282B10.2050507@divms.uiowa.edu> On 01/28/2012 06:11 PM, Michael Hennebry wrote: > One of the things I would like to do with kickstart is to get > aproximately the same set of packages I have installed now. > I always forget something that I have to install later, > so just using the anaconda-generated kickstart file would > not do the trick. > I've looked at the kickstart file, I've read about its format > and I've looked at package lists from yum and rpm. > The correspondence is not obvious to me. > > Assuming that the kickstart file is correct, how do I add a package to it? > How do I figure out what name to give in the kickstart file? > > I'm pretty sure that I didn't add tex after install, > but look here: > > [root at localhost ~]# yum provides '*/tex' > ... > texlive-2007-56.fc14.i686 : Binaries for the TeX formatting system > Repo : installed > Matched from: > Filename : /usr/bin/tex > > [root at localhost ~]# rpm -q --all | grep tex > texlive-texmf-2007-36.fc14.noarch > texlive-texmf-fonts-2007-36.fc14.noarch > texlive-utils-2007-56.fc14.i686 > tex-preview-11.86-6.fc14.noarch > gettext-0.18.1.1-5.fc14.i686 > texlive-2007-56.fc14.i686 > texlive-texmf-latex-2007-36.fc14.noarch > texlive-texmf-dvips-2007-36.fc14.noarch > texlive-dvips-2007-56.fc14.i686 > texlive-latex-2007-56.fc14.i686 > gettext-libs-0.18.1.1-5.fc14.i686 > libtextcat-2.2-11.fc13.i686 > > [root at localhost ~]# grep tex anaconda-ks.cfg > @text-internet > > > Also, anaconda-ks.cfg was generated by a F14 install. > I'll be installing F16. > How badly will that bite me? > As a brute force method, to get exactly the packages which you currently have installed now, you can do: rpm -qa --qf '%{name}\n' >rpmlist and then insert your rpmlist into your kickstart file. At a higher level, you can run system-config-kickstart which will try and collect all of the information about packages you have installed and then will kick out a kickstart file you can use. In order to get info about which groups are available, what they install, etc. yum grouplist -v # all groups, pipe it through a pager yum groupinfo text-internet # lists default/mandatory/optional packages As to your question of what installed tex, you can use repoquery to get that info. repoquery --groupmember texlive tells me that it is in the authoring-and-publishing group. Using "yum groupinfo authoring-and-publishing" tells me that it is a mandatory package. So if you specify @authoring-and-publishing in your kickstart file, you will get that package. If you don't want it, then add it to your kickstart file and prefix it with a dash/minus sign. With each new rev of the distro, you get to make sure that all of your favorite packages are getting installed and you'll also have a new list of packages that you don't want installed. You can also do a manual install of F16 and select the packages you want and don't want. Then you do an rpm -qa --qf '%{name}\n' |sort >f16list and do the same on the f14 box. Do a diff and see what changed. Some of them will be things like the change from upstart to systemd others will be random packages that you installed on f14 and not on f16. As to editing the kickstart file to add a single package, just insert the name of the package between the %packages and %end flag. I refer to http://fedoraproject.org/wiki/Anaconda/Kickstart rather often when I'm updating kickstart files. Specifically look at the Chapter 3. Package Selection section. HTH, Hugh From brent.clements at gmail.com Tue Jan 31 19:41:50 2012 From: brent.clements at gmail.com (Brent Clements) Date: Tue, 31 Jan 2012 13:41:50 -0600 Subject: How do I disable san/fiber channel connectivity at boot when using the RH/Centos 6 installer Message-ID: How do I disable san/fiber channel connectivity at boot when using the RH/Centos 6 installer? We have a ton of luns that are provisioned to this server and it takes a long time for us to scroll through the disks to find the local disk for the install when we manually provision a system. is there a nosan or nofiberchannel option for the boot options when booting a boot iso? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From sir_june at yahoo.com Tue Jan 31 21:29:28 2012 From: sir_june at yahoo.com (Sir June) Date: Tue, 31 Jan 2012 13:29:28 -0800 (PST) Subject: kickstart dhcp issues In-Reply-To: References: <4F24DC7C.2060607@cpetro.us> <412FAB59D3769A41864DBCDAA98400151465493C@ex2k.bankofamerica.com> <03B7E54A-320E-4E51-ADF7-662437083E51@a51.org> <617EF12B-7DAE-4101-822C-D95E7B161FBA@a51.org> <1328022996.62675.YahooMailNeo@web65702.mail.ac4.yahoo.com> Message-ID: <1328045368.69218.YahooMailNeo@web65701.mail.ac4.yahoo.com> alright. i guess i have another minor issue.? still with DHCP. Our? LAN's DHCP is handled by Microsft 2003 server. :((?? with /21 for DHCP range? (192.168.10.x -> 192.168.17.x) My query is,? can I run a Redhat DHCP on the same LAN segment?? How do i make sure that only my new-server will get IP from Redhat DHCP via PXE and no other clients will get any from Redhat DHCP.? or shall i say,? all other machines will get DHCP from the Windows DHCP , and only the server I want to install Redhat will get IP from the Redhat DHCP. thanks in advance. Sirjune ________________________________ From: "CHU, STEPHEN H" To: Sir June Sent: Tuesday, January 31, 2012 10:22 AM Subject: RE: kickstart dhcp issues Sirjune, ? Try ksdevice=link or ksdevice=bootif. Those worked for me every time. ? Steve ? From:Sir June [mailto:sir_june at yahoo.com] Sent: Tuesday, January 31, 2012 10:17 AM To: Discussion list about Kickstart Subject: Re: kickstart dhcp issues ? I thank you all for the comments, solutions and suggestions. as of yesterday,? I was able to install? RHEL5.5 via kickstart using? linux ks=http://192.168xxx.xxx/redhat/ks.cfg? dhcptimeout=500 although it still asks me as to which ethernet to use, (eth0..eth5). it continues afterwards.? I tried specifying ksdevice=eth0 and noipv6? but the installation wont proceed and keeps on coming back to the ipv4 and ipv6 selections. I will try all the suggestions & options mentioned here. thanks, Sirjune ? ________________________________ From:Angus Clarke To: Discussion list about Kickstart Sent: Monday, January 30, 2012 3:13 PM Subject: Re: kickstart dhcp issues ? Perhaps - I didn't read the Dell solution as specifying MAC addresses is sufficient and already available, at least for my requirements (Ethernet interfaces) All the best ~Angus On 30 January 2012 20:06, Kaj Niemi wrote: I think this is what the dell naming scheme was designed to prevent? :-) ? ? ? Kaj ? On Jan 30, 2012, at 18:36, Angus Clarke wrote: I notice that without specifying the device MAC address in the config files you are concerned with, and then later adding additional NICs on the PCIe bus - results in the PCIe NICs preceding the onboard NICs (eth0 changes to represent the NIC on the lowest PCIe bus.) HP DL380 G7 and RHEL5.2 x86_64 ? _______________________________________________ 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: