Can anyone out there tell me how to configure a Radeon 1950Pro video card to work with special effects? I would appreciate it. Danny On Wed, 2008-02-06 at 10:57 -0600, tclug-list-request at mn-linux.org wrote: > Send tclug-list mailing list submissions to > tclug-list at mn-linux.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > or, via email, send a message with subject or body 'help' to > tclug-list-request at mn-linux.org > > You can reach the person managing the list at > tclug-list-owner at mn-linux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tclug-list digest..." > > > Today's Topics: > > 1. Re: Open standards for government documents > (Brian D. Ropers-Huilman) > 2. Re: Open standards for government documents (Troy) > 3. Re: sudo (Mike Miller) > 4. Re: sudo (Andy Schmid) > 5. Re: sudo (Mike Miller) > 6. Re: Open standards for government documents (Steve Cayford) > 7. Re: Open standards for government documents (Troy.A Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 6 Feb 2008 06:52:58 -0600 > From: "Brian D. Ropers-Huilman" <brian at ropers-huilman.net> > Subject: Re: [tclug-list] Open standards for government documents > To: "Tony Yarusso" <tonyyarusso at gmail.com> > Cc: ubuntu-us-mn at lists.ubuntu.com, tclug-list at mn-linux.org > Message-ID: > <f0e11c480802060452w610f72adr5601abbb61cce2c at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Feb 6, 2008 12:26 AM, Tony Yarusso <tonyyarusso at gmail.com> wrote: > > As noted on my blog, I attended my caucus tonight, and decided to present a > > resolution for mandating the use of ISO-approved open standards for all new > > government documents and all being newly converted to electronic form, > > > > I was wondering if anyone else had similar resolutions brought up in their > > precinct, and if so, what was the result? The only concern raised against > > mine was wondering what the potential cost would be, although I think we > > have a solid argument there in that it would cost essentially nothing to > > implement open formats in a forward-only manner, and the real cost only > > comes in with retroactively converting existing documents > > I am a strong proponent of open source and have even been accused of > evangelicalizing at times. I pushed my extended family to move to > OpenOffice years ago, as I did. > > Having said that, however, we need to be careful when we talk about > costs. There certainly will be a cost involved in such a conversion, > not in the cost of the format or of the software to produce documents > in that format, but in terms of training. Like it or not, there are > differences in the applications that support open formats and those > that don't and those differences will have to be trained before users > are fully accepting of the new applications and their new formats. > > I just needed to point that one out. > > We did not stay for our actual caucus last night as our kids would > have melted. I'm not aware of any discussion in that regard either, > but I applaud you for bringing it up and am excited that your > resolution passed. > > -- > Brian D. Ropers-Huilman > > > > ------------------------------ > > Message: 2 > Date: Wed, 6 Feb 2008 07:46:51 -0600 > From: Troy <troythetechguy at gmail.com> > Subject: Re: [tclug-list] Open standards for government documents > To: "Brian D. Ropers-Huilman" <brian at ropers-huilman.net> > Cc: ubuntu-us-mn at lists.ubuntu.com, tclug-list at mn-linux.org > Message-ID: > <34de7f3d0802060546p6dfb598fwf125281092955712 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Great idea Tony. I wish I would have thought of offering the open standard > as a resolution as my caucus too. > > As Brian points out, there is the cost of training involved with any > conversion. However, I think this touches on the fundamental issue of how > we teach people to use software. This topic was mentioned in another list > that I am a member, and the consensus was we teach kids to use MS Word, not > word processing software. It would be nice if schools at least touched on > alternatives to MS products. > > Troy > > On Feb 6, 2008 6:52 AM, Brian D. Ropers-Huilman <brian at ropers-huilman.net> > wrote: > > > On Feb 6, 2008 12:26 AM, Tony Yarusso <tonyyarusso at gmail.com> wrote: > > > As noted on my blog, I attended my caucus tonight, and decided to > > present a > > > resolution for mandating the use of ISO-approved open standards for all > > new > > > government documents and all being newly converted to electronic form, > > > > > > I was wondering if anyone else had similar resolutions brought up in > > their > > > precinct, and if so, what was the result? The only concern raised > > against > > > mine was wondering what the potential cost would be, although I think we > > > have a solid argument there in that it would cost essentially nothing to > > > implement open formats in a forward-only manner, and the real cost only > > > comes in with retroactively converting existing documents > > > > I am a strong proponent of open source and have even been accused of > > evangelicalizing at times. I pushed my extended family to move to > > OpenOffice years ago, as I did. > > > > Having said that, however, we need to be careful when we talk about > > costs. There certainly will be a cost involved in such a conversion, > > not in the cost of the format or of the software to produce documents > > in that format, but in terms of training. Like it or not, there are > > differences in the applications that support open formats and those > > that don't and those differences will have to be trained before users > > are fully accepting of the new applications and their new formats. > > > > I just needed to point that one out. > > > > We did not stay for our actual caucus last night as our kids would > > have melted. I'm not aware of any discussion in that regard either, > > but I applaud you for bringing it up and am excited that your > > resolution passed. > > > > -- > > Brian D. Ropers-Huilman > > > > _______________________________________________ > > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > > tclug-list at mn-linux.org > > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > > > > > -- > Website of the week: > http://www.ubuntu.com/ > > The Free Alternative to M$ Office: > http://www.openoffice.org > > My Blog: > http://troythetechguy.blogspot.com > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20080206/de445f54/attachment-0001.htm > > ------------------------------ > > Message: 3 > Date: Wed, 6 Feb 2008 08:46:15 -0600 (CST) > From: Mike Miller <mbmiller at taxa.epi.umn.edu> > Subject: Re: [tclug-list] sudo > To: Andy Schmid <andyschmid at gmail.com> > Cc: tclug-list at mn-linux.org > Message-ID: <Pine.GSO.4.60.0802060841101.6955 at taxa.epi.umn.edu> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Wed, 6 Feb 2008, Andy Schmid wrote: > > > On Feb 5, 2008 5:11 PM, Mike Miller <mbmiller at taxa.epi.umn.edu> wrote: > > > >> Thanks, Dave. Very interesting. How about: A random string is the > >> hardest password to guess. > > > > > > I disagree. There is the chance (albeit very slim to none) that a > > random string can produce a password such as '1234', which can be easily > > cracked. > > I thought about that too, but the thing is, if the wouldbe cracker knows > that it is a random string (and he would know if that was the design of > the system), there will be no benefit to his guessing first things like > "1234," but if he knows that you have disallowed things like "1234", then > you have helped him by cutting back on the number of things he must guess. > > So when using random strings you would *not* want to have rules like "must > include both upper case lower case letters, digits and non-alphanumeric > characters," because that rule would help a brute-force attacker. > > Mike > > > > ------------------------------ > > Message: 4 > Date: Wed, 6 Feb 2008 08:58:20 -0600 > From: "Andy Schmid" <andyschmid at gmail.com> > Subject: Re: [tclug-list] sudo > To: "Mike Miller" <mbmiller at taxa.epi.umn.edu> > Cc: tclug-list at mn-linux.org > Message-ID: > <7b7c42a30802060658k19c7d285ya357f7ffa4b5dd4b at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > On Feb 6, 2008 8:46 AM, Mike Miller <mbmiller at taxa.epi.umn.edu> wrote: > > > On Wed, 6 Feb 2008, Andy Schmid wrote: > > > > > On Feb 5, 2008 5:11 PM, Mike Miller <mbmiller at taxa.epi.umn.edu> wrote: > > > > > >> Thanks, Dave. Very interesting. How about: A random string is the > > >> hardest password to guess. > > > > > > > > > I disagree. There is the chance (albeit very slim to none) that a > > > random string can produce a password such as '1234', which can be easily > > > cracked. > > > > I thought about that too, but the thing is, if the wouldbe cracker knows > > that it is a random string (and he would know if that was the design of > > the system), there will be no benefit to his guessing first things like > > "1234," but if he knows that you have disallowed things like "1234", then > > you have helped him by cutting back on the number of things he must guess. > > > > So when using random strings you would *not* want to have rules like "must > > include both upper case lower case letters, digits and non-alphanumeric > > characters," because that rule would help a brute-force attacker. > > > > Mike > > > > This is a good point. But most brute force attacks are done using common > passwords across many hosts (typically from worms). If you have constraints > put in place that are wide enough, the number of password permutations is > still astronomical, with the chance of weak passwords being produced > eliminated. Though, its a good idea all around to disable login access for > the root account, as well as any other accounts you do not want logging in. > > Andy > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20080206/9b7d48b7/attachment-0001.htm > > ------------------------------ > > Message: 5 > Date: Wed, 6 Feb 2008 10:32:50 -0600 (CST) > From: Mike Miller <mbmiller at taxa.epi.umn.edu> > Subject: Re: [tclug-list] sudo > To: TCLUG List <tclug-list at mn-linux.org> > Message-ID: <Pine.GSO.4.60.0802061031030.450 at taxa.epi.umn.edu> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Wed, 6 Feb 2008, Andy Schmid wrote: > > > Though, its a good idea all around to disable login access for the root > > account, as well as any other accounts you do not want logging in. > > Yep. I understand that concept. I like to become root sometimes, but I > like the idea of sudo logging, so maybe I'd try to do things that way. > > I'm still mostly on Solaris (sparc) right now but it is time for a change! > > Mike > > > > ------------------------------ > > Message: 6 > Date: Wed, 06 Feb 2008 10:35:42 -0600 > From: Steve Cayford <strayf at freeshell.org> > Subject: Re: [tclug-list] Open standards for government documents > To: TCLUG <tclug-list at mn-linux.org> > Message-ID: <47A9E1DE.2020302 at freeshell.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Tony Yarusso wrote: > > [...] > > I was wondering if anyone else had similar resolutions brought up in > > their precinct, and if so, what was the result? The only concern raised > > against mine was wondering what the potential cost would be, although I > > think we have a solid argument there in that it would cost essentially > > nothing to implement open formats in a forward-only manner, and the real > > cost only comes in with retroactively converting existing documents (and > > the prioritization of my resolution was worded accordingly), and > > regardless would be far less than the cost of trying to recover data > > after a vendor went bankrupt, changed its terms, or any other similar > > drastic blocking event to current documents. > > [...] > > Our precinct did not have time to go through all the resolutions and they > had to be passed along to the senate district conference en masse. So I > don't know what all the resolutions contained. I should have included a > resolution like that myself, but didn't think of it. > > As far as the cost... won't the older documents have to be converted to > something else at some point anyway? It seems like converting to an open > format could actually be cheaper than converting to Microsoft's next > document format. > > -Steve > > > > ------------------------------ > > Message: 7 > Date: Wed, 06 Feb 2008 10:55:22 -0600 > From: "Troy.A Johnson" <troy.johnson at health.state.mn.us> > Subject: Re: [tclug-list] Open standards for government documents > To: "Tony Yarusso" <tonyyarusso at gmail.com>, "Brian D. Ropers-Huilman" > <brian at ropers-huilman.net> > Cc: ubuntu-us-mn at lists.ubuntu.com, tclug-list at mn-linux.org > Message-ID: <47A99218.9048.009E.0 at health.state.mn.us> > Content-Type: text/plain; charset=US-ASCII > > >>> On 2/6/2008 at 6:52 AM, in message > <f0e11c480802060452w610f72adr5601abbb61cce2c at mail.gmail.com>, "Brian D. > Ropers-Huilman" <brian at ropers-huilman.net> wrote: > > On Feb 6, 2008 12:26 AM, Tony Yarusso <tonyyarusso at gmail.com> wrote: > >> As noted on my blog, I attended my caucus tonight, and decided to present a > >> resolution for mandating the use of ISO-approved open standards for all new > >> government documents and all being newly converted to electronic form, > >> I was wondering if anyone else had similar resolutions brought up in their > >> precinct, and if so, what was the result? The only concern raised against > >> mine was wondering what the potential cost would be, although I think we > >> have a solid argument there in that it would cost essentially nothing to > >> implement open formats in a forward-only manner, and the real cost only > >> comes in with retroactively converting existing documents > ... > > Having said that, however, we need to be careful when we talk about > > costs. There certainly will be a cost involved in such a conversion, > > not in the cost of the format or of the software to produce documents > > in that format, but in terms of training. Like it or not, there are > > differences in the applications that support open formats and those > > that don't and those differences will have to be trained before users > > are fully accepting of the new applications and their new formats. > > Keep in mind, however, that though some might not need training > for new versions of Microsoft Office, many do. And that training costs > are not limited to initial product roll out. There are many factors to be > considered: > > - Initial and ongoing end user training > - Upgrades and patching > - Buying, managing, and tracking licenses > - Researching, interpreting, and compensating for changing licensing terms > - Negotiating pricing at time of purchase > > All of these take time and should be weighed on the cost side, > and I think there may be more. There are some of the same costs > for OpenOffice or similar products, but the purchasing and licensing > issues go out the window. > > It gets even more expensive if you want to convert documents, > for whatever reason. Unannounced, undercover document > conversion projects occur with almost every new version of > Microsoft Office. They show up in higher numbers of Microsoft > Office related trouble tickets, if nowhere else. > > > > > > > > > ------------------------------ > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > End of tclug-list Digest, Vol 38, Issue 6 > ***************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20080207/b81b76c9/attachment-0001.htm