- WLUG - wlug.mailman3.com

RE: [Wlug] DRM/TCPA/Palladium

by Karl Hiramoto

Scenario #2 on POST after you install Linux. :) TCPA Error: Untrusted Operating System Detected. Please Insert Your Micro$oft CD for reinstall On Tue, 22 Oct 2002, Keller, Tim wrote: > The problem I see is when you go out and buy a PC, blowout the partitions > that have "longhorn" (MS's next OS) and install linux, reboot the machine > and get this error at the POST screen: > > "TCPA Error: BOOT DEVICE DOES NOT CONTAIN VALID BOOT KEY" > > I don't see the people building the whole DRM infrastructure giving out > details on how to change keys since their whole authentication > infrastructure is based around the idea that every machine has a unique key > so they can track things on a PC by PC basis. In their view, the idea of > installing an operating system that doesn't have DRM built into it at the > kernel level is an unacceptable option. The only way for DRM to be > effective is to have a say in every action on your machine. Start an > application and "DRM" verifies that the application is allowed to run on the > machine. Insert a piece of media and "DRM" verifies that your allowed to > access it. Go to a particular website and "DRM" decides if your allowed to > access said website... > > On the privacy side of this, what's to keep the whole infrastructure from > also keeping detailed info on what apps/media/peripheral/websites you > access. Yeah, you could opt out of it, but by not opting in, your PC > becomes utterly crippled, unable to play DVD's (since it can't verify > authenticity), unable to run verified apps, etc... > > I see all kinds of other very onerous privacy issues with this... > > Tim. > > -----Original Message----- > From: Gary Hanley [mailto:gary@hanley.net] > Sent: Monday, October 21, 2002 21:53 PM > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] DRM/TCPA/Palladium > > > On Mon, 21 Oct 2002, Karl Hiramoto wrote: > > http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html > > Thoughts? Should we boycot? > > Boycott what? We run Linux. :-) > > The best thing you can do is make your local politicians aware of your > opinion on the matter. > > Also, consider joining: > > www.eff.org > > -- Gary > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 Yahoo_IM = karl_hiramoto ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø I'm a Lisp variable -- bind me!

Oct. 22, 2002

debian pkgs

by brad

Hi All, Do the debian users here know how to install a package into a prefix directory? For example i want my kde stuff to be installed in /usr/local/kde, not /usr. Is this possible with aptitude? Thanks, -brad

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by doug waud

Hi all > I can't find any documentation that refers to /etc/modules, either. > I'd like to read up on this, because I find that I'm adding drivers to > support fibre HBA's. Being naive, I tried man modules.conf and got a lot of information. At the very top was The behavior of modprobe and depmod can be modified by the (optional) configuration file /etc/modules.conf I think that puts modules.conf itself into context. And the rest of those man pages should help as a first step in reading up on this. (I cannot point you farther since this has been as far as I have had to go in the past.) doug

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by Charles R. Anderson

On Tue, Oct 22, 2002 at 10:30:41AM -0400, Bill Mills-Curran wrote: subssn594> rpm -q --whatprovides /etc/modules.conf subssn594> file /etc/modules.conf is not owned by any package rpm -qf /etc/modules.conf would be a better choice, but it returns the same result in this case. subssn594> I can't find any documentation that refers to /etc/modules, either. subssn594> I'd like to read up on this, because I find that I'm adding drivers to subssn594> support fibre HBA's. Look into mkinitrd. You can tell it to add certain modules to the initial ram disk (so you could even have / on a fibre HBA if you wanted). -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by Bill Mills-Curran

On Tue, 22 Oct 2002, Brian J. Conway wrote: > Date: Tue, 22 Oct 2002 09:51:53 -0400 (EDT) > From: Brian J. Conway <bconway(a)alum.wpi.edu> > Reply-To: wlug(a)mail.wlug.org > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] Problem Solved! > > > What's the modules.conf syntax for explicitly loading? I've only used > > modules.conf for module options, not a replacement for modprobe. > > As far as I know, the /etc/modules is part of initscripts (not modutils) > and explicitly loads modules. I don't know if you can explicitly load > modules with modules.conf . > > [bconway@erasmus /]$ rpm -qf /etc/modules > initscripts-6.40.2-41mdk > [bconway@erasmus /]$ cat /etc/modules > # /etc/modules: kernel modules to load at boot time. > # > # This file should contain the names of kernel modules that are > # to be loaded at boot time, one per line. Comments begin with > # a `#', and everything on the line after them are ignored. > > #scsi_hostadapter > > -b Brian, /etc/modules is not in the standard initscripts rpm's from RedHat, so I don't have that. BTW, /etc/modules.conf is not owned by any package, either: rpm -q --whatprovides /etc/modules.conf file /etc/modules.conf is not owned by any package I can't find any documentation that refers to /etc/modules, either. I'd like to read up on this, because I find that I'm adding drivers to support fibre HBA's. Thanks, Bill

Oct. 22, 2002

RE: [Wlug] DRM/TCPA/Palladium

by Keller, Tim

The problem I see is when you go out and buy a PC, blowout the partitions that have "longhorn" (MS's next OS) and install linux, reboot the machine and get this error at the POST screen: "TCPA Error: BOOT DEVICE DOES NOT CONTAIN VALID BOOT KEY" I don't see the people building the whole DRM infrastructure giving out details on how to change keys since their whole authentication infrastructure is based around the idea that every machine has a unique key so they can track things on a PC by PC basis. In their view, the idea of installing an operating system that doesn't have DRM built into it at the kernel level is an unacceptable option. The only way for DRM to be effective is to have a say in every action on your machine. Start an application and "DRM" verifies that the application is allowed to run on the machine. Insert a piece of media and "DRM" verifies that your allowed to access it. Go to a particular website and "DRM" decides if your allowed to access said website... On the privacy side of this, what's to keep the whole infrastructure from also keeping detailed info on what apps/media/peripheral/websites you access. Yeah, you could opt out of it, but by not opting in, your PC becomes utterly crippled, unable to play DVD's (since it can't verify authenticity), unable to run verified apps, etc... I see all kinds of other very onerous privacy issues with this... Tim. -----Original Message----- From: Gary Hanley [mailto:gary@hanley.net] Sent: Monday, October 21, 2002 21:53 PM To: wlug(a)mail.wlug.org Subject: Re: [Wlug] DRM/TCPA/Palladium On Mon, 21 Oct 2002, Karl Hiramoto wrote: > http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html > Thoughts? Should we boycot? Boycott what? We run Linux. :-) The best thing you can do is make your local politicians aware of your opinion on the matter. Also, consider joining: www.eff.org -- Gary _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by Brian J. Conway

> What's the modules.conf syntax for explicitly loading? I've only used > modules.conf for module options, not a replacement for modprobe. As far as I know, the /etc/modules is part of initscripts (not modutils) and explicitly loads modules. I don't know if you can explicitly load modules with modules.conf . [bconway@erasmus /]$ rpm -qf /etc/modules initscripts-6.40.2-41mdk [bconway@erasmus /]$ cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. #scsi_hostadapter -b

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by Bill Mills-Curran

On Tue, 22 Oct 2002, Brian J. Conway wrote: > Date: Tue, 22 Oct 2002 09:22:11 -0400 (EDT) > From: Brian J. Conway <bconway(a)alum.wpi.edu> > Reply-To: wlug(a)mail.wlug.org > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] Problem Solved! > > > You'll probably want to build a new /boot/initrd-xxxx (along with an > > appropriate boot option) so that it loads automatically for smp. > > You could also add any modules you want to be explicitly loaded at boot > time to /etc/modules . > > -b What's the modules.conf syntax for explicitly loading? I've only used modules.conf for module options, not a replacement for modprobe. Thanks, Bill

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by Brian J. Conway

> You'll probably want to build a new /boot/initrd-xxxx (along with an > appropriate boot option) so that it loads automatically for smp. You could also add any modules you want to be explicitly loaded at boot time to /etc/modules . -b

Oct. 22, 2002

Re: [Wlug] Problem Solved!

by Bill Mills-Curran

On Mon, 21 Oct 2002, Marc Hughes wrote: > Date: Mon, 21 Oct 2002 19:45:31 -0400 > From: Marc Hughes <mhughes(a)wpidalamar.com> > Reply-To: wlug(a)mail.wlug.org > To: wlug(a)wlug.org > Subject: [Wlug] Problem Solved! > > I figured out my SMP / X problem. For some reason the AGPGART and RADEONFB > modules aren't loading automatically like they do in the single cpu kernel. > But if I modprobe them, X works fine. > > Thanks anyways guys! > > -Marc Marc, You'll probably want to build a new /boot/initrd-xxxx (along with an appropriate boot option) so that it loads automatically for smp. Bill

Oct. 22, 2002