From beyonddc.storage at gmail.com Thu Sep 1 19:18:34 2011 From: beyonddc.storage at gmail.com (Chun Tat David Chu) Date: Thu, 1 Sep 2011 15:18:34 -0400 Subject: Inducing package checksum failure in Anaconda Message-ID: Hi All, I am currently using Anaconda from RHEL5.2 and trying to induce a checksum failure on a RPM. What I did is in an existing YUM repo, I manually modify a RPM. My assumption is by modifying a RPM, the sha1 checksum value specified in the primary.xml.gz in the repodata directory will be differ from the modified RPM. When I said modifying a RPM, I mean rebuild a RPM and replace the one from the repo with the new one. My expectation is to see an error message from Anaconda indicating unexpected checksum value however that is not the case, the package get installed successfully. It appears to me that the repodata is not being use by Anaconda for integrity checking. Can someone please confirm my finding? Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From tegner at renget.se Fri Sep 2 08:32:27 2011 From: tegner at renget.se (Jon Tegner) Date: Fri, 02 Sep 2011 10:32:27 +0200 Subject: nfs mount under %post Message-ID: <20110902083227.201FDCBBA515A@bmail04.one.com> Hi All, for a long time I have been using the line "mount -o nolock,rw 192.168.0.198:/tftpboot /mnt/nfs_tftpboot" under RHEL 5, however, when trying to used under RHEL 6 I fail. Has something been changed here? Thanks, /jon -------------- next part -------------- An HTML attachment was scrubbed... URL: From hbrown at divms.uiowa.edu Fri Sep 2 12:32:01 2011 From: hbrown at divms.uiowa.edu (Hugh Brown) Date: Fri, 02 Sep 2011 07:32:01 -0500 Subject: nfs mount under %post In-Reply-To: <20110902083227.201FDCBBA515A@bmail04.one.com> References: <20110902083227.201FDCBBA515A@bmail04.one.com> Message-ID: <4E60CCC1.7070708@divms.uiowa.edu> On 09/02/2011 03:32 AM, Jon Tegner wrote: > Hi All, > > > > for a long time I have been using the line > > > > > "mount -o nolock,rw 192.168.0.198:/tftpboot /mnt/nfs_tftpboot" > > > > > under RHEL 5, however, when trying to used under RHEL 6 I fail. > > > > > Has something been changed here? > > > > > Thanks, > > > > > /jon I can report that I'm successfully doing: mkdir -pv $NFS_DIR mount -v -t nfs -o nolock,ro $SERVER:$SCRIPT_PATH $NFS_DIR via kickstart for RHEL 6.1 Hugh From niall at identitynetworks.com Mon Sep 5 09:18:01 2011 From: niall at identitynetworks.com (Niall Mark El-Assaad) Date: Mon, 5 Sep 2011 10:18:01 +0100 Subject: Is it possible to install from a hard disk directory? Message-ID: With the latest versions of syslinux it is now possible to build the install ISO so that it can be written to a USB flash. I've got it up and running and the image gets mounted as a hard disk at /tmp/hdimage However I can't work out how to tell anaconda to install from /tmp/hdimage/RPMS The only option I can see is to provide the path to a directory containing the ISO images. Is there some option to tell it to use a mounted filesystem? thanks, From forltran at yahoo.com Sat Sep 10 16:57:20 2011 From: forltran at yahoo.com (Lambert Tran) Date: Sat, 10 Sep 2011 09:57:20 -0700 (PDT) Subject: No subject Message-ID: <1315673840.95008.YahooMailMobile@web180108.mail.gq1.yahoo.com> http://hla-la.com/invitation.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From forltran at yahoo.com Sat Sep 10 22:35:08 2011 From: forltran at yahoo.com (Lambert Tran) Date: Sat, 10 Sep 2011 15:35:08 -0700 (PDT) Subject: No subject Message-ID: <1315694108.21130.YahooMailMobile@web180114.mail.gq1.yahoo.com> http://bemnutrir.com/invitation.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From tvrajeshkumar at gmail.com Fri Sep 16 15:13:57 2011 From: tvrajeshkumar at gmail.com (Rajesh Kumar T V) Date: Fri, 16 Sep 2011 11:13:57 -0400 Subject: kickstart problem in stage2 Message-ID: Hi all, I am having problem while using anaconda installer.for my custom build Following are the images used : a) Fedora-12-ppc-DVD.iso b) kernel-2.6.32.26-175.fc12.src.rpm I am able to build the install.img successfully and using nfs mount for getting the images. I am able to mount successfully. My output in the shell prompt for the mount command bash-4.0# mount rootfs on / type rootfs (rw,relatime) /proc on /proc type proc (rw,relatime) /dev on /dev type tmpfs (rw,relatime) /dev/pts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000) /sys on /sys type sysfs (rw,relatime) none on /tmp type tmpfs (rw,relatime) 192.168.66.2:/opt/ngin/rpmBuild/images/images on /mnt/stage2 type nfs4 (ro,noatime,vers=4,rsize=8192,wsize) bash-4.0# In the kickstart text screen after I specify the server name and path it fails giving the following error: 12:20:26 INFO : starting STEP_STAGE2 12:21:33 ERROR : failed to mount loopback device /dev/loop0 on /mnt/runtime as /mnt/stage2//install.img I am using the following patch for sqfs, after extracting a) unsquashfs -d "$D/sqfs" "$D/iso.dir/images/install.img" b) patch -d "$D/sqfs" -p1 < "$D/sqfs.patch" c) mksquashfs "$D/sqfs" install.img -all-root --- a/usr/lib/anaconda/platform.py +++ b/usr/lib/anaconda/platform.py @@ -531,7 +531,7 @@ elif ppcMachine == "PS3": return PS3(anaconda) else: - raise SystemError, "Unsupported PPC machine type" + return IPSeriesPPC(anaconda) elif iutil.isS390(): return S390(anaconda) elif iutil.isSparc(): --- a/usr/lib/anaconda/users.py +++ b/usr/lib/anaconda/users.py @@ -198,7 +198,11 @@ if isCrypted: self.admin.setpassUser(rootUser, password, True) else: - self.admin.setpassUser(rootUser, cryptPassword(password, algo=algo), True) + password = cryptPassword(password, algo=algo) + if password == None: + print "Warning - Root password not set!" + else: + self.admin.setpassUser(rootUser, cryptPassword(password, algo=algo)) if lock: self.admin.lockUser(rootUser) >From the discussions in the internet, I understand some patch is required. I am not sure which patch will help me fix this. Please let me know how to cross this stage. Thanks, Rajesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From jreg2k at gmail.com Wed Sep 21 11:14:11 2011 From: jreg2k at gmail.com (James James) Date: Wed, 21 Sep 2011 13:14:11 +0200 Subject: Backup before kickstart Message-ID: Hi, I am very happy to use kickstart to install my computers but I was wondering if there is a way to do some lvm partition backup before launch kickstart. The idea is to create, from the kickstart file, another partition and do a rsync from a partition to the new one. Once the rsync is done, install the os and in the post-install script restore the data. I don't know if it is possible. :-) Regards. James -------------- next part -------------- An HTML attachment was scrubbed... URL: From despite at gmail.com Wed Sep 21 23:18:44 2011 From: despite at gmail.com (Bradley Peterson) Date: Wed, 21 Sep 2011 18:18:44 -0500 Subject: raid --useexisting isn't working in F14 Message-ID: I'm trying to kickstart Fedora 14 onto an existing system. In older versions of Fedora, I could just do raid --useexisting. But, now I'm getting this error, before anaconda even fully loads: Running anaconda 14.22, the Fedora system installer - please wait. 17:46:04 The following error was found while parsing the kickstart configuration file: The following problem occurred on line 39 of the kickstart file: Partitions required for raid install exited abnormally [1/1] The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete. The raid lines of the kickstart look like this: raid /boot --fstype=ext4 --level=1 --device=md0 --useexisting raid / --fstype=ext4 --level=5 --device=md1 --useexisting raid /usr --fstype=ext4 --level=5 --device=md2 --useexisting raid /var --fstype=ext4 --level=5 --device=md3 --useexisting raid /data --fstype=ext4 --level=5 --device=md4 --useexisting --noformat I tried adding part commands for each partition, and listing them on the raid lines, and it got a bit further, but then errored with something like "specified raid device which doesn't exist: md0" Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.neuberger at gmail.com Thu Sep 22 21:27:12 2011 From: daniel.neuberger at gmail.com (Daniel Neuberger) Date: Thu, 22 Sep 2011 17:27:12 -0400 Subject: Multiple CDs for install Message-ID: Anyone know how to use multiple CDs for a KS install? We're on RHEL 5.5 and the best documentation I've found is http://fedoraproject.org/wiki/Anaconda/Customization, which isn't that helpful. I'm having trouble figuring out how to setup my repositories and run the needed commands correctly. Some better documentation would be very helpful. Thanks for the help! - Daniel From hbrown at divms.uiowa.edu Fri Sep 23 13:17:09 2011 From: hbrown at divms.uiowa.edu (Hugh Brown) Date: Fri, 23 Sep 2011 08:17:09 -0500 Subject: Multiple CDs for install In-Reply-To: References: Message-ID: <4E7C86D5.9010604@divms.uiowa.edu> On 09/22/2011 04:27 PM, Daniel Neuberger wrote: > Anyone know how to use multiple CDs for a KS install? We're on RHEL 5.5 > and the best documentation I've found is > http://fedoraproject.org/wiki/Anaconda/Customization, which isn't that > helpful. I'm having trouble figuring out how to setup my repositories > and run the needed commands correctly. Some better documentation would > be very helpful. > > Thanks for the help! > > - Daniel > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list If you are just downloading the RHEL cd iso images, then you can put them all in a directory on an nfs server and then set nfs --server --dir in your kickstart file. Anaconda finds them and switches from one iso image to the next as it progresses. However, once the DVDs were made available, I switched to using those isos instead. Hugh From daniel.neuberger at gmail.com Fri Sep 23 13:47:40 2011 From: daniel.neuberger at gmail.com (Daniel Neuberger) Date: Fri, 23 Sep 2011 09:47:40 -0400 Subject: Multiple CDs for install In-Reply-To: <4E7C86D5.9010604@divms.uiowa.edu> References: <4E7C86D5.9010604@divms.uiowa.edu> Message-ID: On 09/23/2011 09:17 AM, Hugh Brown wrote: > If you are just downloading the RHEL cd iso images, then you can put > them all in a directory on an nfs server and then set > > nfs --server --dir > > in your kickstart file. Anaconda finds them and switches from one iso > image to the next as it progresses. > > However, once the DVDs were made available, I switched to using those > isos instead. Thanks, to clarify, we have our build, but the resulting folder is larger than what fits on one DVD. It works fine using the http method or even using the ISO to install a VM, but we need to be able to install from physical DVDs as well. Does anyone know of a good reference showing how to split the install across multiple DVDs? Thanks. - Daniel From Moray.Henderson at ict-software.org Tue Sep 27 14:05:44 2011 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Tue, 27 Sep 2011 15:05:44 +0100 Subject: Multiple CDs for install In-Reply-To: References: <4E7C86D5.9010604@divms.uiowa.edu> Message-ID: <001201cc7d1e$8e14f210$aa3ed630$@Henderson@ict-software.org> > From: Daniel Neuberger [mailto:daniel.neuberger at gmail.com] > Sent: 23 September 2011 14:48 > On 09/23/2011 09:17 AM, Hugh Brown wrote: > > If you are just downloading the RHEL cd iso images, then you can put > > them all in a directory on an nfs server and then set > > > > nfs --server --dir isos> > > > > in your kickstart file. Anaconda finds them and switches from one iso > > image to the next as it progresses. > > > > However, once the DVDs were made available, I switched to using those > > isos instead. > > Thanks, to clarify, we have our build, but the resulting folder is > larger than what fits on one DVD. It works fine using the http method > or even using the ISO to install a VM, but we need to be able to > install > from physical DVDs as well. Does anyone know of a good reference > showing how to split the install across multiple DVDs? The command to do that is splittree.py, part of the anaconda-runtime package and located in /usr/lib/anaconda-runtime. It does provide a brief usage message and, as a python script, you can read the list of command options from the script itself. It is normally run after buildinstall when creating new install CDs. The more modern way of doing it is to use one of the release-building packages. I can never remember the difference between Pungi and Revisor, but you can look them up on the Fedora wiki (or check the Kickstart list archives - they are mentioned here quite regularly). Moray. "To err is human; to purr, feline."