Re: TCPA
On Sun, Nov 03, 2002 at 12:19:44PM -0500, Noah L. Meyerhans wrote: > The only negative thing I see comming out of TCPA is that content > producers (Hollywood, etc) will release copies of their > movies/music/whatever for download in a format that can only be accessed > on TCPA systems. This is the major threat. Personally, I would not be > bothered by this. I am, because it goes a bit further than that. In the U.S., RIAA is a subsidized group. There are specific taxes on recording media which are paid to high profile members of this business. Congress has routinely been rewriting copyright law to make the terms of this law more favorable to members of this business. Congress has also passed some broadly scoped laws favoring those who dominate this industry (http://www.riaa.org/Copyright-Laws-4.cfm). Basically, there's a lot of complexity here, and uless we can express the underlying concepts clearly and meaningfully to an otherwise uncaring public I think we can anticipate an ever increasing flood of random restrictions on the legality of software development. I don't think that TCPA will kill open software. But I do think that it's part of an ongoing effort to erode the freedoms which are behind open software. FYI, -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PLEASE: standard package README file/orientation
From: Steve Greenland <[EMAIL PROTECTED]> > > ... Current policy > > requires that /usr/doc/ exist (possibly as a symlink to > > /usr/share/doc/). On Wed, Aug 23, 2000 at 07:17:32PM -0400, Daniel Barclay wrote: > Then why don't more package implement that policy? Please give some examples of packages which do not? > > > Debian packages don't provide that orientation reliably at all. > > > > ls -l /usr/doc/foo > > dpkg -L foo |grep bin > > dpkg -L foo |grep man > > dpkg -L foo |grep info > > > > works for *every* package. (Yes, I know it would be more efficient > > to combine into one dpkg -L command, I left it as an exercise for the > > reader.) > > If Debian really thinks that is sufficient, then this is hopeless. Actually, I'd say that grep bin/ would be better than grep bin (without the slash). Similarly, for documentation, you might want to use something like egrep 'man/|info/|doc/'. Or, failing that, do a web search on the topic you're interested in. I agree that we could do better about indexing or cross indexing our documentation. But anything better than grepping the list of files provided by the package really has to be done on a case-by-case basis. [Do you understand why? It's because further improvements must be in the form of better content.] -- Raul
Need help configuring postfix
Hi, I'm probably just being stupid, but I can't figure out how to configure postfix. How do you configure postfix so that most of the time mail is delivered directly, but some of the time it's delivered to a specific smtp server. Also, it must deliver most mail in my primary mail domain remotely -- unless there's a local email username which corresponds to the local part of the email address, those should be delivered locally. So, [EMAIL PROTECTED] is delivered locally, and [EMAIL PROTECTED] but [EMAIL PROTECTED] is delivered remotely to the mx for domain.org. [Also, I need to be able to run a script which toggles delivery of remote messages between the usual mx rules and smarthost rules, but that's not so urgent.] I could probably figure this out if I sat down with the documentation for a while and played with it, but at the moment I don't have an environment where it's very safe to experiment. [It's got some tools installed on it which I need to address some other problems, but it's sending mail to root which winds up going to a number of people.] Thanks, -- Raul
Re: New dpkg upload - please test!
On Thu, Oct 14, 1999 at 06:14:15PM +1000, Hamish Moffatt wrote: > To what end? No offence is intended to any maintainers, but > some of the splits lately seem a bit pointless to me. After recent > runs of 'apt-get dist-upgrade', I've been left without telnet, > ftp and rlogin; these are so small it hardly seems worth the > effort of separating them. In addition to the tip by Wichert, I'd like to warn that apt-get dist-upgrade is designed to uninstall less important packages if that would let a more important package upgrade to a new version. In my opinion, these semantics are only worthwhile on a relatively new installation where you're trying to work out the wrinkles. apt-get upgrade semantics are considerably safer. -- Raul
umich ldap and ms outlook ...?
Has anyone gotten the umich ldap client to talk to an ms outlook ldap server? It's not working right for me, and I don't know if it's my own stupidity or outlooks. Thanks, -- Raul
Re: Package maintainer script policy.
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> amazed Raul, of all people, had to have this pointed out to him.
I fail to see that you've demonstrated that ${1+"$@"} is different
from "$@" for any posix shell. Which, I thought, was the issue we
were talking about.
--
Raul
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Package maintainer script policy.
Manoj Srivastava <[EMAIL PROTECTED]> wrote: > Well, if $@ is empty, "$@" expands to ""; Is this mandated by the posix standard? If so, this is an example of how debian's current /bin/sh is not posix. If not, then this is just plain bogus. -- Raul -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: GREAT NEWS!!! Oracle 8 on Linux by 1999!
Jorge Sousa <[EMAIL PROTECTED]> wrote: > Want a good RDBMS for Linux??? Also, postgresql is a part of debian 2.0. [If you want high performance, you'll need to change /etc/postgresql/postmaster.init so that it has PGFSYNC=no]. -- Raul -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
Pat Kennedy <[EMAIL PROTECTED]> wrote: > Just from the point of view of a typical user, eg, me just doing > a quick scan of the debian-user archives doesn't take all that long. > They're very up-to-date, usually just a day or so behind. Browsing > the archives with navigator presents a nice threaded layout, easily > scanned in a few minutes. Besides, you might actually learn something > in spite of yourself. And if you find an answer, you'll conserve Net > bandwidth + make it easier for the next user to perhaps find HIS > answer in the > 100 emails/per day posted to debian-user. Certainly. And, if it's feasable to check the bug archives, you should check those as well. http://www.debian.org/Bugs (skip down a bit, enter the package name, then browse). But that's a recommendation, not an iron-clad rule. Once you've successfully reported some real bugs, I think we should trust your judgement some, too. If you find yourself in the akward position of having information that looks like a significant bug, but not having a system which is capable of checking the bug-tracking system for outstanding reports against that bug, it's sometimes still worthwhile filing that bug report. There's a certain amount of judgement that's required here. For example, if it's something that's likely to hurt someone else, it's much more important than if it's something that won't hurt anyone and is easy to work around. Good luck, -- Raul -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
Dale Scheetz <[EMAIL PROTECTED]> writes: > > Well, I disagree with this point of view. Yes, Debian wishes to support > > newcomers to Linux. That is why we have debian-user. We have a > > responsibility to those new users to "train" them to be "free" users. > > They can only do that if they become familiar with the ins and outs of the > > "Debian Way". John Goerzen <[EMAIL PROTECTED]> wrote: > But by actually submitting a bug report in the first place, they're > already helping. The maintainer can either fix it or open a dialogue > up with the submitter if more information is needed. Slow down folks. [Er... except on getting hamm released.] Dale is talking from the viewpoint of being libc maintainer. John is talking about the application view of the system. In general, I agree with John's point of view. However, before reporting that something about libc is broken, it's worthwhile doing a certain amount of research. [If you find that the point you're researching is undocumented, or that the documentation doesn't adequately describe the situation, that may itself be a bug, of course.] That said, "info libc" doesn't even mention the debian bug tracking system, let alone that the web pages should be consulted before reporting a bug on libc. -- Raul -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: LyX
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > PS when you tell me where it is on your ftp site, and I find it, I'll know > I went temporally insane. I haven't checked the ftp site, but my copy of lyx is marked as coming from "contrib/text". I expect that the copyright doesn't let us distribute it properly. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian from the Stampede's POV
> On Sat, 23 May 1998 16:25:46 +1000, Anthony Towns wrote: > >The "other data" in Debian's case is stuff like dependency information, > >installation and removal scripts, and the maintainer's contact address. Steve Lamb <[EMAIL PROTECTED]> wrote: > Proprietary to Debian... Note to self: The debian administrator's guide needs an appendix on broken-system maneuvers. This would, after appropriate disclaimers, delve into the file formats of the current packaging system for cases where the files have been damaged, and/or where the dpkg suite isn't available. Make sure to discuss issues not handled by these techniques, and make sure to reference the chapter on how to write bug reports (since presumably something would be broken for these techniques to be needed). [As so many people have already pointed out that ar is not proprietary to Debian, I hope I don't have to delve further into this issue at this time.] -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian from the Stampede's POV
Steve Lamb <[EMAIL PROTECTED]> wrote: > Then why discredit the idea, then point out all the niceties in your > current prefered system when they aren't comparable at all? For what it's worth, the debian control information has always been present in tgz format, never in binary format. The old .deb files required a shell script and dd to extract the .tgz files, but it wasn't a very complicated shell script. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New ae uploaded to Incoming
Dale Scheetz <[EMAIL PROTECTED]> wrote: > While I can add this binding back into the ae.rc file with no > difficulties, and probably should. It is exactly those function keys that > these keybinding are supposed to be fixing. There are many terminals > without function keys, all send a control key... There aren't many control keys. Maybe control-t (teach)? Control-e (explain) might also be viable, but normally, it's end-of-line in emacs. [Control-t is transpose in emacs, and ae doesn't need to support that.] -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New ae uploaded to Incoming
Dale Scheetz <[EMAIL PROTECTED]> wrote: > Well, the choice I made was not all that correct either. The correct > choice would be a C-H sequence of some sort, but this is problematical at > several levels. C-? is fine for those environments where it's not DEL, but the proper way to implement help has all unbound keys suggest the cannonical help key (for example: "press F1 for help"). -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's the storywith 2.0?
Bill Leach <[EMAIL PROTECTED]> wrote: > I am a bit frustrated with hamm right now. As of just before hamm went from > 'unstable' to 'frozen' almost every upgrade on my PC box 'breaks something'. > I was literally 'spoiled' by the fact that during the last 6+ months of > development under unstable Debian hamm was more 'solid' than probably any > other Linux. Likewise. I've got some boxes I put together using "unstable", and I don't trust "frozen" enough to upgrade them. I was hoping to upgrade them before release, but it looks like that's just not going to happen. I don't think we can do much for hamm, but I'd like to see some "burn in boxes" to aid in testing packages before release for slink. I'll see if I can come up with one myself... -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Beowulf
Camm Maguire <[EMAIL PROTECTED]> wrote: > I would greatly appreciate any advice from the readers of this list on > what hardware would be best for this project. This is the first time I've seen somebody mention putting together a debian beowulf system. I suspect you'd do better asking the beowulf people... [I don't even know if gigabit ethernet drivers are stable yet.] That said, I've been itching for an excuse to work on this kind of system. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Poor interaction between chown and quota
Pete Templin <[EMAIL PROTECTED]> wrote: > This would solve problem 2, but not problem 1. I have a wonderful > workaround for problem 2: NFS mount /var/spool/mail on another server, > install qpopper, and change the IP address of pop.jdweb.com. However, > this only works if management & store staff (which are the same two > people) used the correct hostnames in everyone's setup. :) nfs semantics does unpleasant things for a mail spool. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Roxen packaged (web server)
Martin Schulze <[EMAIL PROTECTED]> wrote: > There is one thing that could be done better. Roxen is the only > webserver that comes as a Debian package but does not server port 80 > by default. You *have* to configure it by hand - i.e. by your > favourite browser. This might be considered a feature, as it allows some other web server to be installed on the same machine as Roxen. -- Raul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
xterm subtleties
I'm trying to configure xterm so that, for example, the screen isn't restored after exiting less. >From reading the manual page, I'd expect that a resource of the form *titeInhibit: True or *TiteInhibit: True would do the trick. However, this doesn't seem to have any effect. Anyone know if there's a way of doing this (without recompiling either less or xterm)? Thanks, -- Raul
Re: dselect complaints
Craig Sanders: > If you write a python-tk interface for dselect, maybe somebody > could use your python code as a basis for writing a perl-tk > interface... Aside: compared to the volume of stuff needed to use tk reasonably (enough X to do other tasks reasonably in the same environment), python is rather tiny. -- Raul
Re: dselect complaints
William S. Gribble: > If you don't want feedback about the tools, might I suggest that > you give up their maintenance to someone who does? Dselect as it > exists is nothing more or less than a working prototype of the tool > it needs to be. That's not the point. Ian has had feedback. Lot's of feedback. Lots, and lots of feedback. The issues are well known (and he pointed this out in his email message). He's also asked for help on dealing with some of the issues. I don't know how much he's gotten. This is a big project, and some of these issues are non-trivial. Giving up completely at the first sign of difficulty isn't going to solve anything. If you want to help, I think you ought to be able to without having Ian stop working on that part of the project. IF it turns out that someone else is capable of managing dpkg/dselect and is doing significant development, etc., *then* is the time to talk about Ian stepping out of the way. At the moment, Ian is about as obstructionist as a fifteen lane through-way (and heading the right way). -- Raul
Checking if the network is up
Luis Francisco Gonzalez: > Is there any way of checking whether the network is responding so > that I only run popclient when it is? That usually depends on what exactly you mean by "the network". If you're using diald or some such, take a look at the result of `route`. If the network is always "logically up" on your machine, but frequently not "physically up" you'll need to probe for a response from some remote system. Take a look at the man page for ping and read about the -c and -n options. You'll need to run grep on the result because the presence or absence of a remote host won't affect ping's return code. -- Raul
Re: How to remove a user?
Andreas Wehler > A> After searching a while for a program or script to completely > A> remove a user I didn't found something and did it per hand. Is > A> this neccessary? Thanks. Removing a user is something that should be done with thought. In some circumstances (user never existed), it's just a matter of removing the user's home directory and the entries in /etc/passwd and /etc/group. Other times (when the user really exists) it may be more appropriate to change the user's shell to /bin/false (or something hand crafted along the lines of /usr/local/bin/why-your-account-is-turned-off-user) for a period of time before removing stuff. Also, if the user really existed, there may be files outside the home directory that also need to be dealt with (e.g. /var/spool/mail/user, or /home/friend/shared/foo). What "dealt with" means depends on the situation... -- Raul
Re: smail 3.1.29.1-22 append_header="..." problem
Martin Alonso Soto Jacome: > > Speaking of junk e-mail, I did some more work on my junkmail > > daemon today. junkmail is an autoresponder I wrote to "deal with" > > the ever-increasing amount of unsolicited commercial email I > > receive every day. Instead of getting angry and writing a very > > nasty reply (usually starting off with F*** Off & Die), I just > > bounce it to user junkmail on my system, delete it and forget > > about it. I think this is a bad move for the case where email return address is forged and commercial email gives you an 800 number or some such. Best workaround I've been able to think up for the general case is to give people an md5-ish token based on their email address and some local bits. Set up an autoresponder to hand out tokens (so only people with valid return addresses can get them) and bounce messages through the autoresponder if they don't have a good token. Unfortunately, this is more appropriate to mailing lists than personal messages. [Mailing list can remind user of their token in every message -- X-Token: (or Token: if IANA approves).] On the third hand, most of the spams I've examined recently have had unforged return addresses. And an argument could be made that use of an forged return address by a commercial entity for advertising purposes is false advertising (and thus subject to legal action). -- Raul
