Hi Sergio,
Thanks for the note!
OK, now I understand what you meant. Sorry for being so dense here. I boot
directly into X-Windows so I never get a chance to ["never need to" is
another way of saying this] tupe 'sudo' before typing 'startx'. Linux is
perfectly happy to boot directly into XWindows even for a regular user. It
is clear that different versions of linux behave differently, and I don't
have enough experience to know what is 'usual' and what is 'unusual' in what
I see here ;)
Ubuntu Linux boots directly to XWindows environment even for a simple user.
That is what it does in its standard form. It won't even ALLOW root to log
in directly to XWindows, although that is easy to change and I have done so
here. Here, when I boot directly into Ubuntu XWindows with a regular user
account, I can start to run Linrad without doing sudo and I can even see all
of the xwindows linrad screens OK without doing sudo. But I don't get any
spectrum or audio. Running linrad as suggested, with 'sudo linrad' gives me
the audio and everything runs fine.
So for me not being sudo does not keep me out of X Windows, and it does not
keep me out of the XWindows Linrad screens. But not being sudo does prevent
Linrad from working properly.
In exploring all of this I did find out something interesting that would
only affect those trying to run Linrad as multiple different users on the
same machine. This has nothing to do with whether you are running Linrad va
the standard install from a tarball and then having compiled on your own
machine or whether you used the debian archive to install it. It is the
same either way. I have verified that it is identical on the systems here
where I installed Linrad the 'old fashioned way' as well as via the
xlinrad.deb file.
When it writes the par files do disk, Linrad sets the permissions on all of
the par files so that only the owner can write to them. So only the user
who originally ran Linrad from a given directory and set up the parameters
can run Linrad on that machine from that directory. Anyone else must do one
of two things: run it from another directory where a new set of par files
will be generated, or changed the permissions on the par files.
To keep disk clutter to a minimum, I set up the xlinrad.deb archive so that
all xlinrad activity occurs in the directory /usr/xlinrad.
So if you are running Linrad as installed from the xlinrad package, if
several different users each try to use Linrad [at different times] on the
same machine, only the original user, the one who made the par files, will
be able to use Linrad by typing 'linrad'. The others will not be able to
access the files.
As just noted, there are two ways around this:
[1] I got around this by going, as the owner, to /usr/xlinrad and doing:
chmod 666 *
chmod 777 linrad
chmod 777 xlinrad
This allows anyone to read or write to all files, and in addition allows
anyone to execute the linrad script and xlinrad, which it invokes.
One could also just copy xlinrad to another directory and run it by typing
./xlinrad
and things would work fine. Your par files would then be written to
whatever directory you were working from.
73,
Roger
W3SZ
Sergio writes:
Hello Roger,
very good. As I said I wasn't a 'sudoer' (hi, it sounds like being a bit
strange person, hey I am a sudoer now...what?) and I always access as a
standard user. So just by typing su - and password and launching linrad
one can still get stuck with the software being unable to drive the screen
properly. That can be solved by giving the proper rights of access to the
screen but a rookie might have some problems to do it. That's why I
dropped the little suggestion to cut short and go for 'sudo'. Surely if
one starts the X session as root he/she won't even notice that.
Hey I am your user now, please keep the package updated... hihi just
kidding of course, but I truly wish you'd like to do so in the future.
Great idea. Installing linrad now it is even easier than the windows
version...
73s Sergio
w3sz wrote:
Hi, Sergio,
Thanks for the kind note! I am very glad things are working for you.
Enjoy Leif's great piece of software!
The instructions did say: "Just type 'linrad' [linrad' [or 'sudo linrad'
Roger Rehr
W3SZ
http://www.nitehawk.com/w3sz
#############################################################
This message is sent to you because you are subscribed to
the mailing list <linrad@antennspecialisten.se>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>