From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problems with the current IPFire Build
Date: Sat, 01 Jul 2017 12:50:27 +0100 [thread overview]
Message-ID: <1498909827.20312.21.camel@ipfire.org> (raw)
In-Reply-To: <000801d2eeac$21a5df30$64f19d90$@apolinarski.de>
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
Hi,
On Mon, 2017-06-26 at 20:43 +0200, Wolfgang Apolinarski wrote:
> Hi,
>
> continuing on my series of problems with the current next build, I currently
> have the following problems:
Yes, we are still in the middle of getting in stable. Hence it is called next.
I have just packaged the core update and the nightly builds will hopefully run
through. And then the big testing starts.
> - unbound (well, you already know about the problem of the name resolution)
That should be fixed.
> - segfaulting hwclock on /usr/local/bin/settime and during startup
> (S60setclock) and shutdown (K47setclock)
> - grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE
> against limit 0 for /sbin/hwclock
I still haven't looked into this.
> - "error: no symbol table. (...) Press any key to continue..." before the
> kernel is loaded, right after grub.
> - even when no key is pressed, the boot continues
This is the first time I hear about this. Could you please open a ticket and
collect all information about this problem that you have?
The system is booting up fine on my virtual machines that I used for testing.
> Sorry that I bother you only with problems this time, but I want to make sure
> that this "normal" for the current next, before I rebase and re-sent the
> apache patches.
No that's fine. That's what this list is for :)
>
> Best regards,
> Wolfgang
> PS.: I also can have a look at some of these issues, just not today and I
> wanted to make sure that these issues are not only because of VirtualBox.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-07-01 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 18:43 Wolfgang Apolinarski
2017-07-01 11:50 ` Michael Tremer [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=1498909827.20312.21.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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