Anaconda-devel September 2008

anaconda-devel@lists.stg.fedoraproject.org

33 participants
41 discussions

[PATCH] removal of libdhcp
by David Cantrell 21 Dec '08

21 Dec '08

No patch attached because it's quite large. I apologize for the length, but considering this replaces a library and introduces a new struct it meant a new file and changing calls everywhere. http://dcantrel.fedorapeople.org/anaconda/iface/ iface.h - Header file explaining the iface API. iface_t structure replacing pumpNetIntf and networkDeviceConfig, and all of the functions. iface.patch - The changes, it's about 90% complete at this point. *.txt - Explanations and notes. This patch removes anaconda's use of libdhcp, which also means removing libdhcp4client and libdhcp6client. For static network configuration, I am using libnl. To gather current network interface information, I am using libnl. To control IPv6 autoconf, I read/ write /proc since that's all we can do right now. For DHCP and DHCPv6, I run dhclient and dhcp6c, respectively. I'd like everyone to have a look at iface.h and the patch file. It's not complete yet, so I probably know about the obvious things (the FIXMEs and the useless debugging printfs and the incomplete isys.py code and so on). The goal with iface.patch is to get us closer to using NetworkManager in stage 1 and stage 2. I envision the NM changeover to be just as large, but hopefully by then we will have decided to nuke certain parts of loader entirely. Completely eliminating libdhcp and friends will be a nice step. There are some other things that need discussion as well. mkinitrd currently uses libdhcp, for example. This had me thinking we could generate libisys in an anaconda-devel package for things like mkinitrd, but I'm just brainstorming. Maybe I should put the iface code elsewhere? I dunno. At any rate, mkinitrd needs to be not left out. Work in progress, comments welcome. -- David Cantrell <dcantrell(a)redhat.com> Red Hat / Honolulu, HI

8 28

Re: Can the install method be contained within a kickstart file that is referenced via a %include option
by Niels de Vos 11 Nov '08

11 Nov '08

Hello Matt, Matthew Richards wrote: > I suppose that having a Stage0 solution would indeed be more elegant > than an updates.img solution. I'm guessing that you would not have to > rebuild a Stage0 image very often but would have to re-generate an > updates.img patch any time you moved to a new version of Anaconda. It's not that elegant, just working around limitations of anaconda. > I'm curious about this "some kind of detection with two ks.cfgs" that > you refer to. It sounds like you are implying that this is done via a > custom patch to Anaconda? I can't help wondering if Anaconda is > flexible enough to allow this sort of thing without a custom patch > by, say, placing 2 ks= options in the bootloader config - but that > would probably result in either an error or only one of the ks.cfg > files being parsed . . . sorry, just thinking as I type. The patch in Bugzilla (#) exactly does make this possible. With this patch, a ks= option allows more than one ks.cfg. However, it's just an other workaround for missing functionality. I still don't know what the best way would be to implement this correctly in anaconda/kickstart. > It is a bit of a challenge to guess what you are getting at with my > limited Linux app development knowledge, but I imagine you are > proposing to: > > (1) Build a new initrd.img containing only the resources needed for > your basic environment and the tasks that you need to perform ( I > have little idea what this would contain but I suppose I could find > out from Anaconda-Init source and its dependencies, or from LSB, or > from Linux From Scratch or something similar). These are not the references I would suggest. It's probably far more easy to look into a standard /boot/initrd-$(uname -r).img. They are now in cpio.gz format, extract it like: mkdir /tmp/my-initrd cd /tmp/my-initrd gunzip /boot/initrd-$(uname -r).img | cpio -id The script init is the starting point and can be extended/replaced. It might be adviseable to include a busybox or something like it ;) > (2) Write a new Stage0-Anaconda-Init based on Stage1 Anaconda-Init, > that will run your tasks and then finish by loading Stage1 initrd.img > and running /sbin/loader? No, don't write a stage0-anaconda-init. It is more like "stage0 bootstraps anaconda". In the init you would do a minimal setup of the system (like a standard initrd.img) and some extras: * detect the install target (search for /dev/sda,sdb,...) * detect the install source (search for/dev/sda,sdb,http,nfs,...) * create a tmp-directory * extract the original initrd.img which includes the loader * sed ks.cfg and save it in the same tmp-directory * exec chroot tmp-directory /bin/loader Note that the loader parses /proc/cmdline, therefore you can set ks=file:///tmp/ks.cfg as boot option. > How's that for a guess? Close, but don't think too complicated. Only try to do the minimal things needed. Everything what the proposed stage0 does can easily be written in shell-scripts. Good luck, Niels -- WINCOR NIXDORF International GmbH Sitz der Gesellschaft: Paderborn Registergericht Paderborn HRB 3507 Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193 Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet. This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

3 4

Re: anaconda installer problem in livecd
by kala 26 Sep '08

26 Sep '08

Thank you for replying I tried to solve the problem but i couldn't i am pasting both anaconda log file and syslog file syslog maessages Sep 27 06:05:32 localhost yum: Erased: pymol Sep 27 06:05:43 localhost kernel: md: raid0 personality registered for level 0 Sep 27 06:05:43 localhost kernel: md: raid1 personality registered for level 1 Sep 27 06:05:43 localhost kernel: xor: automatically using best checksumming function: pIII_sse Sep 27 06:05:43 localhost kernel: pIII_sse : 5388.000 MB/sec Sep 27 06:05:43 localhost kernel: xor: using function: pIII_sse (5388.000 MB/sec) Sep 27 06:05:43 localhost kernel: async_tx: api initialized (async) Sep 27 06:05:43 localhost kernel: raid6: int32x1 464 MB/s Sep 27 06:05:43 localhost kernel: raid6: int32x2 761 MB/s Sep 27 06:05:43 localhost kernel: raid6: int32x4 554 MB/s Sep 27 06:05:43 localhost kernel: raid6: int32x8 390 MB/s Sep 27 06:05:43 localhost kernel: raid6: mmxx1 1445 MB/s Sep 27 06:05:43 localhost kernel: raid6: mmxx2 2500 MB/s Sep 27 06:05:43 localhost kernel: raid6: sse1x1 1351 MB/s Sep 27 06:05:43 localhost kernel: raid6: sse1x2 1925 MB/s Sep 27 06:05:43 localhost kernel: raid6: sse2x1 2238 MB/s Sep 27 06:05:43 localhost kernel: raid6: sse2x2 2847 MB/s Sep 27 06:05:43 localhost kernel: raid6: using algorithm sse2x2 (2847 MB/s) Sep 27 06:05:43 localhost kernel: md: raid6 personality registered for level 6 Sep 27 06:05:43 localhost kernel: md: raid5 personality registered for level 5 Sep 27 06:05:43 localhost kernel: md: raid4 personality registered for level 4 Sep 27 06:05:43 localhost kernel: md: raid10 personality registered for level 10 Sep 27 06:05:43 localhost kernel: GFS2 (built Aug 4 2008 14:09:34) installed Sep 27 06:05:43 localhost kernel: Lock_Nolock (built Aug 4 2008 14:09:43) installed Sep 27 06:05:44 localhost kernel: JFS: nTxBlock = 8082, nTxLock = 64659 Sep 27 06:05:44 localhost kernel: SGI XFS with ACLs, security attributes, large block numbers, no debug enabled Sep 27 06:05:44 localhost kernel: SGI XFS Quota Management subsystem Sep 27 06:05:44 localhost kernel: device-mapper: multipath round-robin: version 1.0.0 loaded Sep 27 06:05:44 localhost kernel: device-mapper: multipath emc: version 0.0.3 loaded Sep 27 06:06:46 localhost gconfd (root-3693): starting (version 2.22.0), pid 3693 user 'root' Sep 27 06:06:46 localhost gconfd (root-3693): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Sep 27 06:06:46 localhost gconfd (root-3693): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Sep 27 06:06:46 localhost gconfd (root-3693): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Sep 27 06:08:51 localhost kernel: npviewer.bin[3729]: segfault at 0 ip 01176cac sp bfa5f378 error 4 in libflashplayer.so[d72000+778000] anaconda log file 06:05:44 INFO : using only installclass _Fedora 06:05:44 INFO : anaconda called with cmdline = ['/usr/sbin/anaconda', '--method=livecd:///dev/mapper/live-osimg-min', '--lang', 'en_US.UTF-8', '--noselinux'] 06:05:44 INFO : Display mode = g 06:05:44 INFO : Method = livecd:///dev/mapper/live-osimg-min 06:05:49 INFO : Starting graphical installation... 06:05:49 INFO : Detected 1024M of memory 06:05:49 INFO : Swap attempt of 1000M to 2000M 06:05:49 WARNING : step installtype does not exist 06:05:49 WARNING : step confirminstall does not exist 06:05:49 WARNING : step complete does not exist 06:05:50 INFO : moving (1) to step welcome 06:05:51 INFO : moving (1) to step keyboard 06:05:52 INFO : moving (1) to step networkdevicecheck 06:05:52 INFO : moving (1) to step network 06:05:53 INFO : moving (1) to step timezone 06:05:53 INFO : moving (1) to step accounts The exception error is evoked from this segemet of gui.py code except ImportError, e: print e win = MessageWindow(_("Error!"), _("An error occurred when attempting " "to load an installer interface " "component.\n\nclassName = %s") % (className,), type="custom", custom_icon="warning", custom_buttons=[_("_Exit"), _("_Retry")]) of 1332 of coloum 14 of /usr/share/lib/anaconda i have also removed python related software packages from the system(from liveusb) but it still shows the same error the iw/account_gui.py code is given as import gtk import string import gui from iw_gui import * from rhpl.translate import _ from flags import flags import cracklib class AccountWindow (InstallWindow): def getScreen(self, anaconda): self.rootPassword = anaconda.id.rootPassword self.intf = anaconda.intf (self.xml, self.align) = gui.getGladeWidget("account.glade", "account_align") self.icon = self.xml.get_widget("icon") self.capslock = self.xml.get_widget("capslock") self.pwlabel = self.xml.get_widget("pwlabel") self.pw = self.xml.get_widget("pw") self.confirmlabel = self.xml.get_widget("confirmlabel") self.confirm = self.xml.get_widget("confirm") # load the icon gui.readImageFromFile("root-password.png", image=self.icon) . . . . . and it goes on, i will paste the whole file if you want so it still shows the error "An error occurred when attempting to load an installer interface component. > > className = AccountWindow" kindly help kala bharath

1 0

Network installation from CD
by Dag Wieers 26 Sep '08

26 Sep '08

Hi, In a corporate environment we are not allowed to use DHCP/PXE for doing network installations. This means we have to look for other solutions. Our solution is to use an ISO image (mounted via a KVM solution) to kick off that network installation. A big problem currently is that the order of the network interfaces is arbitrary (depends on the order of the drivers loaded) and is not influence by the order of the PCI slots. So in our case we have a bunch of e1000, bnx2 and tg3 in systems we have to install. The first onboard interface (usually tg3 or bnx2) almost never is eth0, but instead can be eth2, eth3 or higher. (Depending on the number of "other" NICs) This is problematic because Anaconda never gives a very good analysis of why the download of the kickstart fails. Very unpleasant if you want system deployements done by Service Operations. So our solution was to provide ksdevice=MAC-ADDRESS , which works fine in the first phase for downloading the kickstart file, but then the kickstart file again has a network-directive with a --device= parameter. Here is where the trouble starts. The --device= cannot handle MAC addresses, in other words we either ommit the parameter (causing us to get a list of interfaces, which we do not want because the list does not tell which one is the right interface). Using ksdevice=bootif and providing BOOTIF=MAC-ADDRESS on the commandline does not help either because the second phase always wants to reconfigure the network. In fact we don't want the second phase to reconfigure the network, we want it to retain the working network configuration that worked fine for downloading the kickstart file. So here's my question: Is there a way to have the second phase network configuration NOT take place, or have it use the interface that was correctly downloading the kickstart file ? I could not find it anywhere and none of my tests seem to indicate that this is at all possible. -- -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors]

2 2

anaconda installer problem in livecd
by kala 25 Sep '08

25 Sep '08

Dear friendsI have created a customized live cd using livecd-tools and i have modified the look by making use of generic logos package , i have used the packages for repo from the standard fedora-i386-dvd-iso and updates from a fedora mirror, i have used the supplied kickstart files to configure and create the image file, and i am successful in creating so , but the fedora-installer(anaconda) which is present in the desktop doesnt work , i have already posted problem at fedora fourm , they said to include @admin-tools which i have already done , even then it still shows the same error, "An error occurred when attempting to load an installer interface component. className = AccountWindow" i have also included a screen shot at the forum page http://forums.fedoraforum.org/showthread.php?p=1064927#post1064927 <http://forums.fedoraforum.org/showthread.php?p=1064927#post1064927> kindly help me , i am in very much in need of this to be enabled -- kala bharath

4 6

Re: Change of growing swap partition size limits?
by Joel Granados 25 Sep '08

25 Sep '08

----- "Hans de Goede" <hdegoede(a)redhat.com> wrote: > Radek Vykydal wrote: > > Hi, > > > > do you think we should use suggested swap size in partitioning? > > And how? > > > > How it works now: > > ----------------- > > > > The only case when it is used is when the partition is set to grow > > without limit > > starting at size smaller than suggested maximum - then the > suggested > > maximum (something like 2*ramsize) is _silently_ used both in > kickstart > > and ui. > > > > I.e., the case for ks is: > > - --size is smaller than suggested maximum > > - --maxsize is not used > > - --grow is used > > > > and for ui: > > - "Size (MB):" is smaller than suggested maximum > > - "Fill to maximum allowable size" is selected > > > > (How) do we want to change it? > > ------------------------------ > > > > 1) in kickstart: > > > > I think that, supposing ks install is done by people who know what > they > > do, we > > shouldn't limit the qrow based on suggested maximum. The worst thing > is > > that > > it is, and has to be, done silently because it is kickstart. > > On the other hand, there is a workaround for our limiting - if you > > really want > > to fill all remaining space with swap, use big enough --maxsize. By > > > using the > > workaround you are kind of forced to say: "Yes, I really want to do > it". The thing that we want when the user specifies "--grow" in a swap line is to creat a swap that grows to a sane size ("Sane" being expressed in the function swapsuggestion function). My point is: treating the swap lines differently from the partition lines is just common sense. Grow in a non swap partition means: grow until maxsize, with maxsize defaulting to the available size. and on a swap partition it means grow until maxsize, whre maxsize defaults to whatever the functions suggests (2*ram). Is this sane, or am I just crazy? > > > > 2) in ui: > > > > We should at least inform user that we used the suggested maximum > (now > > he can only notice it in updated partition list), or perhaps better, > let > > him > > decide. I was looking at possible patch and came to 2 options: > > > > A) Limit "Edit Partition" dialog. If the File System Type is swap, > > disable the "Fill to maximum allowable size" option. > > > > or > > B) After leaving "Edit Partition" dialog with "OK", if any > calculated > > swap partition sizes exceed the suggested maximum due to "Fill to > maximum > > allowable size" selection, give a dialog like: > > > > +---------------------------------------------------------+ > > | This setting would result in exceedeng of the suggested | > > | size 666MB for these swap partitions: | > > | /dev/hda3: would grow to 1500MB | > > | | > > | Modify Partition Continue | > > +---------------------------------------------------------+ > > I vote for B. Because the swap partition can be the last thing that the user is doing and he can say "please fill the rest of the HD with swap". If he might be making a mistake, we at least warn him. > > > > "Modify Partition" takes the user back to "Edit Partition" dialog, > > "Continue" uses the exceeding values. For the just confirmed swap > > partitions, > > user is never asked again. (Note that there can be ugly cases like > when > > two swap partitions have "Fill to maximum allowable size" selected > > and by shrinking some other partition in "Edit Partition" you > > make both of them exceed the suggested maximum). > > > > Now, what do you think about change of partitioning wrt swap size > > suggestion? > > A or B? > > I think A is the best, making swap partitions fill the remainder of > the disk > does not seem to make much sens. Unless remainder of the disk is sane :). Like when 1Gig of disk remains. > > > Or only in ks? > > I would leave ks as is, both for compatiblity with existing ks files > as well as > because in an automated install the current way of doing things makes > some sense. > > Regards, > > Hans > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/anaconda-devel-list -- Joel Andres Granados Red Hat / Brno Czech Republic

1 0

Re: anaconda installer problem in livecd
by kala 25 Sep '08

25 Sep '08

Is that a Big Mistake , I am working on my college project of creating a bioinformatics linux workbench http://opendiscovery.org.in , i have already posted this question on livecd-mail list and fedora forums weeks ago with no replies, i am just asking for help i am not demanding any -- kala bharath

1 0

Change of growing swap partition size limits?
by Radek Vykydal 24 Sep '08

24 Sep '08

Hi, do you think we should use suggested swap size in partitioning? And how? How it works now: ----------------- The only case when it is used is when the partition is set to grow without limit starting at size smaller than suggested maximum - then the suggested maximum (something like 2*ramsize) is _silently_ used both in kickstart and ui. I.e., the case for ks is: - --size is smaller than suggested maximum - --maxsize is not used - --grow is used and for ui: - "Size (MB):" is smaller than suggested maximum - "Fill to maximum allowable size" is selected (How) do we want to change it? ------------------------------ 1) in kickstart: I think that, supposing ks install is done by people who know what they do, we shouldn't limit the qrow based on suggested maximum. The worst thing is that it is, and has to be, done silently because it is kickstart. On the other hand, there is a workaround for our limiting - if you really want to fill all remaining space with swap, use big enough --maxsize. By using the workaround you are kind of forced to say: "Yes, I really want to do it". 2) in ui: We should at least inform user that we used the suggested maximum (now he can only notice it in updated partition list), or perhaps better, let him decide. I was looking at possible patch and came to 2 options: A) Limit "Edit Partition" dialog. If the File System Type is swap, disable the "Fill to maximum allowable size" option. or B) After leaving "Edit Partition" dialog with "OK", if any calculated swap partition sizes exceed the suggested maximum due to "Fill to maximum allowable size" selection, give a dialog like: +---------------------------------------------------------+ | This setting would result in exceedeng of the suggested | | size 666MB for these swap partitions: | | /dev/hda3: would grow to 1500MB | | | | Modify Partition Continue | +---------------------------------------------------------+ "Modify Partition" takes the user back to "Edit Partition" dialog, "Continue" uses the exceeding values. For the just confirmed swap partitions, user is never asked again. (Note that there can be ugly cases like when two swap partitions have "Fill to maximum allowable size" selected and by shrinking some other partition in "Edit Partition" you make both of them exceed the suggested maximum). Now, what do you think about change of partitioning wrt swap size suggestion? A or B? Something different? Get rid of it completely? Or only in ks? Thanks for your comments. Radek

3 2

[PATCH] Give more useful names to other bootable devices
by Will Woods 24 Sep '08

24 Sep '08

Give more useful names to other bootable devices. This patch for booty would give more useful (descriptive, anyway) names to the other operating systems that booty finds. The patch is untested but really obvious. I'm guessing that trademark concerns are the only thing that kept someone from doing this sooner. I'm not a lawyer, but I'm almost positive this is Fair Use, as we're just using the marks to identify the product. Microsoft's page on the matter[1] says: "You may use the Windows trademark in a referential phrase such as 'works with Windows XP,' ..." And Apple has very similar guidelines[2] about the use of "Mac OS". Naturally I'll defer to Legal here, but it seems pretty obviously OK. -w [1] http://www.microsoft.com/about/legal/trademarks/usage/windows.mspx [2] http://www.apple.com/legal/trademark/guidelinesfor3rdparties.html --- bootloaderInfo.py | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bootloaderInfo.py b/bootloaderInfo.py index 207242c..8aa39c4 100644 --- a/bootloaderInfo.py +++ b/bootloaderInfo.py @@ -189,9 +189,9 @@ class BootImages: for (dev, type) in devs: if not self.images.has_key(dev): if type in dosFilesystems and doesDualBoot(): - self.images[dev] = ("Other", "Other", type) + self.images[dev] = ("Other", "Windows", type) elif type in ("hfs", "hfs+") and rhpl.getPPCMachine() == "PMac": - self.images[dev] = ("Other", "Other", type) + self.images[dev] = ("Other", "Mac OS X", type) else: self.images[dev] = (None, None, type) -- 1.5.5.2

4 6

VT320 Terminal on Anaconda - Usability Issue
by Arthur Rodrigo Sawazachi Valadares 24 Sep '08

24 Sep '08

Hi, I wanted to know if using terminal vt320 is essencial to anaconda for some reason. I ask this because there is an unexpected behavior when running anaconda on PowerPCs, although Alt+Tab is the official backtab shortcut, people usually use shift+tab as well. If you do a shift tab on an X machine it works as alt+tab or just tab (on non-x terminals), which is not too bad. If you do it on a PPC it works as ESCAPE for some reason, which leads it to next screen (like F12). If I change the $TERM variable to linux instead of vt320 it works fine (shift+tab untabs or just tabs). Another option would be to change newt library to capture shift+tab as well ( ^[[Z ), since alt+tab has the issue of being captured by OS, still working/testing this one. The user could do Esc+Tab, but it's not very natural to know alt+tab = esc+tab = ^[tab. Any comments and enlightenment are appreciated =) Arthur V.

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 September 2008