LCFG Port to Fedora 12

Progress meeting 18 March 2010

Chris, Iain, Stephen, Alastair.

We went through the devproj plan and commented on various bits. Things not mentioned here are complete:

Install F12

Stephen has a better way of configuring Mock: include dice/options/mock.h and put yourself in the mock group and you'll have lcfg-mock, which configures Mock for you. It now puts packages it's built straight into a local yum repository so they can be used as dependencies for other packages, so as long as you ask it to build things in the right order it should be able to work its way through hundreds of packages.

RPM Repositories

Just to clarify, the devel bucket is for temporary packages. It'll be emptied regularly, say monthly. It'll only be available to machines following the develop release. During the port we're putting local component packages there until we've tested them at which point we'll submit them to the lcfg bucket instead.

Essential Headers

Chris will check in inf/os/f12.h then invert the setting of profile.components so that the file removes unwanted things from it one by one rather than building up a new one. That way we'll progressively use more and more of the lcfg-level setting.

Chris will check that the arch i686 default setting for updaterpms is set at lcfg level for f12.

Auto-build and run tests for all LCFG components

The latest update of the Fedora 12 openssh package has Simon's patches in it so we can use this rather than a local version.

Stephen's blog has the command to get your machine's keytab installed. In fact his blog has a lot of advice on getting an F12 machine installed and up to date with the LCFG port so far.

Create basic development platform

Updaterpms should be left open for now because of the genhdfile warning problem, but we can tick off lcfg-updaterpms and pkgsubmit.

Components necessary to keep a machine LCFG managed

We should add to this stage Go through boot procedure and check default configuration for platform.

lcfg-nsu: tip for Chris: try asking it to ban you (or not to allow you) then check you can't nsu any more!

lcfg-pam: Iain will tackle this. First take a complete copy of /etc/pam.d and put it somewhere safe! After that, the aim is to get lcfg-pam to reproduce the default configuration at the LCFG level, then build on that at the inf level, and build on it further at the dice level. The pam afs module we've been using is pretty ropey: we should probably switch to using Russ Allbery's pam-openafs-session module.

lcfg-syslog: Stephen is adapting this to make it function on F12 and optionally use either syslogd or rsyslogd. This is an interim solution rather than the more complete solutions mentioned in devproj 138.

lcfg-tcpwrappers: works for Stephen. It just manages hosts.allow/deny.

lcfg-defetc-f12: Although Stephen has added what we need to this, we should leave it open for now in case we need to add more to it.

Components for auth/authz, directory services and dns in client mode

lcfg-dns, lcfg-kerberos, lcfg-ntp, lcfg-openldap - are all in old CVS and won't install on F12.

In place of lcfg-dns we could maybe use lcfg-resolvconf for the time being.

In place of lcfg-kerberos and lcfg-openldap we could use the file component for now, at least for the inf level.

In place of lcfg-ntp we could look to see if there's an /etc/sysconfig file which configures ntp? If so we could configure that with the file component.

Chris has now upgraded his openafs so can now try building perl-AFS for f12 32 bit.

lcfg-nsswitch: Stephen has tested it and it works.

lcfg-openssh: Stephen has tested it and it works.

lcfg-cyrussasl: not tackled yet.

Alastair: you wanted to be reminded to ask the Inf unit how they were getting on.

X support

In future ports this could come later, after the Installation step.

lcfg-xfree: leave this until the end of the project; we may not need it at all.

lcfg-gdm: will be needed.

Other components

lcfg-rpmcache: delete from the list, we don't need or use this any more.

lcfg-xinetd: isn't needed just now, we don't think we use it much.

lcfg-mailcap: use this simply to replicate the F12 mailcap (the one that uses xdg-open).

lcfg-mailng: last time we had to ask Scott Larnach to convert the sendmail config for us! Perhaps we could postfix instead? Tim has done work on this already. Stephen will ask Tim about this.

lcfg-prelink: Whoever does this should compare the F12 and SL5 prelink configurations to see what will need to be added for F12.

lcfg-alias: manages the /etc/aliases file. Can we dump this?

Installation systems

lcfg-hardware: Stephen has tested this and tweaked it to make it work with F12. Note that modprobe.conf is now deprecated and we should drop files into modprobe.d instead. Alastair will check what we use this for.

Alastair is finalising the installroot.

He hasn't yet tackled the installbase but this shouldn't be too arduous a job.

The new first stage of the install process is all ready to be packaged up.

lcfg-install: is next on Alastair's list.

lcfg-kernel: has been rewritten by Stephen. It's a new component with the same resources as the old one. It copes with the changes in F12 and manages things more sensibly. It seems to work on F12 but needs thorough testing. It should be built from subversion.

lcfg-fstab: will be tackled by Alastair.

lcfg-network: Alastair or Stephen will tackle this.

lcfg-grub: does F12 use grub 2? If so this will need big changes.

Other Stages

Other stages haven't been tackled or thought about yet.

Chris should start a DICE wiki page for the F12 port, so we can collect useful things there and start to list useful info such as what's changed.

-- ChrisCooke - 18 Mar 2010

Topic revision: r1 - 18 Mar 2010 - 17:02:27 - ChrisCooke
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies