For those of you, still using my binary packages. It’s just a waste of disk space for me (6.8G to be exact), so I decided to remove them. I’m gonna give people one week to grab yourself a copy. I’m gonna keep the bashrc and all the other stuff I wrote back when I was still interested in binary packages, but the binary packages are gonna vanish!
Again, grab yourself a copy if you need them, at some point next week (probably on Friday), I’m simply gonna rm -rf them.
Well, as for replacing my current fileserver (which I seriously need to consider replacing), I’ll just pick up these things:
So after browsing some more for a replacement for my current fileserver, I’d like to share the latest stages with you people. Thanks to Mike (who mentioned that binutils-2.18* already does the LDFLAGS=”-Wl,-z,relro” part) I replaced it with “-Wl,-O1”. Same old place, there’s fresh stages … (and thanks again to Mike, with working util-linux-2.13-r2).
I also tried getting a Gentoo/Hardened stage for PowerPC working, but that fails as due to >glibc-2.3 needing =gcc-4*. Though luck ….
Oh, yeah. If anyone is looking for the specs, they are in my overlay.
For what it’s worth, I’ve been trying to get some stages together the last few days. Thanks to solar and Brent, the ppc-stages are now coming along quite fast.
I haven’t really tested them yet, but for what it’s worth, you’ll find stages based on Saturday’s snapshot (that is 200780105 for those not smart enough to take a look at the calendar) here for the following profiles:
Now remember, this isn’t *official* release material. This is just *MY* effort (for now) to provide current stages.
And just a side-note for those brewing their own (uClibc) soup: if you remerge system/world, you’ll have to keyword =sys-libs/uclibc.0.9.28.3-r2. Otherwise you’ll stumble on bug 195368, which is fixed thanks to solar, just not marked stable yet.
As I’m way better writing stuff than saying it with my own words, here a short “Thank you!“
OK, as some of you have noticed; I prepared my box for the new toolchain, recompiled the stuff Kevin mentioned in the exact same order wrote down in his README, and it looks like it actually works with all my stuff I have on my box; except sys-libs/grub! *sigh*
Apparently, grub segfaults at boot and/or while running it from the chroot in the exact same spot, the new QA warnings complain about ..
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
* QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:222: warning: dereferencing type-punned pointer will break strict-aliasing rules builtins.c:4862: warning: dereferencing type-punned pointer will break strict-aliasing rules disk_io.c:1027: warning: dereferencing type-punned pointer will break strict-aliasing rules disk_io.c:1057: warning: dereferencing type-punned pointer will break strict-aliasing rules tparm.c:719: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:222: warning: dereferencing type-punned pointer will break strict-aliasing rules builtins.c:4862: warning: dereferencing type-punned pointer will break strict-aliasing rules disk_io.c:1027: warning: dereferencing type-punned pointer will break strict-aliasing rules disk_io.c:1057: warning: dereferencing type-punned pointer will break strict-aliasing rules tparm.c:719: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c:181: warning: dereferencing type-punned pointer will break strict-aliasing rules |
So, I unpacked the libc and grub debug files, to get a clue where it’s failing and fed the program execution into gdb and viola:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /sbin/grub --no-floppy Program received signal SIGSEGV, Segmentation fault. grub_putstr (str=0xa1660489) at char_io.c:174 in char_io.c (gdb) quit The program is running. Exit anyway? (y or n) |
I’m not yet sure if it really is the same spot, but I’ll let Kevin have a shot at it …
Today (OK, it’s yesterday now, it’s again after 12:00) I had a little fun with pappy (Alexander Gabert) preparing 2.6.18 for prime time 😀
|
1 2 3 4 5 6 7 8 9 10 |
$ ls -AGg 2.6.18 -rw-r--r-- 1 1593 Jan 25 23:25 1500_cvs-2007-1000.patch -rw-r--r-- 1 797 Jan 25 23:25 4000_deprecate-sk98lin.patch -rw-r--r-- 1 32192 Jan 25 23:25 4105_dm-bbr.patch -rw-r--r-- 1 125781 Jan 25 23:25 4300_squashfs-3.1.patch -rw-r--r-- 1 5710 Jan 25 23:25 4405_alpha-sysctl-uac.patch -rw-r--r-- 1 864955 Jan 25 23:25 4450_grsec-2.1.9-2.6.18.6-200611100917.patch -rw-r--r-- 1 910 Jan 25 23:25 4451_grsec-2.1.9-2.6.18.2-mute-warnings.patch -rw-r--r-- 1 1034 Jan 25 23:25 4452_selinux-avc_audit-log-curr_ip-grsec.patch -rw-r--r-- 1 2097 Jan 25 23:25 4453_pax_curr_ip-fixes.patch |
So far all patches are applying fine and according to Alexander it even works on his workstation. But I’ll wait for Steve/Ned to get back to me telling me if this release works for them or not (as they had serious issues with their hardened desktops – something about the cursor being stuck in the corners).
You may also ask, what for is this mute-warning patch. Basically the new grsecurity patch increased the kernel’s verbosity while running make about two times 😮 . Thus we decided to revert the warnings to the ones used in vanilla (that’s via CFLAGS).