[DNG] package search methods was ( USB mount problem)
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, Why does apt-cache search gvfs-udisk* not find these? Why does apt-file search gvfs_udisk* not find these? Why does the package search page on debian.org and devuan.org not find these? apt-file search requires entering the exact name. I may not know that. What flippin' good is it? Best regards, Fred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
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
<--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
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
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
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
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
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] Hopman and inotify
Le 13/06/2021 à 23:29, Haines Brown a écrit : > I tried hopman some years ago and loved it, But when installed on a > new machine failed copy the code. Would anyone indulge me by pointing > to a link to the current stete of the application? > I've not followed the change in git repository of Devuan. In the mean time i tried to put into the same source tree all the files necessary for internationalization and didn't find a satisfactory way to do it. I have some work to do to clean up the tree from internationalization files and correct a little bug. Then I should push the tree to the new git repository. Then I will let you know. I have been lazy during the two last years. Motivation is back but I'm currently travelling. -- Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ..maybe webmin?, was: Cockpit removal might make sense
On 15/06/2021 10:42, Olaf Meeuwissen via Dng wrote: > > If projects decide to throw in their lot with systemd > (as in not accepting patches to cater to non-systemd setups), I think > they deserve to be plonked by distributions that don't support systemd. As a matter of interest, can anyone say how often this is happening? -- Mark Rousell ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ..maybe webmin?, was: Cockpit removal might make sense
tito via Dng writes: > On Sun, 13 Jun 2021 19:41:28 +0900 > Olaf Meeuwissen via Dng wrote: > >> d...@d404.nl writes: >> >> > Not hindered by any knowledge about system programming I am >> > wondering how much work it would be to implement a socket >> > activation interface without systemd. Although what I read about >> > its design it is unnecessary complicated. Using a tinylog component >> > in systemd until syslogd is loaded is one example of such >> > complicating solution. >> > >> > Has anyone invested some time in analyzing systemd's socket >> > activation and mind to share it on this list or in email? >> >> When I read[1] >> >> Cockpit itself doesn’t eat resources or even run in the background >> when you’re not using it. It runs on demand, thanks to systemd >> socket activation. > > Hi, > would it be possible to start it with a initscript and let it run? > and totally ignore this socket stuff? Probably, but then cockpit would "eat resources". >> all I could think of was that inetd and xinetd have been doing that >> job for a (couple of) decade(s) already. Of course, running (x)inetd also eats resources but the question then becomes whether running systemd consumes more resources then (x)inetd plus your choice of init. # That's assuming you're willing to consider running systemd to begin # with ;-) >> The only other mention of systemd on that webpage is one in a longish >> "subset of tasks you can perform on each host running Cockpit" that >> says you can >> >> Inspect and interact with systemd-based services > > Having briefly looked and grepped the source when I removed webmin > from my systems (when it was backdoored) the biggest problem > is that cockpit calls systemctl, hostnamectl and friends directly so > without systemd functionality is crippled as no alternative functions > are provided. It could be an idea and helpful for devuan mastering > the systemd dependency epidemic to create some wrappers for > this systemd binaries as compatibility layer rather than try to modify > every program out there that thinks it needs to depend on systemd, > that way you just modify the dependencies of the cockpit package, > resign it and you are good to go. While I can understand your line of thinking, I think it's a bit of a slippery slope. If projects decide to throw in their lot with systemd (as in not accepting patches to cater to non-systemd setups), I think they deserve to be plonked by distributions that don't support systemd. # FTR, I have no sympathy for cockpit. A (remote) command-line suits me # just fine. Folks not comfortable with that shouldn't be administering # "servers" to begin with, IMNSHO. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
