"Walter Dnes" <[EMAIL PROTECTED]> writes: >> I see nothing really like this on bugzilla although their are other >> access violations there. I guess it needs to be turned in as a bug but >> fisrst tell me if its really a bug or something to do with my >> ill-informed setup.
Thanks for noticing my post Walter. > A couple of things to look at... > 1) Do you have "SANDBOX" mentioned anywhere in /etc/make.conf ? No > 2) Grasping at straws here, have you made any manual changes to > /etc/profile ? The reason I'm asking is because > /usr/share/sandbox/sandbox.bashrc sources /etc/profile I don't recall having done so, and looking it over now I don't see any thing funky looking like I might have put there. I did have an `echo reading /etc/profile' in there at one point trying to unravel something and wanted to see when it was sourced, but I removed that long ago. There is quite a lot of sourcing going on in /etc/profile too, like /etc/profile.env /etc/profile.d/bash-conpletion I wish they'd sort of leave the init scripts a little less complicated to unravel. Or at least.. I wish I knew a way to in one command make the os tell me where everthing in env came from (which file I mean). It seams a little wild that it would go after my .bash_history. What would it be doing there... what would it write there and why? A little less subjective test: I'm building up a small vmware appliance from new install disc (2007.X) and diffing that /etc/profile against the one where the trouble is shows no differences at all. -- [EMAIL PROTECTED] mailing list
