Re: [DNG] grep handles ISO-8859 encoded text file as binary file.
Hughe Chung escribió: Hi, I got to use -a option to search words on C code files. $ grep tesselate dome_math.c Binary file dome_math.c matches Is this only due to encoding, or may be due to a DOS/Unix difference? If I were to bet, I would say that the file dome_math.c is not correctly formatted, or has an incorrect BOM at start, or so. Create copies of two of these files (one of each class) with just the first three lines, and try again. Paste the files to the list if still happening. Regards Noel er Envite binqxDLVsAWlL.bin Description: Clave PGP pública pgpNI3OfUmPmz.pgp Description: Firma digital PGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Didier Kryn escribió: This isn't just a theoretical thing, lots of people don't label their thumb drives. Another issue is a lot of thumb drives have the same label. I bet there are millions with the label "backup". But there are tools on Linux to add a label to a filesystem; here is the first thing I do to a new usb stick: /sbin/dosfslabel /dev/sdb1 $my_name Very usefull when exchanging sticks. Didier All my sticks are labeled, and I labeled none of them. They all just came factory formatted as fat and factory labeled with the producer's name. This is my EMTEC stick (at /media/EMTEC) , this my BASF stick (at /media/BASF)... useful enough, since I do not use to plug several sticks at the same time, and even less several of the same brand. Regards Noel er Envite binah7nz_Ljli.bin Description: Clave PGP pública pgpVyc3lVCJVp.pgp Description: Firma digital PGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 28/04/2016 02:16, Steve Litt a écrit : I think my original handled that, by creating a database of UUID, label and device name (and now it's going to need to include user mounting it too). So a little universal shellscript can go in the database (which of course is a simple file), find the label, and read across the row to find its current device so you can plug that into an environment variable and use that. I think the smartest job would be to read a config files for instructions based on the uuid. Then, only if there aren't instructions for the uuid of the removable media, fall back to label, This gives an opportunity to the admin to carefully craft what she wants to do with the most important media. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Steve Litt escribió: I don't know of a way to tell pmount or udev/vdev/eudev to assign a particular device to a thumb drive, without manually doing all the mknod and all that. Excellent idea, very useful. But if something's already assigned to that device, you're sol. Insert pendrive labeled BACKUP -> Mount at /media/BACKUP Insert another pendrive also labeled BACKUP -> Mount at /media/BACKUP_1 Not so hard :D Regards Noel er Envite bind673l1rG_r.bin Description: Clave PGP pública pgpmcLy7AENVY.pgp Description: Firma digital PGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 28/04/2016 01:29, Steve Litt a écrit : No matter what you do, somebody's going to pull one out without umounting. I've done it. Lots of people have. Oops! Perhaps we can include a daemon that runs sync command every 10 seconds. I doubt that would have much effect, but would probably minimize problems with just yanking out thumb drives. Every human makes errors. But there should be an easy way to do things properly. I wouldn't run this daemon. Anyway, after copying lots of photos or videos, sync (or umount) can take minutes. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 28/04/2016 01:24, Steve Litt a écrit : On Wed, 27 Apr 2016 19:35:08 +0200 Didier Kryn wrote: Le 27/04/2016 19:13, Steve Litt a écrit : Not all filesystems have labels. For my information, could you list some? Every filesystem I ever used to format disks had one (ext?, reiserfs, btrfs, vfat) Didier You can make one with fdisk or cfdisk or parted or gparted or similar. Just fail to include a label. This isn't just a theoretical thing, lots of people don't label their thumb drives. Another issue is a lot of thumb drives have the same label. I bet there are millions with the label "backup". But there are tools on Linux to add a label to a filesystem; here is the first thing I do to a new usb stick: /sbin/dosfslabel /dev/sdb1 $my_name Very usefull when exchanging sticks. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chroot sees wrong version of libc
Le 27/04/2016 23:29, Haines Brown a écrit : I found I had to bind mount /sys before I could install grub2. A few tricks: It is most of the times necessary to bind-mount /proc and /sys when working in a chroot. Depending what you do, /dev may also be necessary. Also copy /etc/hosts and /etc/resolv.conf when working with network. Happy that it worked :-) Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] grep handles ISO-8859 encoded text file as binary file.
Hi, I got to use -a option to search words on C code files. $ grep tesselate dome_math.c Binary file dome_math.c matches $ file *.c 3ds_utils.c: C source, ISO-8859 text dome_3ds.c: C source, ASCII text dome.c: C source, ASCII text dome_cover.c: C source, ASCII text dome_file.c: C source, ASCII text dome_layout.c: C source, ASCII text dome_math.c: C source, ISO-8859 text dome_struts.c: C source, ASCII text main.c: C source, ASCII text utils.c: C source, ASCII text $ grep -a tesselate dome_math.c static void tesselate1(const Dome *in, Face face, int f, Dome *out, tesselate(const Dome *in, Dome *out, int f) tesselate1(in, in->faces[i], f, out, &fcount, could not be a binary file. &vcount, &ecount); tesselate1(const Dome *in, Face face, int f, Dome *out, fprintf(stderr, “Internal error: out of faces in tesselate\n”); fprintf(stderr, “Internal error: out of vertices in tesselate\n”); There was a bug report. https://lists.gnu.org/archive/html/bug-grep/2014-12/msg00049.html ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On 04/28/2016 09:28 AM, fsmithred wrote: You could get the label from lsblk, do 'pmount label' and it will be mounted at /media/label. Every time you plug in a thumb drive labeled backup, it'll go to the same place. If you unmount the drive, /media/label will no longer exist, so you could even have the backup script check to make sure it's there. I am a little bit fuzzy as to what distro did it, but I recall quite a few did. Then along came unmemorable UUIDs. Sometimes I wonder if I am the only one who labels partitions still. Glad to see I am not alone. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On 04/27/2016 08:16 PM, Steve Litt wrote: > On Wed, 27 Apr 2016 19:51:54 -0400 > Hendrik Boom wrote: > >> On Wed, Apr 27, 2016 at 07:24:29PM -0400, Steve Litt wrote: >>> >>> Another issue is a lot of thumb drives have the same label. I bet >>> there are millions with the label "backup". >> >> And I'd like all my drives labelled "backup" to be mounted at the >> same mountpoint so I can use one backup script for all of them. >> >> I really believe in multiple backups. >> >> -- hendrik > > Ohhh! I see what you're doing: You're keying completely off > labels so scripts work. Makes perfect sense. > > I don't know of a way to tell pmount or udev/vdev/eudev to assign a > particular device to a thumb drive, without manually doing all the > mknod and all that. Excellent idea, very useful. But if something's > already assigned to that device, you're sol. > > But... > > I think my original handled that, by creating a database of UUID, label > and device name (and now it's going to need to include user mounting it > too). So a little universal shellscript can go in the database (which > of course is a simple file), find the label, and read across the row to > find its current device so you can plug that into an environment > variable and use that. > > SteveT > You could get the label from lsblk, do 'pmount label' and it will be mounted at /media/label. Every time you plug in a thumb drive labeled backup, it'll go to the same place. If you unmount the drive, /media/label will no longer exist, so you could even have the backup script check to make sure it's there. -fsr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, Apr 27, 2016 at 08:16:31PM -0400, Steve Litt wrote: > On Wed, 27 Apr 2016 19:51:54 -0400 > Hendrik Boom wrote: > > > On Wed, Apr 27, 2016 at 07:24:29PM -0400, Steve Litt wrote: > > > > > > Another issue is a lot of thumb drives have the same label. I bet > > > there are millions with the label "backup". > > > > And I'd like all my drives labelled "backup" to be mounted at the > > same mountpoint so I can use one backup script for all of them. > > > > I really believe in multiple backups. > > > > -- hendrik > > Ohhh! I see what you're doing: You're keying completely off > labels so scripts work. Makes perfect sense. > > I don't know of a way to tell pmount or udev/vdev/eudev to assign a > particular device to a thumb drive, without manually doing all the > mknod and all that. Excellent idea, very useful. But if something's > already assigned to that device, you're sol. > > But... > > I think my original handled that, by creating a database of UUID, label > and device name (and now it's going to need to include user mounting it > too). So a little universal shellscript can go in the database (which > of course is a simple file), find the label, and read across the row to > find its current device so you can plug that into an environment > variable and use that. The current method of keying off the UUID in /etc/fstab doesn't work; it won't allow specifying more than on UUID at a mount point, even if they are never presented at once. (which is something I'd never do to two independent backup drives) -- hendrik > > SteveT > > Steve Litt > April 2016 featured book: Rapid Learning for the 21st Century > http://www.troubleshooters.com/rl21 > ___ > 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] For all you automounter programmers
On Wed, 27 Apr 2016 19:51:54 -0400 Hendrik Boom wrote: > On Wed, Apr 27, 2016 at 07:24:29PM -0400, Steve Litt wrote: > > > > Another issue is a lot of thumb drives have the same label. I bet > > there are millions with the label "backup". > > And I'd like all my drives labelled "backup" to be mounted at the > same mountpoint so I can use one backup script for all of them. > > I really believe in multiple backups. > > -- hendrik Ohhh! I see what you're doing: You're keying completely off labels so scripts work. Makes perfect sense. I don't know of a way to tell pmount or udev/vdev/eudev to assign a particular device to a thumb drive, without manually doing all the mknod and all that. Excellent idea, very useful. But if something's already assigned to that device, you're sol. But... I think my original handled that, by creating a database of UUID, label and device name (and now it's going to need to include user mounting it too). So a little universal shellscript can go in the database (which of course is a simple file), find the label, and read across the row to find its current device so you can plug that into an environment variable and use that. SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, Apr 27, 2016 at 07:24:29PM -0400, Steve Litt wrote: > > Another issue is a lot of thumb drives have the same label. I bet there > are millions with the label "backup". And I'd like all my drives labelled "backup" to be mounted at the same mountpoint so I can use one backup script for all of them. I really believe in multiple backups. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, 27 Apr 2016 19:22:06 +0200 Didier Kryn wrote: > Le 27/04/2016 19:17, Steve Litt a écrit : > > On Wed, 27 Apr 2016 09:10:25 +0200 > > Didier Kryn wrote: > > > > > >> Wishlist: the "automounter" shouldn't mount automatically, by > >> default. It should rather offer an easy mount-handle, and the > >> umount counterpart. > > What is an "easy mount-handle"? > > > > > I mean there might be a list of connected removable media, > showing which ones are mounted and a way to toggle mount/umount for > each of them. I remind you that filesystems mus be unmounted before > they are removed; this is what is called "remove safely" or "eject" > by DEs' helpers. Yes! One program pops up upon insertion of a thumb drive, and asks mount or not on that thumbdirve and shows the result. But another program, started by the user, lists every thumb drive, whether it's mounted or not, if it's mounted the user who has it mounted, and gives mount options for the unmounted ones, and umount options, IF THE USER IS THE ONE WHO MOUNTED IT, for the mounted ones. No matter what you do, somebody's going to pull one out without umounting. I've done it. Lots of people have. Oops! Perhaps we can include a daemon that runs sync command every 10 seconds. I doubt that would have much effect, but would probably minimize problems with just yanking out thumb drives. -- SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, 27 Apr 2016 19:35:08 +0200 Didier Kryn wrote: > Le 27/04/2016 19:13, Steve Litt a écrit : > > Not all filesystems have labels. > For my information, could you list some? Every filesystem I ever > used to format disks had one (ext?, reiserfs, btrfs, vfat) > > Didier You can make one with fdisk or cfdisk or parted or gparted or similar. Just fail to include a label. This isn't just a theoretical thing, lots of people don't label their thumb drives. Another issue is a lot of thumb drives have the same label. I bet there are millions with the label "backup". SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Hi, what about -> https://ignorantguru.github.io/udevil ? On 2016-04-26 15:08, Steve Litt wrote: Hi all, It seems like everyone in the Devuan community has written his or her own usb drive automounter, and I've just discovered something that will help us all. The thumb drive you buy at the store is formatted with a Windows file system, and that's a good thing because it's mountable pretty much by any device or computer. Sneakernet at its best. But you must be root to mount it unless it's declared in /etc/fstab, which is a bad idea for a number of reasons. And if you mount it as root, normally the owner is root, and with its (typical) 755 permissions, a normal user can't write to it. Defeating its whole purpose. What you really want is for anyone in a certain group to be able to write to it. I used group "floppy", because a USB drive is a pretty good analog to a floppy, and floppies aren't even used much anymore. So do the mount like this: mount -o gid=floppy,fmask=113,dmask=002 /dev/sdd1 /mnt/thumb or mount -o gid=floppy,fmask=113,dmask=002 /dev/sdd1 /mnt/sdd1 The gid= means the thumb drive and all its files are group "floppy", and the fmask and dmask make directories 775 and 664 respectively, so group "floppy" can write. I haven't yet tried this on a genuine ext4 formatted thumb drive, so I don't know whether it would have any downside there. If so, the different mount options would only appear if the thumb drive was determined to be vfat/fat/msdos etc. SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Stop slacking you lazy bum! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On 04/27/2016 01:27 PM, Steve Litt wrote: >> >> That's pretty much what my usb-mounter does. Inotifywait runs when >> you log into the desktop, and when you plug in a thumb drive, it pops >> up a window showing you the partitions on that device. You then >> choose one to mount, and the script runs pmount in your name. > > That sounds *perfect* to me, always assuming the "window" is a CLI > question and answer i X isn't running. Where's the source code? I'd like > to start using it. > > Somebody suggested we package an automounter for Devuan. What you > describe sounds like the right thing. > Source code? Here's a link to a tarball that contains the scripts and instructions on what goes where. I haven't packaged it, because I didn't think it was finished. https://sourceforge.net/projects/refracta/files/testing/usbwait.tar.gz/download > >> Bypassing the popup window and automounting would be a simple edit, > > My no-user-confirmation version was problematic and vaguely disturbing. > I'd leave the user in the loop. > >> as would making it work without a gui. > > Yes. This being Devuan, some facility for asking and recieving an > answer should be provided even if X isn't runnnig. > Try the following for a no-gui solution. Once you've mounted something(s) you can see what removable devices are mounted by running pmount with no arguments. Then 'pumount sdd1' or whatever to unmount it. If we worked labels into this somehow, you could 'pumount label'. If you try to mount the same partition twice, pmount complains and the script exits. No harm done. #!/usr/bin/env bash # # thumb-pick.sh usbdevlist=$(/usr/sbin/hwinfo --usb --short | awk '/dev\/sd/ {print $1}') usbdevfulllist=$(/usr/sbin/hwinfo --usb --short | awk '/dev\/sd/ {print $0}') if [[ $(echo "$usbdevlist" | wc -l) = 1 ]] ; then device="$usbdevlist" else echo -e "\n\tLIST OF USB DRIVES\n$usbdevfulllist\n\nSelect a device:" select opt in $usbdevlist ; do device=$(echo "$opt" | awk '{ print $1 }') break done fi partition_list=$(lsblk -l | grep ${device##*/}[1-9] | awk '{ print $1 }') echo -e "\n\nSelect a partition to mount:" select part in $partition_list ; do pmount "$part" || exit 1 df -h exit 0 done Have fun with it. -fsr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chroot sees wrong version of libc
Haines Brown writes: > On Wed, Apr 27, 2016 at 06:05:56PM +0200, Didier Kryn wrote: >> Le 27/04/2016 17:47, Haines Brown a écrit : >> > >> >I'm doing a cross install of devuan Alpha 4 onto a newly partitioned >> >hard disk (/dev/sda1) in same box as my running Debian Wheezy system >> >(/dev/sdb1). I partitioned, formatted and mounted the needed new disk's >> >partitions; I downloaded debootstrap_1.0.75-1*.deb to a working >> >directory in my current sytem; I unpacked the data tarball, Finally I >> >ran the devuan debootstrap to install a base system on the target >> >drive. >> > >> > # debootstrap --no-check-gpg jessie /mnt/debinst \ >> >http://packages.devuan.org/merged >> > >> >> I think you should use the --foreign option of debootstrap. >> >> first 'debootstrap --no-check-gpg jessie /mnt/debinst' >> >> then 'chroot /mnt/debinst debootstrap --second-stage' > > Didier, thanks! That was the answer. I was confused by the debootstrap > man page because it sounded like the --foreign option was for > non-matching architectures. And that's what it is. There's absolutely no problem with debootstrapping a Devuan jessie on Debian wheezy amd64 using either amd64 or i386 (if the kernel supports this) and in my opinion, the error messages you wrote about earlier are impossible to reproduce in the way you claimed to have seen them. In particular, the /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /bin/bash) refers to the C library from the libc-i686 (wheezy) package and no -i686 package gets installed when running debootstrap as you wrote. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chroot sees wrong version of libc
On Wed, Apr 27, 2016 at 06:05:56PM +0200, Didier Kryn wrote: > Le 27/04/2016 17:47, Haines Brown a écrit : > > > >I'm doing a cross install of devuan Alpha 4 onto a newly partitioned > >hard disk (/dev/sda1) in same box as my running Debian Wheezy system > >(/dev/sdb1). I partitioned, formatted and mounted the needed new disk's > >partitions; I downloaded debootstrap_1.0.75-1*.deb to a working > >directory in my current sytem; I unpacked the data tarball, Finally I > >ran the devuan debootstrap to install a base system on the target > >drive. > > > > # debootstrap --no-check-gpg jessie /mnt/debinst \ > > http://packages.devuan.org/merged > > > > I think you should use the --foreign option of debootstrap. > > first 'debootstrap --no-check-gpg jessie /mnt/debinst' > > then 'chroot /mnt/debinst debootstrap --second-stage' Didier, thanks! That was the answer. I was confused by the debootstrap man page because it sounded like the --foreign option was for non-matching architectures. But adding that option to debootstrap allowe me to go through the entire devuan installation. There were a couple hiccups, but I await the devuan installation guide before bringing them up. I found I had to bind mount /sys before I could install grub2. My /dev directly already well populated; I had no /proc directory, but mount tells me: none on /proc type proc (rw,relatime). The /sys directory exists, but is empty, so I do # mount -o bind /sys/ /mnt/debinst/sys and grub installation then went smoothly. Finally I decided to beef things up with tasksel. I wanted at this point to install print server and SSH server. I select and try to install them. But I get: "tasksel: apt-get failed (100)". This error often because of error in sources.list. All I have in it is one line: deb http://packages.devuan.org/merged jessie main However, I have no problem installing cups-client (the equivalent of printer-server?), xorg and fluxbox individually. Whenever I install packages I'm warned that that the packages are untrusted and I have to tell aptitude to proceed anyway. I wonder if tasksel fails because it cannot convey a willingness to risk installing untrustworthy package? I should now have a bootable system thanks to your help. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, Apr 27, 2016 at 01:27:08PM -0400, Steve Litt wrote: > On Wed, 27 Apr 2016 08:25:02 -0400 > fsmithred wrote: > > > On 04/26/2016 09:32 PM, Steve Litt wrote: > > > On Tue, 26 Apr 2016 18:19:32 -0400 > > > fsmithred wrote: > > > > > > > > >> I like pmount for mounting usb devices. It's pretty smart. For > > >> removable devices, you don't need to list them > > >> in /etc/pmount.allow, and it handles encrypted filesystems > > >> (cryptsetup/luks). > > > > > > > > > Ahh, now I remember. Pmount isn't an AUTOmounter, you still must > > > tell it which device to mount. It doesn't mount the second you plug > > > in your thumb drive. > > > > > > Therefore: pmount, when combined with the inotifywait automounters > > > we've all made, should be perfect. > > > > > > Those pmount automounter commands should run as the user who plugs > > > in the thumb, so rather than running straight from the init, they > > > should probably run when you log in, and if there's already a copy > > > running when you log in, it does nothing. > > > > > > SteveT > > > > > > > That's pretty much what my usb-mounter does. Inotifywait runs when > > you log into the desktop, and when you plug in a thumb drive, it pops > > up a window showing you the partitions on that device. You then > > choose one to mount, and the script runs pmount in your name. > > That sounds *perfect* to me, always assuming the "window" is a CLI > question and answer i X isn't running. Where's the source code? I'd like > to start using it. > > Somebody suggested we package an automounter for Devuan. What you > describe sounds like the right thing. > > > > Bypassing the popup window and automounting would be a simple edit, > > My no-user-confirmation version was problematic and vaguely disturbing. > I'd leave the user in the loop. > > > as would making it work without a gui. > > Yes. This being Devuan, some facility for asking and recieving an > answer should be provided even if X isn't runnnig. If X isn't running on the local screen, is what I suspect you mean. Assuming the cocept is a "local screen" is well-defined. It might not be ideal to post the mount on the screen of someone who has logged in remotely by ssh -X. But what if one ssh -x's in from a user that *is* on the local screen? etc., etc. Being able to ask what's been plugged in recently with a CLI command might also be useful. > > > I don't know what happens if > > there are multiple users logged in at the same time, but that might > > be an edge case. It should certainly take account of who is logged in locally, ane whose virtul X terminnal is actually on the screen. I once had a system that would automount plugged-in USBs for the first user it found in the /etc/p0assword file (starting at UID 1000, of course), whether s/he/it was logged in at the momet or not. This was *always* the wrong choice. I had to become root to unmount; only after that could I become mysseld and mount again. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 27/04/2016 19:13, Steve Litt a écrit : Not all filesystems have labels. For my information, could you list some? Every filesystem I ever used to format disks had one (ext?, reiserfs, btrfs, vfat) Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Tochpad scrolling on devuan
On Wed, 27 Apr 2016 11:25:19 +0200 aitor_czr wrote: > On 04/27/2016 11:21 AM, aitor_czr wrote: > > If so, try doing: > > synclient TouchpadOff=1 > > > > for enabling the touchpad, and: > > > > synclient TouchpadOff=0 > > > > for disabling it. > > Sorry, it's in the other way around: > > synclient TouchpadOff=0 > > enables the touchpad :) And for even more fun, here's the "touchtoggle" shellscript I put on every laptop, linked to hotkey Ctrl+Shift+j: = #!/bin/sh curstate=`synclient | grep -i TouchpadOff | sed -e"s/.*= //"` if test "$curstate" = "1"; then synclient TouchpadOff=0 else synclient TouchpadOff=1 fi = SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, 27 Apr 2016 08:25:02 -0400 fsmithred wrote: > On 04/26/2016 09:32 PM, Steve Litt wrote: > > On Tue, 26 Apr 2016 18:19:32 -0400 > > fsmithred wrote: > > > > > >> I like pmount for mounting usb devices. It's pretty smart. For > >> removable devices, you don't need to list them > >> in /etc/pmount.allow, and it handles encrypted filesystems > >> (cryptsetup/luks). > > > > > > Ahh, now I remember. Pmount isn't an AUTOmounter, you still must > > tell it which device to mount. It doesn't mount the second you plug > > in your thumb drive. > > > > Therefore: pmount, when combined with the inotifywait automounters > > we've all made, should be perfect. > > > > Those pmount automounter commands should run as the user who plugs > > in the thumb, so rather than running straight from the init, they > > should probably run when you log in, and if there's already a copy > > running when you log in, it does nothing. > > > > SteveT > > > > That's pretty much what my usb-mounter does. Inotifywait runs when > you log into the desktop, and when you plug in a thumb drive, it pops > up a window showing you the partitions on that device. You then > choose one to mount, and the script runs pmount in your name. That sounds *perfect* to me, always assuming the "window" is a CLI question and answer i X isn't running. Where's the source code? I'd like to start using it. Somebody suggested we package an automounter for Devuan. What you describe sounds like the right thing. > Bypassing the popup window and automounting would be a simple edit, My no-user-confirmation version was problematic and vaguely disturbing. I'd leave the user in the loop. > as would making it work without a gui. Yes. This being Devuan, some facility for asking and recieving an answer should be provided even if X isn't runnnig. > I don't know what happens if > there are multiple users logged in at the same time, but that might > be an edge case. > > So, who else beside you and me wrote something to mount thumb drives? SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 27/04/2016 19:17, Steve Litt a écrit : On Wed, 27 Apr 2016 09:10:25 +0200 Didier Kryn wrote: Wishlist: the "automounter" shouldn't mount automatically, by default. It should rather offer an easy mount-handle, and the umount counterpart. What is an "easy mount-handle"? I mean there might be a list of connected removable media, showing which ones are mounted and a way to toggle mount/umount for each of them. I remind you that filesystems mus be unmounted before they are removed; this is what is called "remove safely" or "eject" by DEs' helpers. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chroot sees wrong version of libc
Haines Brown writes: [...] > # LANG=C.UTF-8 chroot /mnt/debinst /bin/bash > /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version >`GLIBC_2.15' not found (required by /bin/bash) > /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version >`GLIBC_2.15' not found (required by >/lib/i386-linux-gnu/libncurses.so.5) > /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version >`GLIBC_2.15' not found (required by >/lib/i386-linux-gnu/libtinfo.so.5) [...] That's an error you should see when trying to run the downloaded bash binary without doing a chroot first (the wheezy libc doesn't define GLIBC_2.15), eg, (di2 is a debootrapped i386 Devuan jessie on a amd64 host), [rw@doppelsaurus]~#cd /tmp/di2 [rw@doppelsaurus]/tmp/di2#bin/bash bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by bin/bash) The library name also comes from the Wheezy system, it should be /lib/i386-linux-gnu/libc.so.6 for the one which was downloaded. You could try to have a look at the downloaded library. Assuming you're root and the cwd is the top-level download directory (/mnt/debinst in your case) then nm -D `find -name libc.so.6` | grep GLIBC should print A GLIBC_2.0 A GLIBC_2.1 A GLIBC_2.1.1 A GLIBC_2.1.2 A GLIBC_2.1.3 A GLIBC_2.10 A GLIBC_2.11 A GLIBC_2.12 A GLIBC_2.13 A GLIBC_2.14 A GLIBC_2.15 A GLIBC_2.16 A GLIBC_2.17 A GLIBC_2.18 A GLIBC_2.2 A GLIBC_2.2.1 A GLIBC_2.2.2 A GLIBC_2.2.3 A GLIBC_2.2.4 A GLIBC_2.2.6 A GLIBC_2.3 A GLIBC_2.3.2 A GLIBC_2.3.3 A GLIBC_2.3.4 A GLIBC_2.4 A GLIBC_2.5 A GLIBC_2.6 A GLIBC_2.7 A GLIBC_2.8 A GLIBC_2.9 A GLIBC_PRIVATE ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, 27 Apr 2016 09:10:25 +0200 Didier Kryn wrote: > Wishlist: the "automounter" shouldn't mount automatically, by > default. It should rather offer an easy mount-handle, and the umount > counterpart. What is an "easy mount-handle"? SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, 27 Apr 2016 06:47:38 + Noel Torres wrote: > Steve Litt escribió: > > Therefore: pmount, when combined with the inotifywait automounters > > we've all made, should be perfect. > > > > Those pmount automounter commands should run as the user who plugs > > in the thumb, so rather than running straight from the init, they > > should probably run when you log in, and if there's already a copy > > running when you log in, it does nothing. > > Could we just create a package with that "devuan-automounter" and > publish it? > > Regards > > Noel I don't think my automounter is ready for prime time. And after fsr's point about pmount, I think I might change the whole philosophy of my automounter to take advantage of pmount. Fsr's automounter might be more ready to accompany the distro. SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, 27 Apr 2016 06:46:24 + Noel Torres wrote: > Joel Roth escribió: > > As a suggestion for an aspiring automounter writer (or > > reminder to self) I was thinking that if we can get a > > sufficiently unique identifier from the device (UUID, etc.) > > it might be nice to map that to a memorable mount target. > > It could be a noun or adjective-noun from a list that would > > be automatically chosen and written to the device after > > mounting. > > [...] > > Too weird? Okay, I'm open, just something better than > > /mnt/sde7. > > Why not just the Label of the filesystem being mounted? Not all filesystems have labels. SteveT Steve Litt April 2016 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chroot sees wrong version of libc
Le 27/04/2016 17:47, Haines Brown a écrit : A question I raised was left unanswered because the thread drifted into other issues. So let me repose the question in an appropriately named thread. I'm doing a cross install of devuan Alpha 4 onto a newly partitioned hard disk (/dev/sda1) in same box as my running Debian Wheezy system (/dev/sdb1). I partitioned, formatted and mounted the needed new disk's partitions; I downloaded debootstrap_1.0.75-1*.deb to a working directory in my current sytem; I unpacked the data tarball, Finally I ran the devuan debootstrap to install a base system on the target drive. # debootstrap --no-check-gpg jessie /mnt/debinst \ http://packages.devuan.org/merged Basically this went well, and in about 5-10 minutes I had the files for a basic devuan system on the target drive. However, some hiccups along the way: W: Couldn't download package mount (ver 2.26.2-6+devuan arch i386) ... W: Couldn't download package coreutils (ver 8.23-r arch i386) ... W: Retrying failed download of http://packages.devuan/org/merged/pool/DEBIAN/main/g/gnutls28/ \ libgnutls-deb0028_3.3.8-6+debv8ud_i386.deb ... W: Couldn't download package insserv (ver 1.14.0-5 qrch i386) ... I: Validating libpam-modules 1.1.8-3.1+deb8u1+b1 W: Retrying failed download of http://packages.devuan.org/merged/pool/DEBIAN/main/p/ \ pam/libpam-modules_1.1.8-3.1+deb8u1+b1_i386.deb ... I: Retrieving startpar 0.59-3 W: Couldn't download package startpar (ver 0.59-3 arch i386) ... I: Retrieving udev 215-17+deb8u4 W: Couldn't download package udev (ver 215-17+deb8u4 arch i386) I: Retrieving tar 1.27.1-2+b1 I: Validating tar 1.27.1-2+b1 W: Retrying failed download of http://packages.devuan.org/merged/pool/DEBIAN/main/t/tar/ \ tar_1.27.1-2+b1_i386.deb I: Retrieving tar 1.27.1-2+b1 ... E: Couldn't download packages: mount coreutils insserv startpar udev Why were these five packages not found? They are obviously critical. When I go to https://packages.devuan.org/merged/, the pool directory is empty. A puzzle. But I suppose none of this is relevant to my effort next to chroot into the new system: # LANG=C.UTF-8 chroot /mnt/debinst /bin/bash /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /bin/bash) /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libncurses.so.5) /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libtinfo.so.5) This seems to be a problem running chroot from my running machine and is irrelevant to the lean devuan target I just installed. If so, failure to download some packages is irrelevant to the chroot problem. I gather glibc is part of libc. So do these errors indicate that the libc version on my running machine is incompatible with its version of chroot? I do: $ ldd /bin/bash ... libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7609000) $ ldd /usr/sbin/chroot ... libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7643000) Haines Brown _ I think you should use the --foreign option of debootstrap. first 'debootstrap --no-check-gpg jessie /mnt/debinst' then 'chroot /mnt/debinst debootstrap --second-stage' Explanation: the installation of the packages must be done in the chroot, while downloading debootstrap can only be done in the old system. This is the same method which is used to debootstrap a different architecture. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] chroot sees wrong version of libc
A question I raised was left unanswered because the thread drifted into other issues. So let me repose the question in an appropriately named thread. I'm doing a cross install of devuan Alpha 4 onto a newly partitioned hard disk (/dev/sda1) in same box as my running Debian Wheezy system (/dev/sdb1). I partitioned, formatted and mounted the needed new disk's partitions; I downloaded debootstrap_1.0.75-1*.deb to a working directory in my current sytem; I unpacked the data tarball, Finally I ran the devuan debootstrap to install a base system on the target drive. # debootstrap --no-check-gpg jessie /mnt/debinst \ http://packages.devuan.org/merged Basically this went well, and in about 5-10 minutes I had the files for a basic devuan system on the target drive. However, some hiccups along the way: W: Couldn't download package mount (ver 2.26.2-6+devuan arch i386) ... W: Couldn't download package coreutils (ver 8.23-r arch i386) ... W: Retrying failed download of http://packages.devuan/org/merged/pool/DEBIAN/main/g/gnutls28/ \ libgnutls-deb0028_3.3.8-6+debv8ud_i386.deb ... W: Couldn't download package insserv (ver 1.14.0-5 qrch i386) ... I: Validating libpam-modules 1.1.8-3.1+deb8u1+b1 W: Retrying failed download of http://packages.devuan.org/merged/pool/DEBIAN/main/p/ \ pam/libpam-modules_1.1.8-3.1+deb8u1+b1_i386.deb ... I: Retrieving startpar 0.59-3 W: Couldn't download package startpar (ver 0.59-3 arch i386) ... I: Retrieving udev 215-17+deb8u4 W: Couldn't download package udev (ver 215-17+deb8u4 arch i386) I: Retrieving tar 1.27.1-2+b1 I: Validating tar 1.27.1-2+b1 W: Retrying failed download of http://packages.devuan.org/merged/pool/DEBIAN/main/t/tar/ \ tar_1.27.1-2+b1_i386.deb I: Retrieving tar 1.27.1-2+b1 ... E: Couldn't download packages: mount coreutils insserv startpar udev Why were these five packages not found? They are obviously critical. When I go to https://packages.devuan.org/merged/, the pool directory is empty. A puzzle. But I suppose none of this is relevant to my effort next to chroot into the new system: # LANG=C.UTF-8 chroot /mnt/debinst /bin/bash /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /bin/bash) /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libncurses.so.5) /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libtinfo.so.5) This seems to be a problem running chroot from my running machine and is irrelevant to the lean devuan target I just installed. If so, failure to download some packages is irrelevant to the chroot problem. I gather glibc is part of libc. So do these errors indicate that the libc version on my running machine is incompatible with its version of chroot? I do: $ ldd /bin/bash ... libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7609000) $ ldd /usr/sbin/chroot ... libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7643000) Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Problem to come with pmount is, it doesn't seem to be maintained any longer. I use version 0.9.99-alpha-1 (in experimental at 25 Mar 2011, still there, install to Jessie). That one handles "loopback" and luks files, far as I know earlier versions did not, or not properly. D On 27 April 2016 at 13:25, fsmithred wrote: > On 04/26/2016 09:32 PM, Steve Litt wrote: >> On Tue, 26 Apr 2016 18:19:32 -0400 >> fsmithred wrote: >> >> >>> I like pmount for mounting usb devices. It's pretty smart. For >>> removable devices, you don't need to list them in /etc/pmount.allow, >>> and it handles encrypted filesystems (cryptsetup/luks). >> >> >> Ahh, now I remember. Pmount isn't an AUTOmounter, you still must tell >> it which device to mount. It doesn't mount the second you plug in your >> thumb drive. >> >> Therefore: pmount, when combined with the inotifywait automounters >> we've all made, should be perfect. >> >> Those pmount automounter commands should run as the user who plugs in >> the thumb, so rather than running straight from the init, they should >> probably run when you log in, and if there's already a copy running >> when you log in, it does nothing. >> >> SteveT >> > > That's pretty much what my usb-mounter does. Inotifywait runs when you log > into the desktop, and when you plug in a thumb drive, it pops up a window > showing you the partitions on that device. You then choose one to mount, > and the script runs pmount in your name. Bypassing the popup window and > automounting would be a simple edit, as would making it work without a > gui. I don't know what happens if there are multiple users logged in at > the same time, but that might be an edge case. > > So, who else beside you and me wrote something to mount thumb drives? > > -fsr > > ___ > 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] Tochpad scrolling on devuan
Good you got scrolling to work. In case it helps, this is what works for me to enable tap functions, rather than mess with xorg configs: synclient TapButton1=1 LBCornerButton=2 RBCornerButton=3 MaxTapTime=140 SingleTapTimeout=140 MaxDoubleTapTime=140 Try first in a user terminal, if it works script it and put in user's "autostart". D On 27 April 2016 at 14:18, fuumind wrote: > Hi all! > > Thank you for all the great help with getting my touchpad working better! I > now have two finger scrolling working (I discovered in the process that my > hardware do support it.) Adding the option line 'Option "VertTwoFingerScroll" > "on"' to the file /usr/share/X11/xorg.conf.d/50-synaptics.conf and > unloading/reloading psmouse.ko did the trick. I am not sure wether the kernel > upgrade made any difference and I am not very inclined to downgrade atm. :) > > All the best! > fuumind > > On Tue, 26 Apr 2016 13:29:14 +0100 > "dev1fanboy" wrote: > >> The synaptics driver is usually the way to go. Check if it's installed by >> dpkg -l | grep synaptics, if not then apt-get install >> xserver-xorg-input-synaptics. >> >> Usually any options you want will have to be configured as the defaults are >> pretty basic, the archlinux wiki has some good info on the options: >> https://wiki.archlinux.org/index.php/Touchpad_Synaptics >> >> The default configuration is in /usr/share/X11/xorg.conf.d/50-synaptics.conf >> >> Cheers, >> >> chillfan >> >> On Tuesday, April 26, 2016 12:46 PM, fuumind wrote: >> > Thanks for the link! >> > >> > My kernel went from 3.16 to 4.4 but still no scrolling. >> > >> > also: >> > >> > lsmod|grep -iE "apple|cyapa|sermouse|synap|psmouse|vsxx|bcm" >> > btbcm 16384 1 btusb >> > bluetooth 516096 24 bnep,btbcm,btrtl,btusb,btintel >> > psmouse 122880 0 >> > >> > And freeciv looks a lot nicer as well :) >> > >> > Maybe there are some configuration changes needing to be done for X after >> > all. >> > >> > /fuumind >> > >> > On Tue, 26 Apr 2016 11:20:03 +0100 >> > David Hare wrote: >> > >> >> deb http://packages.devuan.org/merged jessie-backports main >> >> >> >> in your sources.list.. Do be careful to comment that line immediately >> >> after use, I'm not the only one who had problems with unintentional >> >> "upgrades" from backports. >> >> >> >> Some of my posts might not have made the list properly, my usual mail >> >> client is temporarily out of order. >> >> >> >> >> >> >> >> On 26 April 2016 at 08:12, fuumind wrote: >> >> > I doubt that my hardware is too new. It is a Dell Latitude E6410 that >> >> I bought second hand a couple of years ago. :) >> >> > >> >> > How would I go about upgrading to a backported kernel? Is there a repo >> >> somewhere I can use or do I need to build it myself? >> >> > >> >> > /fuumind >> >> > >> >> > >> >> > On Mon, 25 Apr 2016 21:27:39 -0400 >> >> > Hendrik Boom wrote: >> >> > >> >> >> On Tue, Apr 26, 2016 at 02:01:46AM +0100, David Hare wrote: >> >> >> > On 26 April 2016 at 02:00, David Hare wrote: >> >> >> > > I recently did a devuan-based install on a quite new Dell >> >> laptop. >> >> >> > > Many things did not work properly (sound, wlan, touchpad). A >> >> newer >> >> >> > > "backport" kernel sorted it all. >> >> >> > > >> >> >> > > On 25 April 2016 at 20:19, fuumind >> >> wrote: >> >> >> > >> Hi! >> >> >> > >> >> >> >> > >> I am trying to get touchpad scrolling working on my new Devuan >> >> setup. So far I've figured out that it is probably pmouse that >> >> is driving the hardware by stealing the following from >> >> http://unix.stackexchange.com/questions/131432/which-driver-is-handling-my-touchpad >> >> : >> >> >> >> >> >> >> >> >> I've been using devuan since sometime last year on an old eeepc >> >> >> netbook, maybe 5 years old. It just worked. Could it be that your >> >> >> hardware is too new? I find its touchpad to be something of a >> >> nuisance. >> >> >> I touch it by accident and things go strange. I prefer to use my USB >> >> >> wireless mouse. >> >> >> >> >> >> David Hare had success with a backported kernel. >> >> >> >> >> >> I've had problems like this a few times with new hardware. My ten >> >> year >> >> >> old server wouldn't do X when it was new. Regular updates, and it >> >> >> worked fine after about six months. >> >> >> >> >> >> Mind you, as a server it was OK that it only did text terminals for a >> >> >> while. >> >> >> >> >> >> -- hendrik >> >> >> >> >> >> > >> >> >> >> > >> lsmod|grep -iE "apple|cyapa|sermouse|synap|psmouse|vsxx|bcm" >> >> >> > >> >> >> >> > >> and getting >> >> >> > >> >> >> >> > >> psmouse99249 0 >> >> >> > >> >> >> >> > >> Apart from this all I seem to be able to find on the net is alot >> >> about setting up X for synaptics. >> >> >> > >> >> >> >> > >> As I am unsure how to proceed I would appreciate any guidance! >> >> >> > >> >> >> >> > >> /fuumind >> >> >> > >> ___ >> >> >> > >> Dng mailing l
Re: [DNG] Tochpad scrolling on devuan
Hi all! Thank you for all the great help with getting my touchpad working better! I now have two finger scrolling working (I discovered in the process that my hardware do support it.) Adding the option line 'Option "VertTwoFingerScroll" "on"' to the file /usr/share/X11/xorg.conf.d/50-synaptics.conf and unloading/reloading psmouse.ko did the trick. I am not sure wether the kernel upgrade made any difference and I am not very inclined to downgrade atm. :) All the best! fuumind On Tue, 26 Apr 2016 13:29:14 +0100 "dev1fanboy" wrote: > The synaptics driver is usually the way to go. Check if it's installed by > dpkg -l | grep synaptics, if not then apt-get install > xserver-xorg-input-synaptics. > > Usually any options you want will have to be configured as the defaults are > pretty basic, the archlinux wiki has some good info on the options: > https://wiki.archlinux.org/index.php/Touchpad_Synaptics > > The default configuration is in /usr/share/X11/xorg.conf.d/50-synaptics.conf > > Cheers, > > chillfan > > On Tuesday, April 26, 2016 12:46 PM, fuumind wrote: > > Thanks for the link! > > > > My kernel went from 3.16 to 4.4 but still no scrolling. > > > > also: > > > > lsmod|grep -iE "apple|cyapa|sermouse|synap|psmouse|vsxx|bcm" > > btbcm 16384 1 btusb > > bluetooth 516096 24 bnep,btbcm,btrtl,btusb,btintel > > psmouse 122880 0 > > > > And freeciv looks a lot nicer as well :) > > > > Maybe there are some configuration changes needing to be done for X after > > all. > > > > /fuumind > > > > On Tue, 26 Apr 2016 11:20:03 +0100 > > David Hare wrote: > > > >> deb http://packages.devuan.org/merged jessie-backports main > >> > >> in your sources.list.. Do be careful to comment that line immediately > >> after use, I'm not the only one who had problems with unintentional > >> "upgrades" from backports. > >> > >> Some of my posts might not have made the list properly, my usual mail > >> client is temporarily out of order. > >> > >> > >> > >> On 26 April 2016 at 08:12, fuumind wrote: > >> > I doubt that my hardware is too new. It is a Dell Latitude E6410 that > >> I bought second hand a couple of years ago. :) > >> > > >> > How would I go about upgrading to a backported kernel? Is there a repo > >> somewhere I can use or do I need to build it myself? > >> > > >> > /fuumind > >> > > >> > > >> > On Mon, 25 Apr 2016 21:27:39 -0400 > >> > Hendrik Boom wrote: > >> > > >> >> On Tue, Apr 26, 2016 at 02:01:46AM +0100, David Hare wrote: > >> >> > On 26 April 2016 at 02:00, David Hare wrote: > >> >> > > I recently did a devuan-based install on a quite new Dell > >> laptop. > >> >> > > Many things did not work properly (sound, wlan, touchpad). A > >> newer > >> >> > > "backport" kernel sorted it all. > >> >> > > > >> >> > > On 25 April 2016 at 20:19, fuumind > >> wrote: > >> >> > >> Hi! > >> >> > >> > >> >> > >> I am trying to get touchpad scrolling working on my new Devuan > >> setup. So far I've figured out that it is probably pmouse that > >> is driving the hardware by stealing the following from > >> http://unix.stackexchange.com/questions/131432/which-driver-is-handling-my-touchpad > >> : > >> >> > >> >> > >> >> I've been using devuan since sometime last year on an old eeepc > >> >> netbook, maybe 5 years old. It just worked. Could it be that your > >> >> hardware is too new? I find its touchpad to be something of a > >> nuisance. > >> >> I touch it by accident and things go strange. I prefer to use my USB > >> >> wireless mouse. > >> >> > >> >> David Hare had success with a backported kernel. > >> >> > >> >> I've had problems like this a few times with new hardware. My ten > >> year > >> >> old server wouldn't do X when it was new. Regular updates, and it > >> >> worked fine after about six months. > >> >> > >> >> Mind you, as a server it was OK that it only did text terminals for a > >> >> while. > >> >> > >> >> -- hendrik > >> >> > >> >> > >> > >> >> > >> lsmod|grep -iE "apple|cyapa|sermouse|synap|psmouse|vsxx|bcm" > >> >> > >> > >> >> > >> and getting > >> >> > >> > >> >> > >> psmouse99249 0 > >> >> > >> > >> >> > >> Apart from this all I seem to be able to find on the net is alot > >> about setting up X for synaptics. > >> >> > >> > >> >> > >> As I am unsure how to proceed I would appreciate any guidance! > >> >> > >> > >> >> > >> /fuumind > >> >> > >> ___ > >> >> > >> 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 > >> > > >> > > >> > -- > >> > fuumind > >
Re: [DNG] For all you automounter programmers
On 04/26/2016 09:32 PM, Steve Litt wrote: > On Tue, 26 Apr 2016 18:19:32 -0400 > fsmithred wrote: > > >> I like pmount for mounting usb devices. It's pretty smart. For >> removable devices, you don't need to list them in /etc/pmount.allow, >> and it handles encrypted filesystems (cryptsetup/luks). > > > Ahh, now I remember. Pmount isn't an AUTOmounter, you still must tell > it which device to mount. It doesn't mount the second you plug in your > thumb drive. > > Therefore: pmount, when combined with the inotifywait automounters > we've all made, should be perfect. > > Those pmount automounter commands should run as the user who plugs in > the thumb, so rather than running straight from the init, they should > probably run when you log in, and if there's already a copy running > when you log in, it does nothing. > > SteveT > That's pretty much what my usb-mounter does. Inotifywait runs when you log into the desktop, and when you plug in a thumb drive, it pops up a window showing you the partitions on that device. You then choose one to mount, and the script runs pmount in your name. Bypassing the popup window and automounting would be a simple edit, as would making it work without a gui. I don't know what happens if there are multiple users logged in at the same time, but that might be an edge case. So, who else beside you and me wrote something to mount thumb drives? -fsr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Tochpad scrolling on devuan
On 04/27/2016 11:21 AM, aitor_czr wrote: If so, try doing: synclient TouchpadOff=1 for enabling the touchpad, and: synclient TouchpadOff=0 for disabling it. Sorry, it's in the other way around: synclient TouchpadOff=0 enables the touchpad :) Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Tochpad scrolling on devuan
Hi fuumind, On 04/26/2016 10:32 PM, aitor_czr wrote: On 04/26/2016 08:04 PM, fuumind wrote: >>Hi fuumind, >> > >> >On 04/26/2016 02:00 PM, fuumind wrote: >>> >>Thanks for the link! >>> >> >>> >>My kernel went from 3.16 to 4.4 but still no scrolling. >>> >> >>> >>also: >>> >> >>> >>lsmod|grep -iE "apple|cyapa|sermouse|synap|psmouse|vsxx|bcm" >>> >>btbcm 16384 1 btusb >>> >>bluetooth 516096 24 bnep,btbcm,btrtl,btusb,btintel >>> >>psmouse 122880 0 >>> >> >>> >>And freeciv looks a lot nicer as well:) >>> >> >>> >>Maybe there are some configuration changes needing to be done for X >>> >>after all. >> > >> >The configuration of the kernel for the touchscreens drivers is in the >> >*Input Device Drivers*. >> > >> >Run "make menuconfig", and go to: >> > >> >Device drivers >> Input Device support >> Touchscreens >> > >> >HTH, >> > >> > Aitor. >Did you try loading the "hid-multitouch.ko" module. This module is >located in "/lib/modules/ *kernel_version* /kernel/drivers/hid". >You can load it typing: > >/sbin/modprobe hid-multitouch > >You can add this command to "/etc/rc.local" > >Now type "lsmod" and it will appear in the list of the loaded modules. > >Cheers, > > Aitor. Sorry, you are talking about*touchpads* and i'm talking about *touchscreens* Aitor. I think that you need evdev, either builtin or as a module. In menuconfig this is at: Device drivers >> Input Device support >> Event interface Now make sure your Synaptics touchpad is functioning. Run: cat /proc/bus/input/devices And you will get something like this in the list (note of the *Handlers* line): I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input0 U: Uniq= H: Handlers=sysrq kbd event0 B: PROP=0 B: EV=120013 B: KEY=4 200 3803078 f800d001 fedf ffef fffe B: MSC=10 B: LED=7 [ ... etc ... ] If so, try doing: synclient TouchpadOff=1 for enabling the touchpad, and: synclient TouchpadOff=0 for disabling it. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 27/04/2016 09:08, Joel Roth a écrit : Do you label all your filesystems? I don't, but you're right that is a different function that needed be confuted with an automounter. I do, even for the hard disk; it's a reminder of where are /usr, /var and /home. The labels show up in cfdisk. For the usb memory sticks, it is very convenient to format the first partition as vfat and give a label to all partitions. The first partition will show up with its label under Windows and all partitions will do the same in Linux (kde/gnome/xfce). Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
Le 27/04/2016 08:46, Noel Torres a écrit : Joel Roth escribió: As a suggestion for an aspiring automounter writer (or reminder to self) I was thinking that if we can get a sufficiently unique identifier from the device (UUID, etc.) it might be nice to map that to a memorable mount target. It could be a noun or adjective-noun from a list that would be automatically chosen and written to the device after mounting. [...] Too weird? Okay, I'm open, just something better than /mnt/sde7. Why not just the Label of the filesystem being mounted? This is what graphical mount-helpers of most DEs do, and it's the most sensible thing to do. However, the skilled admin might want to bypass this by providing a specific config for a specific uuid, like trigger some backup. Wishlist: the "automounter" shouldn't mount automatically, by default. It should rather offer an easy mount-handle, and the umount counterpart. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] For all you automounter programmers
On Wed, Apr 27, 2016 at 06:46:24AM +, Noel Torres wrote: > Joel Roth escribió: > >As a suggestion for an aspiring automounter writer (or > >reminder to self) I was thinking that if we can get a > >sufficiently unique identifier from the device (UUID, etc.) > >it might be nice to map that to a memorable mount target. > >It could be a noun or adjective-noun from a list that would > >be automatically chosen and written to the device after > >mounting. > >[...] > >Too weird? Okay, I'm open, just something better than > >/mnt/sde7. > > Why not just the Label of the filesystem being mounted? Do you label all your filesystems? I don't, but you're right that is a different function that needed be confuted with an automounter. Cheers, joel > Regards > > Noel > er Envite > -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG v1.4.12 (GNU/Linux) > > mQGiBEBaVWkRBACkDEIMdqB4j0FUD+h7CBAPa3T4IxNDTVTjaOdeARNVSVBitvKK > NIVBT/XfrEKAxCOBzjRfAS9vTO2IYSxW9I7M/ONEsjQa1QEGfva9p03Bo1pDoYa8 > zd8pymZsLdBYTTZrxWgYWj4qY6TnRiZYi8xUoW3xEvKwmLYz02xp3OL6bwCgjuYt > 1OemA3j2coVPd4Ye0uERS30D/R3GCqMV4/wfSWjs6994aL1NK8hZ2VdfgCiFW2s0 > IIFiy5ts29azu9S322OJZ4WmYEnrHe0fNRVzed1lTZ/yPfX3mcmBprkN+Z4b4fXz > HtsZA2UeAfchhWHs5TFuSkBCYY1BiDnDYeEPhK+0bALgdf/jWi6/bb4NpTd9NOU5 > eQS+A/9FcDsYU4MdFi+CVivy0vbLo9LYwPyyYB5giwhvDIDx7zHcjX/Z5Nf+gZoR > oM7RIxiFvmu9PP7msPVuBd320ypAilffMf2/2bJ4/NEE4PTW5wE0e6q0W5GPjc3b > l32KcEi9ovohYt4aoitvB1r6zB5d5+E+AijzG8VDM4fvM5jLUrQsTm9lbCBUb3Jy > ZXMgKEVudml0ZSkgPGVudml0ZUB0ZWxlZm9uaWNhLm5ldD6IXgQTEQIAHgUCQFpV > aQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBwtADz7sfDcjApAJ4xvdZY594W > trUrpNL5zlO+8/MKdgCfcjWh3UOSLOI8e1v29Bnmn9sixvO0OE5vZWwgRGF2aWQg > VG9ycmVzIFRhw7FvIChFbnZpdGUpIDxlbnZpdGVAdGVsZWZvbmljYS5uZXQ+iF4E > ExECAB4FAkBaViwCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQcLQA8+7Hw3IB > 0wCeNcdiYyQXi8IhQ8PL01So/ud3oHcAn1nDi56Ggydw2pp6eFjINL3bIETjtCtO > b2VsIFRvcnJlcyAoRW52aXRlKSA8ZW52aXRlQHJvbGFtYXNhby5vcmc+iF4EExEC > AB4FAkBaVlwCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQcLQA8+7Hw3I0JgCe > Omt0YdaqbvrdnXa/dWNqh8AwS4cAniX0VT08dAleudGTpAgmjSkawlORtC5Ob2Vs > IERhdmlkIFRvcnJlcyBUYcOxbyA8ZW52aXRlQHJvbGFtYXNhby5vcmc+iGAEExEC > ACAFAkhyHmsCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRBwtADz7sfDciiu > AJ4zn1YzDj5birUgW0Uvz8l59MH6GwCfY4G1+Mk5GG5n8YnkkboJWT7uV0m0VU5v > ZWwgRGF2aWQgVG9ycmVzIFRh8W8gKERlcGFydGFtZW50byBkZSBBc3Ryb25vbe1h > IHkgQXN0cm9m7XNpY2EpIDxub2VsLnRvcnJlc0B1di5lcz6IYAQTEQIAIAUCSaHS > YgIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEHC0APPux8Ny2EkAnjqXO1HS > IebxR/2M+Be9A+qOgJ6VAJwMpuNQ/TE7RlwGDiFSTG11K3ONhbkCDQRAWlWXEAgA > 2MMjeuEeeHHHgOX5zHqr4lCg/GYzERYS8c5xjPFFypjmedW6TdQu3YPsSMLZuFrO > 4CUG12R9ofptboqw+DSz64eGaznBwxXEqCmFXjGa2RAKQxqmZW8bU44wdAlSKi7u > iIIYoCnLZuB4Uxa8LAgFeNuPzW3JE2pPcab0oZy+uvpAcXnbbAdnJAxra8Cnooh/ > wgwCdx5Cz+o03GKU0bSEGN8fCkywgMy/3vk+ZY8ZtGonDIvVWgQSlAUkkuS/ollw > VGPSUabKR/S8Zywka5ObIs/Okm3OmUeh3YldiXsrRUuKZcTMARYw98HVhi6j67Si > IElG9nETpBbZUkOU0EaqKwADBgf/ff45K9c5UCROghKd6OvruS1n3kgo0219xxPC > 0fwbdbzuADN4pFfeC/h4/yaJTy17lhgDtrHVQxHr3OItRIOejQ1Sw5joJSYgPWxR > yY6s2m/2+hr/0N7jIs3BSclHA1VraBNxA7RN7Kopd1RUvJDnVJLciTXw/5y+6PQE > iNGN9zYBgAYmjaSm9Y4lqplxiTNfhVSHUS8/EjgYtiVCniFvQmF+QT+OmtXyuXwn > Q+kt9ZUG5U8HjucAyAeDYEp9UhxoJZvikz7daIOy93OqeOhzypolR9Z2tZE355Dr > X5TF4ohq/0WYftnX7ytYl+d1P7vPlir0a9POFMwKFirNpU5fvYhJBBgRAgAJBQJA > WlWYAhsMAAoJEHC0APPux8NyqkgAoIQNP1RD45b0iWFPRjmkxwAnh0/tAJ0SbU3T > G7RLmT/DAZf2QPI0mL3JpQ== > =7jij > -END PGP PUBLIC KEY BLOCK- [-- Error: could not find beginning of PGP message! --] > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng