Anaconda-devel November 2004

anaconda-devel@lists.stg.fedoraproject.org

32 participants
38 discussions

anaconda hangs after parport (FC2 & FC3)
by Abe Shelton 17 Jan '05

17 Jan '05

Greetings, We have a couple of dual PIII Boxx Technologies boxes here that anaconda consistently hangs on shortly after the check media md5sum menu. We've tried both FC2 or FC3Beta boot media, and using the boot options such as "linux text noprobe" all to no avail. Right before the box locks up (hard, no capslock, ctrl-alt-del, no nothing), anaconda shows: on vt3: *inserted /tmp/parport.ko on vt4: <6>device-mapper: 4.1.0-ioctl (2003-12-10) init ... We've tried assorted SCSI controllers, VGA cards, etc, and every anaconda option we can find but nothing seems to work. (http://rau.homedns.org/twiki/bin/view/Anaconda/AnacondaISOLINUXOptions) Perhaps there is a way to cause anaconda to show more debugging output? Or to have it step through its install instructions one at a time? Any hints or advice would be much appreciated. Thanks! Abe

1 1

python 2.4
by Matthew Miller 06 Dec '04

06 Dec '04

>From the changelog: * Sun Nov 07 2004 Jeremy Katz <katzj(a)redhat.com> - 10.2.0.0-1 - Switch to python 2.4 Does switch mean "now works with", or "now requires"? There's so many other things that look tasty in the changelog that I'm tempted to use some snapshot of the devel version of anaconda for our FC3-derived release. But perhaps I should be disuaded. :) -- Matthew Miller mattdm(a)mattdm.org <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/>

10 31

still curious about "extra" space needed for install
by Robert P. J. Day 30 Nov '04

30 Nov '04

i'm still curious about what it means to say that FC3 installation requires "additional disk space" as described below. ===== The disk space requirements listed below represent the disk space taken up by Fedora Core 3 after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. ===== additional disk space where? and i'm asking about both /Fedora/base/stage2.img, and /var/lib/rpm. thanks. rday

3 3

lochangfd error
by Shen Qian 29 Nov '04

29 Nov '04

Hi, I use a custom-build anaconda10.0.The NFS installation works well, but the cd-rom installation has a fatal error.Just at the end of transmitting stage2.img to harddrive,anaconda raise a fatal exception: File "/usr/lib/anaconda/image.py",line200,in systemMounted isys.lochangefd("/tmp/loop",self.loopbackFile) File "/usr/lib/anaconda/isys.py",line 118,in lochangefd _isys.lochangefd(loop,targ) SystemError:(14,"Bad address") Could anyone tell me the reason? Thanks, Shen

1 0

Creating a virtual image with Anaconda
by Dimitrie O. Paun 29 Nov '04

29 Nov '04

Hi folks, Hot on the heels of Stateless Linux, I decided to give the whole diskless workstation idea a try. In doing so, I realized it would be a good idea if I could create an image that I could later serve via NFS to my diskless clients, and it seemed like anaconda is the answer to all my problems. However, after a cursory look at the documentation and the source, I can't seem to figure it out. What I want from Anaconda is: -- to skip all the questions about formatting and so on that are really applicable to a real image, and just go to the application selection screen. This seems doable via kickstart, right? -- install the selected RPM's into a directory of my choosing. Now this seems to be a perfect fit for anaconda, but it's not at all aparent how to accomplish it. Am I missing something? If not, and the feature is to be implemented, would it be a big deal? If it's not a huge effort, I'd be willing to implement it, with a bit of guidance from the anaconda-gurus. But before I set out on this path, is this a desirable feature for anaconda, or is there another way that I have overlooked? -- Dimi.

4 7

installing on CDless laptop using grub and isolinux
by Robert P. J. Day 29 Nov '04

29 Nov '04

i asked about installing FC3 on a CD-less laptop on the fedora list just a while ago, and i was given the following link: http://www-2.cs.cmu.edu/~colohan/docs/fedora_upgrade.html which looks like it will do just what i want. (the laptop is, in fact, running FC2 at the moment, so i appear to be good to go.) my only question is, that web page talks strictly about doing an upgrade. i would like to totally repartition the drive and use LVM, which is not the way it's set up now. the question is, once i use grub to get the initial kernel and initrd, and i select an NFS install, and i repartition and start the install, is there no further use for all of the isolinux/ stuff i copied onto the hard drive on the laptop? that is, am i safe in assuming that the install process is done with all of the isolinux/ stuff so that the repartitioning won't hurt anything? that *seems* to be the case, but i'd rather know for sure. thanks. rday

5 6

running out of space during FC3 install
by Robert P. J. Day 27 Nov '04

27 Nov '04

earlier today, i tried to do an NFS-based install onto a laptop. everything went well, until the final (/var) filesystem was being formatted, then the install just hung with the formatting progress bar at about 90%. how odd, i thought. i checked one of the other VCs -- intermittent NFS errors -- so i started over, same kind of install. and a hang at *exactly* the same place, in the final part of formatting /var. ok, so that's not coincidence. give up on NFS install, go with the local CDROM and the CDs, partition everything the same way, and this time, i get *just* past the formatting, at which point i get the message that anaconda is transferring the install image to the hard disk. and then i get an "out of space" error, "disk full?" or something to that effect (this is from memory). now, first, i'll assume that the NFS install was actually getting to the same point, i just never saw it, and i never got that error. it only showed up when i did the CDROM-based install. does that make sense? it's sure annoying to now know why the NFS install was failing. but i'm curious -- why would i be running out of space? i partition my setup so that i need a fairly small root filesystem, and i picked 256M for mine. anaconda certainly didn't complain about this. but what i'm not sure about is this section in the release notes: ===== The disk space requirements listed below represent the disk space taken up by Fedora Core 3 after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. ===== "additional disk space is required"? where? in the root filesystem? i could have sworn that *somewhere* i remember reading that the install image is copied into ***RAM***, not onto the hard drive. so what does this have with needing extra space on the hard drive? for no good reason i can think of, i repartitioned and bumped the root filesystem up from 256M to 512M and it worked like a charm. so can someone clarify *exactly* what this required additional space is for? and if it's really necessary to allocate extra space in the root FS, shouldn't anaconda warn the user about insufficient space in the first place? that excerpt from the release notes is really not terribly informative. rday

2 2

Forcing package removal via comps.xml?
by Toralf Lund 25 Nov '04

25 Nov '04

Is there any way I can force specific packages to be removed on upgrade installation, via directives in comps.xml? Essentially, I want the effect of rpm "Obsoletes:", only I'd like pre-built packages to "obsolete" ones not mentioned there, and I'd rather not re-build the rpms if I can avoid it. - Toralf

1 0

RE: pkgorder failure (was: Using old anaconda-runtime to builddistribution?) [bcc][faked-from][heur]
by Peter Sönnergren 25 Nov '04

25 Nov '04

Have you set PYTHONPATH=/usr/lib/anaconda ? //Peter -----Original Message----- From: Toralf Lund [mailto:toralf@procaptura.com] Sent: den 22 november 2004 14:19 To: anaconda-devel-list(a)redhat.com Subject: pkgorder failure (was: Using old anaconda-runtime to builddistribution?) [bcc][faked-from][heur] Toralf Lund wrote: > I just tried building a customised version of the fedora core 3 > distribution. Seemed to work all right, but (networked) upgrade > installation failed when the actual package update was about to start, > without any real error messages (just "installation failure".) > > The thing is, I used a fairly old anaconda-runtime, version 9.0-4, > because I don't actually have a Fedora Core 3 system yet; I thought I > might switch directly to the customised distro... Is this something > that's known not to work? I mean, have the image formats changed or > anything? Maybe the problem is related to "--fileorder" issues mentioned in other posts. I've always omitted that option, mainly because the "pkgorder" utility has never really worked for me; it fails like this: /usr/lib/anaconda-runtime/pkgorder fc3/ i386 > fc3/Fedora/base/pkgorder Traceback (most recent call last): File "/usr/lib/anaconda-runtime/pkgorder", line 10, in ? import whiteout ImportError: No module named whiteout make: *** [fc3/Fedora/base/pkgorder] Error 1 Help, anyone? - T _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list

2 1

core 3: package signatures required?
by Matthew Kent 23 Nov '04

23 Nov '04

Not sure if this belongs here or the kickstart list but I'm trying to figure out whats crashing the installer when I try kickstarting with some custom rpms. I've narrowed it down to not signing my packages. If I recompile with a proper signature, anaconda installs them fine. If I don't, it just segfaults and everything dies. Are package signatures now required for all rpms? I couldn't find any mention in the release notes or anaconda ChangeLog, and these same rpms/specfiles worked in my Core 2 kickstart. On a related note I'm finding the lack of documentation really time consuming. I just discovered a few more kickstart options by downloading the anaconda src rpm, installing it, extracting the tarball, and reading the ChangeLog. Which doesn't strike me as the most efficient way to get at this information. Has anyone considered writing an updated customization guide? Or do RHEL users get access to proper documentation I'm just not seeing... -- Matthew Kent \ SA \ bravenet.com

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel November 2004