Re: [DNG] USB mount problem

[aitor]

Hi Steve,


En 20 de junio de 2021 23:09:42 Steve Litt  
escribió:



How can I
download, compile and install *hopman* on my existing Void Linux
computer?


I have trouble with my network connection at home; so, a short comment from 
my mobile:


After several failed attempts trying to build hopman under Void Linux 
during last weekend, finally i decided to replace the use of CMake by the 
classic GNU Autotools. My configure.ac and Makefile.am files build the 
whole project -at least in Devuan-, including Didier's interface (in Gtk+) 
and mine (in Gtkmm) at the same time, and linking succesfully against the 
required libraries. I'll get around to build hopman in Void when I have time.


Cheers,

Aitor.




Enviado con Aqua Mail para Android
https://www.mobisystems.com/aqua-mail
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Michael Neuffer]

On 6/27/21 11:28 AM, Arnt Karlsen wrote:

It is always been;

  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade
and occasionally one of the upgrades will suggest
  sudo apr autoremove

..playing around with all the "apt family members" helps you find
solutions whenever any of the members fails to solve a dependency
etc puzzle.

..pick a favorite goto member and use that as your "daily driver"
to keep your apt depencency puzzle database manageable, and keep
yourself proficient on the other members so you can use those to
find solutions whenever your goto member fails to solve a puzzle.



And don't forget the trusty old dselect

To this day it is my main tool.

One of the most important behavioral differences between the

dselect and apt  descendants is that the dselect dependency solver will 
remove packages by default, while apt solvers do not.



Cheers

  Mike

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Arnt Karlsen]

On Sun, 27 Jun 2021 00:18:41 +1000, terryc wrote in message 
<20210627001841.1966c...@dragonfly.woa.com.au>:

> On Sat, 26 Jun 2021 13:33:56 +0200
> "d...@d404.nl"  wrote:
> >
> > The right command is  apt full-upgrade.
> > 
> > The main difference between full-upgrade and upgrade is
> > full-upgrade also delete dependencies which are no longer used.

..doh!

> > I guess that the older version apt-get dist-upgrade does do
> > something similar.  
> 
> Weirdly, I've never heard of apt full-upgrade.

..possibly a case of not paying attention when reading manpages, 
or in my case today, not reading all of todays posts in this 
thread before posting on things I didn't recall. ;oD

> It is always been;
>  sudo apt-get update
>  sudo apt-get upgrade
>  sudo apt-get dist-upgrade
> and occasionally one of the upgrades will suggest
>  sudo apr autoremove 

..playing around with all the "apt family members" helps you find
solutions whenever any of the members fails to solve a dependency
etc puzzle.

..pick a favorite goto member and use that as your "daily driver" 
to keep your apt depencency puzzle database manageable, and keep 
yourself proficient on the other members so you can use those to 
find solutions whenever your goto member fails to solve a puzzle.

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[terryc]

On Sat, 26 Jun 2021 13:33:56 +0200
"d...@d404.nl"  wrote:

> On 26-06-2021 11:45, o1bigtenor via Dng wrote:
> > On Fri, Jun 25, 2021 at 6:10 PM Patrick Bartek via Dng
> >  wrote:  
> >> On Fri, 25 Jun 2021 11:34:32 +0200
> >> Alessandro Vesely via Dng  wrote:
> >>  
> >>> On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote:  
>  I have found that each desktop uses its own method of
>  automounting. PCManFM may have the mounting code built-in. Or it
>  may use udiskie. Check PCManFM's dependencies and see if udiskie
>  is listed. Did you install udiskie yourself? If not, then some
>  other app did and it's probably needed. If it's not causing
>  problems, leave it be.  
> >>>
> >>> Right.  For spacefm it is udevil.
> >>>
> >>> Curiously, spacefm was mounting smoothly until yesterday, on
> >>> chimaera
> >>> + openbox.  After I did a system upgrade, I couldn't mount an USB
> >>> key any more, until I manually installed udevil.  What happened,
> >>> dependency changes?  
> >> This is one of the "gotchas" that can happen when running an "in
> >> development" version.  As far as why it happen: could be a number
> >> of things.  Most of the time, it's because a dependency, like
> >> udevil to spacefm, become mismatched version-wise.  That is,
> >> udevil has become "too old" to work with spacefm, and the upgrade
> >> process uninstalls it. Try "full-grade" instead of just "upgrade"
> >> to get the newer version of the dependencies when "upgrading." In
> >> fact, this is the recommended procedure when running an "in
> >> development" or testing version. 
> > Please - - - not understanding the command(s) suggested.
> > I usually use :
> > # apt update
> > # apt upgrade
> >
> > so you're suggesting the use of
> > # apt update
> > # apt full-grade
> > or is that
> > # apt full-upgrade?
> >
> > TIA  
> 
> The right command is  apt full-upgrade.
> 
> The main difference between full-upgrade and upgrade is full-upgrade 
> also delete dependencies which are no longer used. I guess that the 
> older version apt-get dist-upgrade does do something similar.

Weirdly, I've never heard of apt full-upgrade.

It is always been;
 sudo apt-get update
 sudo apt-get upgrade
 sudo apt-get dist-upgrade
and occasionally one of the upgrades will suggest
 sudo apr autoremove 




> 
> Grtz
> 
> Nick
> 
> 

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Sat, 26 Jun 2021 04:45:46 -0500
o1bigtenor  wrote:

> On Fri, Jun 25, 2021 at 6:10 PM Patrick Bartek via Dng
>  wrote:
> >
> > On Fri, 25 Jun 2021 11:34:32 +0200
> > Alessandro Vesely via Dng  wrote:
> >  
> > > On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote:  
> > > >
> > > > I have found that each desktop uses its own method of
> > > > automounting. PCManFM may have the mounting code built-in. Or
> > > > it may use udiskie. Check PCManFM's dependencies and see if
> > > > udiskie is listed. Did you install udiskie yourself? If not,
> > > > then some other app did and it's probably needed. If it's not
> > > > causing problems, leave it be.  
> > >
> > >
> > > Right.  For spacefm it is udevil.
> > >
> > > Curiously, spacefm was mounting smoothly until yesterday, on
> > > chimaera
> > > + openbox.  After I did a system upgrade, I couldn't mount an USB
> > > key any more, until I manually installed udevil.  What happened,
> > > dependency changes?  
> >
> > This is one of the "gotchas" that can happen when running an "in
> > development" version.  As far as why it happen: could be a number of
> > things.  Most of the time, it's because a dependency, like udevil to
> > spacefm, become mismatched version-wise.  That is, udevil has become
> > "too old" to work with spacefm, and the upgrade process uninstalls
> > it. Try "full-grade" instead of just "upgrade" to get the newer
> > version of the dependencies when "upgrading." In fact, this is the
> > recommended procedure when running an "in development" or testing
> > version. 
> 
> Please - - - not understanding the command(s) suggested.
> I usually use :
> # apt update
> # apt upgrade
> 
> so you're suggesting the use of
> # apt update
> # apt full-grade
> or is that
> # apt full-upgrade?
> 
> TIA

full-upgrade.  Sorry. Or

apt-get dist-upgrade

will accomplish the same thing.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[d...@d404.nl]

On 26-06-2021 11:45, o1bigtenor via Dng wrote:

On Fri, Jun 25, 2021 at 6:10 PM Patrick Bartek via Dng
 wrote:

On Fri, 25 Jun 2021 11:34:32 +0200
Alessandro Vesely via Dng  wrote:


On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote:

I have found that each desktop uses its own method of automounting.
PCManFM may have the mounting code built-in. Or it may use udiskie.
Check PCManFM's dependencies and see if udiskie is listed. Did you
install udiskie yourself? If not, then some other app did and it's
probably needed. If it's not causing problems, leave it be.


Right.  For spacefm it is udevil.

Curiously, spacefm was mounting smoothly until yesterday, on chimaera
+ openbox.  After I did a system upgrade, I couldn't mount an USB key
any more, until I manually installed udevil.  What happened,
dependency changes?

This is one of the "gotchas" that can happen when running an "in
development" version.  As far as why it happen: could be a number of
things.  Most of the time, it's because a dependency, like udevil to
spacefm, become mismatched version-wise.  That is, udevil has become
"too old" to work with spacefm, and the upgrade process uninstalls it.
Try "full-grade" instead of just "upgrade" to get the newer version of
the dependencies when "upgrading." In fact, this is the recommended
procedure when running an "in development" or testing version.


Please - - - not understanding the command(s) suggested.
I usually use :
# apt update
# apt upgrade

so you're suggesting the use of
# apt update
# apt full-grade
or is that
# apt full-upgrade?

TIA


The right command is  apt full-upgrade.

The main difference between full-upgrade and upgrade is full-upgrade 
also delete dependencies which are no longer used. I guess that the 
older version apt-get dist-upgrade does do something similar.


Grtz

Nick




OpenPGP_signature
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[o1bigtenor via Dng]

On Sat, Jun 26, 2021 at 5:03 AM Alessandro Vesely via Dng
 wrote:
>
> On Sat 26/Jun/2021 11:45:46 +0200 o1bigtenor wrote:
> > so you're suggesting the use of
> > # apt update
> > # apt full-grade
> > or is that
> > # apt full-upgrade?
>
> apt-get dist-upgrade?
>
Methinks that's something else again - - - - but - - - I'm getting
confused!!!

When I look up the man page for apt - - - h - - - its now apt-rpm
and last updates are from 2008 (just a wee while ago). Can't seem to
find anything
somewhat contemporary - - - - - hm - - - - - just quite confused!!!

Regards
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Alessandro Vesely via Dng]

On Sat 26/Jun/2021 11:45:46 +0200 o1bigtenor wrote:

so you're suggesting the use of
# apt update
# apt full-grade
or is that
# apt full-upgrade?


apt-get dist-upgrade?


Best
Ale
--

















___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[o1bigtenor via Dng]

On Fri, Jun 25, 2021 at 6:10 PM Patrick Bartek via Dng
 wrote:
>
> On Fri, 25 Jun 2021 11:34:32 +0200
> Alessandro Vesely via Dng  wrote:
>
> > On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote:
> > >
> > > I have found that each desktop uses its own method of automounting.
> > > PCManFM may have the mounting code built-in. Or it may use udiskie.
> > > Check PCManFM's dependencies and see if udiskie is listed. Did you
> > > install udiskie yourself? If not, then some other app did and it's
> > > probably needed. If it's not causing problems, leave it be.
> >
> >
> > Right.  For spacefm it is udevil.
> >
> > Curiously, spacefm was mounting smoothly until yesterday, on chimaera
> > + openbox.  After I did a system upgrade, I couldn't mount an USB key
> > any more, until I manually installed udevil.  What happened,
> > dependency changes?
>
> This is one of the "gotchas" that can happen when running an "in
> development" version.  As far as why it happen: could be a number of
> things.  Most of the time, it's because a dependency, like udevil to
> spacefm, become mismatched version-wise.  That is, udevil has become
> "too old" to work with spacefm, and the upgrade process uninstalls it.
> Try "full-grade" instead of just "upgrade" to get the newer version of
> the dependencies when "upgrading." In fact, this is the recommended
> procedure when running an "in development" or testing version.
>

Please - - - not understanding the command(s) suggested.
I usually use :
# apt update
# apt upgrade

so you're suggesting the use of
# apt update
# apt full-grade
or is that
# apt full-upgrade?

TIA
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Fri, 25 Jun 2021 11:34:32 +0200
Alessandro Vesely via Dng  wrote:

> On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote:
> > 
> > I have found that each desktop uses its own method of automounting.
> > PCManFM may have the mounting code built-in. Or it may use udiskie.
> > Check PCManFM's dependencies and see if udiskie is listed. Did you
> > install udiskie yourself? If not, then some other app did and it's
> > probably needed. If it's not causing problems, leave it be.  
> 
> 
> Right.  For spacefm it is udevil.
> 
> Curiously, spacefm was mounting smoothly until yesterday, on chimaera
> + openbox.  After I did a system upgrade, I couldn't mount an USB key
> any more, until I manually installed udevil.  What happened,
> dependency changes?

This is one of the "gotchas" that can happen when running an "in
development" version.  As far as why it happen: could be a number of
things.  Most of the time, it's because a dependency, like udevil to
spacefm, become mismatched version-wise.  That is, udevil has become
"too old" to work with spacefm, and the upgrade process uninstalls it.
Try "full-grade" instead of just "upgrade" to get the newer version of
the dependencies when "upgrading." In fact, this is the recommended
procedure when running an "in development" or testing version.

B 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Alessandro Vesely via Dng]

On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote:


I have found that each desktop uses its own method of automounting.
PCManFM may have the mounting code built-in. Or it may use udiskie.
Check PCManFM's dependencies and see if udiskie is listed. Did you
install udiskie yourself? If not, then some other app did and it's
probably needed. If it's not causing problems, leave it be.



Right.  For spacefm it is udevil.

Curiously, spacefm was mounting smoothly until yesterday, on chimaera + 
openbox.  After I did a system upgrade, I couldn't mount an USB key any more, 
until I manually installed udevil.  What happened, dependency changes?



Best
Ale
--












___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Didier Kryn]

Le 23/06/2021 à 14:38, Dr. Nikolaus Klepp a écrit :
> Anno domini 2021 Wed, 23 Jun 13:34:39 +0200
>  Didier Kryn scripsit:
>> Le 23/06/2021 à 12:49, Dr. Nikolaus Klepp a écrit :
>>> Anno domini 2021 Wed, 23 Jun 12:16:50 +0200
>>>  Didier Kryn scripsit:
 [...]
     There is no other way to know which partitions are mounted or not
 than read /proc/self/mounts. inotify does not work on pseudo-filesystems
 like /sys or /proc. Therefore, either this is done by the front-end or
 by the back-end.
>>> Oh, inotifywatch perfectly works on /sys and /dev when you are root, in 
>>> fact that's what I use as part of my automounter when I run fvwm:
>>     Of course it works on /dev; tmpfs and devtmpfs behave like real
>> filesystems. This is what Hopman is based on (~:
>>
>>     Hopman isn't root, doesn't need to be, and shouldn't be. And inotify
>> doesn't work on /proc (at least for non-root).
> Well, inotifywait does work  on /dev /sys and /proc for non-root, too. At 
> least it does here on chimaera. Just try these:
>
> $ inotifywait -rm /proc/
> $ inotifywait -rm /sys/devices/pci*
>
> What does not work is /sys/block, but that's a cosmetic problem, as you alway 
> can watch for /sys and fiilter the output.
    I don't need to poll or watch /sys. I browse it when inotify tells
me something about /dev, to see if it is a partition and if it is removable.
>
> How does hopman differ from e.g. "inotifywait -rm /dev/disk" or "inotifywait 
> -rm /dev/block" + some lines of shell magic to get a nice output? 
    Because It does it all in just one single process and also browses
/sys to filter events as explained above and all the rest of the work:
display the status, collect mouse-clicks, launch helpers, wait() them,
display their error messages, all asynchrohously. It is easy to make a
toy script to play with it but really unpractical to do a complete job.
> If polling /proc/self/mounts is required, where is the point in not polling 
> /sys/block/sd*/removable, too?

    1st because polling one file only is less load for the system; 2nd
because when there are no removable device in the system, then there is
no need to poll it, and this is most of the time. As long as there is no
removable device, Hopman is sleeping 100% the time, except briefly when
a file is created/deleted in /dev.

    Reading /proc/self/mounts is triggered by an alarm which is enabled
only when there is a removable device in the system.

--     Didier

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Dr. Nikolaus Klepp]

Anno domini 2021 Wed, 23 Jun 13:34:39 +0200
 Didier Kryn scripsit:
> Le 23/06/2021 à 12:49, Dr. Nikolaus Klepp a écrit :
> > Anno domini 2021 Wed, 23 Jun 12:16:50 +0200
> >  Didier Kryn scripsit:
> >> [...]
> >>     There is no other way to know which partitions are mounted or not
> >> than read /proc/self/mounts. inotify does not work on pseudo-filesystems
> >> like /sys or /proc. Therefore, either this is done by the front-end or
> >> by the back-end.
> > Oh, inotifywatch perfectly works on /sys and /dev when you are root, in 
> > fact that's what I use as part of my automounter when I run fvwm:
> 
>     Of course it works on /dev; tmpfs and devtmpfs behave like real
> filesystems. This is what Hopman is based on (~:
> 
>     Hopman isn't root, doesn't need to be, and shouldn't be. And inotify
> doesn't work on /proc (at least for non-root).

Well, inotifywait does work  on /dev /sys and /proc for non-root, too. At least 
it does here on chimaera. Just try these:

$ inotifywait -rm /proc/
$ inotifywait -rm /sys/devices/pci*

What does not work is /sys/block, but that's a cosmetic problem, as you alway 
can watch for /sys and fiilter the output.

How does hopman differ from e.g. "inotifywait -rm /dev/disk" or "inotifywait 
-rm /dev/block" + some lines of shell magic to get a nice output? If polling 
/proc/self/mounts is required, where is the point in not polling 
/sys/block/sd*/removable, too?


Nik



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Didier Kryn]

Le 23/06/2021 à 12:49, Dr. Nikolaus Klepp a écrit :
> Anno domini 2021 Wed, 23 Jun 12:16:50 +0200
>  Didier Kryn scripsit:
>> [...]
>>     There is no other way to know which partitions are mounted or not
>> than read /proc/self/mounts. inotify does not work on pseudo-filesystems
>> like /sys or /proc. Therefore, either this is done by the front-end or
>> by the back-end.
> Oh, inotifywatch perfectly works on /sys and /dev when you are root, in fact 
> that's what I use as part of my automounter when I run fvwm:

    Of course it works on /dev; tmpfs and devtmpfs behave like real
filesystems. This is what Hopman is based on (~:

    Hopman isn't root, doesn't need to be, and shouldn't be. And inotify
doesn't work on /proc (at least for non-root).

--     Didier

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Dr. Nikolaus Klepp]

Anno domini 2021 Wed, 23 Jun 12:16:50 +0200
 Didier Kryn scripsit:
> [...]
>     There is no other way to know which partitions are mounted or not
> than read /proc/self/mounts. inotify does not work on pseudo-filesystems
> like /sys or /proc. Therefore, either this is done by the front-end or
> by the back-end.

Oh, inotifywatch perfectly works on /sys and /dev when you are root, in fact 
that's what I use as part of my automounter when I run fvwm:

# # inotifywait -rm /sys/
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/sys/class/ OPEN,ISDIR power_supply
/sys/class/power_supply/ OPEN,ISDIR 
/sys/class/ ACCESS,ISDIR power_supply
/sys/class/power_supply/ ACCESS,ISDIR 
/sys/class/ ACCESS,ISDIR power_supply
/sys/class/power_supply/ ACCESS,ISDIR 
/sys/class/ CLOSE_NOWRITE,CLOSE,ISDIR power_supply
/sys/class/power_supply/ CLOSE_NOWRITE,CLOSE,ISDIR 
/sys/devices/system/cpu/cpufreq/policy0/ OPEN scaling_cur_freq
/sys/devices/system/cpu/cpufreq/policy0/ ACCESS scaling_cur_freq
/sys/devices/system/cpu/cpufreq/policy0/ CLOSE_NOWRITE,CLOSE scaling_cur_freq
/sys/class/ OPEN,ISDIR power_supply
/sys/class/power_supply/ OPEN,ISDIR 
...

# inotifywait -rm /dev/char/
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/dev/char/ CREATE 189:135
/dev/char/ CREATE 188:0
/dev/char/ ATTRIB 189:135
...

# inotifywait -rm /dev/block
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/dev/block/ CREATE 8:16
/dev/block/ CREATE 8:18
/dev/block/ CREATE 8:17
/dev/block/ ATTRIB 8:17
...

Nik



> 
> 
> >
> >>     Both Hopman-cli and the GUI must read hopmanrc at startup (it seems
> >> simpler to have a single file to configure both). Possibly the name of
> >> the GUI application might be specified in hopmanrc and Hopman-cli would
> >> launch it.
> > What's configurable in hopmanrc? Shouldn't it "just work" for all 
> > partitions/devices? The GUI part most likely will need some config, e.g 
> > automounting certain devices/partitions etc.
> 
>     hopmanrc provides a lot of possiblities to parameterise the
> application, such as window appearance, behaviour and position, location
> of pid-file and helper applications to mount/umount/open/eject
> partitions/devices.
> 
> --     Didier
> 
> 
> 
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Didier Kryn]

Le 23/06/2021 à 11:50, Dr. Nikolaus Klepp a écrit :
> Hi!
>
> Anno domini 2021 Wed, 23 Jun 00:00:11 +0200
>  Didier Kryn scripsit:
>> Le 22/06/2021 à 19:10, Steve Litt a écrit :
>> [...]
>>     Hopman-cli would write to the pipe 3 sorts of messages, with all the
>> necessary details:
>>
>> - a device special file associated to a removable partition has been
>> detected in /dev
>> - a symlink has been detected in /dev/disk/by-label, pointing to a
>> removable partition
>> - a device special file associated to a removable partition has been
>> removed
> IMO this sounds good. I would just make it react on all partitions, not only 
> the removable: there are broken devices out in the wild that lie about their 
> removability. And there are devices that have wrong entries in the hw 
> database (e.g. old Casio cameras).

    No, Hopman should not show /home, /var, etc... Currently it relies
on /sys to tell which device is removable. Removable partitions might
also be declared in the config file as regular expressions.

>
> Oh, hopman would only send data, not receive from the client side, would it?
>
>> [...]
>>     Then it's up to the GUI application to
>>
>> - parse these messages, maintain and display a list of removable
>> partitions and their labels,
>> - on click, spawn helpers to mount/umount/open partitions and
>> potentially eject disks, check completion and report errors,
>> - periodically read /proc/self/mounts and report mountpoints of
>> removable partitions on the display.
> Why parse /proc/self/mounts? IMO it would make more sense if hopman-cli sends 
> " mounted on yyy" or "xxx unlounted" over the pipe, as it is already 
> monitoring stuff.

    There is no other way to know which partitions are mounted or not
than read /proc/self/mounts. inotify does not work on pseudo-filesystems
like /sys or /proc. Therefore, either this is done by the front-end or
by the back-end.


>
>>     Both Hopman-cli and the GUI must read hopmanrc at startup (it seems
>> simpler to have a single file to configure both). Possibly the name of
>> the GUI application might be specified in hopmanrc and Hopman-cli would
>> launch it.
> What's configurable in hopmanrc? Shouldn't it "just work" for all 
> partitions/devices? The GUI part most likely will need some config, e.g 
> automounting certain devices/partitions etc.

    hopmanrc provides a lot of possiblities to parameterise the
application, such as window appearance, behaviour and position, location
of pid-file and helper applications to mount/umount/open/eject
partitions/devices.

--     Didier




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Dr. Nikolaus Klepp]

Hi!

Anno domini 2021 Wed, 23 Jun 00:00:11 +0200
 Didier Kryn scripsit:
> Le 22/06/2021 à 19:10, Steve Litt a écrit :
> [...]
>     Hopman-cli would write to the pipe 3 sorts of messages, with all the
> necessary details:
> 
> - a device special file associated to a removable partition has been
> detected in /dev
> - a symlink has been detected in /dev/disk/by-label, pointing to a
> removable partition
> - a device special file associated to a removable partition has been
> removed

IMO this sounds good. I would just make it react on all partitions, not only 
the removable: there are broken devices out in the wild that lie about their 
removability. And there are devices that have wrong entries in the hw database 
(e.g. old Casio cameras).

Oh, hopman would only send data, not receive from the client side, would it?

> [...]
>     Then it's up to the GUI application to
> 
> - parse these messages, maintain and display a list of removable
> partitions and their labels,
> - on click, spawn helpers to mount/umount/open partitions and
> potentially eject disks, check completion and report errors,
> - periodically read /proc/self/mounts and report mountpoints of
> removable partitions on the display.

Why parse /proc/self/mounts? IMO it would make more sense if hopman-cli sends 
" mounted on yyy" or "xxx unlounted" over the pipe, as it is already 
monitoring stuff.

>     Both Hopman-cli and the GUI must read hopmanrc at startup (it seems
> simpler to have a single file to configure both). Possibly the name of
> the GUI application might be specified in hopmanrc and Hopman-cli would
> launch it.

What's configurable in hopmanrc? Shouldn't it "just work" for all 
partitions/devices? The GUI part most likely will need some config, e.g 
automounting certain devices/partitions etc.

Oh, udisksctl as mount-helper will make the job easy :)

Nik

> [...]



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Steve Litt]

Didier Kryn said on Wed, 23 Jun 2021 00:00:11 +0200

>Le 22/06/2021 à 19:10, Steve Litt a écrit :
>> Didier Kryn said on Tue, 22 Jun 2021 18:00:17 +0200
>>  
>>> Le 22/06/2021 à 14:20, Steve Litt a écrit :  

>    Both Hopman-cli 

Let's call it Hopman-Backend. It shouldn't have to do any user interface
work of any kind: Just implement an API or Domain Specific Language
(DSL). If somebody wants a CLI (Command Line Interface) front end to
it, that could be developed using ncurses, dmenu etc.

> and the GUI must read hopmanrc at startup (it seems
>simpler to have a single file to configure both). 

I disagree with the single file. Tom wants to use a Python/Tk front
end. Dick wants to use a GTk front end. Harry wants to use a CLI front
end. Each of those front-ends should have its own config. If this is
structured right, the only thing the front end should need to know
about the back end is the filenames of any fifos, pipe files, etc.
Naturally, the API or DSL should be in a file available to the back end
and any front end.

> Possibly the name of
>the GUI application might be specified in hopmanrc and Hopman-cli would
>launch it.

That works for me. Or just put the front end as a command line arg to
the back end. One of them has to launch the other, unless we want a
process manager/supervisor to run the back end at boot.

>
>    Both applications must die immediately when the pipe is broken.

That sounds doable.

>
>    I don't think the GUI is a piece of cake, but you seem to have some
>experience (~: 

Not really. The only thing is, the front end is just a front end that
interoperates with the API or DSL. My program would do nothing
complicated. I actually wrote something similar in 1986, command line
interface, on DOS, in order to interact with a VAX miles away. Worked
just fine. The VAX guys gave me the commands the VAX expected and the
responses it put out, and I just made the front end.

> Note that this a reactive program: it must react on
>input data available, 

I assume you mean input data *from the backend* *to the front end* is
available. I can handle that with polling or by having the back end
throw a signal at the front end. If the back end forked the front end,
then the front end knows the PID to signal.

> mouse-click, 

If I'm understanding correctly, reacting on mouse-click is what GUI
front ends do.

> and child-termination, 

Which child?

> while
>periodically reading /proc/self/mounts. 

Periodically reading /proc/self/mounts is something the back end would
do.


> I think the most difficult is
>to check the result of helpers and forward their messages to the user.

I'm not familiar with helpers.

The way I visualize it, when the back end has new data for the front
end, it writes that data to a pipe or file or whatever, and then
signals the front end (perhaps SIGUSR1). Once the front end has the
data, it's the front end's job to translate the raw data to something
easy to digest for the user.

>
>    If this seems too difficult, Hopman-cli could take care of mount
>helpers, but this would require a bidirectional communication, making
>it impossible to launch both applications from the command-line
>(Hopman-cli should be in charge of launching the GUI).

hopman-init hopman-backend my_hopman_frontend

hopman-init's whole purpose is to receive the PID of hopman-backend and
inform hopman-backend of its own PID. Hopman-backend then forks
my_hopman_frontend, so hopman-backend gets the PID of
my_hopman_frontend during the fork. Hopman-backend later informs
my_hopman_frontend of hopman-backend's PID as data. So each can signal
the other when there's data ready.

By the way, when I did something similar to the preceding paragraph,
some of my friends told me there's a better way than signalling data
ready with a signal. I forgot what they told me though.


SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Didier Kryn]

Le 22/06/2021 à 19:10, Steve Litt a écrit :
> Didier Kryn said on Tue, 22 Jun 2021 18:00:17 +0200
>
>> Le 22/06/2021 à 14:20, Steve Litt a écrit :
>>> How bout making a CLI Hopman with an API somebody can interact with
>>> in gtk, or CLI, or PHP, or Tcl/Tk, or Python/Tk, or pretty much
>>> anything else?  
>>     I have thought of this initially before doing it with Gtk2. But it
>> means a dual-process application (Hopman + a GUI written in Tk, PHP
>> ...). In a mode of operation like inotifywait, a formatted message
>> would be emitted by Hopman to standard outputeverytime the status
>> changes. I probably rejected this solution because it implied to
>> develop the two programs, which at least is twice more work.
>>
>>     If there are volonteers to develop the GUIs, I can think of this
>> CLI version.
> I'll volunteer to make a Python3/Tk version. I'll need specifications
> from you, either written or formulated via a set of emails between us,
> offlist.

    Let's continue on list for generalities since it might trigger
reactions. This is my suggestion:

    Hopman-cli would write to the pipe 3 sorts of messages, with all the
necessary details:

- a device special file associated to a removable partition has been
detected in /dev
- a symlink has been detected in /dev/disk/by-label, pointing to a
removable partition
- a device special file associated to a removable partition has been
removed

    At startup Hopman-cli looks for removable partitions already
present; then it relies on inotify; but the messages would be the same
for initial discovery and for online creation.

    Then it's up to the GUI application to

- parse these messages, maintain and display a list of removable
partitions and their labels,
- on click, spawn helpers to mount/umount/open partitions and
potentially eject disks, check completion and report errors,
- periodically read /proc/self/mounts and report mountpoints of
removable partitions on the display.

    Both Hopman-cli and the GUI must read hopmanrc at startup (it seems
simpler to have a single file to configure both). Possibly the name of
the GUI application might be specified in hopmanrc and Hopman-cli would
launch it.

    Both applications must die immediately when the pipe is broken.

    I don't think the GUI is a piece of cake, but you seem to have some
experience (~: Note that this a reactive program: it must react on input
data available, mouse-click, and child-termination, while periodically
reading /proc/self/mounts. I think the most difficult is to check the
result of helpers and forward their messages to the user.

    If this seems too difficult, Hopman-cli could take care of mount
helpers, but this would require a bidirectional communication, making it
impossible to launch both applications from the command-line (Hopman-cli
should be in charge of launching the GUI).

    Maybe this is similar to what Aitor does with his dual-threaded version.

    Cheers.

--     Didier




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Steve Litt]

Didier Kryn said on Tue, 22 Jun 2021 18:00:17 +0200

>Le 22/06/2021 à 14:20, Steve Litt a écrit :

>> How bout making a CLI Hopman with an API somebody can interact with
>> in gtk, or CLI, or PHP, or Tcl/Tk, or Python/Tk, or pretty much
>> anything else?  
>
>    I have thought of this initially before doing it with Gtk2. But it
>means a dual-process application (Hopman + a GUI written in Tk, PHP
>...). In a mode of operation like inotifywait, a formatted message
>would be emitted by Hopman to standard outputeverytime the status
>changes. I probably rejected this solution because it implied to
>develop the two programs, which at least is twice more work.
>
>    If there are volonteers to develop the GUIs, I can think of this
>CLI version.

I'll volunteer to make a Python3/Tk version. I'll need specifications
from you, either written or formulated via a set of emails between us,
offlist.

I can probably also make a Kivy version.

Thanks,

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Didier Kryn]

Le 22/06/2021 à 14:20, Steve Litt a écrit :
> aitor said on Tue, 22 Jun 2021 08:24:04 +0200
>
>> Hi Steve,
>>
>> On 20/6/21 23:09, Steve Litt wrote:
>>> Huh? The preceding link appears to be a whole distro. How can I
>>> download, compile and install*hopman*  on my existing Void Linux
>>> computer?  
>> The unique existent development files of gtk in Void Linux seem to be 
>> 3.24 or higher:
>>
>> http://54.37.137.89/pkgs.void/package/gtkmm 
>> 
> I should have made this suggestion a year ago, and it might be too late
> now, but I'll make it just in case...
>
> How bout making a CLI Hopman with an API somebody can interact with in
> gtk, or CLI, or PHP, or Tcl/Tk, or Python/Tk, or pretty much anything
> else?

    I have thought of this initially before doing it with Gtk2. But it
means a dual-process application (Hopman + a GUI written in Tk, PHP
...). In a mode of operation like inotifywait, a formatted message would
be emitted by Hopman to standard outputeverytime the status changes. I
probably rejected this solution because it implied to develop the two
programs, which at least is twice more work.

    If there are volonteers to develop the GUIs, I can think of this CLI
version.

>
> The API could include the list of all access points, sortable by alpha
> or by strength. There could be a function that takes access point,
> encryption type, passphrase or long pass string,
    What? Hopman only watches device special files associated to
partitions, full stop.
>  this function being
> fed by whatever GUI input screen wanted. Most of all, you could include
> a document of the definition of what a GUI Hopman looks like and what
> it doesn't, so all the implementations are roughly the same except for
> appearance. I could write that document for you.
>
> My local LUG, GoLUG, once featured a genius named Gary Miller, who is
> now programming for the angels. He taught me the concept of the Gary
> Miller program architecture. What Gary did is write a program with a
> text interface: Perhaps not even a very understandable text interface.
> He put this interface at a given port number. He then published how
> you'd need to interact with that port in order to properly manipulate
> his program to produce the intended results.

    No need for a port, a simple anonymous pipe is fine.

    Cheers.

--     Didier


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Steve Litt]

aitor said on Tue, 22 Jun 2021 08:24:04 +0200

>Hi Steve,
>
>On 20/6/21 23:09, Steve Litt wrote:
>> Huh? The preceding link appears to be a whole distro. How can I
>> download, compile and install*hopman*  on my existing Void Linux
>> computer?  
>
>The unique existent development files of gtk in Void Linux seem to be 
>3.24 or higher:
>
>http://54.37.137.89/pkgs.void/package/gtkmm 
>

I should have made this suggestion a year ago, and it might be too late
now, but I'll make it just in case...

How bout making a CLI Hopman with an API somebody can interact with in
gtk, or CLI, or PHP, or Tcl/Tk, or Python/Tk, or pretty much anything
else?

The API could include the list of all access points, sortable by alpha
or by strength. There could be a function that takes access point,
encryption type, passphrase or long pass string, this function being
fed by whatever GUI input screen wanted. Most of all, you could include
a document of the definition of what a GUI Hopman looks like and what
it doesn't, so all the implementations are roughly the same except for
appearance. I could write that document for you.

My local LUG, GoLUG, once featured a genius named Gary Miller, who is
now programming for the angels. He taught me the concept of the Gary
Miller program architecture. What Gary did is write a program with a
text interface: Perhaps not even a very understandable text interface.
He put this interface at a given port number. He then published how
you'd need to interact with that port in order to properly manipulate
his program to produce the intended results.

It's a beautiful concept. Gary didn't need to worry about user
interface at all. The person writing the GUI (or CLI) side of it didn't
need one bit of subject matter expertise. And best of all, the Gary
Miller program architecture avoided the volleyball code all too common
today, where, regardless of boasts to the contrary, subject matter and
user interface are intermixed into a jumbled stew (yeah RAILS, I'm
talking about you), and the result was execution bouncing all around
between subject matter and presentation.

My life would be simpler if Suckless Tools' dmenu had been built with
the Gary Miller program architecture. It's a great program, but it's
volleyball code, almost impossible to separate the string selectable
list from X calls. And now comes Wayland. And what if I want to use
this great program from CLI (which I do).

I don't think the Gary Miller program architecture needs a port. The
GUI could fork the system expertise part, and possessing the system
expertise part's PID, could send signals and send data thru a named
pipe or fifo or even a directory full of files or whatever.

I think the Gary Miller method works well with Domain Specific
Languages (DSLs). I've never written a full blown Gary Miller system,
but I've written plenty of programs with DSLs, and they worked out
great.

Anyway, back on topic, I think Hopman is much too good a program to
depend on Gtk2 or 3 or 4 or Qt or Xforms or any other presentation
method, or any particular distro or lack thereof.

Aitor, where can I download the Hopman source code so I can at least
look at it?

Thanks,

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

Hi Steve,

On 20/6/21 23:09, Steve Litt wrote:

Huh? The preceding link appears to be a whole distro. How can I
download, compile and install*hopman*  on my existing Void Linux
computer?


The unique existent development files of gtk in Void Linux seem to be 
3.24 or higher:


http://54.37.137.89/pkgs.void/package/gtkmm 



The recently released gtkmm-4 might be implemented sooner o later, but i 
guess there is no
plan to do such thing with gtk2. However, i'm trying to develop hopman 
in a way that it can be

built either with gtk2 or gtk3, and maybe gtk4 in a non foreseeable future.

Indeed, yesterday i tried to build hopman in gtkmm-3. My first attempt 
failed and i needed to make some
changes in the code (available in the git repository). Now it works with 
both gtkmm-2 and gtkmm-3,
but the behaviour of the gui is quite different where mouse events is 
concerned depending on the chosen
version of gtk, and this adaptation will take me some time to get it 
working as expected.


One clarification: my builds with gtk3 were in devuan, but the compiler 
failed in Void.
I needed to install base-devel to get g++ working, is it right? I'll try 
to deal with the origin of this failure.

  Also, do I need to have to use pmount in order to allow
hopman to do its thing?


Absolutely not. Runtime dependencies will be a choice of the user. This 
is the reason d'être of hopmanrc.


Cheers,

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Steve Litt]

aitor said on Sun, 20 Jun 2021 03:27:49 +0200

>Hi Steve,
>
the current state of vdev is stableenough for daily
>use. You can download the image from here:
>
>https://www.gnuinos.org/Beowulf/ 

Huh? The preceding link appears to be a whole distro. How can I
download, compile and install *hopman* on my existing Void Linux
computer? Also, do I need to have to use pmount in order to allow
hopman to do its thing?

Thanks,

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

Hi Steve,

On 12/6/21 21:29, Steve Litt wrote:

If there are missing symlinks in /dev/disk, why not fix that root cause
and let the inotify authors worry about different device handlers,
rather than base your program logic on something the systemd people can
change any time, possibly forcing vdev and eudev to change in order to
keep up?

After doing some changes in the code of vdev, symlinks are added
and removed as expected in /dev/disk, /dev/input. Vdev also is responding
to the removal of usb devices by software (e.g. using "eject"). Other
issues related to virtual machines have been fixed too, and now gnuinos
vdev is running fine in both qemu and virtualbox.Imho, the current state of
vdev is stableenough for daily use. You can download the image from here:

https://www.gnuinos.org/Beowulf/ 

On the other hand, the program logic of hopman is the same whether the
device manager is eudev or vdev: that is, inotify watching /dev/disk for 
creation

of symlinks.

One clarification: if you want to test hopman, don't use any virtual 
machine.

Test it during live sessions or after a hard disk installation instead.

In the event of any issue, please let me know. Thanks in advance,

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Thu, 17 Jun 2021 09:04:06 +0200
al3xu5  wrote:

> Tue, 15 Jun 2021 11:41:09 -0700 - Patrick Bartek
> :
> 
> > On Mon, 14 Jun 2021 17:59:24 +0200
> > al3xu5  wrote:
> >   
> > > [...]
> > > I have openbox+lxde & PCManFM: usb drives are automatically
> > > mounted (by udisks2) and are shown and usable (open and umount)
> > > thanks to PCManFM.
> > > 
> > > I have also udiskie, which i nice, but not strictly necessary in
> > > my case... Am I right?
> > 
> > I have found that each desktop uses its own method of automounting.
> > PCManFM may have the mounting code built-in. Or it may use udiskie.
> > Check PCManFM's dependencies and see if udiskie is listed.   
> 
> No: PCManFM do not require udiskie. I think you are right saying it
> should have the mounting code built-in.

Or it uses some other method. As long as it works. :)

B

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[al3xu5]

Tue, 15 Jun 2021 11:41:09 -0700 - Patrick Bartek :

> On Mon, 14 Jun 2021 17:59:24 +0200
> al3xu5  wrote:
> 
> > [...]
> > I have openbox+lxde & PCManFM: usb drives are automatically mounted
> > (by udisks2) and are shown and usable (open and umount) thanks to
> > PCManFM.
> > 
> > I have also udiskie, which i nice, but not strictly necessary in my
> > case... Am I right?  
> 
> I have found that each desktop uses its own method of automounting.
> PCManFM may have the mounting code built-in. Or it may use udiskie.
> Check PCManFM's dependencies and see if udiskie is listed. 

No: PCManFM do not require udiskie. I think you are right saying it should
have the mounting code built-in.


> Did you
> install udiskie yourself? 

Yes: I installed udiskie "separately", when PCManFM was already installed.


> If not, then some other app did and it's
> probably needed. 

Looking at the PCManFM deps seems to confirm it has the mounting code
built-in...

$ apt-cache depends pcmanfm
pcmanfm
  Depends: libatk1.0-0
  Depends: libc6
  Depends: libcairo2
  Depends: libfm-gtk4
  Depends: libfm4
  Depends: libfontconfig1
  Depends: libfreetype6
  Depends: libgdk-pixbuf2.0-0
  Depends: libglib2.0-0
  Depends: libgtk2.0-0
  Depends: libpango-1.0-0
  Depends: libpangocairo-1.0-0
  Depends: libpangoft2-1.0-0
  Depends: libx11-6
  Depends: shared-mime-info


> If it's not causing problems, leave it be.  

Indeed, I have both.


Regards
al3xu5

-- 
Say NO to copyright, patents, trademarks and industrial design
restrictions!


Public GPG/PGP key: 8FC2 3121 2803 86E9 F7D8  B624 DA50 835B 2624 A36B


pgp8gtqc4dwxj.pgp
Description: Firma digitale OpenPGP
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Tue, 15 Jun 2021 12:32:25 -0700
Fred  wrote:

