[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: How NSA access was built into Windows



On Thursday 18 January 2007 10:13, Lyvim Xaphir wrote:
>On Tue, 2007-01-16 at 01:55 -0500, Gene Heskett wrote:
>> I believe you will have to build a generic kernel.org kernel,
>> configured without that support, something I have underway right now,
>> using 2.6.20-rc4.  I was amazed at the number of options I found
>> turned on that a proper 'make oldconfig' should absolutely never have
>> turned on.  My scripts take care of everything but grub.conf for a
>> kernel install, so when its done all I should have to do is reboot
>> since I'm already running 2.6.20-rc4.  Several things I found may even
>> account for the apparent slowness of later kernels.  Things like 15
>> seconds to launch firefox on an xp-2800 athlon with a gig of ram?
>
>When you get that kernel up and running, see if you can then do without
>libselinux installed.
>
I'm not sure as I haven't tried to pull that yet.  But without the stuff 
in the kernel, the logs are being filled by cron processes stuff, but the 
stuff, like amanda, seem to run normally.

Lots of this sort of stuff:

 **Unmatched Entries**
    crond[1014]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[10236]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[10948]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11318]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11414]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[1142]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11610]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11637]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11646]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11720]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)
    crond[11842]: pam_loginuid(crond:session): set_loginuid failed opening 
loginuid: 1 Time(s)

and that continues for several pages in the logwatch report.

>I took it out with --nodeps and it basically hosed the system.
>
Ouch!  I was going to see just how much yumex wanted to remove as deps, 
but have had router problems that have taken center stage the last few 
days, so this has been simmering on the back burner.
>
>
>LX
>--
>°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
>Off Topic or Political Discussions:
>http://mandrakeot.mdw1982.com/
>http://www.mdw1982.com/mailman/listinfo/mandrakeot
>
>"Character is what you do when nobody's looking." - J.C. Watts
>°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2007 by Maurice Eugene Heskett, all rights reserved.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]