Ombra wrote:The point being whatever you want to call these bits & pieces of code (or whatever) they are in the kernel. Secondly, whether you view them as harmless or not, I'd like to find a list of them so I can eradicate them (once I learn how).
They are in the kernel source, because the kernel also runs on many embedded systems that require such controls. That does not mean the code is enabled in kernels supplied with distros.
If you want to make sure your kernel contains none of the features you dislike, compile your own.
Incidentally, the only references to Trusted Gentoo that Google turned up for me was a 7+ year old announcement of a project to use TCP with Gentoo, no mention since and no mention of DRM anywhere.
'Trusted Gentoo' (along with 'Knoppix 5.1.1 for Trusted Computing', and several others I did not bother to note down) was mentioned on some site as being riff with DRM...er, I mean loaded up with wonderful Trusted Computing features! I obviously did not pursue it.
"That does not mean the code is enabled in kernels supplied with distros."
From your wording, I assume it means that the code may or may not be enabled in kernels, and if this is correct, the obvious question would be how to avoid those having the code enabled (although this would only be a stop-gap solution to buy time). So far as I know, anything enabled can be disabled, anything disabled can be enabled, and its only a matter of time before someone finds out how to re-enable such disabled crud remotely...so the only sure thing is not to have this code at all, which brings us to:
If you want to make sure your kernel contains none of the features you dislike, compile your own."
Far easier for you to say than for a newbie to do, but this was exactly my conclusion, and the reason for this posting from the start. So lets forget the pro/anti DRM debate, and focus on the nitty-gritty of how I can get a DRM-free kernel and OS. If this was XP Pro, the process would go something like this:
1. Find list detailing the exact file names and locations of all the Trusted Computing junk targeted for erasure. I assume its the same for Linux, except one must do this for both kernel & OS (distro).
2. Find out exactly how
to delete the targets. In XP Pro, its a two-part process. XPLite or nLite can be used to do custom-install, sans most of Lil Billie's well-hidden crud. Other software can be used to terminate any crapola that survived the pre-installation process. So how about with Linux?
Educate me...I need all the help and advice possible on this.