开云体育

Hello.
I am new to Vector Network Analysers and I thought I would take advantages of this affordable piece of test gear to learn something.
I am finding my way round the menus ok with the stand alone item but have hit a couple of stumbling blocks with the Nanovna-saver software.
Running nanovna-saver.exe with windows 10 I can connect to the VNA ok but the program crashes when I start to enter parameters. On occasions if I enter parameters and connect in a certain order I get results but after a while when changing things it will crash.
I though I would try it on Linux Mint. The installation went well until I tried to instal pyqt5. I was unable to do this as it says I don't have permission to download to the particular folder.
Any advice would be gratefully received.
Don, m5aky

Hi Don,
permission issues I can't really help with - I expect that's a matter of
being root or not, or using sudo or not.

On Windows, I'm sorry to hear that you're experiencing crashes. If you
would like to run the program with the parameter "-D logfile.txt" (or
another filename of your choice), you can create a log of debug statements
from the software, so I can see what's going on. Running the software from
a command prompt (cmd.exe) should also allow you to see the final error
message/stack trace - I'd like to have that as well for debugging!

Thanks for trying it out, and for taking the time to report the errors you
are experiencing! :-)

--
Rune / 5Q5R

On Thu, 26 Sep 2019 at 11:19, Don Vosper via Groups.Io <donald.vosper=
[email protected]> wrote:

Hello.
I am new to Vector Network Analysers and I thought I would take advantages
of this affordable piece of test gear to learn something.
I am finding my way round the menus ok with the stand alone item but have
hit a couple of stumbling blocks with the Nanovna-saver software.
Running nanovna-saver.exe with windows 10 I can connect to the VNA ok but
the program crashes when I start to enter parameters. On occasions if I
enter parameters and connect in a certain order I get results but after a
while when changing things it will crash.
I though I would try it on Linux Mint. The installation went well until I
tried to instal pyqt5. I was unable to do this as it says I don't have
permission to download to the particular folder.
Any advice would be gratefully received.
Don, m5aky

Attention: for those with an interest in employing a Linux system to

run Rune's application. All others skip over this post.

Don, at the risk of telling what you understand perfectly well,

permit an observation on the Linux systems of interest here. Even if you
understand already, others less familiar with Linux may be helped.

Window$ oriented users may be accustomed to "doing as they please"

in a Window$ system. I'm long, long out of Window$ and things may have
improved greatly over the years but, in the past, installing software
was unconstrained. That was one of the, er, open windows to malware.

In the Linux systems of interest here, the day to day user is just

that, a mere user and nothing more. Much in the "machinery" of the
system is closed to him and thereby to malware.

Installing software is something very important because that is a

route to malware entry. The root user, the ultimate systems authority,
is permitted to install software and to do anything else; the day to day
user is not. So, Don, never arrange the system so that, day to day, you
are operating as the root user.?? /None of us ever does that./ ? Please
don't think that by contriving your Linux system to operate like Window$
an improvement is being made. The reputation Window$ has established
over the years for security is all you need to know in that regard. You
don't want a system like that. Most of us ordinary Linux system users
don't use an anti malware program. Compare that, please, to Window$
systems where an entire industry has built up devoted to trying to keep
out malware and to clean up what does get in. At least in the past, a
good deal of c.p.u. overhead in a Window$ system was devoted to dealing
with malware threats. Not so in Linux.

The engineer mentioned, who is now using a Linux Mint system, is

employed by a company whose enterprise customers forbid the use so much
as a single line of Micro$oft code in anything his company ships right
down to cameras and video recording systems! When you see a news item
about institutions that have had systems failures or ransomware attacks,
listen carefully and look at the screens on the terminals. It's some
Micro$oft enterprise system that has failed. That's very dirty laundry,
too, and we will not be seeing even five percent of what is actually
going on.

So, then, how to install software such as that required to run

Rune's superb application? The way it is done is by "borrowing" the root
user's privileges. That is a very big step. The user "borrowing" root
user's privileges must consider very carefully what he is about in
installing software and what he is about in gaining access to sensitive
system directories and their files because, of course, he is exposing
his system to malware. The software to be installed must be known to be
clean of malware. There is very much to be said on the topic of assuring
that uncorrupted software or other files are being downloaded. There is
not room here to discuss the matter and, anyway, I am no expert.
Authoritative material must be consulted if you wish to follow up the topic.

What you almost certainly have encountered is an attempt to load a

file into an area of files owned by the root user. That was what Rune
meant by "permission". The machine will not permit a day to day user to
do that. A day to day user has no business in there and Linux is doing
its job of keeping itself clean. Having assured yourself of exactly what
you are about to do, you may assume, for the moment, the privileges of
the almighty root user without actually becoming the root user. The
command " ? sudo ? " says "System, permit me to assume the mantle of the
root user...temporarily." When you invoke that command, the system will
demand your root user's password. When you did the installation, one of
the things that the installing program asked you for was the password
that you would like to use as the root user. That password /must/ be
different from the normal, that is to say day to day user's, log in
password! You now understand why. If those two passwords are not
different, Don, change the root user's password at once and make the new
one a good one. A look on the web will show how that's done, it is simple.

When that demand for the root user's password is made following

entering a command preceded by " ? sudo ?? ", that robust root user's
password is entered.

With that root user's password entered in response to the challenge,

you are "The Man". You can get in anywhere and do anything. Be careful,
Don; as an inexperienced Linux user, you are playing with fire.?

When you come to execute certain sensitive routines other than

installing software, you may be required to use the " ?? sudo???? "
command. That is quite normal. It tells you to think carefully what you
are about to do. Something else it should say to you, when you have
built up some experience, is:"Is this making sense? Why is the system
suddenly asking for this root privilege? I have done this before simply
as an ordinary user. I'm going to stop right here and think what is
going on. Is something trying to get into my system?" Don't
automatically invoke root's privileges; know what is going on. Though
it's exceedingly rare, you may have come across malware trying to get
into your system.

Now after all that security talk, Don, malware might seem to be the

same issue it is in Window$; it certainly isn't but as a beginner it is
important to understand what being the root user is all about.

In conclusion...a free living Window$ user of many years' experience

may see all this as pointless pack drill. This is /not/ pointless pack
drill, Don. The fellows who have been working on the Linux based systems
over the years have not been laid back dilettantes. They are smart
cookies and, with the software wide open to invigilation, there are the
eyes of many other smart cookies picking over what they are doing. Any
change to the software has followed a strict protocol of testing and
inspection before it was ever released for use in a system. Please
compare that to the sorry record established by Micro$oft! Smart users
all over the world have contributed ideas for making the code even more
efficient and robust year upon year and the process is going on still as
you read this. Collectively these guys are smarter than any one of us.
We ordinary users do not know better. We are well advised to take
advantage of the Linux security protocols.

John

at radio station VE7AOV.

+++++


On 2019-09-26 2:45 a.m., Rune Broberg wrote:

Hi Don,
permission issues I can't really help with - I expect that's a matter of
being root or not, or using sudo or not.

On Windows, I'm sorry to hear that you're experiencing crashes. If you
would like to run the program with the parameter "-D logfile.txt" (or
another filename of your choice), you can create a log of debug statements
from the software, so I can see what's going on. Running the software from
a command prompt (cmd.exe) should also allow you to see the final error
message/stack trace - I'd like to have that as well for debugging!

Thanks for trying it out, and for taking the time to report the errors you
are experiencing! :-)

--