

how about a hardened toolchain + gcc-4.2 + glib-2.6 is that possible? I'm running gcc 4.1.2 + glibc 2.6 here, haven't been able to get a 4.2.0 hardened compiler yet ...thoffmeyer wrote:Tell me your wishes/features/sex you'd want in the guide, srsly people, tell me what YOU want. Kthnx.



hey, it's just an optionmdeininger wrote:sounds good, but i'd strongly advise against reiser4. lots of people seem to have fairly unpredictable issues that change around from kernel to kernel (sometimes it's all good, sometimes you can't read files with (filesize mod 3 == 0). very weird issues like that)... 'plain' reiserfs would be a better option.
(no trolling intended or anything, i'm all for alpha and beta software myself, just that reiser4 really seems like an unpredictable beast :/)

Yeah, I haven't used reiser4 in awhile, in fact today I just got a brand new gentoo install and used reiserfs.mdeininger wrote:sounds good, but i'd strongly advise against reiser4. lots of people seem to have fairly unpredictable issues that change around from kernel to kernel (sometimes it's all good, sometimes you can't read files with (filesize mod 3 == 0). very weird issues like that)... 'plain' reiserfs would be a better option.
(no trolling intended or anything, i'm all for alpha and beta software myself, just that reiser4 really seems like an unpredictable beast :/)

looks niceNeither of these will be used in the guide, they're both easy installs and you can use one if you like (pkgcore is pretty nice though, very easy to use and same configs and everything as portage - it can also run side by side with portage)

Because both are sooo easy to install I don't think it's necessary to be documented, and me personally don't care for either one (not because they're bad). I use portage because it's the most complete of all 3, and even though it's not BAM like a c++ alternative, it's not a problem for me.kernelOfTruth wrote:looks niceNeither of these will be used in the guide, they're both easy installs and you can use one if you like (pkgcore is pretty nice though, very easy to use and same configs and everything as portage - it can also run side by side with portage)![]()
I hope it's fast enough on this poor ol' laptop, I'll give it a try tomorrow,
so why not include both as alternatives? paludis & pkgcore ?

Wouldn't that make pkgcore WORSE? If it was nearly identical to portage it would have alot of the same pitfalls. Note that I'm not saying that pkgcore is terrible (although I use paludis on my Gentoo installations), I'm just trying to get what you mean by "Since they're nearly identical it has to be better".cheater1034 wrote:Also, just thought I'd address this now b/c someone will ask for it. If you want pkgcore or paludis (I think pkgcore is 10x better because it's nearly identical to portage). I've used both, both are extremely easy installs and both are automatic installs (emerge pkgcore or emerge paludis and run the script).
I don't think XFS could be considered "bleeding edge" by any standards, it's fairly mature and stable now. I agree about no insane CFLAGS or LDFLAGS, however I would recommend suggesting prelink as part of the standard install.seren wrote:I think ext3 tined with journal_data_witeback is best bet. and for a bleeding edge file system we should use xfs. no insane ldflags or cflags keep it conservative.

Well, I LOVE the portage interface and commands, partly because I'm so used to it, but I think it's absolutely perfect aside from the fact it's written in python.predatorfreak wrote:Wouldn't that make pkgcore WORSE? If it was nearly identical to portage it would have alot of the same pitfalls. Note that I'm not saying that pkgcore is terrible (although I use paludis on my Gentoo installations), I'm just trying to get what you mean by "Since they're nearly identical it has to be better".cheater1034 wrote:Also, just thought I'd address this now b/c someone will ask for it. If you want pkgcore or paludis (I think pkgcore is 10x better because it's nearly identical to portage). I've used both, both are extremely easy installs and both are automatic installs (emerge pkgcore or emerge paludis and run the script).
Yeah, I haven't used them in awhile, and I know SD was instantly replaced by ingo, but I might as well use con's patches for 1 release while they're still there. Though I'm doubting I'll use SD now because it's deprecated.Also, I don't think SD is utterly superior to CFS anymore, in the early stages of CFS development, it definitely was, but CFS is VERY mature now and is generally equal to or better than SD, in my usage I can't tell the difference really.
Prelink will be part of the standard install with hashstyle, glibc 2.6 and gcc 4.2.1 (I think, not final)I don't think XFS could be considered "bleeding edge" by any standards, it's fairly mature and stable now. I agree about no insane CFLAGS or LDFLAGS, however I would recommend suggesting prelink as part of the standard install.seren wrote:I think ext3 tined with journal_data_witeback is best bet. and for a bleeding edge file system we should use xfs. no insane ldflags or cflags keep it conservative.

I'd say Reiser4 over Ext4. Last no-kernel I used with R4 worked awesome and kept up. Although I'm a bit skeptical since this install without a no-kernelthoffmeyer wrote:Tell me your wishes/features/sex you'd want in the guide, srsly people, tell me what YOU want. Kthnx.

NO This install will have no-sources!!!Master Chef wrote:I'd say Reiser4 over Ext4. Last no-kernel I used with R4 worked awesome and kept up. Although I'm a bit skeptical since this install without a no-kernelthoffmeyer wrote:Tell me your wishes/features/sex you'd want in the guide, srsly people, tell me what YOU want. Kthnx.



gcc overlay (kudos to seren)Telexen wrote:I think it's wise to stay away from gcc 4.2.0 as well. I've tried to run it several times on x86 and amd64 ... multiple problems on both. I've been waiting for an ebuild for 4.2.1 just to see if a few of the problems I had are fixed and for optimizations.

I'm using his overlay, no problems at all with my gentookernelOfTruth wrote:gcc overlay (kudos to seren)Telexen wrote:I think it's wise to stay away from gcc 4.2.0 as well. I've tried to run it several times on x86 and amd64 ... multiple problems on both. I've been waiting for an ebuild for 4.2.1 just to see if a few of the problems I had are fixed and for optimizations.

yeah, it's working great here, toocheater1034 wrote:I'm using his overlay, no problems at all with my gentookernelOfTruth wrote:gcc overlay (kudos to seren)Telexen wrote:I think it's wise to stay away from gcc 4.2.0 as well. I've tried to run it several times on x86 and amd64 ... multiple problems on both. I've been waiting for an ebuild for 4.2.1 just to see if a few of the problems I had are fixed and for optimizations.

please see my post in the gcc 4.2.0 threadkernelOfTruth wrote:gcc overlay (kudos to seren)Telexen wrote:I think it's wise to stay away from gcc 4.2.0 as well. I've tried to run it several times on x86 and amd64 ... multiple problems on both. I've been waiting for an ebuild for 4.2.1 just to see if a few of the problems I had are fixed and for optimizations.

