Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Johnathan Mantey wrote: Notice that it makes a 'by-id' entry. It also makes a 'by-uuid', which may be more interesting for this use case. Johnathan, Yes, using the UUID would be better, but my understanding is that is unique to each device so it's not generic for any portalble USB drive. Thanks, Rich
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Johnathan Mantey wrote: No you don't. The /lib/udev/rules.d has a rule that fully populates the /dev/disk subdirectory with the same name and same information on each boot. This should be everything you need to use fstab directly. Johnathan, Then I'm not understanding. Here, /run/udev/rules.d/ was empty until I added some. When I reboot this desktop and insert a thumb drive the kernel might see it as /dev/sdg (which is what's in /etc/fstab) or /dev/sdh (which isn't in /etc/fstab.) Thanks, Rich
Re: [PLUG] Brave Browser Video Issue
On 3/25/24 12:53, Dick Steffens wrote: Turns out that's the same version I have on my machine that is working, so maybe something else is causing the problem. The next thing I'm thinking of doing is a total uninstall of brave on one of the non-working machines, and then a fresh install. I'll try that after lunch. I tried: sudo apt remove brave-browser sudo apt purge brave-browser sudo apt install brave-browser Problem remains. What else could be interfering with video in brave-browser? -- Regards, Dick Steffens
[PLUG] has anyone come across this problem? (and how to fix it?)
I have an HP Office Jet Pro 8600-N ink-jet printer, and used the HP Office Jet Device Management Program under linux. (HPLIP) to handle the print queue. Sometimes I sent a print job from a LibreOffice document to this printer, but forgot that my system is not currently connected to the LAN network, so naturally things halt and I get a message that the printer has been placed in "pause" mode and to reactivate it. Unfortunately, the printer configuration is written over and the "set default printer" checkbox is turned off and the printer is removed from default category. I am forced to go to the Yast2 manager and reedit the printer configuration and turn on the "make default printer" check box again. This is time consuming and it takes about 3 mins for the Yast2 program to run through all the printer drivers (must be thousands) Has anyone figured out how to avoid having the printer removed as default printer when the system is not connected to the LAN and a print command is issued? Randall
Re: [PLUG] something I am considering doing...
Paul: I tried to keep it simple on my end with just the ELF-64 file description. When I first saw all the scripts and other items pop-up under the category "executable" I was dismayed for awhile, but decided to keep it to that known file type which definitely IS an executable. This trimmed the files down from the 600K to the 14K or so (on my system) Randall On 3/25/24 07:19, Paul Heinlein wrote: On Sun, 24 Mar 2024, American Citizen wrote: Paul: Thanks for your post. Exactly what would you consider a valid statement for locating the executables? Finding executable files is not, to my mind, the same as find executable files for which I'd expect a man page. I'd suppose expect a man page for most occupants of * /bin * /usr/bin * /usr/sbin * /sbin Some denizens of /usr/libexec might warrant man pages too. One problem is that a lot of files in /usr/bin are symlinks or wrapper scripts; I'm not sure there's any "right" way to deal with them. Another problem is utilities that are often superceded by shell builtin commands. Most people don't run /usr/bin/test; they use the shell builtin 'test' or '['. So a man page for /usr/bin/test might be deceptive if its operations are not identical with those of your shell. Yet another problem is with schemes like /etc/alternatives that map a common utility name to a specific release. Different distributions handle alternatives differently; I don't have a suse system, so you'd need to look at your own setup to see what alternatives can be set there. I guess this is my long-winded way of saying that I'm not sure I know how I'd go about identifying "executables I should reasonably expect to have a man page" on my systems.
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Johnathan Mantey wrote: I found the rules I was after /lib/udev/rules.d These rules create a device for my USB drive here: /dev/disk/by-id/usb-JetFlash_Transcend_8GB_B101484C-0:0 Johnathan, Yes, I can create a udev rule file that has the vendor and ID for each USB pen drive I have, Currently about a dozen. Which means that each time I acquire a new one, or use one from someone else, I need to enter a new line in that .rules file. That's no different from tailing /var/log/messages and having root mount the drive. Regards, Rich
Re: [PLUG] Brave Browser Video Issue
On 3/25/24 11:03, Michael Ewan wrote: I followed these steps when Brave on Mint was telling me to update but Mint said that it was the latest version. sudo apt install curl sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg echo "deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main"|sudo tee /etc/apt/sources.list.d/brave-browser-release.list sudo apt update sudo apt install brave-browser Attempted to follow the above, but it thinks the latest version is what is installed. rsteff@ThinkCentre-M58p:~$ sudo apt install brave-browser Reading package lists... Done Building dependency tree Reading state information... Done brave-browser is already the newest version (1.64.109). The following packages were automatically installed and are no longer required: gir1.2-goa-1.0 gnome-software-common libappstream-glib8 libfwupdplugin1 libgspell-1-2 libgspell-1-common libllvm10 libxmlb1 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. rsteff@ThinkCentre-M58p:~$ Turns out that's the same version I have on my machine that is working, so maybe something else is causing the problem. The next thing I'm thinking of doing is a total uninstall of brave on one of the non-working machines, and then a fresh install. I'll try that after lunch. -- Regards, Dick Steffens
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Rich Shepard wrote: Nothing useful there. I can plug in a drive and have fdisk -l identify the Actually, that's `tail -f /var/log/messages.' And rebooting the machine returned the USB port to /dev/sdg. Rich
Re: [PLUG] Assigning labels to USB pen drives
I found the rules I was after /lib/udev/rules.d These rules create a device for my USB drive here: /dev/disk/by-id/usb-JetFlash_Transcend_8GB_B101484C-0:0 On Mon, Mar 25, 2024 at 12:22 PM MC_Sequoia wrote: > "Clarification: how to mount any inserted USB pen drive on /media/thumb." > > Sounds like you want to create a custom mount point for your USB thumb > drives? > > If so, This should walk you through the steps. > https://linuxconfig.org/howto-mount-usb-drive-in-linux > >
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, MC_Sequoia wrote: Sounds like you want to create a custom mount point for your USB thumb drives? If so, This should walk you through the steps. https://linuxconfig.org/howto-mount-usb-drive-in-linux Mike, Nothing useful there. I can plug in a drive and have fdisk -l identify the drive numer then have root mount it. No different from what I've done for years. The point of creating a udev rule is to have the kernel recognize the drive regardless of its loading order and using that information to mount it on /media/thumb/. Regards, Rich
Re: [PLUG] Linux man pages and documentation?
"I will leave aside the fact that no one submits an executable file to Linux; each distribution (Red Hat, Debian, etc) picks the executable files to include with the Linux kernel." Ah,so executable files are only developed and maintained by the Linux kernel team? If I were to write an app, ROFL!, but for the sake of discussion, I'd rely on already established executable files that are hopefully documented enough for me to hook into? And not every executable is worthy of its own manual page? And the Linux kernel team makes the decision on how exes are documented or if documented?
Re: [PLUG] Assigning labels to USB pen drives
"Clarification: how to mount any inserted USB pen drive on /media/thumb." Sounds like you want to create a custom mount point for your USB thumb drives? If so, This should walk you through the steps. https://linuxconfig.org/howto-mount-usb-drive-in-linux
Re: [PLUG] Linux man pages and documentation?
On Mon, 25 Mar 2024, MC_Sequoia wrote: "I was surprised to find < 15% of the command executables were documented. Naturally I was hoping for something like 50% to 75%." I'm starting a new thread from Randall's thread about man pages, because I'm getting lost and confused with all the scripting and I'm kind of stuck on one very simple common sense idea and that is, how can anyone submit an executable file to Linux without documentation? I will leave aside the fact that no one submits an executable file to Linux; each distribution (Red Hat, Debian, etc) picks the executable files to include with the Linux kernel. Here's one scenario where several executable files have no documentation. The Texinfo suite, usually accessed via /usr/bin/info, includes a program called /usr/sbin/fix-info-dir. It's a shell script that replaces missing menu items in info sections. The script has a --help option, but no man page. It's there mostly for developers who are writing info pages, not for users. Python's pydoc utility sort of falls into this category too. Similarly, the "less" pager distribution often includes a shell script called lesspipe.sh. The latter has no man page, though its use is documented in the main less man page. There are other application suites, like git, that come with several example or template executables; none has a man page and, honestly, who would write a man page for a sample program? Other program suites like sudo include, e.g., /usr/libexec/sudo/sesh, which I can only imagine to be some sort of helper program for the main sudo application, but sesh is otherwise undocumented. The same is true of the grcat and pwcat utilities distributed with gawk. The dovecot imap/pop server goes hog-wild in this manner! -- Paul Heinlein heinl...@madboa.com 45°22'48" N, 122°35'36" W
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Rich Shepard wrote: Now the last step: How do I modify /etc/fstab so it lets me read and write to any pen drive inserted in a USB port? Clarification: how to mount any inserted USB pen drive on /media/thumb. Rich
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Rich Shepard wrote: But, inserting and removing a USB pen drive does not add new lines to /tmp/udev.log. Well! The web pages on udev rules were incomplete. The correct command is udevadm control --reload-rules This works. I wrote 41-usb-permissions.rules: SUBSYSTEM=="usb", MODE:="0666" When I insert and remove different pen drives the action is recorded in /tmp/udev.log. Now the last step: How do I modify /etc/fstab so it lets me read and write to any pen drive inserted in a USB port? Rich
[PLUG] Linux man pages and documentation?
"I was surprised to find < 15% of the command executables were documented. Naturally I was hoping for something like 50% to 75%." I'm starting a new thread from Randall's thread about man pages, because I'm getting lost and confused with all the scripting and I'm kind of stuck on one very simple common sense idea and that is, how can anyone submit an executable file to Linux without documentation? Maybe I don't really understand what the OP is seeing as a problem or is actually trying to do? According to the Linux Man-Pages Project there are actually missing man pages - https://www.kernel.org/doc/man-pages/missing_pages.html Is the goal of the OP to try and solve this problem through the use of AI? This isn't a question of an executable file not being documented, but just having a man page, which I thought would be requirement for an executable file submitted but apparently isn't. Sent with [Proton Mail](https://proton.me/) secure email.
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Rich Shepard wrote: But, inserting and removing a USB pen drive does not add new lines to /tmp/udev.log. Very interesting update. Advice on udev web sites I read say to reboot the host rather than running `udevadm control --reload'. So I rebooted. The two rules in /run/udev/rules.d/ are gone! WTF? Rich
Re: [PLUG] Brave Browser Video Issue
I followed these steps when Brave on Mint was telling me to update but Mint said that it was the latest version. sudo apt install curl sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg echo "deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main"|sudo tee /etc/apt/sources.list.d/brave-browser-release.list sudo apt update sudo apt install brave-browser On Mon, Mar 25, 2024 at 10:38 AM Dick Steffens wrote: > On 3/25/24 05:30, David Fleck wrote: > > Try hamburger -> Help -> About > > Thanks. > > Unfortunately, I don't find anything there to help me force an update. I > have four machines running either Xubuntu 20.04, or 22.04. Two of the > machines, one of each version, have updated brave successfully. Two of > them, running 20.04, updated in a way that I get a white window instead > of video. If I hover over the progress bar, I see a thumbnail of the > video, and audio is working. But I don't see the video. The two machines > where video is working updated twice, the first time breaking video, and > the second time fixing it. From that I conclude that the two machines > that are still broken need to be forced to update again. None of the > links I've found offer a way to manually update brave. Any ideas how to > fix this? > > -- > Regards, > > Dick Steffens >
Re: [PLUG] Brave Browser Video Issue
On 3/25/24 05:30, David Fleck wrote: Try hamburger -> Help -> About Thanks. Unfortunately, I don't find anything there to help me force an update. I have four machines running either Xubuntu 20.04, or 22.04. Two of the machines, one of each version, have updated brave successfully. Two of them, running 20.04, updated in a way that I get a white window instead of video. If I hover over the progress bar, I see a thumbnail of the video, and audio is working. But I don't see the video. The two machines where video is working updated twice, the first time breaking video, and the second time fixing it. From that I conclude that the two machines that are still broken need to be forced to update again. None of the links I've found offer a way to manually update brave. Any ideas how to fix this? -- Regards, Dick Steffens
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Johnathan Mantey wrote:
My initial reaction would be to look at creating UDEV rules for those
devices.
Reading several udev-related web pages I created two shell scripts installed
in /usr/local/bin and rule 80-test.rules in /run/udev/rules.d
- device_added.sh -
#!/usr/bin/bash
echo "USB device added at $(date)" >>/tmp/udev.log
--
- device_removed.sh -
#!/usr/bin/bash
echo "USB device removed at $(date)" >>/tmp/udev.log
--
- 80-test.rules -
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
RUN+="/bin/device_added.sh"
SUBSYSTEM=="usb", ACTION=="remove", ENV{DEVTYPE}=="usb_device",
RUN+="/bin/device_removed.sh"
--
Inserting a USB pen drive no /tmp/scripts.log was created. I touched that
filename and reran `udevadm control --reload' but /tmp/scripts.log was
empty. As root, directly running the two device files in /usr/local/bin
added the proper content.
But, inserting and removing a USB pen drive does not add new lines to
/tmp/udev.log.
Advice needed.
Rich
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Johnathan Mantey wrote: I can't remember if the results are enumerated in the /lib directory. You may want to spend a few web searches seeing if you can find where they live. Johnathan, On my Slackware hosts they're in /run/udev, but the rules.d/ subdirectory is empty. Huh! Earlier releases had content there. Regards, Rich
Re: [PLUG] Assigning labels to USB pen drives
On Mon, 25 Mar 2024, Johnathan Mantey wrote: My initial reaction would be to look at creating UDEV rules for those devices. Assuming they are well behaved and have unique USB serial numbers you should be able to craft rules that will create consistent /dev symbolic links to wherever the kernel places them. There's also a very extensive set of existing UDEV rules that enumerate USB devices as fully as they can. I can't remember if the results are enumerated in the /lib directory. You may want to spend a few web searches seeing if you can find where they live. Thanks, Johnathan. Rich
[PLUG] Assigning labels to USB pen drives
For permanently attached drives I've assigned their PARTUUID to mount them in /etc/fstab. With 6 continuosly attached drives (/dev/sda-/dev/sdf) portable USB drives were seen as either /dev/sdg or /dev/sdg1 and that's how they're mounted in /etc/fstab. Yesterday afternoon the kernel decided to see these pen drives as /dev/sdh and /dev/sdh1. How can I assign a generic pen drive label in /etc/fstab so any pen drive inserted in a USB port on a host so it can be mounted on /media/thumb or /media/stick depending on how that brand of pen drive is seen? TIA, Rich
Re: [PLUG] something I am considering doing...
On Sun, 24 Mar 2024, American Citizen wrote: Paul: Thanks for your post. Exactly what would you consider a valid statement for locating the executables? Finding executable files is not, to my mind, the same as find executable files for which I'd expect a man page. I'd suppose expect a man page for most occupants of * /bin * /usr/bin * /usr/sbin * /sbin Some denizens of /usr/libexec might warrant man pages too. One problem is that a lot of files in /usr/bin are symlinks or wrapper scripts; I'm not sure there's any "right" way to deal with them. Another problem is utilities that are often superceded by shell builtin commands. Most people don't run /usr/bin/test; they use the shell builtin 'test' or '['. So a man page for /usr/bin/test might be deceptive if its operations are not identical with those of your shell. Yet another problem is with schemes like /etc/alternatives that map a common utility name to a specific release. Different distributions handle alternatives differently; I don't have a suse system, so you'd need to look at your own setup to see what alternatives can be set there. I guess this is my long-winded way of saying that I'm not sure I know how I'd go about identifying "executables I should reasonably expect to have a man page" on my systems. -- Paul Heinlein heinl...@madboa.com 45°22'48" N, 122°35'36" W
Re: [PLUG] Brave Browser Video Issue
Try hamburger -> Help -> About -- - David Fleck On Monday, March 25th, 2024 at 12:20 AM, Dick Steffens wrote: > On 3/23/24 21:59, Dick Steffens wrote: > > > I've just run the latest updates from Ubuntu for my Xubuntu machines, > > which included Brave browser. In each case, video does no longer > > display. Audio works, and is the audio for the video I'm trying to > > watch. I can successfully watch the same URL with Firefox, so I'm > > assuming something went wrong with the Brave update. > > > > And it appears that they've heard from other folks, because I just had > > another update notice that included Brave. After running that, video > > works again. > > > > If it happened to you, wait a bit and try again. It will probably fix > > itself. > > > One of my machines provided a link to run the update again, but two > others did not. I have unsuccessfully looked for how to force an update > using Xubuntu. Both machines are running Xubuntu 20.04. The machine that > called for another update, the one that fixed the video problem, is > running Xubuntu 22.04. Looking online for how to update Brave tells me > to click on the hamburger button, and then on about, but the window > brought up by the hamburger button does not have an about link. > > Ideas on what to do next will be appreciated. > > -- > Regards, > > Dick Steffens
