I did a search on nc, and I found: https://linuxhandbook.com/nc-command/ * So I found that on the AntiX (debian buster) I need to enter netcat and on my Pine64 Arm board, like a raspberry pi, (Armbian), I can use just nc But so far I haven't figured out how to make them connect. On the antiX I did sudo netcat -l 22 and then on the pine 64, I did sudo nc 10.248.1.143 22 and it does not seem to connect. I wonder if it is because I am using 22 to get from my windows to the Pine64, in order to go linux to linux. I guess netcat has a windows version, but I haven't looked for it yet. Glenn ----- Original Message ----- From: "K0LNY_Glenn" <glenn@ervin.email> To: "Willem van der Walt" <wvdwalt@xxxxxxxxxx> Cc: "Speakup is a screen review system for Linux." <speakup@xxxxxxxxxxxxxxxxx> Sent: Friday, August 26, 2022 1:38 PM Subject: Re: hopefully some help with AntiX Hi Willem, Can I operate the terminal with ncat like with SSH? Thanks. ----- Original Message ----- From: "Willem van der Walt" <wvdwalt@xxxxxxxxxx> To: "K0LNY_Glenn" <glenn@ervin.email> Cc: "Speakup is a screen review system for Linux." <speakup@xxxxxxxxxxxxxxxxx> Sent: Friday, August 26, 2022 1:19 PM Subject: Re: hopefully some help with AntiX Hi Glenn, I think you should use nc. I will send you detailed instructions tomorrow. Regards, Willem On Fri, 26 Aug 2022, K0LNY_Glenn wrote: > [The e-mail server of the sender could not be verified (SPF Record)] > > Hi Brian, > The trouble is that I cannot SCP because I cannot SSH into it. > It has audio, and I can use apt, but AntiX has its own limited repository. > It has something I think it was called apt-antiX or something, but it is > menu driven, and that does not work with OCR on the screen. > So it seems fast and viable, but I cannot get anything into it. > If I put stuff on a thumb drive and plugged it in, without speech output, > I > couldn't possibly get all guesses needed to find the device in > /media/demo. > Thanks though. > > Glenn > ----- Original Message ----- > From: "Brian Buhrow" <buhrow@xxxxxxxxxx> > To: "K0LNY_Glenn" <glenn@ervin.email>; "Chime Hart" > <chime@xxxxxxxxxxxxxxxxxxx> > Cc: "Willem van der Walt" <wvdwalt@xxxxxxxxxx>; "Speakup is a screen > review > system for Linux." <speakup@xxxxxxxxxxxxxxxxx>; <buhrow@xxxxxxxxxx> > Sent: Friday, August 26, 2022 10:12 AM > Subject: Re: hopefully some help with AntiX > > > Hello Glen. Here are a couple of suggestions to try and figure out what's > going on. > > It sounds like the machine you're installing is up and running to some > extent, i.e. you believe > it has enough network to go out and download packages from repositories. > If that's true, then I suggest building yourself a data file on the > machine > about its > state and then scp it back to your working machine for post mortom > analysis. > In this way, you > can be smarter about what's really going on with it rather than just > trying > our suggestions and > getting more and more frustrated. > > Depending on the state of the machine, there are a couple of ways to > approach this task. > > 1. If you have the script command installed, > I suggest: > cd /tmp > script > > Then, do a dump of the dmesg output of the machine, a dump of a list of > packages on the > machine, a dump of the network configuration on the machine, using such > commands as ifconfig > and netstat, (if this is Ubuntu based, there's a command that replaces > netstat that I don't > remember off the top of my head.) > > The script command will capture your commands, and the output they > generate, > into a file called > typescript in the current directory (/tmp above). When you've collected a > bunch of data, exit > the shell you started with the script command and scp the file > "typescript" > back to your > working installed machine and look it over. Keep in mind there will be > some > portions of it > that will look like giberish because it captures all the terminal escape > sequences to format > the screen as well, but it will give you a lot more knowledge about what > is > going on. Also, it > will tell you which commands worked and which didn't, and why. > > You may need to repeat this process of collecting a script file from the > machine several times, > using the knowledge you gained from the last round, to try more informed > commands. > > 2. If the script command is not available, then create your own > approximation of the script > command by doing the following: > > cd /tmp > touch typescript > dmesg >> typescript 2>&1 > . . . > > Repeat commands, followed by >> typescript 2>&1 > > over and over again, as described above, to dump the output of both > standard > out and standard > error (path for error messages) into your hand made typescript file. > > When you have collected enough initial data to try doing an analysis, scp > the typescript file > back to your working machine and have a look at it. > > Keep in mind that when you reboot the Antics machine, the /tmp/typescript > file will be erased. > > My apologies for not being familiar with the aptitude commands to give you > examples of how to > get package listings from the machine directly. > > Although, dumping the output of > aptitude --help >> /tmp/typescript 2>&1 > into your typescript file should give you pretty good directions on how to > use it. > > Hope this helps. > > -Brian > > >
