"Peter Davoust" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sun, 20 Aug 2006 18:02:20 +0000:
> Sorry, I didn't realise. I'm only semi-hardcore. First: What is kill > file, and second, by mail label do you mean, like "To: John Doe > <[EMAIL PROTECTED]>" or something else I'm not familiar with? Basically, > is this a good e-mail? Yes. (There's the thing about top posting, but while that can be irritating, it's not a security issue so is seen as comparatively minor. That said, http://www.blakjak.demon.co.uk/gey_stv0.htm does a good job of explaining it. Top posting is irritating because it makes it hard to reply or to follow the context, but it's potentially security related like HTML is, so it's not nearly as bad, nor does it usually mean kill filing, tho someone might choose to simply skip responding to a particular post if it's too hard to rearrange context to make the reply look right.) Kill file is the filtering mechanism many mail and news clients have. To "kill file" someone (also known as "filtering", as in "to filter someone out") means creating an entry that hides their messages so they aren't seen, either marking them as read, or deleting them from one's local client entirely (they still get to other users who've not kill filed, however), like one might do with spam, or other messages one doesn't want to see or bother with. The name comes from the fact that in many clients, there's a separate file that contains all these entries. BTW and conversely, it's also possible to "watch" a poster, that is, score their posts up so they stand out from others, to be viewed first. Some clients will put kills (also called ignores) and watches in the same file, but it's only called kill filing when the posts are ignored, not when they are watched. The reference to mail labels was a bit confusing, sorry. There could have been a comma between mail, and labels. Thus, "Choosing HTML for your mail, labels you [as a newbie or a spammer/cracker]". "Labels" can thus be read as "makes you look like" -- HTML messages make you look like a newbie, or a spammer or cracker. > By the way, I tried to use digikam with a digital camera (big suprise > there) and it couldn't find the device. I added myself to the plugdev > group, still nothing. Now I'm thinking that that's a different issue, > because it doesn't actually hotplug the device. I'll play with kernel > options and get back to you again. One thing that's useful with USB is to check dmesg (type dmesg at the command prompt), aka the kernel log. When you plug something in, or on boot if it's plugged in on boot, the kernel log should detect the device plugged in and load or activate the appropriate driver, as necessary. If there's no logged response at all (the device isn't detected), it normally indicates the kernel's core USB drivers aren't working right, so it can't see anything on the USB at all. If it detects the device plugged in, saying something about what it is, but doesn't mention loading drivers for it, it usually means USB is working but the kernel can't find an appropriate driver to load for that particular device. (Note that some devices have user-space not kernel drivers. This is most often the case with scanners and printers.) HTH (Hope that helps.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
