From: Matteo Riondato <matteo@freebsd.org>
To: Juergen Lock <qemu-l@jelal.kn-bremen.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [FreeSBIE LVC] freesbie in qemu...
Date: Sat, 21 Oct 2006 12:57:50 +0200 [thread overview]
Message-ID: <20061021105750.GA1018@krapfengeist> (raw)
In-Reply-To: <20061020174925.GA44116@saturn.kn-bremen.de>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
On Fri, Oct 20, 2006 at 07:49:25PM +0200, Juergen Lock wrote:
> Hi!
>
> I tried FreeSBIE LVC (see announcement here:
> http://www.riondabsd.net/2006/10/13/announce-freesbie-lvc-is-out/
> ) in qemu today (with kqemu), and noticed a few things (stated X with
> startx):
>
> 1. xfdesktop+Xorg+python together constantly kept the cpu busy (I've
> seen this with earlier versions of FreeSBIE too, just run `top' on
> a shell to check)
Yes. This is gdesklets' fault. I'm planning to remove gdesklets and
use something else.
> 2. as a result, firefox takes ages to startup, and when it finally
> starts it notices a ssl key out of date because the clock seems to be
> way in the future (somewhere in 2087!?)
MM..this can be qemu's fault. Anyway, I think I'll enable ntpd at
boottime.
>, and then it displays the
> `firefox updated' page.
Yes. My fault. It will be solved.
> 3. and there were a few (I think) `clock went backwards' messages on
> the (guest's) console.
This is qemu's fault. I have no doubts about it.
Thanks for the report, it is much appreciated.
I hope you'll enjoy FreeSBIE EW even more.
Best regards
--
Matteo Riondato
FreeBSD Committer (http://www.freebsd.org)
G.U.F.I. Staff Member (http://www.gufi.org)
FreeSBIE Developer (http://www.freesbie.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2006-10-21 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 17:49 [Qemu-devel] [FreeSBIE LVC] freesbie in qemu Juergen Lock
2006-10-21 10:57 ` Matteo Riondato [this message]
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=20061021105750.GA1018@krapfengeist \
--to=matteo@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-l@jelal.kn-bremen.de \
/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;
as well as URLs for NNTP newsgroup(s).