Anaconda-devel February 2007

anaconda-devel@lists.fedoraproject.org

24 participants
30 discussions

RE: PATCH: Partition auto-detection and HD exploded tree installation
by Uday Prakash 06 Feb '07

06 Feb '07

I forgot to include the related pykickstart patch. It can be downloaded from: http://www.abodiosoftware.com/patches/pykickstart-0.93_abodio.patch This patch removes the exception when neither biospart nor partition are specified in the kickstart file. Thanks, Uday. > -----Original Message----- > From: anaconda-devel-list-bounces(a)redhat.com [mailto:anaconda-devel- > list-bounces(a)redhat.com] On Behalf Of Uday Prakash > Sent: Monday, February 05, 2007 6:23 PM > To: anaconda-devel-list(a)redhat.com > Subject: Re: PATCH: Partition auto-detection and HD exploded tree > installation > > All, > > Following up on my previous email, I have implemented a patch that > auto-detects the source and kickstart devices. The file can be > downloaded > from > http://www.abodiosoftware.com/patches/anaconda- > 11.2.0.19_abodio_autodetect.p > atch and is for Anaconda Version #11.2.0.19. Please consider this patch > for > inclusion in the anaconda sources. > > As a reminder, this patch allows the kickstart and method options to be > specified at the command line as follows (note the empty partition > section > between the two colons): > > ks=hd::/path/to/ks.cfg, and > method=hd::/path/to/install/files > > And, within the kickstart file, a hard drive install can be specified > as > follows (note the lack of a --partition directive): > > harddrive --dir=/path/to/install/files > > This patch is modified slightly from the one I had initially provided. > The > original patch selected the first partition encountered with the > kickstart/install files on it. This (new) patch gives the user more > control > and: > > * if the number of partitions with the file/directory is 0, do > nothing, or > * if the number of partitions with the file/directory is 1, use that > one, > or > * else pop up the dialog box and ask the user which partition to use. > > Thanks much, > Uday. > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/anaconda-devel-list

1 0

Re: PATCH: Partition auto-detection and HD exploded tree installation
by Uday Prakash 05 Feb '07

05 Feb '07

The link to the patch got broken into two lines. Hopefully, it works this time :). http://www.abodiosoftware.com/patches/anaconda-11.2.0.19_abodio_autodetect.… -Uday > > > >-----Original Message----- >From: anaconda-devel-list-bounces(a)redhat.com >[mailto:anaconda-devel-list-bounces@redhat.com] On Behalf Of Uday Prakash >Sent: Monday, February 05, 2007 6:23 PM >To: anaconda-devel-list(a)redhat.com >Subject: Re: PATCH: Partition auto-detection and HD exploded tree >installation > >All, > >Following up on my previous email, I have implemented a patch that >auto-detects the source and kickstart devices. The file can be downloaded >from >http://www.abodiosoftware.com/patches/anaconda-11.2.0.19_abodio_autodetect.p >atch and is for Anaconda Version #11.2.0.19. Please consider this patch for >inclusion in the anaconda sources. > >As a reminder, this patch allows the kickstart and method options to be >specified at the command line as follows (note the empty partition section >between the two colons): > > ks=hd::/path/to/ks.cfg, and > method=hd::/path/to/install/files > >And, within the kickstart file, a hard drive install can be specified as >follows (note the lack of a --partition directive): > > harddrive --dir=/path/to/install/files > >This patch is modified slightly from the one I had initially provided. The >original patch selected the first partition encountered with the >kickstart/install files on it. This (new) patch gives the user more control >and: > > * if the number of partitions with the file/directory is 0, do nothing, or > * if the number of partitions with the file/directory is 1, use that one, >or > * else pop up the dialog box and ask the user which partition to use. > >Thanks much, >Uday. > >_______________________________________________ >Anaconda-devel-list mailing list >Anaconda-devel-list(a)redhat.com >https://www.redhat.com/mailman/listinfo/anaconda-devel-list > >

1 0

Re: PATCH: Partition auto-detection and HD exploded tree installation
by Uday Prakash 05 Feb '07

05 Feb '07

All, Following up on my previous email, I have implemented a patch that auto-detects the source and kickstart devices. The file can be downloaded from http://www.abodiosoftware.com/patches/anaconda-11.2.0.19_abodio_autodetect.p atch and is for Anaconda Version #11.2.0.19. Please consider this patch for inclusion in the anaconda sources. As a reminder, this patch allows the kickstart and method options to be specified at the command line as follows (note the empty partition section between the two colons): ks=hd::/path/to/ks.cfg, and method=hd::/path/to/install/files And, within the kickstart file, a hard drive install can be specified as follows (note the lack of a --partition directive): harddrive --dir=/path/to/install/files This patch is modified slightly from the one I had initially provided. The original patch selected the first partition encountered with the kickstart/install files on it. This (new) patch gives the user more control and: * if the number of partitions with the file/directory is 0, do nothing, or * if the number of partitions with the file/directory is 1, use that one, or * else pop up the dialog box and ask the user which partition to use. Thanks much, Uday.

1 0

DNS queries using source port 32768
by Jack Neely 05 Feb '07

05 Feb '07

Folks, I've had some problems installing RHEL on a specific VLAN at work. The problem is that the loader does DNS requests but the router was dropping the DNS replies therefore the loader couldn't resolve its IP and the URL where the kickstart lived. Turns out that UDP packets heading toward the servers on this VLAN with destination port of 32768 are dropped by an ACL put in place to meet some security requirements of an out sourced credit card charging company. The security policy states some concerns that this is a port that solaris commonly uses for the NFS statd RPC server. The security folks here expressed concern that the loader wasn't randomizing the DNS port as normal resolvers do. I know the environment for the loader is pretty restrictive. Is it possible to choose a more random port and/or incriment the port used if DNS queries are failing? Jack -- Jack Neely <jjneely(a)ncsu.edu> Campus Linux Services Project Lead Information Technology Division, NC State University GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89

2 2

Modify Anaconda Fedora Extras
by Vincent Fonteneau 05 Feb '07

05 Feb '07

Hi, I'm looking in Anaconda sources to find a way to modify Fedora Extras Repository. I mean I would like to replace "Fedora Extras" with "My Repository" directly without the need to add it during the FC6 installation (adding repositorires). Is it possible ? Does anybody else have done it ? Thanks. Vincent

2 2

Re: pungi ignores a lot of RPMs when building CD image
by Jeroen Janssen 03 Feb '07

03 Feb '07

Hi, On 2/1/07, Jesse Keating <jkeating(a)redhat.com> wrote: > It would appear that pkgorder doesn't know about the other groups you have in > your comps file perhaps. pkgorder is just a python script, I'd poke at it > and see how it figures out the order, and see if perhaps you need to change > your group names in comps. After looking at pkgorder it seems it has a hardcoded list of groups it adds for resolving the order. Maybe a 'fallback' to add any remaining groups that were not selected yet would be a good improvement of pkgorder? (and a solution to this problem). I'll see if I can come-up with a patch to pkgorder that does this. Best regards, Jeroen Janssen

3 5

[PATCH] Add --exclude option to kickstart repo command
by Ed Swierk 02 Feb '07

02 Feb '07

yum allows configuring each repository to exclude certain packages from view, which is handy to ensure that packages in a local repository take precedence over whatever happens to be in the fedora-updates repository. These patches are my attempt to add an --exclude option to the kickstart repo command (although I'm not sure whether this is the correct venue for pykickstart changes). --Ed

1 0

Re: pungi ignores a lot of RPMs when building CD image
by Remy Bohmer 02 Feb '07

02 Feb '07

Hello All, I got it! but, it is very strange... ;-)) I debugged the pkgorder script and found the following: * At the routine 'processTransaction()' the complete lists of dependencies is available, then it calls the routine printMatchingPkgs() to print the packages to standard, after it has checked that they are available. * The filemask that is passed to printMatchingPkgs() through 'fpattern', is build up as follows: <os-dir>/Product/package*. Where Product starts with a capital, but my product_name in the pungi configuration does NOT star with a capital. So, the product-dir in the os-dir does not start with a capital. So, no dependency files can be found, leaving a os-disc1 with just a few files in it... I searched through the entire tree several times, but nowhere I have listed the productname with a capital, so this capital must be introduced by the tooling itself ! (Fedora also starts with a capital... Redhat also, and probably other distros using anaconda also?) So, to be able to build a customised CD, you must use a product_name in Pungi that starts with a capital. I have changed this in my build environment and now it works! I believe the problem is introduced by collecting the dependencies in the routine addGroups() -> ds.ResolveDeps() in the pkgorder script. For me it is going to deep in the external tooling, which I do not fully understand yet how they work. Maybe someone else recognises this phenomenon and can pick it up from here? Or if someone can give me some tips on this, I can look further into it... Kind Regards, Remy Bohmer 2007/2/2, Remy Bohmer <mythtv.bohmer(a)gmail.com>: > Hello All, > > I renamed all my groups to 'core', 'base', 'base-x' and > 'development-tools', and it does not make any difference... So, I > believe it is not only related to the group naming in the comps > file... I am going to debug this some more today. > > If anyone has a good idea about this, please let me know. > > > Kind Regards, > > Remy > > 2007/2/1, Jesse Keating <jkeating(a)redhat.com>: > > On Thursday 01 February 2007 05:40, Remy Bohmer wrote: > > > Attached are the results of this command: > > > /usr/lib/anaconda-runtime/pkgorder > > > /home/me/cdbuildtree/results/myrelease/i386/os i386 myproduct > > > > > > I replaced 'myproduct' with 'Fedora'. No differences. > > > The produced list is exactly like the list of RPM's in my os-disc1- > > > directory. Thus, much too short... > > > > > > Does this give you some new ideas? > > > > It would appear that pkgorder doesn't know about the other groups you have in > > your comps file perhaps. pkgorder is just a python script, I'd poke at it > > and see how it figures out the order, and see if perhaps you need to change > > your group names in comps. > > > > -- > > Jesse Keating > > Release Engineer: Fedora > > > > >

1 0

FC6 and iw/netconfig_dialog.py
by Vincent Fonteneau 01 Feb '07

01 Feb '07

Hi, I'm trying to install the FC6 distribution and i've encoutered some problems vith adding new repository. In fact I' ve configured the network during installation and when trying to add other repository installation I'm getting this error: Tracebakc (most recent call first) File "/usr/lib/anaconda/iw/netconfig_dialog.py", line 69, in _netdevChanged if netdev.get("ipaddr"): self.xml.get_widget("ipv4AddressEntry").set_text(netdev.get("ipaddr")) AttributeError: 'NoneType' object has no attribute 'set_text' Is it normal ? Then if i'm trying to re-install the FC6 using dhcp and then adding new repository and then using again dhcp network configureation, it seems to work. Is there a patch or some coorections for that, b'cause i would like to add repository without using dhcp during network installation ? Thank for help Vincent

2 1

FC6 and iw/netconfig_dialog.py
by Vincent Fonteneau 01 Feb '07

01 Feb '07

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel February 2007