Anaconda-devel March 2007

anaconda-devel@lists.stg.fedoraproject.org

32 participants
39 discussions

Community ks.cfg directory proposal
by Greg Morgan 09 Apr '07

09 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Would a community kick start directory/repository be possible? The idea is that a body of kick start scripts would be developed by the community. So, if a squid server is needed, say, the ksrepo/squidserver/ks.cfg file could be used to implement such a system. Advantages: 1.) A repository of system patterns could be developed and maintained. 2.) The scripts may be helpful in testing future fedora releases. 3.) Example, snippets of ks.cfg code would be available to new kick start users. 4.) Users could rebuild the CD set with additional files that require a separate download. a.) A place for %pre files would be on CD1. b.) A place for %post files would be on the last CD in the set. It would be great if these ks files were on the first CD for easy boot time access, if there is not too great of a size impact. It would be great if a person could override the defaults in a sample script with an "include" file placed in a special directory on, say, a USB key drive, local hard drive, etc. The defaults to be overridden may include things like a 192 non-routing IP address, etc. This would allow some scripts to be used as is without any script or CD rewriting. Regards, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGCuNCxyxe5L6mr7IRAlk6AJ9oJZRPMmb7wJYwOV/ymfjy9C2VPgCeOvFr WcfmexevEJzCKY2e2fgCWEU= =z/De -----END PGP SIGNATURE-----

8 10

Load kickstart, not found?
by xxxxxx xxxxx 31 Mar '07

31 Mar '07

Hi all, Yet another question. I have a custom distro CD, with various kickstarts: Here's an example layout: A. System type A: - RAID5 - RAID1 - RAID0 - NO RAID (1 disk) B. System type B: - RAID5 - RAID1 - RAID0 - NO RAID (1 disk) And so on.. Now, I have my kickstarts setup like this: cdrom:/ks/system-a/raid1.cfg etc etc However, anaconda ALWAYS asks for "where's your kickstart". If I hit enter, it seems to take it anyway. But that question is annoying, as it should be automated. ALT+F3 mode gives a message like "cdrom not found". Which is rather weird, especially since it DOES load after I hit enter to re-confirm... Any idea's? Thanks!

1 0

Force certain arch mode?
by xxxxxx xxxxx 31 Mar '07

31 Mar '07

Hi all, I have a question, a little different from James Pearson's one... but also regarding arch's. Situation: I have a custom distro which I use to install on systems. Some systems are i586 (forced), i686 (forced) and others are ix86_64. Now... The i586 and i686 systems are special systems. They do not have CDROM drives. So I install these in normal workstations. These workstations are 64bit ones. Now, I want to make a CD with all arch RPMs: i586, i686 and ix86_64. There are 3 installer options in my menu: A. Install on local system, use local arch (so whichever, i586, i686, 64b... Using the "auto determine" method of anaconda) B. Install on sys586 C. Install on sys686 What I want to do is that when I use a 64b installer workstation but pick option B or C, it FORCES anaconda to install either i586/686 RPMs instead of the local system's arch, ix86_64. Is there a way to do this? E.g. by passing on values to isolinux.cfg? Thanks!!

1 0

patch for 206479.
by Joel Andres Granados 29 Mar '07

29 Mar '07

Hi List: I found this one as should be resolved for FC7. I think the patch makes it happen. tested it, and everything seems to be fine. The diff is attached. It basically fixes the lack of a acceleration key for the logical volume list in the "Make LVM volume group" window. hope it helps. I have also posted my comments on the bug. regards --- lvm_dialog_gui.py-11.2.0.40 2007-03-29 17:35:12.000000000 +0200 +++ lvm_dialog_gui.py 2007-03-29 17:34:55.000000000 +0200 @@ -1116,7 +1116,8 @@ # pack all logical volumne stuff in a frame lvtable.set_border_width(12) l = gtk.Label() - l.set_markup("<b>%s</b>" %(_("Logical Volumes"),)) + l.set_text_with_mnemonic("_Logical Volumes") + l.set_mnemonic_widget(self.logvollist) frame = gtk.Frame() frame.set_label_widget(l) frame.add(lvtable)

1 0

Wrapping a dist with a boot/kickstart disc.
by Johnson, Richard 29 Mar '07

29 Mar '07

Hi folks- How does one generate a boot disk (CD) wrapping a distro? The constraint is that the original distro disk(s) remain unmodified (fwiw: a RHEL3 variant) The minimal boot disk supplies the installer kernel, splash screens, and a kickstart. My plan is to pull the installer from the distro, but not any of the RPMS. My first attempt booted; asked for the distro CD; and promptly refused to recognize it. Since this is my first attempt with anaconda I'm full of questions. To start: Do I still need a .discinfo if no RPMS come from the boot disk? - If so, must it match the distro? How about a .buildstamp? Do I need a <distro>/base directory providing the anaconda ramdisks? Is there a cookbook for this sort of operation? BTW-does http://rau.homedns.org/twiki/bin/view/Anaconda/ <http://rau.homedns.org/twiki/bin/view/Anaconda/PreparingTheBuildEnviron ment> have a new home? Thx, --rich

1 0

Installing both x86_64 and i386 RPMS on a x86_64 system
by James Pearson 29 Mar '07

29 Mar '07

I have my own internal customised installation tree for CentOS 4 that is used for installs over NFS - I've added extra RPMS to my x86_64 distro and updated comps.xml and re-generated the hdlist files. This works fine in most cases - except when I have both x86_64 and i386 versions of the same RPM - only the x86_64 package gets installed (or if there is only an i386 RPM, then this gets installed OK). I know this works fine for x86_64/i386 RPMS that are part of the default distro, so I'm obviously missing something somewhere ... Anyone know how I make sure both x86_64 and i386 RPMS get installed? Thanks James Pearson

