[PLUG] Clinic - other dates? PLUG Digest, Vol 81, Issue 25

wes plug at the-wes.com
Sun Jun 19 09:59:24 PDT 2011


The Clinic is hosted on the third Sunday of each month from 1pm-5pm.

-wes

On Sun, Jun 19, 2011 at 9:49 AM, Bob Staser <bobstaser at gmail.com> wrote:

> Will there be another clinic hosted by PLUG in the near future?
> I have an LXE vehicle mount terminal that I'd like some help with.
> I kinda threw out my back on Friday, and it's heavy enough that I' don't
> really want to lift it today.
> I looked at the Free Geek calendar, and they don't list today's clinic, or
> any others.
>
> Sorry if this is the wrong forum or format for my question, I'm new here.
>
> Thanks!
>
> Bob Staser
> bobstaser at gmail.com
>
> -----Original Message-----
> From: plug-bounces at lists.pdxlinux.org
> [mailto:plug-bounces at lists.pdxlinux.org] On Behalf Of
> plug-request at lists.pdxlinux.org
> Sent: Saturday, June 18, 2011 12:00 PM
> To: plug at lists.pdxlinux.org
> Subject: PLUG Digest, Vol 81, Issue 25
>
> Send PLUG mailing list submissions to
>        plug at lists.pdxlinux.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.pdxlinux.org/mailman/listinfo/plug
> or, via email, send a message with subject or body 'help' to
>        plug-request at lists.pdxlinux.org
>
> You can reach the person managing the list at
>        plug-owner at lists.pdxlinux.org
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of PLUG digest..."
>
>
> Today's Topics:
>
>   1. Re: Clinic! (Jeffery Mathis)
>   2. Re: Clinic! (John Jason Jordan)
>   3. Re: USB Serial Port Adapters (Fred James)
>   4. Re: USB Serial Port Adapters (Jason Barnett)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 17 Jun 2011 20:00:44 -0700
> From: Jeffery Mathis <jamathis79 at gmail.com>
> Subject: Re: [PLUG] Clinic!
> To: "General Linux/UNIX discussion and help,    civil and on-topic"
>        <plug at lists.pdxlinux.org>
> Message-ID: <BANLkTinX-_LbUXxe3LoCuUuYsQ50ZGCoWQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I would be interested in helping out.
> On Jun 17, 2011 4:05 PM, "John Jason Jordan" <johnxj at comcast.net> wrote:
> > Yes, it's this Sunday, June 19!
> >
> > Do you have a Linux computer that's being a brat? Bring it to the
> > Clinic!
> >
> > Do you have a computer you'd like to install Linux on but need some
> > hand-holding? Bring it to the Clinic!
> >
> > We have meece, keyboards and monitors, so if it's a desktop all you
> > need to bring is the box. We also have the latest versions of all
> > major distros. And we'll even have coffee and munchables.
> >
> > And if you know Linux and would like to help people with their Linux
> > problems, we need you too. In fact, we may be short on experts this
> > time, so your appearance would be welcome.
> >
> > Where?
> >
> > Free Geek, 1741 SE 10th Avenue, Portland 97214.
> >
> > When?
> >
> > 1 to 5 pm, Sunday, June 19, 2011.
> >
> > _______________________________________________
> > PLUG mailing list
> > PLUG at lists.pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 17 Jun 2011 20:18:30 -0700
> From: John Jason Jordan <johnxj at comcast.net>
> Subject: Re: [PLUG] Clinic!
> To: plug at lists.pdxlinux.org
> Message-ID: <20110617201830.1300ebcd at mailhost.pdx.edu>
> Content-Type: text/plain; charset=US-ASCII
>
> On Fri, 17 Jun 2011 20:00:44 -0700
> Jeffery Mathis <jamathis79 at gmail.com> dijo:
>
> >I would be interested in helping out.
>
> Terrific!
>
> No applications or approvals are required. Just show up.
>
> Hope to see you there!
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 17 Jun 2011 22:45:58 -0500
> From: Fred James <fredjame at fredjame.cnc.net>
> Subject: Re: [PLUG] USB Serial Port Adapters
> To: "General Linux/UNIX discussion and help; civil and on-topic"
>        <plug at lists.pdxlinux.org>
> Message-ID: <4DFC1F76.4020401 at fredjame.cnc.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Jackman wrote:
> > Why can't udev rules be applied here?
> >
> > On Fri, Jun 17, 2011 at 6:48 PM, Fred James <fredjame at fredjame.cnc.net>
> wrote:
> >
> >> Tim Wescott wrote:
> >>
> >>> (omissions for brevity)
> >>>   I did an experiment: I started with my Fax modem and the board I'm
> >>> developing plugged in.  I did ls /dev/ttyU*.
> >>> Then I unplugged the development board and did ls again.  Then I
> >>> plugged in a debugger that has its own USB serial port adapter, and
> >>> did ls again.  Here's my results:
> >>>
> >>> tim at servo:~$ ls /dev/ttyU*
> >>> /dev/ttyUSB0  /dev/ttyUSB1
> >>> tim at servo:~$ ls /dev/ttyU*
> >>> /dev/ttyUSB0
> >>> tim at servo:~$ ls /dev/ttyU*
> >>> /dev/ttyUSB0  /dev/ttyUSB1
> >>>
> >>> What _did_ happen is that at different times the same device --
> >>> ttyUSB1
> >>> -- got mapped to different physical devices.  That is what I _do
> >>> not_ want to happen.  What I want to happen is to plug in the
> >>> development board and have /dev/ttyUSBdevelop appear, and to plug in
> >>> the debugger and have /dev/ttyUSBdebug appear (or some similar
> me-defined mapping).
> >>> Different devices.  Different, _unique_, identifiers.
> >>>
> >>> Otherwise, every time I plug a bunch of stuff in to the machine, I'm
> >>> going to have to do a bunch of hand work to figure out what ports
> >>> map to what devices at the moment.
> >>>
> >>>
> >> Tim Wescott
> >> Thought 1:  If you can use CLI (command line interface) to determine
> >> what you need to know, then a (BASH) script can be written to do that.
> >> Thought 2:  If a device can be identified (example: ttyUSB1 is the
> >> debugger), then it can be mounted to a directory (example:
> >> ~/debugger) Thought 3:  If 1 and if 2, then the two can be written
> together in a script.
> >> Does any of that help?
> >> Regards
> >> Fred James
> >>
> Jackman
> According to <http://reactivated.net/writing_udev_rules.html#about>, it
> can
> ...
> "
>
> udev rules are flexible and very powerful. Here are some of the things you
> can use rules to achieve:
>
>    * Rename a device node from the default name to something else
>    * Provide an alternative/persistent name for a device node by
>      creating a symbolic link to the default device node
>    * Name a device node based on the output of a program
>    * Change permissions and ownership of a device node
>    * Launch a script when a device node is created or deleted
>      (typically when a device is attached or unplugged)
>    * Rename network interfaces
>
> "
> Regards
> Fred James
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 18 Jun 2011 09:49:01 -0700
> From: Jason Barnett <jason.barnett71 at gmail.com>
> Subject: Re: [PLUG] USB Serial Port Adapters
> To: "General Linux/UNIX discussion and help,    civil and on-topic"
>        <plug at lists.pdxlinux.org>
> Message-ID: <BANLkTi=36RjK7qKh4C=W7Z2oW1PgNhOSSQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Here is a link that gives an example of this exact situation.  The example
> shows using a FTDI chip and having the UDEV rule compare against the serial
> number of the device so it should work for specific devices.
>
> https://wiki.archlinux.org/index.php/Bus_pirate
>
> Jason
>
> On Fri, Jun 17, 2011 at 8:45 PM, Fred James
> <fredjame at fredjame.cnc.net>wrote:
>
> > Jackman wrote:
> > > Why can't udev rules be applied here?
> > >
> > > On Fri, Jun 17, 2011 at 6:48 PM, Fred James
> > > <fredjame at fredjame.cnc.net>
> > wrote:
> > >
> > >> Tim Wescott wrote:
> > >>
> > >>> (omissions for brevity)
> > >>>   I did an experiment: I started with my Fax modem and the board
> > >>> I'm developing plugged in.  I did ls /dev/ttyU*.
> > >>> Then I unplugged the development board and did ls again.  Then I
> > plugged
> > >>> in a debugger that has its own USB serial port adapter, and did ls
> > >>> again.  Here's my results:
> > >>>
> > >>> tim at servo:~$ ls /dev/ttyU*
> > >>> /dev/ttyUSB0  /dev/ttyUSB1
> > >>> tim at servo:~$ ls /dev/ttyU*
> > >>> /dev/ttyUSB0
> > >>> tim at servo:~$ ls /dev/ttyU*
> > >>> /dev/ttyUSB0  /dev/ttyUSB1
> > >>>
> > >>> What _did_ happen is that at different times the same device --
> > >>> ttyUSB1
> > >>> -- got mapped to different physical devices.  That is what I _do
> > >>> not_ want to happen.  What I want to happen is to plug in the
> > >>> development board and have /dev/ttyUSBdevelop appear, and to plug
> > >>> in the debugger and have /dev/ttyUSBdebug appear (or some similar
> me-defined mapping).
> > >>> Different devices.  Different, _unique_, identifiers.
> > >>>
> > >>> Otherwise, every time I plug a bunch of stuff in to the machine,
> > >>> I'm going to have to do a bunch of hand work to figure out what
> > >>> ports map
> > to
> > >>> what devices at the moment.
> > >>>
> > >>>
> > >> Tim Wescott
> > >> Thought 1:  If you can use CLI (command line interface) to
> > >> determine what you need to know, then a (BASH) script can be written
> to
> do that.
> > >> Thought 2:  If a device can be identified (example: ttyUSB1 is the
> > >> debugger), then it can be mounted to a directory (example:
> > >> ~/debugger) Thought 3:  If 1 and if 2, then the two can be written
> > >> together in a
> > script.
> > >> Does any of that help?
> > >> Regards
> > >> Fred James
> > >>
> > Jackman
> > According to <http://reactivated.net/writing_udev_rules.html#about>,
> > it can ...
> > "
> >
> > udev rules are flexible and very powerful. Here are some of the things
> > you can use rules to achieve:
> >
> >    * Rename a device node from the default name to something else
> >    * Provide an alternative/persistent name for a device node by
> >      creating a symbolic link to the default device node
> >    * Name a device node based on the output of a program
> >    * Change permissions and ownership of a device node
> >    * Launch a script when a device node is created or deleted
> >      (typically when a device is attached or unplugged)
> >    * Rename network interfaces
> >
> > "
> > Regards
> > Fred James
> >
> > _______________________________________________
> > PLUG mailing list
> > PLUG at lists.pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> >
>
>
> ------------------------------
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
>
> End of PLUG Digest, Vol 81, Issue 25
> ************************************
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>



More information about the PLUG mailing list