From: Oliver Schinagl <oliver@schinagl.nl>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Upstart on Gentoo - report #3
Date: Sun, 11 Jul 2010 21:20:02 +0200 [thread overview]
Message-ID: <4C3A1962.8000406@schinagl.nl> (raw)
Exams are finally behind us and summer has started. I wish I had more
time so far, but I'm only slightly behind schedule.
I have fixed and can now use the libnih ebuild as it is a requirement
for upstart. I'm building upstart from the vcs and installing it in
/usr/local for now. I can boot the most basic thing and now the real
work starts I suppose :) Decisions will have to be made and real
problems tackled.
For those curious, I fixed my hard-drive issues from before (apparently
the LSI controller I have does not like smart requests) and my PSU of my
desktop is still broken. I switched to using VirtualBox on my laptop
from KVM, because my CPU lacks the virtual bit. I enabled and installed
KVM on my server, so i'm gonna see if I can use that aswell. And after
weeks of not being able to figure out why virtualbox was crashing when
accessing shared folders, might be just an upgrade I overlooked.
Happy GSoCing in this killer heat (we have hit 36C the other day :S)
Oliver
reply other threads:[~2010-07-11 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C3A1962.8000406@schinagl.nl \
--to=oliver@schinagl.nl \
--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