Anaconda-devel October 2007

anaconda-devel@lists.stg.fedoraproject.org

24 participants
26 discussions

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

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

speaking of time
by Curtis Doty 28 Oct '07

28 Oct '07

Am I the only one that frequently uses anaconda to install on boxen that may have a screwey CMOS clock from the factory? It's really annoying to have a fresh install with timestamps far in the future or past. With network installs, I'm in the habit of adding this to kickstart: %pre rdate -s time.nist.gov hwclock -w %end #%pre Could anaconda automatically do something similar if a network is available? ../C

3 2

Re: anaconda ChangeLog, 1.3145, 1.3146 fsset.py, 1.342, 1.343 kickstart.py, 1.394, 1.395 partRequests.py, 1.74, 1.75
by Jeremy Katz 28 Oct '07

28 Oct '07

On Fri, 2007-10-26 at 16:10 -0400, pjones(a)redhat.com wrote: > Log Message: > - add --fsprofile support to lvm, paritition, and raid. > - remove --bytes-per-inode support. Removing the support completely is going to break people's kickstart configs, so we probably need to do something to handle the option from kickstart without requiring people to change their configs... Jeremy

1 0

[PATCH] add timestamps to /tmp/anaconda.log
by Christopher Boumenot 26 Oct '07

26 Oct '07

It would be nice to have timestamps in the log file to better understand when things occur. diff -r 0aff5ad26f74 anaconda_log.py --- a/anaconda_log.py Thu Sep 20 14:02:11 2007 -0400 +++ b/anaconda_log.py Fri Oct 26 14:38:45 2007 -0400 @@ -62,0 +62,0 @@ class AnacondaLog: # Add a handler for the duped stuff. No fancy formatting, thanks. self.addFileHandler (sys.stdout, self.stdoutLogger, - fmtStr="%(message)s", minLevel=logging.INFO) + fmtStr="%(asctime)s %(message)s", minLevel=logging.INFO) # Add a simple handler - file or stream, depending on what we're given. def addFileHandler (self, file, addToLogger, minLevel=DEFAULT_LEVEL,

2 1

Option to write %pre, %post in /root/anaconda-ks.cfg
by Alexander Todorov 25 Oct '07

25 Oct '07

Hello list, I've just found that resulting anaconda-ks.cfg does not include the %pre, %post, %traceback scripts from the ks.cfg used for installation. I've talked to several people and here is the result. Why this is missing: 1) If the initial ks.cfg contains some sensitive information it should not get written to disc. - IMO if such info is used it's already present somewhere on disc. - An attacker may sniff the network traffic and discover that info if needed. - /root is accessible to root user Hence there is not much argument of a security point of view to skip the %post in anaconda-ks.cfg Why it should be there: 1) To be able to reproduce the same install over and over again. In some cases %post may be tweaking settings or custom configuration. 2) To keep the configuration used during installation in cases where ks.cfg is generated dynamically/not available after some period, etc. 3) To have things where one expects to be: anaconda-ks.cfg How it should appear in anaconda: - The most reasonable solution is to probably have another option --write-ks-scripts which will enable this functionality. Scripts can be written directly to resulting anaconda-ks.cfg or in separate files e.g. anaconda-ks.pre, anaconda-ks.post, etc. Any comments and concerns are welcome. Greetings, Alexander.

2 1

anaconda branched for f8, git coming soon
by Jeremy Katz 25 Oct '07

25 Oct '07

FYI -- I've now branched anaconda in the final lead-up to Fedora 8. Critical fixes needed for Fedora 8 should be committed to both the f8-branch as well as HEAD. Development will start to roll on again on HEAD. Also, we're planning to do the move of anaconda to be hosted in git on git.fedoraproject.org the beginning of next week. The full history will be imported and commits to elvis will be blocked at that point. I'll send a more complete rundown of checkout instructions, etc then as well. In addition to anaconda, we're going to move booty, rhpl, pykickstart, system-config-kickstart, and pyblock. Jeremy

3 2

[PATCH] larger inodes for ext3 at install time
by Eric Sandeen 24 Oct '07

24 Oct '07

Larger inodes should help out with selinux and/or beagle attributes a bit (xattrs can be stored in-inode) and also makes upgrade to ext4 possible (which needs an in-inode extent list) Should I also file something in bugzilla? Thanks, -Eric Index: anaconda-11.3.0.42/fsset.py =================================================================== --- anaconda-11.3.0.42.orig/fsset.py +++ anaconda-11.3.0.42/fsset.py @@ -576,7 +576,7 @@ class ext3FileSystem(extFileSystem): def __init__(self): extFileSystem.__init__(self) self.name = "ext3" - self.extraFormatArgs = [ "-j" ] + self.extraFormatArgs = [ "-j -I 256" ] self.partedFileSystemType = parted.file_system_type_get("ext3") def formatDevice(self, entry, progress, chroot='/'):

3 8

[PATCH] use less things in /tmp
by Bill Nottingham 24 Oct '07

24 Oct '07

This switches various things to use /dev for device nodes instead of /tmp. Tested by installing on a box with both raid and LVM. I suppose long-term we'd switch to udev and just assume the device nodes are there. Bill

2 2

Own distribution
by PV Juliet 23 Oct '07

23 Oct '07

Hi All, I have my own distribution . I uses ks.cfg to configure the the system . I would like to give raid support in that ks.cfg . I don't know how to proceed for raid support . Can anyone can help me ??? Regards juliet

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 October 2007