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
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
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 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
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
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
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
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
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
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
"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,
"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
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
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
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:
"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
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
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
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
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 -
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.
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
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
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
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
25 matches
Mail list logo
