Re: nano copy/paste dead
On Monday 02 September 2019 12:07:48 David Wright wrote:
> On Mon 02 Sep 2019 at 06:50:34 (-0400), Gene Heskett wrote:
> > On Monday 02 September 2019 03:10:08 Felix Miata wrote:
> > > Gene Heskett composed on 2019-09-02 02:55 (UTC-0400):
> > > > That half a screen height jump is a huge distraction.
> > >
> > > It would if it happened here, but what half a screen jump? An up
> > > or down arrow is three lines here, would be one, like it used to
> > > be, if I could find a way to undo the intentional regression.
> >
> > The scroll jump has always been ten or more lines here, very
> > distracting when the terminal is fill screen and 10 point type.
> > Takes my eyes a good half second to find the cursor again. There
> > are much better editors, like geany, but x won't let geany run as
> > root over an ssh connection. Thats BS.
> >
> > Since wheezy, the security paranoia knows no limits and does not
> > care how inconvenient they make it for the user. I am the ONLY user
> > here, get this #@$%&^ crap out of my way!!! I used to be able to
> > reboot a remote machine and could continue working via ssh 30
> > seconds later even if it took a root session to proceed.
> >
> > But no, someone has decreed that ssh isn't to be started until
> > someone has gone to that machines own keyboard and logged in now.
> > Then they decided ssh wasn't allowed to use x facilities as root.
> >
> > So if I'm working on a machine out in the shed on the hill, writing
> > g-code to make an armstrong bolt out of a piece of 1" square bar
> > stock, I have to get dressed including shoes for snow in the winter,
> > climb the hill and log back in on that machines own keyboard before
> > I can access that machine over an ssh connection from a warm and
> > comfortable office chair here in the house. I'd like to make the
> > person who thought that was a good idea, do that a few dozen times.
> >
> > Sorry Felix, something pulled my trigger.
>
> I don't understand all this (apart from the first bit,
> commented on separately). ssh comes up without any fuss at all.
> It always has done.
>
> Just to show you, I did the following: closed down agog, booted it up
> again (waking it through the wired ethernet interface), unlocked the
> encrypted /home partition, and logged in again as myself; all done
> without getting out of my armchair.
>
> (The first login is to a pseudo-user whose home directory and
> .bash_profile is in /var/local/home/unlock/.bash_profile, and
> which unlocks and mounts /home, and logs out, all automatically.)
>
> Here's what I see on my screen as it all takes place:
>
> agog!david 10:55:24 ~ $
> agog!david 10:55:39 ~ $ sudo /root/shutdown
> Connection to agog closed by remote host.
> Connection to agog closed.
> 255 wren!david 10:55:57 ~ $
> 255 wren!david 10:56:05 ~ $ agog-wake
> Sending magic packet to 255.255.255.255:9 with 00:13:72:83:33:2a
> wren!david 10:56:15 ~ $ agog-unlock
> Mon Sep 2 10:56:40 CDT 2019
> ssh: connect to host agog port 22: No route to host
> 255 wren!david 10:56:58 ~ $
> 255 wren!david 10:57:28 ~ $ agog-unlock
> Mon Sep 2 10:57:33 CDT 2019
> Linux agog 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08)
> x86_64
>
> The programs included with the Debian GNU/Linux system are free
> software; the exact distribution terms for each program are described
> in the individual files in /usr/share/doc/*/copyright.
>
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> Last login: Mon Sep 2 10:42:44 2019 from 192.168.1.17
> (This is /var/local/home/unlock/.bash_profile 2019 February 19)
> Passphrase:
> Unlocked /dev/sda6 as /dev/dm-0.
> /home is now mounted
> Connection to agog closed.
> wren!david 10:57:51 ~ $ agog
> Mon Sep 2 10:57:55 CDT 2019
> Linux agog 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08)
> x86_64
>
> The programs included with the Debian GNU/Linux system are free
> software; the exact distribution terms for each program are described
> in the individual files in /usr/share/doc/*/copyright.
>
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> You have new mail.
> Last login: Mon Sep 2 10:43:05 2019 from 192.168.1.17
> (This is /home/david/.bash_profile 2019 August 23)
> (This is /home/david/.bashrc 2019 August 23 on /dev/sdb5)
> (This is /home/david/.bash-1-agog 2019 January 26 on buster)
> (This is /home/david/.bash-u-usbs 2019 July 28)
> (This is /home/david/.bash-t-transfers 2019 June 17 enp2s0)
> (This is /home/david/.bash-w-web 2019 August 15)
> (This is /home/david/.bash-9-agog 2019 May 02)
> agog!david 10:57:57 ~ $ uptime
> 10:58:01 up 1 min, 1 user, load average: 2.22, 0.93, 0.34
> agog!david 10:58:01 ~ $
>
> Cheers,
> David.
which if I follow the trace above, says ssh is not started until you've
unlocked things. I don't lock, theres nobody else that can get to it
when I'm logged out. So when the login requester is showing on the local
console, x nor ssh isn't running. Both are now dependent on someone
(I'm assuming user 1000 since thats the only warm blooded user here),
and both x and ssh are started by my logging into the local to the
machine console.
Now, there /are/ exceptions. This seems to be a wintel thing, I can
reboot my pi, and log back in and get back to work, but I can't if its a
wintel box on the far end of the cat5. Difference? DarnedifIknow.
Hmmm, some of the wintels are running xfce4 and some are running TDE.
This machine is running TDE. Should be a correlation but I'm still a
quart low on coffee... Doctors orders, dammit.
Thanks David.
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>
Reply to: