[gentoo-amd64] USB-Serial Follow Up

[gentoo-amd64] USB-Serial Follow Up

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

Ok, so now the connection is working, but booting kstars as root is a bad
idea, so how do I get permissions to /dev/ttyUSB0? I've done it once, but
being the clutz I am, I've forgotten. Can someone please pass on some noob
instructions for changing the permissions of a device on hotplug?

Thanks,
-Peter

[-- Attachment #2: Type: text/html, Size: 319 bytes --]

Re: [gentoo-amd64] USB-Serial Follow Up

[felix]

On Fri, Aug 18, 2006 at 04:07:31AM +0000, Peter Davoust wrote:
> Ok, so now the connection is working, but booting kstars as root is a bad
> idea, so how do I get permissions to /dev/ttyUSB0? I've done it once, but
> being the clutz I am, I've forgotten. Can someone please pass on some noob
> instructions for changing the permissions of a device on hotplug?

KERNEL=="ttyUSB3",      NAME="ttyUSB%n", OWNER="nut", GROUP="usb", MODE="0660", SYMLINK="tts/USB%n"

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] USB-Serial Follow Up

[felix]

On Thu, Aug 17, 2006 at 11:30:02PM -0700, felix@crowfix.com wrote:
> On Fri, Aug 18, 2006 at 04:07:31AM +0000, Peter Davoust wrote:
> > Ok, so now the connection is working, but booting kstars as root is a bad
> > idea, so how do I get permissions to /dev/ttyUSB0? I've done it once, but
> > being the clutz I am, I've forgotten. Can someone please pass on some noob
> > instructions for changing the permissions of a device on hotplug?
> 
> KERNEL=="ttyUSB3",      NAME="ttyUSB%n", OWNER="nut", GROUP="usb", MODE="0660", SYMLINK="tts/USB%n"

I forgot to add, this is in my /etc/udev/rules.d/10-udev.rules file.
I don't know if that is a good place or bad place, but it works for me.

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: USB-Serial Follow Up

[Duncan]

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0608172107y3686a483wee43281ad3e60959@mail.gmail.com, excerpted
below, on  Fri, 18 Aug 2006 04:07:31 +0000:

> Ok, so now the connection is working, but booting kstars as root is a bad
> idea, so how do I get permissions to /dev/ttyUSB0? I've done it once, but
> being the clutz I am, I've forgotten. Can someone please pass on some noob
> instructions for changing the permissions of a device on hotplug?

This should point you in the right direction:

$grep ttyUSB /etc/udev/rules.d/*
/etc/udev/rules.d/50-udev.rules:KERNEL=="ttyUSB[0-9]*", NAME="%k", SYMLINK="tts/USB%n", GROUP="tty", MODE="0660"


-- 
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

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: USB-Serial Follow Up

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Ok, so I added myself to the tty group, and I'll try the device again later
tonight.

Thanks,
-Peter

On 8/18/06, Duncan <1i5t5.duncan@cox.net> wrote:
>
> "Peter Davoust" <worldgnat@gmail.com> posted
> 7c08b4dd0608172107y3686a483wee43281ad3e60959@mail.gmail.com, excerpted
> below, on  Fri, 18 Aug 2006 04:07:31 +0000:
>
> > Ok, so now the connection is working, but booting kstars as root is a
> bad
> > idea, so how do I get permissions to /dev/ttyUSB0? I've done it once,
> but
> > being the clutz I am, I've forgotten. Can someone please pass on some
> noob
> > instructions for changing the permissions of a device on hotplug?
>
> This should point you in the right direction:
>
> $grep ttyUSB /etc/udev/rules.d/*
> /etc/udev/rules.d/50-udev.rules:KERNEL=="ttyUSB[0-9]*", NAME="%k",
> SYMLINK="tts/USB%n", GROUP="tty", MODE="0660"
>
>
> --
> 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
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1658 bytes --]

[gentoo-amd64] Re: Re: USB-Serial Follow Up

[Duncan]

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0608180627l9421cefub2160ac60766fe5d@mail.gmail.com, excerpted
below, on  Fri, 18 Aug 2006 13:27:46 +0000:

> Ok, so I added myself to the tty group, and I'll try the device again
> later tonight. <br><br>Thanks,<br>-Peter<br><br><div><span
> class="gmail_quote">
[snip]

Let us know how it goes.

BTW, please use text-only, not HTML, when replying to the list.  I know
you are using gmail, but many of us don't view this list using our
browser and choose not to use an HTML parsing client for security reasons.
In such clients, HTML looks ugly.  As well, choosing HTML for your
mail labels you (to those who care enough about their security to have
made such choices, call us paranoid in return if you wish) at best someone
who doesn't know about the security issues (a newbie), at worst, a
spammer/cracker trying to exploit them to your own ends.  Some choose to
kill file it and/or those who use it automatically, but I try to ask
nicely first, choosing to believe the best until proven otherwise, only
kill filing if the request is ignored.

-- 
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

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Re: USB-Serial Follow Up

[Peter Davoust]

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
<j.doe@gmail.com>" or something else I'm not familiar with? Basically,
is this a good e-mail? 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.

On 8/18/06, Duncan <1i5t5.duncan@cox.net> wrote:
> "Peter Davoust" <worldgnat@gmail.com> posted
> 7c08b4dd0608180627l9421cefub2160ac60766fe5d@mail.gmail.com, excerpted
> below, on  Fri, 18 Aug 2006 13:27:46 +0000:
>
> > Ok, so I added myself to the tty group, and I'll try the device again
> > later tonight. <br><br>Thanks,<br>-Peter<br><br><div><span
> > class="gmail_quote">
> [snip]
>
> Let us know how it goes.
>
> BTW, please use text-only, not HTML, when replying to the list.  I know
> you are using gmail, but many of us don't view this list using our
> browser and choose not to use an HTML parsing client for security reasons.
> In such clients, HTML looks ugly.  As well, choosing HTML for your
> mail labels you (to those who care enough about their security to have
> made such choices, call us paranoid in return if you wish) at best someone
> who doesn't know about the security issues (a newbie), at worst, a
> spammer/cracker trying to exploit them to your own ends.  Some choose to
> kill file it and/or those who use it automatically, but I try to ask
> nicely first, choosing to believe the best until proven otherwise, only
> kill filing if the request is ignored.
>
> --
> 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
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: USB-Serial Follow Up

[Duncan]

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0608201102v84e9115w821e629a293d0674@mail.gmail.com, 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
> <j.doe@gmail.com>" 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

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: USB-Serial Follow Up

[Peter Davoust]

Yeah, I did a dmesg right after I plugged it in, and there was no
mention of the device being created, yet it registered a new usb 2.0
device, so that's why I think it's kernel related. I'm emergeing
kontact right now so I can get better control over who gets html and
who gets plain text. Is quoted text annoying/unsafe too? I never liked
it but I just ignore it since I got gmail.

Thanks,
-Peter
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: USB-Serial Follow Up

[Duncan]

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0608201511k2c68fb0fqed8044e79234940d@mail.gmail.com, excerpted
below, on  Sun, 20 Aug 2006 22:11:30 +0000:

> Yeah, I did a dmesg right after I plugged it in, and there was no
> mention of the device being created, yet it registered a new usb 2.0
> device, so that's why I think it's kernel related.

OK, it's registering the plug event, so at least you got that far and know
the hardware and kernel USB itself is working.

Somewhere along the line, I either missed a post of yours (there's
something going on with Gentoo's mailing list server, many people are
missing posts here and there,
see http://bugs.gentoo.org/show_bug.cgi?id=141904 ), or otherwise haven't
seen the specific device information.  Could you (again?) post the dmesg
output from when it registers the device, what lsusb says about it, and if
that doesn't make it clear, exactly what the hardware is (brand and model
number, short description).

The reason I'm  asking is that with it being detected, we know it's
actually getting to there.  However, some USB devices (like scanners) have
userspace drivers and thus wouldn't load or have a kernel driver.  I want
to see if I can verify that one way or the other, so we know whether to
even look for a kernel device load event, or whether we should be looking
at user space instead.  I want to see this thru to working, but I'm about
at the end of my ability to help with generic level information, so I need
to know a bit more about what the actual device is, and somehow I haven't
picked that up yet. <g>

> I'm emergeing kontact right now so I can get better control over who gets
> html and who gets plain text. Is quoted text annoying/unsafe too? I
> never liked it but I just ignore it since I got gmail.

Quoted text... shouldn't be unsafe.  It can be annoying if done
incorrectly, but isn't unsafe so at least that's not a problem.  The link
I gave you explained it some, but let me try as well.

The idea with quoting is to quote enough context so people know what point
you are replying to, replying to each point after quoting it, as I'm doing
here quoting you by point, replying to each under it.  Ideally, some of
your reply should always be visible -- if the quote block takes up an
entire page with none of your reply visible, you are quoting too much.  If
the point you are replying to is that large a block, try snipping out
irrelevant parts or summarizing, shrinking the quote or summary until your
reply to it, or your reply to the previous point, is always visible.
(There may be occasional exceptions, say when quoting part of a log or
config file, where the information may not be snippable or summarizable
without losing critical information.)

Some people complain that this is too much effort, that it takes too long.
List/group veterans will say no it doesn't, that the process of editing
the quote to the point one is addressing forces one to think more directly
about that point, thus often making one's own thoughts clearer on it,
making the reply better and easier than it would have been otherwise. 
This is in addition to clarifying to the future reader exactly what points
one was replying to, thus reducing confusion.  Additionally, it is said
too many people speak (or in context post) on impulse.  If one doesn't
have the time to properly quote, it can be asked if they really should be
replying at all.  Sometimes it's better not to.  (It's not unusual for me
to type up a reply, and then decide it's really better if I don't send it,
or decide it's not what I wanted to say after all, and that I have to
rewrite it before I can send it.)

-- 
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

-- 
gentoo-amd64@gentoo.org mailing list