> On 6/15/21 11:28 AM, Patrick Bartek via Dng wrote:
> > On Mon, 14 Jun 2021 07:56:39 -0700
> > Fred  wrote:
> >   
> >> On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote:  
> >   
> >>> [big snip]  
> >> Hi,
> >> I found udisks2 installed on the computer that automatically
> >> mounts USB devices but there is no man page so I would not know
> >> how to use it if installed on the other computer.  
> >
> > Not much to using it: apt-get install udisks2 and everything
> > gets set up. I used the defaults. Devices are mounted
> > under /media/"your username". If you run a panel, the udisks2
> > gadget shows up there with additional options. Manual unmounting
> > is necessary, but I use only a window manager (Openbox) and
> > lxpanel for my GUI, so your mileage may vary if you use a
> > desktop environment.
> >
> > Others have shown you how to access the mans.  So, I won't
> > repeat that.
> >
> > B
> > ___
> > Dng mailing list
> > Dng@lists.dyne.org
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> > 
>  Hello,
>  I still need some help with this.
>  I installed udisks2.  The last line of the installation dialog
>  showed what I believe is a warning, maybe of no consequence:  
> >>>
> >>> I did some checking -- It's been a while since I installed Beowulf
> >>> and udisks2 -- and I discovered that you need to use a "front end"
> >>> for udisks2 for it to truly automount.  I used udiskie
> >>> (https://pypi.org/project/udiskie/) which must be started
> >>> manually. Installing it doesn't automatically set it up to
> >>> start.  I just added a stanza to Openbox's autostart script.
> >>> Since I use lxpanel in addition to Openbox, I added the
> >>> "--smart-tray" option, so udiskie will appear in the panel when
> >>> it's in use.  
> >>
> >> The computer that was upgraded from Debian Jessie to Beowulf x86
> >> doesn't have any "front end" for udisks2 installed unless it was
> >> installed automagically.  This computer automounts USB devices
> >> in /media as one of usb0-7.  The one I am having trouble with is a
> >> new install of Beowulf AMD64.  
> > 
> > What desktop was the Jessie computer running before your
> > dist-upgrade to Beowulf? And after?  Many times desktops have their
> > own way of handling automounting usb devices.
> > 
> > The usb mountpoint as /media/usb[0-7] is contrary to the default
> > that udisks2 uses, namely: /media//.  Jessie
> > may have been using udev rules to mount usb.  That's the way you
> > automounted external devices with Wheezy at least.  Jessie came
> > with improvements. Check /etc/udev/rules.d to see if there is
> > anything there.  udev rules should survive a dist-upgrade.
> > 
> > If there is a udev rule to automount, copying it over to your new
> > Beowulf computer should work.
> >   
> Hi,
> The Jessie computer has never used any desktop/DE.  Only openbox and 
> xterms.  I never installed any utility to mount usb devices. 
> /etc/udev/rules.d has 70-persistent-net.rules which has one line 
> concerning ethernet.

Jessie was the first Debian version to use systemd by default as
the init. Perhaps, something was installed as a systemd dependency that
wouldn't have been installed with the new Beowulf computer under
sysvinit that carried forward with a dist-upgrade of Jessie to
Beowulf.  Or you installed something on the old system that wasn't
installed on the new one, and that is doing the automounting.

Of course, this is all speculation.  It would have been nice if you had
notes of what you installed on both systems.  Right now, I doubt if
you'll be able to discover (in a timely manner) what's causing the old
system to automount and the new one not.  

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/15/21 1:24 PM, g4sra via Dng wrote:

<--snip-->

Unfortunately I am not able to find what package contains gvfs-udisks2-vo.

<--snip-->
apt-file search gvfs-udisks2-vo
gvfs-daemons: /usr/lib/gvfs/gvfs-udisks2-volume-monitor
gvfs-daemons: /usr/lib/systemd/user/gvfs-udisks2-volume-monitor.service


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
These don't appear to have anything to do with auto mounting USB devices 
so the reason Jessie upgrade to Beowulf x86 auto mounts and new install 
Beowulf AMD64 does not is still not known.


Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[g4sra via Dng]

<--snip-->
> Unfortunately I am not able to find what package contains gvfs-udisks2-vo.
<--snip-->
apt-file search gvfs-udisks2-vo
gvfs-daemons: /usr/lib/gvfs/gvfs-udisks2-volume-monitor
gvfs-daemons: /usr/lib/systemd/user/gvfs-udisks2-volume-monitor.service

publickey - g4sra@protonmail.com - 0x42E94623.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/15/21 12:32 PM, Fred wrote:

On 6/15/21 11:28 AM, Patrick Bartek via Dng wrote:

On Mon, 14 Jun 2021 07:56:39 -0700
Fred  wrote:


On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote:



[big snip]

Hi,
I found udisks2 installed on the computer that automatically
mounts USB devices but there is no man page so I would not know
how to use it if installed on the other computer.


Not much to using it: apt-get install udisks2 and everything gets
set up. I used the defaults. Devices are mounted
under /media/"your username". If you run a panel, the udisks2
gadget shows up there with additional options. Manual unmounting
is necessary, but I use only a window manager (Openbox) and
lxpanel for my GUI, so your mileage may vary if you use a desktop
environment.

Others have shown you how to access the mans.  So, I won't repeat
that.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Hello,
I still need some help with this.
I installed udisks2.  The last line of the installation dialog
showed what I believe is a warning, maybe of no consequence:


I did some checking -- It's been a while since I installed Beowulf
and udisks2 -- and I discovered that you need to use a "front end"
for udisks2 for it to truly automount.  I used udiskie
(https://pypi.org/project/udiskie/) which must be started manually.
Installing it doesn't automatically set it up to start.  I just
added a stanza to Openbox's autostart script. Since I use lxpanel
in addition to Openbox, I added the "--smart-tray" option, so
udiskie will appear in the panel when it's in use.


The computer that was upgraded from Debian Jessie to Beowulf x86
doesn't have any "front end" for udisks2 installed unless it was
installed automagically.  This computer automounts USB devices
in /media as one of usb0-7.  The one I am having trouble with is a
new install of Beowulf AMD64.


What desktop was the Jessie computer running before your dist-upgrade
to Beowulf? And after?  Many times desktops have their own way of
handling automounting usb devices.

The usb mountpoint as /media/usb[0-7] is contrary to the default that
udisks2 uses, namely: /media//.  Jessie may have
been using udev rules to mount usb.  That's the way you automounted
external devices with Wheezy at least.  Jessie came with improvements.
Check /etc/udev/rules.d to see if there is anything there.  udev rules
should survive a dist-upgrade.

If there is a udev rule to automount, copying it over to your new
Beowulf computer should work.


Hi,
The Jessie computer has never used any desktop/DE.  Only openbox and 
xterms.  I never installed any utility to mount usb devices. 
/etc/udev/rules.d has 70-persistent-net.rules which has one line 
concerning ethernet.


ps -e shows that gvfs-udisks2-vo and udisksd are running.  I don't know 
what the gvfs program is.
man gvfs is interesting and possibly what is doing the auto mount.  It 
was probably installed along with gphoto2 for my camera.  It is not on 
the Beowulf AMD64 computer.  I will try to install it and see what happens.

Best regards,
Fred

Unfortunately I am not able to find what package contains gvfs-udisks2-vo.
Fred




[snip]

The udisksd man page says the daemon is started by dbus-daemon or
systemd.  However, it is not started by inserting a USB device.  I
tried starting it manually (with USB device inserted) and received
this:


It does.  You shouldn't have to manually start it.  To see if
udisks2 is running and working, inset a usb thumb drive, and in a
terminal enter "udisksctl status". The thumb drive should show in
the list of other mounted devices.


udisksctl does see the thumb drive.  The udisksd daemon is running
but it doesn't mount the thumb drive anywhere I can find.  It does
show up in /dev as sdb.


Okay. Udisks2 is working correctly: it sees the drive; but udisks2
won't automount by itself without using a frontend utility or udev
rule.

Try mounting manually using the udisksctl "mount" command to see
if it mounts. See the udisksctl man for the details of using the mount
command.

If that works install udiskie (or set up a udev rule), start it and see
if works.

PS: There are other frontends besides udiskie.  I just used it because
it was the simplest one at the time -- When I upgraded from Wheezy to
Stretch.  Kept same set up when I did a clean install of Beowulf a
year ago.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/15/21 11:28 AM, Patrick Bartek via Dng wrote:

On Mon, 14 Jun 2021 07:56:39 -0700
Fred  wrote:


On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote:



[big snip]

Hi,
I found udisks2 installed on the computer that automatically
mounts USB devices but there is no man page so I would not know
how to use it if installed on the other computer.


Not much to using it: apt-get install udisks2 and everything gets
set up. I used the defaults. Devices are mounted
under /media/"your username". If you run a panel, the udisks2
gadget shows up there with additional options. Manual unmounting
is necessary, but I use only a window manager (Openbox) and
lxpanel for my GUI, so your mileage may vary if you use a desktop
environment.

Others have shown you how to access the mans.  So, I won't repeat
that.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
  

Hello,
I still need some help with this.
I installed udisks2.  The last line of the installation dialog
showed what I believe is a warning, maybe of no consequence:


I did some checking -- It's been a while since I installed Beowulf
and udisks2 -- and I discovered that you need to use a "front end"
for udisks2 for it to truly automount.  I used udiskie
(https://pypi.org/project/udiskie/) which must be started manually.
Installing it doesn't automatically set it up to start.  I just
added a stanza to Openbox's autostart script. Since I use lxpanel
in addition to Openbox, I added the "--smart-tray" option, so
udiskie will appear in the panel when it's in use.


The computer that was upgraded from Debian Jessie to Beowulf x86
doesn't have any "front end" for udisks2 installed unless it was
installed automagically.  This computer automounts USB devices
in /media as one of usb0-7.  The one I am having trouble with is a
new install of Beowulf AMD64.


What desktop was the Jessie computer running before your dist-upgrade
to Beowulf? And after?  Many times desktops have their own way of
handling automounting usb devices.

The usb mountpoint as /media/usb[0-7] is contrary to the default that
udisks2 uses, namely: /media//.  Jessie may have
been using udev rules to mount usb.  That's the way you automounted
external devices with Wheezy at least.  Jessie came with improvements.
Check /etc/udev/rules.d to see if there is anything there.  udev rules
should survive a dist-upgrade.

If there is a udev rule to automount, copying it over to your new
Beowulf computer should work.


Hi,
The Jessie computer has never used any desktop/DE.  Only openbox and 
xterms.  I never installed any utility to mount usb devices. 
/etc/udev/rules.d has 70-persistent-net.rules which has one line 
concerning ethernet.


ps -e shows that gvfs-udisks2-vo and udisksd are running.  I don't know 
what the gvfs program is.
man gvfs is interesting and possibly what is doing the auto mount.  It 
was probably installed along with gphoto2 for my camera.  It is not on 
the Beowulf AMD64 computer.  I will try to install it and see what happens.

Best regards,
Fred


[snip]

The udisksd man page says the daemon is started by dbus-daemon or
systemd.  However, it is not started by inserting a USB device.  I
tried starting it manually (with USB device inserted) and received
this:


It does.  You shouldn't have to manually start it.  To see if
udisks2 is running and working, inset a usb thumb drive, and in a
terminal enter "udisksctl status". The thumb drive should show in
the list of other mounted devices.


udisksctl does see the thumb drive.  The udisksd daemon is running
but it doesn't mount the thumb drive anywhere I can find.  It does
show up in /dev as sdb.


Okay. Udisks2 is working correctly: it sees the drive; but udisks2
won't automount by itself without using a frontend utility or udev
rule.

Try mounting manually using the udisksctl "mount" command to see
if it mounts. See the udisksctl man for the details of using the mount
command.

If that works install udiskie (or set up a udev rule), start it and see
if works.

PS: There are other frontends besides udiskie.  I just used it because
it was the simplest one at the time -- When I upgraded from Wheezy to
Stretch.  Kept same set up when I did a clean install of Beowulf a
year ago.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem and new challenge of Wifi Machine

[Steve Litt]

Patrick Bartek via Dng said on Tue, 15 Jun 2021 11:28:14 -0700

>What desktop was the Jessie computer running before your dist-upgrade
>to Beowulf? And after?  Many times desktops have their own way of
>handling automounting usb devices.

Desktops having their own way of handling usb device automounting is,
in my opinion, a travesty. Kinda like systemd has its own way of
handling home directories and networking.

Do one thing and do it well. That's Hopman. Another thing, as far as I
know (and I hope I'm right), Hopman will also work when there's no GUI,
because there's nothing about CLI that de-necessitates automounting for
the person who needs that convenience. Whether you have fvwm, KDE,
Gnome, Xfce, LXDE, Ratpoison, or no GUI, Hopman just works. That's sure
how I want *my* Linux machine to work.

WM/DEs (Window Manager/Desktop Environments) change, and users' needs
change. Asking them to use a different automounter just because they
decide to get closer or farther from the metal is, IMHO, a bridge too
far. Hopman is the right way to go, for Devuan and every other distro.

Once Hopman is done, I think Aitor and Didier should make a CLI
capable, sans-dbus, distro/WM-DE agnostic Wifi machine --- a replacement
for junk like NetworkManager and Wicd. I'll help --- I've already made
some attempts using WPA-SUPPLICANT and its cousins. I see two
challenges in making such a Wifi machine:

1) It must be operable by a normal user

2) It's by nature a state machine, and those are difficult to implement

A distro/WMDE agnostic Wifi machine would definitely scratch one of my
itches. I'm sick of doing the wpa_passwd thing after manually detecting
the radio beams of the local access points.

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Mon, 14 Jun 2021 17:59:24 +0200
al3xu5  wrote:

> Sun, 13 Jun 2021 21:37:45 -0700 - Patrick Bartek
> :
> 
> > [...]  
> 
> > I did some checking -- It's been a while since I installed Beowulf
> > and udisks2 -- and I discovered that you need to use a "front end"
> > for udisks2 for it to truly automount.  I used udiskie
> > (https://pypi.org/project/udiskie/) which must be started manually.
> > Installing it doesn't automatically set it up to start.  I just
> > added a stanza to Openbox's autostart script. Since I use lxpanel
> > in addition to Openbox, I added the "--smart-tray" option, so
> > udiskie will appear in the panel when it's in use.  
> 
> Hi Patrick
> 
> I have openbox+lxde & PCManFM: usb drives are automatically mounted
> (by udisks2) and are shown and usable (open and umount) thanks to
> PCManFM.
> 
> I have also udiskie, which i nice, but not strictly necessary in my
> case... Am I right?

I have found that each desktop uses its own method of automounting.
PCManFM may have the mounting code built-in. Or it may use udiskie.
Check PCManFM's dependencies and see if udiskie is listed. Did you
install udiskie yourself? If not, then some other app did and it's
probably needed. If it's not causing problems, leave it be.  

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Mon, 14 Jun 2021 07:56:39 -0700
Fred  wrote:

> On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote:

> > [big snip]
>  Hi,
>  I found udisks2 installed on the computer that automatically
>  mounts USB devices but there is no man page so I would not know
>  how to use it if installed on the other computer.  
> >>>
> >>> Not much to using it: apt-get install udisks2 and everything gets
> >>> set up. I used the defaults. Devices are mounted
> >>> under /media/"your username". If you run a panel, the udisks2
> >>> gadget shows up there with additional options. Manual unmounting
> >>> is necessary, but I use only a window manager (Openbox) and
> >>> lxpanel for my GUI, so your mileage may vary if you use a desktop
> >>> environment.
> >>>
> >>> Others have shown you how to access the mans.  So, I won't repeat
> >>> that.
> >>>
> >>> B
> >>> ___
> >>> Dng mailing list
> >>> Dng@lists.dyne.org
> >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >>>  
> >> Hello,
> >> I still need some help with this.
> >> I installed udisks2.  The last line of the installation dialog
> >> showed what I believe is a warning, maybe of no consequence:  
> > 
> > I did some checking -- It's been a while since I installed Beowulf
> > and udisks2 -- and I discovered that you need to use a "front end"
> > for udisks2 for it to truly automount.  I used udiskie
> > (https://pypi.org/project/udiskie/) which must be started manually.
> > Installing it doesn't automatically set it up to start.  I just
> > added a stanza to Openbox's autostart script. Since I use lxpanel
> > in addition to Openbox, I added the "--smart-tray" option, so
> > udiskie will appear in the panel when it's in use.  
> 
> The computer that was upgraded from Debian Jessie to Beowulf x86
> doesn't have any "front end" for udisks2 installed unless it was
> installed automagically.  This computer automounts USB devices
> in /media as one of usb0-7.  The one I am having trouble with is a
> new install of Beowulf AMD64.

What desktop was the Jessie computer running before your dist-upgrade
to Beowulf? And after?  Many times desktops have their own way of
handling automounting usb devices.

The usb mountpoint as /media/usb[0-7] is contrary to the default that
udisks2 uses, namely: /media//.  Jessie may have
been using udev rules to mount usb.  That's the way you automounted
external devices with Wheezy at least.  Jessie came with improvements. 
Check /etc/udev/rules.d to see if there is anything there.  udev rules
should survive a dist-upgrade.

If there is a udev rule to automount, copying it over to your new
Beowulf computer should work.

> > [snip]  
> >> The udisksd man page says the daemon is started by dbus-daemon or
> >> systemd.  However, it is not started by inserting a USB device.  I
> >> tried starting it manually (with USB device inserted) and received
> >> this:  
> > 
> > It does.  You shouldn't have to manually start it.  To see if
> > udisks2 is running and working, inset a usb thumb drive, and in a
> > terminal enter "udisksctl status". The thumb drive should show in
> > the list of other mounted devices.  
> 
> udisksctl does see the thumb drive.  The udisksd daemon is running
> but it doesn't mount the thumb drive anywhere I can find.  It does
> show up in /dev as sdb.

Okay. Udisks2 is working correctly: it sees the drive; but udisks2
won't automount by itself without using a frontend utility or udev
rule.

Try mounting manually using the udisksctl "mount" command to see
if it mounts. See the udisksctl man for the details of using the mount
command.

If that works install udiskie (or set up a udev rule), start it and see
if works.

PS: There are other frontends besides udiskie.  I just used it because
it was the simplest one at the time -- When I upgraded from Wheezy to
Stretch.  Kept same set up when I did a clean install of Beowulf a
year ago.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[al3xu5]

Sun, 13 Jun 2021 21:37:45 -0700 - Patrick Bartek :

> [...]

> I did some checking -- It's been a while since I installed Beowulf and
> udisks2 -- and I discovered that you need to use a "front end" for
> udisks2 for it to truly automount.  I used udiskie
> (https://pypi.org/project/udiskie/) which must be started manually.
> Installing it doesn't automatically set it up to start.  I just added a
> stanza to Openbox's autostart script. Since I use lxpanel in addition
> to Openbox, I added the "--smart-tray" option, so udiskie will appear in
> the panel when it's in use.

Hi Patrick

I have openbox+lxde & PCManFM: usb drives are automatically mounted (by
udisks2) and are shown and usable (open and umount) thanks to PCManFM.

I have also udiskie, which i nice, but not strictly necessary in my
case... Am I right?

> [...]

Regards
al3xu5

-- 
Say NO to copyright, patents, trademarks and industrial design
restrictions!


Public GPG/PGP key: 8FC2 3121 2803 86E9 F7D8  B624 DA50 835B 2624 A36B


pgpn8JSCbPlfA.pgp
Description: Firma digitale OpenPGP
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote:

On Sun, 13 Jun 2021 12:37:00 -0700
Fred  wrote:


On 6/11/21 7:05 AM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 17:37:13 -0700
Fred  wrote:
   

On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 08:49:24 -0700
Fred  wrote:
  

Hello,

I have a new Beowulf AMD64 install and am having trouble mounting
USB storage devices.

The USB keyboard and mouse work ok.  lsusb shows the storage
device is present.  The usbmount program is apparently no longer
available and I haven't been able to find what took its place.
I have another computer that had Debian Jessie installed then was
upgraded to Beowulf x86.  It has usbmount and will automatically
mount USB storage devices.

What do I need to install?


I use udisks2 to automount external USB devices.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
  

Hi,
I found udisks2 installed on the computer that automatically mounts
USB devices but there is no man page so I would not know how to use
it if installed on the other computer.


Not much to using it: apt-get install udisks2 and everything gets
set up. I used the defaults. Devices are mounted under /media/"your
username". If you run a panel, the udisks2 gadget shows up there
with additional options. Manual unmounting is necessary, but I use
only a window manager (Openbox) and lxpanel for my GUI, so your
mileage may vary if you use a desktop environment.

Others have shown you how to access the mans.  So, I won't repeat
that.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
   

Hello,
I still need some help with this.
I installed udisks2.  The last line of the installation dialog showed
what I believe is a warning, maybe of no consequence:


I did some checking -- It's been a while since I installed Beowulf and
udisks2 -- and I discovered that you need to use a "front end" for
udisks2 for it to truly automount.  I used udiskie
(https://pypi.org/project/udiskie/) which must be started manually.
Installing it doesn't automatically set it up to start.  I just added a
stanza to Openbox's autostart script. Since I use lxpanel in addition
to Openbox, I added the "--smart-tray" option, so udiskie will appear in
the panel when it's in use.


The computer that was upgraded from Debian Jessie to Beowulf x86 doesn't 
have any "front end" for udisks2 installed unless it was installed 
automagically.  This computer automounts USB devices in /media as one of 
usb0-7.  The one I am having trouble with is a new install of Beowulf AMD64.





W:
http://deb.debian.org/debian/pool/main/libb/libblockdev/libblockdev-crypto2_2.20-7+deb10u1_amd64.deb:
Automatically disabled Acquire::http::Pipeline-Depth due to incorrect
response from server/proxy. (man 5 apt.conf)

The udisksd man page says the daemon is started by dbus-daemon or
systemd.  However, it is not started by inserting a USB device.  I
tried starting it manually (with USB device inserted) and received
this:


It does.  You shouldn't have to manually start it.  To see if udisks2 is
running and working, inset a usb thumb drive, and in a terminal enter
"udisksctl status". The thumb drive should show in the list of other
mounted devices.


udisksctl does see the thumb drive.  The udisksd daemon is running but 
it doesn't mount the thumb drive anywhere I can find.  It does show up 
in /dev as sdb.





root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
[1] 523
root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon
version 2.8.1 starting

** (udisksd:523): WARNING **: 07:27:15.773: failed to load module
mdraid: libbd_mdraid.so.2: cannot open shared object file: No such
file or directory
sh: 1: dmidecode: not found

(udisksd:523): udisks-WARNING **: 07:27:15.776: Failed to load the
'mdraid' libblockdev plugin
udisks-Message: 07:27:16.017: Acquired the name
org.freedesktop.UDisks2 on the system message bus

If that library file was needed it should have been loaded by the
installer.  I don't know what to do from here.


Do you have a RAID set up?  If not, disregard the warnings.


I do not have a raid setup.




I use openbox and xterms if that info. is needed.


Me, too, with a single lxpanel with menus.  I do not have any desktop
environments, in whole or part, installed. Neither a display manager. I
boot to and login in a terminal and, then, run startx.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Sun, 13 Jun 2021 12:37:00 -0700
Fred  wrote:

> On 6/11/21 7:05 AM, Patrick Bartek via Dng wrote:
> > On Thu, 10 Jun 2021 17:37:13 -0700
> > Fred  wrote:
> >   
> >> On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:  
> >>> On Thu, 10 Jun 2021 08:49:24 -0700
> >>> Fred  wrote:
> >>>  
>  Hello,
> 
>  I have a new Beowulf AMD64 install and am having trouble mounting
>  USB storage devices.
> 
>  The USB keyboard and mouse work ok.  lsusb shows the storage
>  device is present.  The usbmount program is apparently no longer
>  available and I haven't been able to find what took its place.
>  I have another computer that had Debian Jessie installed then was
>  upgraded to Beowulf x86.  It has usbmount and will automatically
>  mount USB storage devices.
> 
>  What do I need to install?  
> >>>
> >>> I use udisks2 to automount external USB devices.
> >>>
> >>> B
> >>> ___
> >>> Dng mailing list
> >>> Dng@lists.dyne.org
> >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >>>  
> >> Hi,
> >> I found udisks2 installed on the computer that automatically mounts
> >> USB devices but there is no man page so I would not know how to use
> >> it if installed on the other computer.  
> > 
> > Not much to using it: apt-get install udisks2 and everything gets
> > set up. I used the defaults. Devices are mounted under /media/"your
> > username". If you run a panel, the udisks2 gadget shows up there
> > with additional options. Manual unmounting is necessary, but I use
> > only a window manager (Openbox) and lxpanel for my GUI, so your
> > mileage may vary if you use a desktop environment.
> > 
> > Others have shown you how to access the mans.  So, I won't repeat
> > that.
> > 
> > B
> > ___
> > Dng mailing list
> > Dng@lists.dyne.org
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >   
> Hello,
> I still need some help with this.
> I installed udisks2.  The last line of the installation dialog showed 
> what I believe is a warning, maybe of no consequence:

I did some checking -- It's been a while since I installed Beowulf and
udisks2 -- and I discovered that you need to use a "front end" for
udisks2 for it to truly automount.  I used udiskie
(https://pypi.org/project/udiskie/) which must be started manually.
Installing it doesn't automatically set it up to start.  I just added a
stanza to Openbox's autostart script. Since I use lxpanel in addition
to Openbox, I added the "--smart-tray" option, so udiskie will appear in
the panel when it's in use.

> W: 
> http://deb.debian.org/debian/pool/main/libb/libblockdev/libblockdev-crypto2_2.20-7+deb10u1_amd64.deb:
>  
> Automatically disabled Acquire::http::Pipeline-Depth due to incorrect 
> response from server/proxy. (man 5 apt.conf)
> 
> The udisksd man page says the daemon is started by dbus-daemon or 
> systemd.  However, it is not started by inserting a USB device.  I
> tried starting it manually (with USB device inserted) and received
> this:

It does.  You shouldn't have to manually start it.  To see if udisks2 is
running and working, inset a usb thumb drive, and in a terminal enter
"udisksctl status". The thumb drive should show in the list of other
mounted devices.  

> root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
> [1] 523
> root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon 
> version 2.8.1 starting
> 
> ** (udisksd:523): WARNING **: 07:27:15.773: failed to load module 
> mdraid: libbd_mdraid.so.2: cannot open shared object file: No such
> file or directory
> sh: 1: dmidecode: not found
> 
> (udisksd:523): udisks-WARNING **: 07:27:15.776: Failed to load the 
> 'mdraid' libblockdev plugin
> udisks-Message: 07:27:16.017: Acquired the name
> org.freedesktop.UDisks2 on the system message bus
>
> If that library file was needed it should have been loaded by the 
> installer.  I don't know what to do from here.

Do you have a RAID set up?  If not, disregard the warnings.

> I use openbox and xterms if that info. is needed.

Me, too, with a single lxpanel with menus.  I do not have any desktop
environments, in whole or part, installed. Neither a display manager. I
boot to and login in a terminal and, then, run startx.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/13/21 4:24 PM, g4sra via Dng wrote:


<--snip-->






The udisksd man page says the daemon is started by dbus-daemon or
systemd. However, it is not started by inserting a USB device.



tried starting it manually (with USB device inserted) and received
this:




root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
[1] 5 3
root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon




version 2.8.1 starting




** (udisksd:523): WARNING **: 07:27:15.773: failed to load module
mdraid: libbd_mdraid.so.2: cannot open shared object file: No such
file or directory




You read it in the man page, you do not start udisksd that way.
what does the following command display when run with root privileges...

udisksctl dump






___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
At the risk of doing something I was not supposed to do, I left out the 
large amount of data concerning the hard drive and DVD drive, about 17K.



/org/freedesktop/UDisks2/Manager:
  org.freedesktop.UDisks2.Manager:
SupportedFilesystems:   ext2
ext3
ext4
vfat
ntfs
exfat
xfs
reiserfs
nilfs2
btrfs
minix
udf
f2fs
swap
Version:2.8.1

-snip hard drive and DVD drive stuff --

/org/freedesktop/UDisks2/drives/SanDisk_Cruzer_Glide_04009817102220224840:
  org.freedesktop.UDisks2.Drive:
CanPowerOff:true
Configuration:  {}
ConnectionBus:  usb
Ejectable:  true
Id: SanDisk-Cruzer-Glide-04009817102220224840
Media:  thumb
MediaAvailable: true
MediaChangeDetected:true
MediaCompatibility: thumb
MediaRemovable: false
Model:  Cruzer Glide
Optical:false
OpticalBlank:   false
OpticalNumAudioTracks:  0
OpticalNumDataTracks:   0
OpticalNumSessions: 0
OpticalNumTracks:   0
Removable:  true
Revision:   1.00
RotationRate:   -1
Seat:   seat0
Serial: 04009817102220224840
SiblingId: 
/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0

Size:   30765219840
SortKey:01hotplug/1623633671017912
TimeDetected:   1623633671017912
TimeMediaDetected:  1623633671017912
Vendor: SanDisk
WWN:


I don't understand what you mean about reading in the man page and 
starting that way.  It is supposed to be started by dbus-daemon.

Best regards,
Fred




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[g4sra via Dng]

<--snip-->

> > > 

> > > The udisksd man page says the daemon is started by dbus-daemon or
> > > systemd. However, it is not started by inserting a USB device. 

> > > tried starting it manually (with USB device inserted) and received
> > > this:
> > > 

> > > root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
> > > [1] 5 3
> > > root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon
> > > 

> > > version 2.8.1 starting
> > > 

> > > ** (udisksd:523): WARNING **: 07:27:15.773: failed to load module
> > > mdraid: libbd_mdraid.so.2: cannot open shared object file: No such
> > > file or directory
> > > 


You read it in the man page, you do not start udisksd that way.
what does the following command display when run with root privileges...

udisksctl dump







publickey - g4sra@protonmail.com - 0x42E94623.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/13/21 1:01 PM, tito via Dng wrote:

On Sun, 13 Jun 2021 12:37:00 -0700
Fred  wrote:


On 6/11/21 7:05 AM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 17:37:13 -0700
Fred  wrote:


On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 08:49:24 -0700
Fred  wrote:


Hello,

I have a new Beowulf AMD64 install and am having trouble mounting
USB storage devices.

The USB keyboard and mouse work ok.  lsusb shows the storage
device is present.  The usbmount program is apparently no longer
available and I haven't been able to find what took its place.
I have another computer that had Debian Jessie installed then was
upgraded to Beowulf x86.  It has usbmount and will automatically
mount USB storage devices.

What do I need to install?


I use udisks2 to automount external USB devices.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
I found udisks2 installed on the computer that automatically mounts
USB devices but there is no man page so I would not know how to use
it if installed on the other computer.


Not much to using it: apt-get install udisks2 and everything gets
set up. I used the defaults. Devices are mounted under /media/"your
username". If you run a panel, the udisks2 gadget shows up there
with additional options. Manual unmounting is necessary, but I use
only a window manager (Openbox) and lxpanel for my GUI, so your
mileage may vary if you use a desktop environment.

Others have shown you how to access the mans.  So, I won't repeat
that.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hello,
I still need some help with this.
I installed udisks2.  The last line of the installation dialog showed
what I believe is a warning, maybe of no consequence:

W:
http://deb.debian.org/debian/pool/main/libb/libblockdev/libblockdev-crypto2_2.20-7+deb10u1_amd64.deb:
Automatically disabled Acquire::http::Pipeline-Depth due to incorrect
response from server/proxy. (man 5 apt.conf)

The udisksd man page says the daemon is started by dbus-daemon or
systemd.  However, it is not started by inserting a USB device.  I
tried starting it manually (with USB device inserted) and received
this:

root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
[1] 523
root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon
version 2.8.1 starting

** (udisksd:523): WARNING **: 07:27:15.773: failed to load module
mdraid: libbd_mdraid.so.2: cannot open shared object file: No such
file or directory
sh: 1: dmidecode: not found

(udisksd:523): udisks-WARNING **: 07:27:15.776: Failed to load the
'mdraid' libblockdev plugin
udisks-Message: 07:27:16.017: Acquired the name
org.freedesktop.UDisks2 on the system message bus

If that library file was needed it should have been loaded by the
installer.  I don't know what to do from here.

I use openbox and xterms if that info. is needed.

Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
try

apt install libblockdev-mdraid2

Ciao,
Tito
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
Doesn't make any difference.  The USB device is not mounted in /media 
and the udisksd daemon is not started.


Another computer that was upgraded from Debian Jessie to Beowulf x86 
mounts devices in /media under one of usb0-7.  The udisksd daemon is 
running.

Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[tito via Dng]

On Sun, 13 Jun 2021 12:37:00 -0700
Fred  wrote:

> On 6/11/21 7:05 AM, Patrick Bartek via Dng wrote:
> > On Thu, 10 Jun 2021 17:37:13 -0700
> > Fred  wrote:
> > 
> >> On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:
> >>> On Thu, 10 Jun 2021 08:49:24 -0700
> >>> Fred  wrote:
> >>>
>  Hello,
> 
>  I have a new Beowulf AMD64 install and am having trouble mounting
>  USB storage devices.
> 
>  The USB keyboard and mouse work ok.  lsusb shows the storage
>  device is present.  The usbmount program is apparently no longer
>  available and I haven't been able to find what took its place.
>  I have another computer that had Debian Jessie installed then was
>  upgraded to Beowulf x86.  It has usbmount and will automatically
>  mount USB storage devices.
> 
>  What do I need to install?
> >>>
> >>> I use udisks2 to automount external USB devices.
> >>>
> >>> B
> >>> ___
> >>> Dng mailing list
> >>> Dng@lists.dyne.org
> >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >>>
> >> Hi,
> >> I found udisks2 installed on the computer that automatically mounts
> >> USB devices but there is no man page so I would not know how to use
> >> it if installed on the other computer.
> > 
> > Not much to using it: apt-get install udisks2 and everything gets
> > set up. I used the defaults. Devices are mounted under /media/"your
> > username". If you run a panel, the udisks2 gadget shows up there
> > with additional options. Manual unmounting is necessary, but I use
> > only a window manager (Openbox) and lxpanel for my GUI, so your
> > mileage may vary if you use a desktop environment.
> > 
> > Others have shown you how to access the mans.  So, I won't repeat
> > that.
> > 
> > B
> > ___
> > Dng mailing list
> > Dng@lists.dyne.org
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> > 
> Hello,
> I still need some help with this.
> I installed udisks2.  The last line of the installation dialog showed 
> what I believe is a warning, maybe of no consequence:
> 
> W: 
> http://deb.debian.org/debian/pool/main/libb/libblockdev/libblockdev-crypto2_2.20-7+deb10u1_amd64.deb:
>  
> Automatically disabled Acquire::http::Pipeline-Depth due to incorrect 
> response from server/proxy. (man 5 apt.conf)
> 
> The udisksd man page says the daemon is started by dbus-daemon or 
> systemd.  However, it is not started by inserting a USB device.  I
> tried starting it manually (with USB device inserted) and received
> this:
> 
> root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
> [1] 523
> root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon 
> version 2.8.1 starting
> 
> ** (udisksd:523): WARNING **: 07:27:15.773: failed to load module 
> mdraid: libbd_mdraid.so.2: cannot open shared object file: No such
> file or directory
> sh: 1: dmidecode: not found
> 
> (udisksd:523): udisks-WARNING **: 07:27:15.776: Failed to load the 
> 'mdraid' libblockdev plugin
> udisks-Message: 07:27:16.017: Acquired the name
> org.freedesktop.UDisks2 on the system message bus
> 
> If that library file was needed it should have been loaded by the 
> installer.  I don't know what to do from here.
> 
> I use openbox and xterms if that info. is needed.
> 
> Best regards,
> Fred
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Hi,
try

apt install libblockdev-mdraid2

Ciao,
Tito
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/11/21 7:05 AM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 17:37:13 -0700
Fred  wrote:


On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 08:49:24 -0700
Fred  wrote:
   

Hello,

I have a new Beowulf AMD64 install and am having trouble mounting
USB storage devices.

The USB keyboard and mouse work ok.  lsusb shows the storage device
is present.  The usbmount program is apparently no longer available
and I haven't been able to find what took its place.  I have
another computer that had Debian Jessie installed then was
upgraded to Beowulf x86.  It has usbmount and will automatically
mount USB storage devices.

What do I need to install?


I use udisks2 to automount external USB devices.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
   

Hi,
I found udisks2 installed on the computer that automatically mounts
USB devices but there is no man page so I would not know how to use
it if installed on the other computer.


Not much to using it: apt-get install udisks2 and everything gets set
up. I used the defaults. Devices are mounted under /media/"your
username". If you run a panel, the udisks2 gadget shows up there with
additional options. Manual unmounting is necessary, but I use only a
window manager (Openbox) and lxpanel for my GUI, so your mileage may
vary if you use a desktop environment.

Others have shown you how to access the mans.  So, I won't repeat that.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hello,
I still need some help with this.
I installed udisks2.  The last line of the installation dialog showed 
what I believe is a warning, maybe of no consequence:


W: 
http://deb.debian.org/debian/pool/main/libb/libblockdev/libblockdev-crypto2_2.20-7+deb10u1_amd64.deb: 
Automatically disabled Acquire::http::Pipeline-Depth due to incorrect 
response from server/proxy. (man 5 apt.conf)


The udisksd man page says the daemon is started by dbus-daemon or 
systemd.  However, it is not started by inserting a USB device.  I tried 
starting it manually (with USB device inserted) and received this:


root@aragog:/home/fred# /usr/lib/udisks2/udisksd &
[1] 523
root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon 
version 2.8.1 starting


** (udisksd:523): WARNING **: 07:27:15.773: failed to load module 
mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file 
or directory

sh: 1: dmidecode: not found

(udisksd:523): udisks-WARNING **: 07:27:15.776: Failed to load the 
'mdraid' libblockdev plugin
udisks-Message: 07:27:16.017: Acquired the name org.freedesktop.UDisks2 
on the system message bus


If that library file was needed it should have been loaded by the 
installer.  I don't know what to do from here.


I use openbox and xterms if that info. is needed.

Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

On 12/6/21 22:27, aitor wrote:

I've just pushed the changes to gitea.devuan.dev. Look at the lines
107-112 in worker.cpp [*]. Yes, I'm using inotify :)


This is the link to the gui:

https://gitea.devuan.dev/aitor_czr/hopman/src/branch/master/hopman-1.0/gtkmm 



And, by the bye, the newest libudev-compat:

https://gitea.devuan.dev/aitor_czr/libudev-compat/src/branch/master 



Cheers,

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

Hi,

On 12/6/21 22:22, Didier Kryn wrote:

     I was never able to understand the ABI of libudev, due to the
absence of a manual. I have a great admiration for Jude and you to have
understood it. I will have a look at libudev-monitor.c . Nevertheless,
and whatever the method used (netlink for libudev or files for
libudev-compat), it relies on the hotplugger to populate its database. I
don't think this makes a big difference, except that udev make things
more confuse by using the same netlink as the kernel to talk to libudev.

     It seems to me that, with libudev-compat you could have Vdevd create
the symlinks, so that your problem would be solved. Do I understand
well? This seems to me completely independant of Hopman which is desirable.


Yes, you understood well. And i think the problem has been partially 
addressed.


Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

Hi Steve,

On 12/6/21 21:29, Steve Litt wrote:

Hi Aitor,

Inotify is the Linux-official way of finding device events. As far as I
know, inotify doesn't care whether you use udev, eudev or vdev, which
in my opinion makes it superior. I'd prefer not to have a Hopman with
all sorts of logic if vdev, elsif eudev, else udev, ESPECIALLY if the
device handler decision is made at compile time. Only slightly
better would be to have three Hopmans: One for each device handler.

If there are missing symlinks in /dev/disk, why not fix that root cause
and let the inotify authors worry about different device handlers,
rather than base your program logic on something the systemd people can
change any time, possibly forcing vdev and eudev to change in order to
keep up?

I've used inotify: It's an excellent way to find specific events,
although the filtering of the event stream is somewhat complex. Why not
reconsider using inotify?


Sorry if i've been unclear... I started my first post saying:

"At the *beginning* my point of view was quite different
because, on the contrary than Didier's design, i didn't use inotify to
become aware of any kernel uevent."

As i explained to Didier a couple of weeks ago, i'm not against the use of 
inotify.
Quite the opposite, i consider it a great tool. But i had problems with the 
mentioned
symlinks in /dev/disk and i took a temporary solution while i was designing the 
gui.
Indeed, the tarball in packages.gnuinos.org contains inotify, but i didn't 
upgrade the git
repository. I've just pushed the changes to gitea.devuan.dev. Look at the lines
107-112 in worker.cpp [*]. Yes, I'm using inotify :)

Cheers,

Aitor.

[*] You'll find the code a mess, i admit, but i'm improving it.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Didier Kryn]

Le 12/06/2021 à 20:59, aitor a écrit :
>
> Hi Didier,
>
> On 12/6/21 19:42, Didier Kryn wrote:
>>     Hello.
>>
>>     My aproach with Hopman was to be totally independant of the
>> hotplugger (udev/eudev/vdev/mdev, even systemd) provided it does the
>> job, which is to create the device special file in /dev (which the
>> kernel can do on its own). Then, if the hotplugger is capable to create
>> a symlink in /dev/disk/by-label, then Hopman uses it to display the disk
>> label and eventually passes it to the mount helper. 
> And this is the problem i was having with vdev. The capability to
> create symlinks in /dev/disk in the right way (maybe my fault),
> and this is the reason whyi was using blkid to get the disk label.
>> Hopman is a single-threaded program;
> I'm used to using a worker thread to make it update the gui without
> crashing. Although, I've been using your single-threaded version
> for a long time and it works fine, doing the job.
>>  its only dependencies are the presence of a
>> kernel with the inotify and signalfd APIs, which is the case since more
>> than a decade, unless disabled during kernel build, which would be evil.
>
> "Moreover, the approach of libudev-compat is generic enough to not
> specific to a particular kernel or device manager" -Jude Nelson.
>
> Btw, i'm splitting the content of the vdev project in vdevd and the
> helpers on the one hand, and libudev-compat on the other,increasing
> the version of libudev-compat in the same rate as libeudev for the
> sake of a less painful packaging maintainence:
>
> https://gitea.devuan.dev/aitor_czr/libudev-compat
> 
>
> What do you think about this?
>
> @Didier: if you are interested in how libudev-compat works, give
> special attention to libudev-monitor.c and libudev-fs.c
>
    Hi AItor.

    I was never able to understand the ABI of libudev, due to the
absence of a manual. I have a great admiration for Jude and you to have
understood it. I will have a look at libudev-monitor.c . Nevertheless,
and whatever the method used (netlink for libudev or files for
libudev-compat), it relies on the hotplugger to populate its database. I
don't think this makes a big difference, except that udev make things
more confuse by using the same netlink as the kernel to talk to libudev.

    It seems to me that, with libudev-compat you could have Vdevd create
the symlinks, so that your problem would be solved. Do I understand
well? This seems to me completely independant of Hopman which is desirable.

    Cheers.

--     Didier


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Steve Litt]

aitor said on Sat, 12 Jun 2021 00:46:08 +0200

 
>Thanks, Steve, it's named Hopman. A project started by Didier Kryn. At 
>the beginning my point of view was quite different
>because, on the contrary than Didier's design, i didn't use inotify to 
>become aware of any kernel uevent. The reason why
>i avoided inotify was related to some missing symlinks in /dev/disk
>when using vdev as device manager (hopman will be
>compatible with both eudev and vdev, and i wanted to use this
>directory as one of the wathdirs for inotify). Now i'm
>considering as a possible better approach to create vdev actions for 
>each (ADD|REMOVE|CHANGE) device events, and their equivalent
>udev rules for eudev to trigger them in a way that hopman only will be 
>notified about changes in the /proc/mounts file
>whenever the user uses pmount or any similar tool -via the gui of 
>hopman- to mount/unmount partitions.

Hi Aitor,

Inotify is the Linux-official way of finding device events. As far as I
know, inotify doesn't care whether you use udev, eudev or vdev, which
in my opinion makes it superior. I'd prefer not to have a Hopman with
all sorts of logic if vdev, elsif eudev, else udev, ESPECIALLY if the
device handler decision is made at compile time. Only slightly
better would be to have three Hopmans: One for each device handler.

If there are missing symlinks in /dev/disk, why not fix that root cause
and let the inotify authors worry about different device handlers,
rather than base your program logic on something the systemd people can
change any time, possibly forcing vdev and eudev to change in order to
keep up?

I've used inotify: It's an excellent way to find specific events,
although the filtering of the event stream is somewhat complex. Why not
reconsider using inotify?

Thanks,

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

On 12/6/21 13:01, aitor wrote:
This is exactly what i was talking about when saying "... to create 
vdev actions for each (ADD|REMOVE|CHANGE) device event". The BIND action
doesn't exist due to the removal of the netlink connection mentioned 
above.


Indeed, the README.md file says that eventfs is currently used to:

 - Give libudev-compat clients a way to receive device events while [ ... ]

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

On 12/6/21 12:47, aitor wrote:

On 12/6/21 12:22, aitor wrote:


Hi again,

On 12/6/21 0:46, aitor wrote:
Now i'm considering as a possible better approach to create vdev 
actions for each (ADD|REMOVE|CHANGE)


In the case of eudev, kernel uevents can be listen by "udevadm monitor".


We should distinguish here between two different events:

- The kernel uevent (BIND|ADD|REMOVE|CHANGE)

- The udev event: sent out by udev after the kernel uevent rule processing

Vdev's libudev-compat library removes this netlink connection to udev 
in favor of sending serialized device events by writing them as files.


And..., whops! Here, Jude Nelson says:

" It is highly recommended that users install eventfs

https://github.com/jcnelson/eventfs 

and use it to host libudev-compat's event directories. "

I didn't install it!

This is exactly what i was talking about when saying "... to create vdev 
actions for each (ADD|REMOVE|CHANGE) device event". The BIND action

doesn't exist due to the removal of the netlink connection mentioned above.

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

On 12/6/21 12:22, aitor wrote:


Hi again,

On 12/6/21 0:46, aitor wrote:
Now i'm considering as a possible better approach to create vdev 
actions for each (ADD|REMOVE|CHANGE)


In the case of eudev, kernel uevents can be listen by "udevadm monitor".


We should distinguish here between two different events:

- The kernel uevent (BIND|ADD|REMOVE|CHANGE)

- The udev event: sent out by udev after the kernel uevent rule processing

Vdev's libudev-compat library removes this netlink connection to udev in 
favor of sending serialized device events by writing them as files.


And..., whops! Here, Jude Nelson says:

" It is highly recommended that users install eventfs

https://github.com/jcnelson/eventfs 

and use it to host libudev-compat's event directories. "

I didn't install it!

Aitor.



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

Hi again,

On 12/6/21 0:46, aitor wrote:
Now i'm considering as a possible better approach to create vdev 
actions for each (ADD|REMOVE|CHANGE)


In the case of eudev, kernel uevents can be listen by "udevadm monitor".

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[aitor]

Hi,

On 11/6/21 23:04, Steve Litt wrote:

As I remember, Aitor created a really nice flash drive mounter. Does
anyone remember it?
Thanks, Steve, it's named Hopman. A project started by Didier Kryn. At 
the beginning my point of view was quite different
because, on the contrary than Didier's design, i didn't use inotify to 
become aware of any kernel uevent. The reason why
i avoided inotify was related to some missing symlinks in /dev/disk when 
using vdev as device manager (hopman will be
compatible with both eudev and vdev, and i wanted to use this directory 
as one of the wathdirs for inotify). Now i'm
considering as a possible better approach to create vdev actions for 
each (ADD|REMOVE|CHANGE) device events, and their equivalent
udev rules for eudev to trigger them in a way that hopman only will be 
notified about changes in the /proc/mounts file
whenever the user uses pmount or any similar tool -via the gui of 
hopman- to mount/unmount partitions.


Turning to the issues with the symlinks in /dev/disk/by-label, 
/dev/disk/by-path, etc... the problem was that all the
links were created statically during the boot process, that is, when 
/sbin/vdevd was started. However, after the removal
of the mouse or the keyboard, say, the missing symlinks in 
/dev/input/by-path, etc... didn't reappear once they were plugged in again.
I was wondering whether or not this was intended, but clearly Jude 
Nelson designed vdev to work dynamically.
After several testings, finally i found the origin of this erratic 
behaviour in the line 1664 of:


https://github.com/jcnelson/vdev/blob/master/vdevd/action.c 



I tried commenting this line and now symlinks appear/disappear in a 
dynamic way. Let's say in passing that i didn't find any unwanted 
colateral effect so far.
I think these are great news considering, on the other hand, that the 
boot time has been reduced to ~20 seconds (in a modern computer), which 
is quite acceptable.


To end, I'm following this thread, and i had in mind to talk about 
hopman here. But i've been busy during these days...


I'll let you know :)

Cheers,

Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Steve Litt]

Fred said on Thu, 10 Jun 2021 17:37:13 -0700


>> 
>> I use udisks2 to automount external USB devices.
>> 
>> B
>> ___
>> Dng mailing list
>> Dng@lists.dyne.org
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>   
>Hi,
>I found udisks2 installed on the computer that automatically mounts
>USB devices but there is no man page so I would not know how to use it
>if installed on the other computer.
>Best regards,
>Fred

As I remember, Aitor created a really nice flash drive mounter. Does
anyone remember it?

SteveT

Steve Litt 
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[g4sra via Dng]

‐‐‐ Original Message ‐‐‐

On Friday, June 11th, 2021 at 2:58 PM, Fred  wrote:

> On 6/10/21 11:29 PM, Stefan Krusche wrote:
<--snip-->
> 

> I did find the man page for udisks. I will study that and the article
> for autofs. Likely one of them will work fine.

The intended use 'autofs' is for automatic mounting of network filesystems in 
real-time as\when you access them.
It requires prior knowledge and configuration of the media to be mounted, it is 
not relevant to directly connected USB devices (unless that device is a network 
interface).

publickey - g4sra@protonmail.com - 0x42E94623.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Thu, 10 Jun 2021 17:37:13 -0700
Fred  wrote:

> On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:
> > On Thu, 10 Jun 2021 08:49:24 -0700
> > Fred  wrote:
> >   
> >> Hello,
> >>
> >> I have a new Beowulf AMD64 install and am having trouble mounting
> >> USB storage devices.
> >>
> >> The USB keyboard and mouse work ok.  lsusb shows the storage device
> >> is present.  The usbmount program is apparently no longer available
> >> and I haven't been able to find what took its place.  I have
> >> another computer that had Debian Jessie installed then was
> >> upgraded to Beowulf x86.  It has usbmount and will automatically
> >> mount USB storage devices.
> >>
> >> What do I need to install?  
> > 
> > I use udisks2 to automount external USB devices.
> > 
> > B
> > ___
> > Dng mailing list
> > Dng@lists.dyne.org
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >   
> Hi,
> I found udisks2 installed on the computer that automatically mounts
> USB devices but there is no man page so I would not know how to use
> it if installed on the other computer.

Not much to using it: apt-get install udisks2 and everything gets set
up. I used the defaults. Devices are mounted under /media/"your
username". If you run a panel, the udisks2 gadget shows up there with
additional options. Manual unmounting is necessary, but I use only a
window manager (Openbox) and lxpanel for my GUI, so your mileage may
vary if you use a desktop environment.

Others have shown you how to access the mans.  So, I won't repeat that.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/10/21 11:29 PM, Stefan Krusche wrote:

Hi Fred,

Am Freitag, 11. Juni 2021 schrieb Fred:


I found udisks2 installed on the computer that automatically mounts
USB devices but there is no man page so I would not know how to use
it if installed on the other computer.


You can find man pages like this:

$ apropos udisks
udisks (8)   - Disk Manager
udisks2.conf (5) - The udisks2 configuration file
udisksctl (1)- The udisks command line tool
udisksd (8)  - The udisks system daemon
umount.udisks2 (8)   - unmount file systems that have been mounted by
UDisks2

Does the same:

$ man -k udisks
udisks (8)   - Disk Manager
udisks2.conf (5) - The udisks2 configuration file
udisksctl (1)- The udisks command line tool
udisksd (8)  - The udisks system daemon
umount.udisks2 (8)   - unmount file systems that have been mounted by
UDisks2

Regards,
Stefan
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
I did find the man page for udisks.  I will study that and the article 
for autofs.  Likely one of them will work fine.


Thanks for the help.
Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Stefan Krusche]

Hi Fred,

Am Freitag, 11. Juni 2021 schrieb Fred:

> I found udisks2 installed on the computer that automatically mounts
> USB devices but there is no man page so I would not know how to use
> it if installed on the other computer.

You can find man pages like this:

$ apropos udisks
udisks (8)   - Disk Manager
udisks2.conf (5) - The udisks2 configuration file
udisksctl (1)- The udisks command line tool
udisksd (8)  - The udisks system daemon
umount.udisks2 (8)   - unmount file systems that have been mounted by
UDisks2

Does the same:

$ man -k udisks
udisks (8)   - Disk Manager
udisks2.conf (5) - The udisks2 configuration file
udisksctl (1)- The udisks command line tool
udisksd (8)  - The udisks system daemon
umount.udisks2 (8)   - unmount file systems that have been mounted by
UDisks2

Regards,
Stefan
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote:

On Thu, 10 Jun 2021 08:49:24 -0700
Fred  wrote:


Hello,

I have a new Beowulf AMD64 install and am having trouble mounting USB
storage devices.

The USB keyboard and mouse work ok.  lsusb shows the storage device
is present.  The usbmount program is apparently no longer available
and I haven't been able to find what took its place.  I have another
computer that had Debian Jessie installed then was upgraded to
Beowulf x86.  It has usbmount and will automatically mount USB
storage devices.

What do I need to install?


I use udisks2 to automount external USB devices.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Hi,
I found udisks2 installed on the computer that automatically mounts USB 
devices but there is no man page so I would not know how to use it if 
installed on the other computer.

Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[terryc]

On Thu, 10 Jun 2021 13:06:07 -0700
Fred  wrote:

> On 6/10/21 10:01 AM, Arnt Karlsen wrote:
> > On Thu, 10 Jun 2021 08:49:24 -0700, Fred wrote in message
> > :
> >   
> >> Hello,
> >>
> >> I have a new Beowulf AMD64 install and am having trouble mounting
> >> USB storage devices.
> >>
> >> The USB keyboard and mouse work ok.  lsusb shows the storage device
> >> is present.  The usbmount program is apparently no longer available
> >> and I haven't been able to find what took its place.  I have
> >> another computer that had Debian Jessie installed then was
> >> upgraded to Beowulf x86.  It has usbmount and will automatically
> >> mount USB storage devices.
> >>
> >> What do I need to install?  
> > 
> > ..easy now, first find out a few things.
> > "fdisk -l " as root will tell you which filesystems you have
> > whenever you stick something into your box.
> > "mount -v /dev/a_filesystem_found_with_fdisk_-l_ /mnt" will
> > either confirm it worked, or be a little bit more verbose
> > about why it failed.
> > Pile on more "-v" if you want more, or chk "info mount".
> > 
> > .."man -k mount " will tell you what mount like things you have
> > installed, "apt-cache search mount " will search for more of
> > these mount like things, e.g. "apt-cache show mount " will give
> > you more details on each search find.
> > 
> > ..I'm really a little too old fashion to advice on those new
> > fancy usb key etc automount things.  Anyone?
> > 
> >   
> Hi,
> fdisk -l showed the device to be /dev/sdb1.
> Using your mount command it was mounted and could be accessed.  I
> guess this answers my question but I was hoping for some automation
> like usbmount where the device is plugged in and it just works.

Does it consistently appears as /dev/sdb1?
If so, you could try defining it in /etc/fstab. Similar to a hard disk
if it is permanently loaded, or similar to cd/dvd drive if otherwise.

When I insert the little SDcards and load external drive devices, I
usually 'sudo dmesg' and note the device listed at the end, then
/mount /dev/sd'X''1/ /mnt/usb'Y'.

In my case, it is usually i for 1, then j, then k, etc.

Do not forget to 'umount /mnt/cdrom' or where ever you have it mounted
before you unplug or remove it.



>
Another poster suggested autofs which I found to be already
> installed.  I suspect it is the replacement for usbmount and I just
> have to study the autofs article to get it configured.
> Thanks for the help!
> Best regards,
> Fred
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Patrick Bartek via Dng]

On Thu, 10 Jun 2021 08:49:24 -0700
Fred  wrote:

> Hello,
> 
> I have a new Beowulf AMD64 install and am having trouble mounting USB 
> storage devices.
> 
> The USB keyboard and mouse work ok.  lsusb shows the storage device
> is present.  The usbmount program is apparently no longer available
> and I haven't been able to find what took its place.  I have another
> computer that had Debian Jessie installed then was upgraded to
> Beowulf x86.  It has usbmount and will automatically mount USB
> storage devices.
> 
> What do I need to install?

I use udisks2 to automount external USB devices.

B
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Fred]

On 6/10/21 10:01 AM, Arnt Karlsen wrote:

On Thu, 10 Jun 2021 08:49:24 -0700, Fred wrote in message
:


Hello,

I have a new Beowulf AMD64 install and am having trouble mounting USB
storage devices.

The USB keyboard and mouse work ok.  lsusb shows the storage device
is present.  The usbmount program is apparently no longer available
and I haven't been able to find what took its place.  I have another
computer that had Debian Jessie installed then was upgraded to
Beowulf x86.  It has usbmount and will automatically mount USB
storage devices.

What do I need to install?


..easy now, first find out a few things.
"fdisk -l " as root will tell you which filesystems you have
whenever you stick something into your box.
"mount -v /dev/a_filesystem_found_with_fdisk_-l_ /mnt" will
either confirm it worked, or be a little bit more verbose
about why it failed.
Pile on more "-v" if you want more, or chk "info mount".

.."man -k mount " will tell you what mount like things you have
installed, "apt-cache search mount " will search for more of
these mount like things, e.g. "apt-cache show mount " will give
you more details on each search find.

..I'm really a little too old fashion to advice on those new
fancy usb key etc automount things.  Anyone?



Hi,
fdisk -l showed the device to be /dev/sdb1.
Using your mount command it was mounted and could be accessed.  I guess 
this answers my question but I was hoping for some automation like 
usbmount where the device is plugged in and it just works.  Another 
poster suggested autofs which I found to be already installed.  I 
suspect it is the replacement for usbmount and I just have to study the 
autofs article to get it configured.

Thanks for the help!
Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] USB mount problem

[Arnt Karlsen]

On Thu, 10 Jun 2021 08:49:24 -0700, Fred wrote in message 
:

> Hello,
> 
> I have a new Beowulf AMD64 install and am having trouble mounting USB 
> storage devices.
> 
> The USB keyboard and mouse work ok.  lsusb shows the storage device
> is present.  The usbmount program is apparently no longer available
> and I haven't been able to find what took its place.  I have another
> computer that had Debian Jessie installed then was upgraded to
> Beowulf x86.  It has usbmount and will automatically mount USB
> storage devices.
> 
> What do I need to install?

..easy now, first find out a few things.
"fdisk -l " as root will tell you which filesystems you have 
whenever you stick something into your box.
"mount -v /dev/a_filesystem_found_with_fdisk_-l_ /mnt" will 
either confirm it worked, or be a little bit more verbose 
about why it failed.  
Pile on more "-v" if you want more, or chk "info mount".

.."man -k mount " will tell you what mount like things you have
installed, "apt-cache search mount " will search for more of 
these mount like things, e.g. "apt-cache show mount " will give 
you more details on each search find.

..I'm really a little too old fashion to advice on those new 
fancy usb key etc automount things.  Anyone?


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng