Re: /dev/serial/by-id

2025-01-07 Thread John Hasler
Max Nikulin writes: > Gene, my congratulations. You have managed to derail the discussion > another time. And you have managed to clutter the list with yet another pointless rant against Gene. Please put him in your killfile and move on. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: /dev/serial/by-id

2025-01-07 Thread Max Nikulin
On 07/01/2025 15:51, gene heskett wrote: stuck very early in the boot process waiting for orca to come alive. Gene, my congratulations. You have managed to derail the discussion another time. I suspect, this kind of deviations is the reason why you are so successful in earning bans. Good lu

Re: /dev/serial/by-id

2025-01-07 Thread Max Nikulin
On 1/7/25 06:01, Timothy M Butterworth wrote: I also ran into the Orca and brltty Hell problem Gene described Just a reminder: this thread started as "new computer arriving soon". Gene hijacked it and Orca is off-topic even in this subthread. Read the subject. Gene does not remember what he

Re: /dev/serial/by-id

2025-01-07 Thread gene heskett
On 1/7/25 06:01, Timothy M Butterworth wrote: On Tue, Jan 7, 2025 at 3:51 AM gene heskett wrote: On 1/6/25 22:13, Max Nikulin wrote: On 06/01/2025 14:09, gene heskett wrote: On 1/5/25 21:21, Max Nikulin wrote: On 05/01/2025 23:28, gene heskett wrote: As for bug number, I'm not the OP, ju

Re: /dev/serial/by-id

2025-01-07 Thread Anssi Saari
Max Nikulin writes: > On 04/01/2025 17:19, gene heskett wrote: >> One does get tired and short tempered when a copy/paste error post >> bullseye that wrecks udev is said to not be fixed before >> trixie. Thats not excusable when the fix is a one line patch we've >> all done years ago. Get it from

Re: /dev/serial/by-id

2025-01-07 Thread gene heskett
On 1/6/25 22:13, Max Nikulin wrote: On 06/01/2025 14:09, gene heskett wrote: On 1/5/25 21:21, Max Nikulin wrote: On 05/01/2025 23:28, gene heskett wrote: As for bug number, I'm not the OP, just a canary. Then ask the author to add the bug number. Tell them that without a link you were not b

Re: /dev/serial/by-id

2025-01-06 Thread Max Nikulin
On 06/01/2025 14:09, gene heskett wrote: On 1/5/25 21:21, Max Nikulin wrote: On 05/01/2025 23:28, gene heskett wrote: As for bug number, I'm not the OP, just a canary. Then ask the author to add the bug number. Tell them that without a link you were not be able to check current state of affa

Re: /dev/serial/by-id

2025-01-05 Thread gene heskett
On 1/5/25 21:21, Max Nikulin wrote: On 05/01/2025 23:28, gene heskett wrote: As for bug number, I'm not the OP, just a canary. Then ask the author to add the bug number. Tell them that without a link you were not be able to check current state of affairs and, as a result, you have secured

Re: /dev/serial/by-id

2025-01-05 Thread Max Nikulin
On 05/01/2025 23:28, gene heskett wrote: As for bug number, I'm not the OP, just a canary. Then ask the author to add the bug number. Tell them that without a link you were not be able to check current state of affairs and, as a result, you have secured your reputation as a liar.

Re: /dev/serial/by-id (was: Re: new computer arriving soon)

2025-01-05 Thread gene heskett
On 1/4/25 22:54, Max Nikulin wrote: On 04/01/2025 17:19, gene heskett wrote: One does get tired and short tempered when a copy/paste error post bullseye that wrecks udev is said to not be fixed before trixie. Thats not excusable when the fix is a one line patch we've all done years ago. Get