Chris Smart posted <[EMAIL PROTECTED]>, excerpted below, on Sun, 03 Apr 2005 09:36:33 +1000:
> From what you have told me, I can only assume that the hardened profile > for amd64 is set to use multilib. > > I could compare the 2005.0/no-multilib profile to the hardened profile > and see what the differences are, perhaps I can create my own new profile. Hmm.. Yes, hardened sort of does its own thing, altho there are discussions about possibly making amd64 hardened (or semihardened anyway) by default, in which case of course the AMD64 herd would be supporting hardened. Comparing the profiles is a good idea and exactly the way I'd go. However, note that with cascading profiles, it's a bit more complex than it used to be. You can't just compare the immediate profile subdir, but must compare the composite profiles, meaning following each parent link from which a profile inherits, all the way up the profile tree, so you get a complete picture of the profile. With cascading profiles, the only things in a profile subdir itself are the things that are different from the profile parent (which in most but not all cases is simply the parent dir, check the "parent" file to be sure). Perhaps the easiest way to check most things, therefore, would be to do an emerge info, switch profiles to the other one temporarily, and do an emerge info again, then compare the results. Naturally, this won't catch variables and stuff in the profile bashrc that doesn't show up in emerge info. For that, you'll have to do a manual compare. Be sure to switch your profile back after testing. =8^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
