public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Seaton <seatonr@dupage.edu>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Project Glentoo: Status Report #4
Date: Sun, 19 Jun 2011 18:42:54 -0500	[thread overview]
Message-ID: <BANLkTi=+aj68t5uaWzsYFWFF+AOpiZxFrg@mail.gmail.com> (raw)

Hi, all.

Project Glentoo is a GSoC project to combine a Plan 9 userspace with a
Gentoo base system.

Early in the week, I managed to hack together a work around for the
issue the #gentoo-releng team was facing last week, but we're still
waiting for the core team to come up with an official fix to the
baselayout issue (bug #371280). I ran into some more issues with the
catalyst build tool, but generating fresh stage1 - 3 cleared
everything up.

On Wednesday, I spent some time trying to get distcc working on an
Amazon EC2 high-compute instance to speed up generation of the process
of building a liveCD image, seeing as it takes quite some time to
generate a fresh image on my aging core2duo. I still haven't managed
to get that working, but it's something I plan to continue to look
into during the upcoming week.

By Thursday, I had successfully generated a new Glentoo liveCD image,
but ran into a problem: the image doesn't automatically log the user
in like the official install media, so it's not very useful. I
debugged for hours, eventually finding out via #gentoo-releng that
this is an issue that the x86 maintainer is aware of. He said that he
is going to ask someone (don't remember who) about leveraging PAM for
use with the official install media to auto-login and deprecating the
livecd-tools package.

While waiting for a fix for the login issue, I've started working on
X11 integration, which is what I'd originally planned to spend the
week on. I'll be unable to test if it works until the login issue is
fixed, but I figure that I can at least get it building while I wait.
Right now, I'm running into a build issue with Python -- something I
hope to fix in the upcoming week.

For this upcoming week, I plan on getting the xorg-x11 package built
and installed as part of the liveCD generation process. After I manage
to get that done, I'm going to either work on a project page for
Glentoo or write some documentation for Catalyst, seeing as the
current documentation is quite sparse. I also might work on getting
distcc via an Amazon EC2 instance running so that I can generate
images faster.

I think the project is progressing at a steady rate, albeit slowly.
Hopefully, once this login issue is cleared up, I will stop being
plagued by build issues. I can dream, can't I? Anyways, Glentoo is
still on schedule to be at the point I originally planned for midterm.

Cheers,
rps



             reply	other threads:[~2011-06-19 23:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 23:42 Robert Seaton [this message]
2011-07-15 14:25 ` [gentoo-soc] Project Glentoo: Status Report #4 Rich Freeman
2011-07-15 14:53   ` Donnie Berkholz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTi=+aj68t5uaWzsYFWFF+AOpiZxFrg@mail.gmail.com' \
    --to=seatonr@dupage.edu \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox