Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #248672

Re: had another crash, reboot usb failed, powerdown reboot usb failed

Show all headers | View raw

On Thursday, 2 June 2022 10:39:33 EDT gene heskett wrote:
> On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote:
> > gene heskett <gheskett@shentel.net> writes:
> > > Do I have to reset those perms everytime I'm forced to reboot,
> > > which
> > > is usually in 5 to 10 days. Or is there someplace in
> > > /lib/udev/rules.d where I can fix this until the next udev update?
> > 
> > It seems almost certain the permissions for /dev/ttyUSB* won't stick,
> > unless you fix them with udev rules (or some other means but udev's
> > the tool for the job in my opinion).
> > 
> > Do you really want to set all ttyUSB* to 777? Not 666 or 660 for
> > example? The usual way is to apply a udev rule to a specific USB
> > product and vendor ID which you can get from lsusb. But to change
> > permissions on device files I think you can do
> > 
> > KERNEL=="ttyUSB*", MODE="0777"
> > 
> > in a udev rule file.
> 
> /dev/ttyUSB* seems to only apply to seriel adapters, which I have two
> of. One driving a cm11a interface to talk to C10 stuff, and one
> driving a ups.

Darn typus, that s/b X10 above, not C10. Short/fat ancient finger 
syndrome.

> Thank you Anssi. Take care and stay well.
> 
> Cheers, Gene Heskett.


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-05-31 09:30 +0200
  Re: had another crash, reboot usb failed, powerdown reboot usb failed "Andrew M.A. Cater" <amacater@einval.com> - 2022-05-31 22:30 +0200
    Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-01 06:30 +0200
      Re: had another crash, reboot usb failed, powerdown reboot usb failed David Wright <deblis@lionunicorn.co.uk> - 2022-06-01 07:00 +0200
        Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-01 07:30 +0200
          Re: had another crash, reboot usb failed, powerdown reboot usb failed David Wright <deblis@lionunicorn.co.uk> - 2022-06-01 22:40 +0200
            Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 01:40 +0200
              Re: had another crash, reboot usb failed, powerdown reboot usb failed David Wright <deblis@lionunicorn.co.uk> - 2022-06-02 17:10 +0200
                Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 18:00 +0200
            Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 04:50 +0200
              Re: had another crash, reboot usb failed, powerdown reboot usb failed Anssi Saari <as@sci.fi> - 2022-06-02 10:10 +0200
                Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 16:40 +0200
                Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 17:50 +0200
                Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 17:50 +0200

csiph-web