public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Efros <powerman@powerman.asdfgroup.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] 2.6.28-hardened-r7 hangs before starting /sbin/init
Date: Thu, 2 Apr 2009 19:09:01 +0300	[thread overview]
Message-ID: <20090402160901.GI32102@home.power> (raw)
In-Reply-To: <4255c2570904020837n128d8ca2ga66c30506b4f3566@mail.gmail.com>

Hi!

On Thu, Apr 02, 2009 at 09:37:09AM -0600, RB wrote:
> I question whether your configurations are *precisely* the same.  If I
> had to guess (and I do), I'd guess that the system in question wasn't
> wholly built with the -hardened toolchain.

Yesterday servers was upgraded to sys-libs/glibc-2.8_p20080602-r1.
After that I've rebuild everything (just for the case) using:

    emerge linux-headers glibc binutils gcc-config gcc &&
    emerge -1 libtool &&
    emerge -b glibc binutils gcc portage &&
    emerge -bke system &&
    emerge -ke world

The `gcc-config -l` output is same on all servers:

 [1] i686-pc-linux-gnu-3.4.6 *
 [2] i686-pc-linux-gnu-3.4.6-hardenednopie
 [3] i686-pc-linux-gnu-3.4.6-hardenednopiessp
 [4] i686-pc-linux-gnu-3.4.6-hardenednossp
 [5] i686-pc-linux-gnu-3.4.6-vanilla

Here is `emerge --info`:
 server with    this issue: http://powerman.name/tmp/emerge-info1
 server without this issue: http://powerman.name/tmp/emerge-info2

/proc/config.gz on both servers are same (except compile date):
    http://powerman.name/tmp/config1

As far as I able to check - server configurations are *same*.

-- 
			WBR, Alex.



  reply	other threads:[~2009-04-02 16:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 14:05 [gentoo-hardened] 2.6.28-hardened-r7 hangs before starting /sbin/init Alex Efros
2009-04-02 15:29 ` Alex Efros
2009-04-02 15:37   ` RB
2009-04-02 16:09     ` Alex Efros [this message]
2009-04-02 16:36       ` Alex Efros
2009-04-02 16:45         ` Alex Efros
2009-04-02 18:54         ` RB
2009-04-02 19:06           ` Alex Efros
2009-04-02 21:17   ` pageexec
2009-04-02 22:22     ` Alex Efros
2009-04-02 22:25       ` klondike
2009-04-02 22:43       ` pageexec
2009-04-02 23:04         ` Alex Efros
2009-04-03  6:50           ` pageexec
2009-04-03 13:27             ` Alex Efros
2010-10-23 12:21           ` Alex Efros
2010-10-23 15:31             ` Alex Efros
2010-10-23 17:15             ` pageexec
2010-10-23 21:44               ` Alex Efros
2010-10-23 22:07               ` [gentoo-hardened] 2.6.32-hardened-r9 to -r22 upgrade issue with PaX Alex Efros
2010-10-23 23:24                 ` klondike
2010-10-24 10:02                   ` Anthony G. Basile
2010-10-25  2:14                     ` Pavel Labushev
2010-10-26  9:37                       ` Alex Efros
2010-10-26 22:30                         ` Pavel Labushev
2010-10-24 10:18                   ` "Tóth Attila"

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=20090402160901.GI32102@home.power \
    --to=powerman@powerman.asdfgroup.com \
    --cc=gentoo-hardened@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