2 2

bug 150670. How to default partition.
by Joel Andres Granados 29 Mar '07

29 Mar '07

Hi All: Found that this issue was not resolved yet for fc7. Personally I would leave the default as it is (100MB->/boot,XXXMB->swap and the resto for /) but the bug discussion does have some details that should be avoided (The issue with the newbie realizing that it would be better to separate the home and OS way after he has finished the installation.) To suggest a solution I would do something like (100MB->boot--- XXXMB->swap---10GB->/ --- the rest for /home :) but thats just me.... I tested it in kickstart and gui installs, everything seems to be fine. So I think its sensible to close the bugs. The diff: diff -ubB anaconda-11.2.0.40/installclass.py anaconda-11.2.0.40-JG/installclass.py --- anaconda-11.2.0.40/installclass.py 2007-03-08 23:03:32.000000000 +0100 +++ anaconda-11.2.0.40-JG/installclass.py 2007-03-28 17:16:53.000000000 +0200 @@ -421,7 +421,7 @@ def setDefaultPartitioning(self, partitions, clear = CLEARPART_TYPE_LINUX, doClear = 1, useLVM = True): - autorequests = [ ("/", None, 1024, None, 1, 1, 1) ] + autorequests = [ ("/", None, 1024, 10240, 1, 1, 1) ] bootreq = getAutopartitionBoot() if bootreq: @@ -429,6 +429,7 @@ (minswap, maxswap) = iutil.swapSuggestion() autorequests.append((None, "swap", minswap, maxswap, 1, 1, 1)) + autorequests.append(("/home", None, 1024, None,1,1,1 )) if doClear: partitions.autoClearPartType = clear

3 3

too much partition clearing
by Chris Lumens 28 Mar '07

28 Mar '07

For reference: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232936 We're just running the partition clearing code too often. Every time through openDevices, we are clearing the disks out. This happens even after partitions have been created. And since it's kind of hard to make physical volumes or RAID members on partitions that don't exist, we explode. One fix could be the addition of some sort of flag that gets set the first time we clear partitions, and then is checked every time. Yuck. Also, openDevices is kind of a mess and needs to be doing less stuff on each of the many times it's called. It especially doesn't need to do something destructive like clearing out the partitions every time. I've moved the clearpart stuff out into its own method and call it from turnOnFilesystems and when we do the early swap stuff. I know this is really subtle code so I may have messed something up. However, basic tests I've performed here today seem okay so far. The patch is attached. Comments welcome. - Chris

2 2

Patch. bug 186439
by Joel Andres Granados 27 Mar '07

27 Mar '07

Hi All: Temporary patch for 186439. The idea is not to crash and to give the user a nice message to change the name of his lv or vg. The message is thrown before kickstart creates the LogicalVolumeRequestSpec of VolumeGroupRequestSpec objects. Another possibility is to change the '-' character to another acceptable character. If I had to choose one from the alphabet it would be 't'. No particular reazon, just like the 't' (diff2). I'll see if fixing it is possible Regards --- ../FC-D/kickstart.py 2007-03-08 19:43:45.000000000 +0100 +++ kickstart.py 2007-03-16 19:00:50.000000000 +0100 @@ -257,6 +257,9 @@ elif (lvd.percent <= 0 or lvd.percent > 100) and not lvd.preexist: raise KickstartValueError, formatErrorMsg(self.lineno, msg="Percentage must be between 0 and 100") + if "-" in lvd.name: + raise KickstartValueError, formatErrorMsg(self.lineno, msg="The '-' character must not be used in logical volume names.") + request = partRequests.LogicalVolumeRequestSpec(filesystem, format = lvd.format, mountpoint = lvd.mountpoint, @@ -605,6 +608,9 @@ if vgd.pesize not in lvm.getPossiblePhysicalExtents(floor=1024): raise KickstartValueError, formatErrorMsg(self.lineno, msg="Volume group specified invalid pesize") + if "-" in vgd.vgname: + raise KickstartValueError, formatErrorMsg(self.lineno, msg="The '-' character must not be used in volume group names.") + # get a sort of hackish id uniqueID = self.handler.ksID self.handler.ksVGMapping[vgd.vgname] = uniqueID --- ../FC-D/kickstart.py 2007-03-08 19:43:45.000000000 +0100 +++ kickstart.py 2007-03-16 19:07:40.000000000 +0100 @@ -257,6 +257,11 @@ elif (lvd.percent <= 0 or lvd.percent > 100) and not lvd.preexist: raise KickstartValueError, formatErrorMsg(self.lineno, msg="Percentage must be between 0 and 100") + if "-" in lvd.name: + #We can also change it and not fail. + lvd.name.replace("-","t") + + request = partRequests.LogicalVolumeRequestSpec(filesystem, format = lvd.format, mountpoint = lvd.mountpoint, @@ -610,6 +615,10 @@ self.handler.ksVGMapping[vgd.vgname] = uniqueID self.handler.ksID += 1 + if "-" in vgd.vgname: + #We can also change it and not fail. + vgd.vgname.replace("-","t") + request = partRequests.VolumeGroupRequestSpec(vgname = vgd.vgname, physvols = pvs, preexist = vgd.preexist,

1 2

Bug 213519 (new)????
by Joel Andres Granados 27 Mar '07

27 Mar '07

Was browsing the anaconda bugs and came across 213519. seems the person who posted it is happy and the issue appears to be resolved. IMO status needs to be changed to CLOSED or NEEDINFO (just to be sure that the guy is happy) Regards

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel March 2007