On Monday 09 September 2019 14:24:50 Gene Heskett wrote: > On Monday 09 September 2019 13:58:03 Greg Wooledge wrote: > > On Mon, Sep 09, 2019 at 01:47:30PM -0400, Gene Heskett wrote: > > > Tell that to pam. Even after editing sudoers, pam won't allow yoou > > > to do squawt as sudo root. BTDT. > > > > If you have a serious complaint or question, you must provide > > details. > > Also true, but those details are close to a year old, and my chances > of remembering it ala copy/paste accuracy are slim and none, so at > this late date, I'll not inflict my typo's on you. > > > Your continued pattern of just ranting "it didn't work" for EVERY > > issue you encounter makes it impossible to help you. > > > > In Debian, universal sudo access is granted to any user in the sudo > > group. If you want to be able to use sudo to run any command as any > > user, add your user account to the sudo group. Either by running > > "adduser $LOGNAME sudo", or by editing the file with "vigr". > > I should paint that on the wall. :) I've been trying by adding me to > sudoers, but that seems to not work as expected. > > > Then, log out and back in to get your new group memberships. > > A detail I forgot, my bad. > > > If that doesn't work in Raspbian, well, too damned bad. This is a > > Debian mailing list. All we know is Debian. > > Touche` However, debian is in effect the broodstock for a lot of these > variations, so what works for debian has a middling high chance of > working with the *pians. > > > > > For safety, you should use "vipw", "vipw -s" and "vigr" to > > > > perform those edits, but it's not actually required on Debian. > > > > > > Screwed up already, I used vipw to put me in front of pi, but now > > > it wants genes passwd, which has not been set. So I'll have to > > > bring that chip to a reader and edit it. > > > > > > Is there an order to make all this just work? But I'll have to > > > wait till realtimepi is done. Estimated another couple hours. > > > > If you duplicate the lines in both /etc/passwd AND /etc/shadow, your > > password for "gene" will be the same as the password for "pi". > > Because they both use the same salted hash in the shadow file. You > > know, the big-ass $1$abcdefgh$crapola string that you saw when you > > edited the file? It's kinda hard to miss. > > Yup, big sore thumb. But I'll have to fix it in a card reader now. > When RealtimePi has finished. > Which it has, I brought the u-sd to a reader and fixed /e/passwd, /e/group, and /e/shadow so they all matched.
but I have another network hookup, using sshfs that is not working for either name gene@coyote:~$ sshfs pi@picnc:/ /sshnet/picnc fuse: bad mount point `/sshnet/picnc': Transport endpoint is not connected gene@coyote:~$ sshfs gene@picnc:/ /sshnet/picnc fuse: bad mount point `/sshnet/picnc': Transport endpoint is not connected What does that tell us? I should see the / directory for any of those 5 mount points, like this: gene@coyote:~$ ls -l /sshnet/shop total 108 drwxr-xr-x 1 root root 4096 Jan 16 2019 bin drwxr-xr-x 1 root root 4096 Feb 22 2019 boot drwxr-xr-x 1 root root 3260 Sep 7 16:34 dev drwxr-xr-x 1 root root 12288 Aug 4 17:23 etc drwxr-xr-x 1 root root 4096 May 18 2015 GenesAmandaHelper-0.61 drwxr-xr-x 1 root root 4096 May 19 2015 home lrwxrwxrwx 1 root root 35 May 18 2015 initrd.img -> /boot/initrd.img-3.4-9-rtai-686-pae drwxr-xr-x 1 root root 4096 Jun 24 2017 lib drwx------ 1 root root 16384 May 18 2015 lost+found drwxr-xr-x 1 root root 4096 May 7 2018 media drwxr-xr-x 1 root root 4096 Apr 19 2014 mnt drwxr-xr-x 1 root root 0 Aug 20 22:03 net drwxr-xr-x 1 root root 4096 Jul 3 2014 opt dr-xr-xr-x 1 root root 0 Aug 20 22:02 proc drwx------ 1 root root 4096 May 6 2018 root drwxr-xr-x 1 root root 900 Aug 22 11:45 run drwxr-xr-x 1 root root 4096 Jun 3 2018 sbin drwxr-xr-x 1 root root 4096 Jun 10 2012 selinux drwxr-xr-x 1 root root 4096 Jul 3 2014 srv drwxr-xr-x 1 gene gene 4096 Sep 24 2015 sshnet dr-xr-xr-x 1 root root 0 Aug 20 22:02 sys drwxrwxrwt 1 root root 4096 Sep 9 16:17 tmp drwxr-xr-x 1 root root 4096 May 19 2015 usr drwxr-xr-x 1 root root 4096 May 21 2015 var lrwxrwxrwx 1 root root 31 May 18 2015 vmlinuz -> boot/vmlinuz-3.4-9-rtai-686-pae Obviously I'd have to cd and sudo to access it all, but 99.9% of the activity takes place in /home/gene, so thats not a huge problem. Right now, the next image I want to dd to a card to run that machine, is locked away behind that error. clues to what I've broken? Humm, went thru the rmdir etc stuff to refresh the directory, and now it works as I go wandering off scratching head. cp took 15 minutes to move it to this machine, and sha512sum will be used to verify the copy. By then I should have my chefs hat on as its dinner time in the right coasts time zone. But the customer has gone to sleep. But I just took that card out and plugged it in, it gets to a text login, but no mouse or keyboard response. Some days it doesn't pay to gnaw thru the straps and get up mornings. Sigh. This is dirt you folks haven't plowed yet, so I do some googling I guess. Thanks Greg. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
