November 2007 - Anaconda-devel - Fedora mailing-lists

%post --name
by Christopher Boumenot 18 Dec '07

18 Dec '07

It would be nice to know what post script is executing, but do to their nature that is impossible. Would you accept a patch that added --name argument to %post (and %pre) to tell Anaconda what the scriptlet's name is? I am open to other suggestions. Thanks, Christopher

4 11

[RFC (crack?)] lang images?
by Bill Nottingham 30 Nov '07

30 Nov '07

At the point that the loader downloads stage2, it already knows what language the user wanted. If we spilt some locale specific data (translations, fonts) out into their own images (squashfs, cpio, whatever) that the loader can pick up/download, then for cases where they're not needed, the stage2 download can be shrunk by ~20MB or so. Bill

2 3

mkinitrd [PATCH] Not resuming is not an error. Return 0 instead of 1.
by Warren Togami 30 Nov '07

30 Nov '07

From 12ed2b1c295422c884d36addfd822af40e959949 Mon Sep 17 00:00:00 2001 From: Warren Togami <wtogami(a)redhat.com> Date: Fri, 30 Nov 2007 15:06:55 -0500 Subject: [PATCH] Not resuming is not an error. Return 0 instead of 1. --- nash/nash.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/nash/nash.c b/nash/nash.c index 2996e0e..9190f5f 100644 --- a/nash/nash.c +++ b/nash/nash.c @@ -1447,7 +1447,7 @@ resumeCommand(char * cmd, char * end) if (strncmp(buf, "S1SUSP", 6) && strncmp(buf, "S2SUSP", 6)) { qprintf("No suspend signature on swap, not resuming.\n"); close(fd); - return 1; + return 0; } if (fstat(fd, &sb)) { -- 1.5.3.4

1 0

mkinitrd [PATCH] Correct the replace regex when $MODULE omits the trailing .ko or .o, so dm-zero does not become dm-ze
by Warren Togami 30 Nov '07

30 Nov '07

From b7342a71959fabd606404ca8ca860398b3d4cc9e Mon Sep 17 00:00:00 2001 From: Warren Togami <wtogami(a)redhat.com> Date: Fri, 30 Nov 2007 14:13:32 -0500 Subject: [PATCH] Correct the replace regex when $MODULE omits the trailing .ko or .o, so dm-zero does not become dm-ze --- mkinitrd | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/mkinitrd b/mkinitrd index e2ebd2f..01094dd 100755 --- a/mkinitrd +++ b/mkinitrd @@ -1613,7 +1613,7 @@ fi usb_mounted="prep" for MODULE in $MODULES; do text="" - module=`echo $MODULE | sed -e "s|.*/||" -e "s/.k\?o$//"` + module=`echo $MODULE | sed -e "s|.*/||" -e "s/\.k\?o$//"` fullmodule=`echo $MODULE | sed "s|.*/||"` options=`sed -n -e ':a' -e '/\\\\$/N; s/\\\\\n//; ta' -e "s/^options[ ][ ]*$module[ ][ ]*//p" $modulefile 2>/dev/null` -- 1.5.3.4

1 0

Partition resizing, take 2
by Jeremy Katz 30 Nov '07

30 Nov '07

Okay, newer patch implementing resizing. Still against an older tree (726a485e58706b70c8fb2b9d4febe938a7c88963) but just to get it out there while I work on the fun of rebasing to the current code and merging with dlehman's encryption bits. The patch implements the following: 1) Adds "pulsing progress bars" for GUI where you have the progress bar bounce due to something taking an indeterminate amount of time. We should also be able to use this for other filesystem creation options that we don't know how long they take. For text mode, this just gives a message and no progress bar 2) Moves writing out partitioning and mounting filesystems to be right after the partitioning screen. Note: this still needs something to let the user know that their changes are going to be done immediately 3) Adds support for resizing partitions in the autopart loop. This requires the pyparted patch which I sent last time 4) Determines the maximum size a partition can be grown to 5) Adds support for resizing ext[23] filesystems and determining the minimum size of the ext[23] filesystem 6) Cleans up the graphical UI when editing a pre-existing partition and adds support for resize. Contrast http://katzj.fedorapeople.org/resize-poc.png to http://katzj.fedorapeople.org/new-edit-part-dialog.png At this point, I'm pretty happy with how things are looking and am probably going to go ahead and commit once I get things rebased unless anyone has any strong concerns. There are still some more things which can be done, but they can be easily done as small follow-up patches. Jeremy

5 12

Testing anaconda
by Ralf Ertzinger 30 Nov '07

30 Nov '07

Hi. Assuming I want to start hacking on anaconda: what is the quickest way to test the stuff I built? And this may be a stupid question, but has python got something like perls '-c' (test the files for syntactical correctness, but do not execute)?

2 1

Logical volume resizing
by Jeremy Katz 29 Nov '07

29 Nov '07

To follow up on yesterday's partition resizing patches, I've now got an additional set of patches on top which add support for resizing logical volumes as well. The first is a bit of an infrastructure thing and more in line with the main resizing series and then there's a patch for the backend and one for the UI. Jeremy

1 3

Check for RELEASE-NOTES file; locale specific extension doesn't exist
by Ray Van Dolson 28 Nov '07

28 Nov '07

Hi all, noticed the following when doing an "askmethod" install of CentOS 5.0. I'm not sure if it's truly an anaconda related issue, but figured this would be a good place to start. Basically, if I do an http method installation, the installer looks for the following files on my web server: RELEASE-NOTES-en_US.UTF-8.html RELEASE-NOTES-en_US.UTF-8 RELEASE-NOTES-en_US.html RELEASE-NOTES-en_US However, on my CentOS 5.0 CD, the only files present are: RELEASE-NOTES-en.html RELEASE-NOTES-en Obviously, it's trivial to create a symlink or something to fix this, but is there a better way to address this? Should CentOS be providing one of the above files, or should anaconda be requesting one of the lower two filenames instead? Maybe I can just override my locale (LANG) settings somewhere before this step. Any insight appreciated, Ray

2 1

Partition resizing, take three
by Jeremy Katz 28 Nov '07

28 Nov '07

1 9

Re: Generating comps.xml
by Prasad H.L. 26 Nov '07

26 Nov '07

As far I know, a tool by name revisor should do what you are suggesting as well as some more things. But, revisor reads from an existing comps file and writes it out into another as per user's selection. It doesnot give support for addiing/modifying/deleting categories and groups in the GUI. Myself and one of my friends are interested in precisely the same. We are modifying revisor's python scripts for doing the same. With Regards, Prasad H. L. ----- Original Message ---- From: Alexander Todorov <atodorov(a)redhat.com> To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list(a)redhat.com> Sent: Thursday, November 22, 2007 3:53:41 PM Subject: Generating comps.xml Hello, I've found this quite old document explaining the comps.xml structure: http://rhlinux.redhat.com/anaconda/comps.html It mentions the getfullcomps.py script to generate the package sections of comps.xml. My comps-extras package contains only images and no helper scripts. Is comps.xml produced manually nowadays? Is there any tool to automate comps.xml generation? If not is anybody interested in implementing such a tool? Is there a need for one? Thanks, Alexander. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

6 8

Let's talk about some F9 (and beyond) features for anaconda
by Jeremy Katz 26 Nov '07

26 Nov '07

I'd like to try and get everyone working on anaconda who wants to see new features, etc over the next six months (the Fedora 9 timeframe) and beyond together next week on IRC for an hour or so to kind of plan things out, figure out who's doing what and timing, etc. Given that, we're going to try to do next Tuesday, November 6th starting at 10 am EST (UTC-0500). We'll be in #anaconda on irc.freenode.net While somewhat short notice, I'd rather get this going sooner rather than later and we can then follow up the IRC discussion with more here on the mailing list (I'll summarize as well as posting the log). Jeremy

9 18

Generating comps.xml
by Alexander Todorov 26 Nov '07

26 Nov '07

Hello, I've found this quite old document explaining the comps.xml structure: http://rhlinux.redhat.com/anaconda/comps.html It mentions the getfullcomps.py script to generate the package sections of comps.xml. My comps-extras package contains only images and no helper scripts. Is comps.xml produced manually nowadays? Is there any tool to automate comps.xml generation? If not is anybody interested in implementing such a tool? Is there a need for one? Thanks, Alexander.

2 1

Re: Generating comps.xml
by Prasad H.L. 25 Nov '07

25 Nov '07

Dear Alexander, I think it will be a good idea to start a project as you are recommending. Firstly, we were thinking of introducing a feature in comps.xml. Instead of having a flat category structure, why not have a tree structure? So, we would like to first propose this tree category structure to be introduced in comps.xml. It can be introduced simply by adding one more tag, say <parentid> for a category. With this new structure of comps.xml file in mind, let me put forward my and my friend's views about the approach for implementing a scheme for modifying comps.xml. 1. Currently, revisor is a nice GUI except for the feature of comps.xml editing. So, we thought of changing revisor for the above purpose. 2. We noticed that revisor uses a similar (but not the same!) GUI as in pirut. As you may already know, the anaconda is already using pirut for displaying package selection GUI. Pirut is doing the job of reading for comps.xml and displaying categories and groups in a GUI. So, pirut's modification can be much more useful than modifying only revisor. 3. So, we came to one view that we will modify pirut so that it will display comps.xml properly. In the revisor, an inherited version of the class used in pirut for package display will be used. This inherited version will provide routines for modification (add/edit/delete) categories and groups. Also, it should provide an interface to drag and drop an rpm package entry to a category/group. Waiting for feedback on above ideas, With Regards, Prasad H. L. ----- Original Message ---- From: Alexander Todorov <atodorov(a)redhat.com> To: hlprasu(a)yahoo.com Sent: Thursday, November 22, 2007 4:17:58 PM Subject: Re: Generating comps.xml Prasad H.L. wrote: > Myself and one of my friends are interested in precisely the same. > We are modifying revisor's python scripts for doing the same. Hello Prasad, it would be interesting to take a look at your modifications. Are they publicly available? If there is enough interest in this field we can start a project and gather some more ideas before writing code. Greetings, Alexander. ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/

1 0

[PATCH] add support for bootman to booty
by Elliot Peele 20 Nov '07

20 Nov '07

These patches add support for bootman to booty as well as expose extlinux as a choice in anaconda. For the time being I am trying to maintain support for installs where bootman is not available. The idea behind bootman is to use a single common bootloader config file that could be used to generate a config file for any supported bootloader. Currently grub and extlinux are the only supported bootloaders. A snapshot of bootman can be found here: ftp://download.rpath.com/autosource/bootman-0.20071120.tar.gz Elliot

1 0

New feature page
by Jeremy Katz 20 Nov '07

20 Nov '07

I've taken the discussions from the IRC meeting and tried to distill things into separate pages with owners, etc and also to integrate it into the rest of the bits on the wiki. If I missed something, let me know or just add it yourself. http://fedoraproject.org/wiki/Anaconda/Features The individual pages for each thing are somewhat from the Fedora feature template, but that was mostly to make some of them easier to turn into actual features for Fedora 9 as opposed to caring that much about the formatting. Jeremy

2 1

Functional reductions of anaconda
by Binbin Wang 19 Nov '07

19 Nov '07

Hi All, I want to do some job about the functional reductions of Anaconda. For example, I want to remove the graphical interface of Anaconda. What should I do to start this task. Thank you very much! Best Regards! Binbin Wang 2007-11-19 -- Wang.bupt

2 1

how can compile anaconda ?
by bentolhoda rajabi 19 Nov '07

19 Nov '07

hi, 1. i want to localize anaconda, and change DefaultTimeZone for example , but when i make & make install it, this change is not visible. why? 2. how can i add farsi to anaconda: you have changed the anaconda script or you have added farsi font to anaconda fonts?

1 0

[PATCH]close file descriptor
by HARA Hiroshi 19 Nov '07

19 Nov '07

Hi, in cryptodev.py after open file descriptors using os.pipe, write pipe is closed but read pipe is not closed. Is it not needed ? thank you in advance.

1 0

Block device encryption support
by David Lehman 16 Nov '07

16 Nov '07

I've made an initial attempt at support for creating LUKS-encrypted partitions at install time. A patch is available here: http://dlehman.fedorapeople.org/anaconda-fscrypto-20071109.patch The basic idea is a class to represent a generic encrypted device, with a subclass for dm-crypt, and another for LUKS (the LUKS class inherits from the dm-crypt class, not the base class). The fsset Device classes all get a member containing either a pass-through encryption device or a LUKS one. The main operations on the Device objects are reworked slightly so that, down to the encryption class code, the code paths are identical for encrypted and non-encrypted devices. Some notes: - My testing was done on rawhide from 24 October, although the patch I posted is against rawhide as of now. - I tested basic LVM (LUKS PVs), RAID 0 (LUKS mdX), and normal partitions. - Code to load the needed crypto kmods is non-existent. I've been using a hacked up /sbin/anaconda for that, but it's not for keeps. - Although I think the building blocks are there, there is no support whatsoever for existing LUKS partitions. Have a look, if interested, and provide feedback. Dave

4 7

PS3 pcidom trace Error - Bug 381541
by Greg Morgan 15 Nov '07

15 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI from the bug post... Received a traceback on PS3 firmware 2.0 PPC with f8 installation. I had to transcribe the message because ALT F[1-7] function keys were not usable. Google reports similar problems http://julipedia.blogspot.com/2007/10/got-it-ps3.html#c7668625964381266145 http://julipedia.blogspot.com/2007/10/got-it-ps3.html#c1098426015556577328 Traceback follows: Running anaconda 11.3.0.50 the Fedora system installer - please wait. Traceback (most recent call last) File"/usr/bin/anaconda", line 779, in < module> floppy Device = probeHW(opts, x_already_set, xserver) File /usr/bin/anaconda line 421, in prowbeHW xserver.probeHW(skipMouseProbe = skipmouseprobe, forceDriver = opts.xdriver) File "/usr/lib/python2.5/site_packages/rhpxl/xserver.py", line 87 in probeHW self.videohw = videocard.VideoCardInfo (forceDriver = forceDriver) File "/usr/lib/python2.5/site_packages/rhpxl/videocard.py", line 149, in __init__ elif osname()[4].count("ppc" ) > 0 and cmd.pcidom > 0: Atribute Error device instance has no attribute 'pcidom' install exited abnormally[1/1] sending termination signals ... done. ... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHOnxDxyxe5L6mr7IRAib+AJ9UWZne1nDF1xM47vWAXd2i4qHSHgCfQI21 rNYGAsI9jtP0liJk6gSCXMM= =BoQg -----END PGP SIGNATURE-----

2 2

Proof of concept, early work in progress code for partition/filesystem resizing
by Jeremy Katz 14 Nov '07

14 Nov '07

I've been looking some at what we need to have to implement resizing of partitions and filesystems within anaconda. At this point, the code is starting to work, although there are still some large-ish holes. Also, there are some functionality pieces that are entirely missing. So to start with the caveats: 1) The UI is just enough to make it possible to test the code and not the UI that we're going to actually want to use. 2) Only implemented for ext[23]. Relatively easy to add additional implementations for other filesystems, though 3) Only implemented for partitions. Not RAID. Not LVM. I'm not sure if we can do RAID. LVM LVs are pretty easy. LVM PVs look like they have a lot more caveats based on looking at the pvresize man page 4) Real minimum and maximum calculations still need to be written. But stubs are there 5) Doesn't really have any error handling to speak of All that said, I have done installs to resized partitions and filesystems which is pretty freaking cool :-) I'm going to keep working on filling in the holes but anyone else that wants to take a look, feel free. I just wanted to get this out there for any comments, thoughts, etc that people have Jeremy

3 4

2 anaconda problems on Alpha platform/Debugging?
by Oliver Falk 14 Nov '07

14 Nov '07

Hi! Yesterday I tried installing an Alphaserver with our latest set of (AlphaCore) packages with a fresh spinned install cd. version for spinning iso: 11.3.0.34-1axp (only mk-images.alpha added) version inside the install medium: anaconda-11.3.0.42-1axp With .42 I wasn't able to spin isos yet - there's also some error I haven't looked into yet. And I'm using pungi for spinning if that does matter. However. I noticed 2 problems: 1) Automatic partitioning doesn't work - it used to work in AC2, but I guess anaconda was patched by someone. If I do add /boot partition via switching to another console and using fdisk and then do a customized partitioning I get trough that point - however, I would really see this fixed upstream. I'll try to find the patch in old srpms. 2) Anaconda dies at the point of setting the root password. It spots some error about not being able to lock the file. Sorry, the real output I don't have anymore. :-( However. This raised a question. What's the best way to debug this? Can I somehow start anaconda on an installed system and do the installation on some loopback device? Any help is appreciated! Best, Oliver

3 8

mkinitrd sbp2 typo?
by Warren Togami 13 Nov '07

13 Nov '07

Did you mean it to be "$module" to match the others, instead of "$modules"? Warren Togami wtogami(a)redhat.com diff --git a/mkinitrd b/mkinitrd index 477b350..300db21 100755 --- a/mkinitrd +++ b/mkinitrd @@ -1464,7 +1464,7 @@ for MODULE in $MODULES; do emit "stabilized /proc/bus/usb/devices" fi # Firewire likes to change the subsystem name every 3 hours. :/ - if [ "$modules" = "sbp2" ]; then + if [ "$module" = "sbp2" ]; then emit "echo Waiting for driver initialization." emit "stabilized /sys/bus/ieee1394/drivers/sbp2" fi

2 1

kickstart not working with fedora 8
by Matthew Milliss 13 Nov '07

13 Nov '07

I've been using kickstart with fedora 6 to run automated installs, I do this by adding the following line to the isolinux.cfg on my fedora install dvd label install_linux kernel vmlinuz append ks=nfs:my.server:/path/ks.cfg initrd=initrd.img I tried a similar thing on fedora 8 label linux menu label ^Install or upgrade an existing system menu default kernel vmlinuz append ks=nfs:my.server:/path/ks.cfg initrd=initrd.img And when I try to install from the dvd I get the following errors. File "/usr/lib/python2.5/site-packages/pykickstart/commands/method.py", line 81, in parse(opts, extra) = op.parse_args(args=args) AttributeError: 'NoneType' object has no attribute 'parse_args' Any ideas what is going on here? Cheers Matt

2 1

mkinitrd-bash devel questions
by Warren Togami 08 Nov '07

08 Nov '07

Hi, pjones said it might be off-topic for this list, but lacking a better place elsewhere he suggested posting here. http://katzj.fedorapeople.org/git/mkinitrd.git/ I am working on fixing bugs in the bash branch of mkinitrd. http://fedorapeople.org/~wtogami/mkinitrd-bash/ Here is my git branch based upon katzj's repo. ======== for i in $(seq 0 127) ; do mknod /dev/loop$i b 7 $i: ; done Is it really necessary to create 128 loop devices in initrd? This seems a little excessive. ======== # If we have ide devices and module ide, do the right thing ide=/proc/ide/ide* if [ -n "$forceide" -o -n "$ide" -a "x$PROBE" == "xyes" ]; then findmodule -ide-disk fi This code never did work properly. 1) ide=/proc/ide/ide* makes $ide == "/proc/ide/ide*", it never did probe. 2) As a result of that, -n "$ide" always was true. 3) /proc/ide doesn't even exist now. 4) ide-disk module doesn't exist now either. Should we just remove this block, --force-ide-probe and PROBE? ======== More later... Warren Togami wtogami(a)redhat.com

1 0

The move to git commences!
by Jeremy Katz 07 Nov '07

07 Nov '07

The move of the various anaconda-related components has begun from elvis.redhat.com (also known as rhlinux.redhat.com and i18n.redhat.com) to be hosted under git.fedoraproject.org has begun. The following is a basic summary of checkout and commit information. Note that if you think you should have commit access and _don't_, let me know. The instructions use "$module" to refer to whatever the module is. Moved modules are anaconda, pykickstart, system-config-kickstart, rhpl, booty, pyblock, firstboot, anaconda-images (not really relevant anymore), anaconda-help (likewise) To get a copy (anonymous) git clone git://git.fedoraproject.org/hosted/$module To get a copy as a committer git clone git+ssh://git.fedoraproject.org/git/hosted/$module.git Once you've committed changes locally, you can push them with git push Branches should be mirrored there as well. To get a local tracking copy of a branch you'll likely want something like git branch --track $branchname ; git checkout $branchname Then pulls when on the branch checkout will mirror the upstream branch and pushes will also go to the branch. If you notice any problems, let me know. Jeremy

7 11

[PATCH] display %post scriplets failues
by Christopher Boumenot 06 Nov '07

06 Nov '07

We have many post scripts that we run during an install, and if one fails it is difficult to tell how or why. I patched Anaconda to display the output of the log file if a post script fails. To enable this functionality, add --log, and --erroronfail to your post script. %post --interpreter /bin/sh --erroronfail --log=/tmp/foo.log if [ ! -f /tmp/check ] ; echo "/tmp/check does not exist" exit 1 fi exit 0 With this patch you can quickly see the error message in the GUI/console without having to do any postmortem work. diff -r 695707da1b0b -r 0aff5ad26f74 kickstart.py --- a/kickstart.py Thu Sep 20 13:59:34 2007 -0400 +++ b/kickstart.py Thu Sep 20 14:02:11 2007 -0400 @@ -70,13 +70,16 @@ class AnacondaKSScript(Script): if self.errorOnFail: if intf != None: - intf.messageWindow(_("Scriptlet Failure"), - _("There was an error running the " - "scriptlet. You may examine the " - "output in %s. This is a fatal error " - "and your install will be aborted.\n\n" - "Press the OK button to reboot your " - "system.") % (messages,)) + if self.logfile is not None and os.path.isfile(messages): + intf.messageWindow(_("Scriptlet Failure"), open(messages).read()) + else: + intf.messageWindow(_("Scriptlet Failure"), + _("There was an error running the " + "scriptlet. You may examine the " + "output in %s. This is a fatal error " + "and your install will be aborted.\n\n" + "Press the OK button to reboot your " + "system.") % (messages,)) sys.exit(0) os.unlink(path) diff -r 695707da1b0b -r 0aff5ad26f74 kickstart.py --- a/kickstart.py Thu Sep 20 13:59:34 2007 -0400 +++ b/kickstart.py Thu Sep 20 14:02:11 2007 -0400 @@ -70,13 +70,16 @@ class AnacondaKSScript(Script): if self.errorOnFail: if intf != None: - intf.messageWindow(_("Scriptlet Failure"), - _("There was an error running the " - "scriptlet. You may examine the " - "output in %s. This is a fatal error " - "and your install will be aborted.\n\n" - "Press the OK button to reboot your " - "system.") % (messages,)) + if self.logfile is not None and os.path.isfile(messages): + intf.messageWindow(_("Scriptlet Failure"), open(messages).read()) + else: + intf.messageWindow(_("Scriptlet Failure"), + _("There was an error running the " + "scriptlet. You may examine the " + "output in %s. This is a fatal error " + "and your install will be aborted.\n\n" + "Press the OK button to reboot your " + "system.") % (messages,)) sys.exit(0) os.unlink(path)

2 1

Meeting IRC log
by Chris Lumens 06 Nov '07

06 Nov '07

For anyone who was unable to attend the anaconda feature meeting we held in #anaconda this morning, I've posted my IRC log here: http://clumens.fedorapeople.org/anaconda-meeting.log Enjoy. - Chris

1 0

Anaconda Incorrectly Detects dmraid
by Christopher Boumenot 06 Nov '07

06 Nov '07

Greetings, We are seeing an issue with anaconda-11.1.2.36 (CentOS 5.0), where it incorrectly detects dmraid on our Dell 2900s (and, 1950s, 2950s). (We were able to track it down to that issue based on the message "Specified nonexistent disk sda in partition command," and /tmp/anaconda.log.) I am not sure why Anaconda detects dmraid. I suspect it looks for a piece of metadata somewhere on the disk, and by pure hapstance our data matches the signature of a dmraid disk set. Has anyone seen this before? Any ideas on how to fix it? We have not seen this issue with RHEL 4u2, or CentOS 4u4, and we have been running/imaging those for the past 1.5 years. Here's a example log from two identical machines, one with the issue, and one without. -- Falsely detects dmraid. -- DEBUG : starting dmraids DEBUG : self.driveList(): ['sda', 'sdb'] DEBUG : DiskSet.skippedDisks: [] DEBUG : DiskSet.skippedDisks: [] DEBUG : starting all dmraids on drives ['sda', 'sdb'] DEBUG : scanning for dmraid on drives ['sda', 'sdb'] DEBUG : got raidset <block.device.RaidSet instance at 0xb7d173ac> (sda sdb) DEBUG : valid: True found_devs: 2 total_devs: 2 DEBUG : adding mapper/ddf1_44656c6c202020201028001510281f0332b494acaae97d7b to isys cache DEBUG : adding mapper/ddf1_44656c6c202020201028001510281f0332b494acaae97d7b to isys cache() DEBUG : adding sda to dm cache DEBUG : removing sda from isys cache DEBUG : adding sdb to dm cache DEBUG : removing sdb from isys cache ## it detected dmraid?!?! -->>DEBUG : starting raid <block.device.RaidSet instance at 0xb7d173ac> with mknod=True DEBUG : done starting dmraids. Drivelist: ['mapper/ddf1_44656c6c202020201028001510281f0332b494acaae97d7b'] INFO : Running kickstart %%pre script(s) INFO : All kickstart %%pre script(s) have been run -- Correctly, does not detect dmraid. -- DEBUG : starting dmraids DEBUG : self.driveList(): ['sda', 'sdb'] DEBUG : DiskSet.skippedDisks: [] DEBUG : DiskSet.skippedDisks: [] DEBUG : starting all dmraids on drives ['sda', 'sdb'] DEBUG : scanning for dmraid on drives ['sda', 'sdb'] DEBUG : done starting dmraids. Drivelist: ['sda', 'sdb'] INFO : Running kickstart %%pre script(s) INFO : All kickstart %%pre script(s) have been run In the meantime, to get around this issue I just commented out all calls to startDmRaid(). I will continue to decipher the code (anaconda, python-pyblock, dmraid-devel) , but I wanted to ask here first. Thanks, Christopher

3 2

[PATCH]Clean up: using "%m" instead of "%s + strerror(errno)"
by HARA Hiroshi 05 Nov '07

05 Nov '07

Hi, I found that some codes use "%m" and some other code use "%s + strerror(errno)" to show error message. so I clean up the whole code to use "%m" instead of "%s + strerror(errno)". this patch is not bug fix or enhancement, but I feel it is better to use one rule in whole code. I'd appreciate it if you could review this attached patch. thank you,

1 0

[PATCH] memory allocating error handling in modstub.c
by HARA Hiroshi 05 Nov '07

05 Nov '07

Hi, I saw our anaconda was started to manage with git in Jeremy's mail.(thanks, Jeremy) so I used it and it's fine for me. then I modified the patch which I have sent before. Current insmod in anaconda has no check point after allocating memory (malloc/strdup/realloc). so I added such kind of check point. I'd appreciate it if you could review this attached patch. thank you,

2 2

More thoughts as we go to git
by Jeremy Katz 05 Nov '07

05 Nov '07

So, a couple more thoughts for consideration as we move to git. Opinions, thoughts, etc appreciated * Get rid of the ChangeLog. We have the information in the commit history and git makes it nice and easy to get that. If we want to still have a ChangeLog in the tarball, we could generate one when creating the archive. Doing this leads to a need to ensure we have good commit messages, but that's largely the case already * Don't carry the RPM spec file in the repository; have it just in the packaging repo instead. Jeremy

7 15

replace 129 lines of code with 18
by Joel Andres Granados 02 Nov '07

02 Nov '07

Hi all: With the objective of making the anaconda code more readable and smaller, I have conjured up a patch that takes away all those "import logging" lines from the code. Since that is a module that is used a lot I simply put it in the __builtin__ as log and stdoutlog. It works nicely on my test machine. Comments would be appreciated!!! Regards. PD: This patch would be accompanied with some wiki documentation that helps to understand the log stuff. -- Joel Andres Granados Red Hat / Brno, Czech Republic

2 1

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 2007