It's not unusual to be allowed to install software, as long as it
doesn't require root access or conflict with anything existing. I've
been using rexx on the freeshell servers, which is fine with non-root
access, and I just work without using features that require root
access.
Maybe a compromise
David Ashley wrote:
> I thik that Mark's main point was that if you do not have root access
> to a machine (physical or virtual) then it would not be ethical to
> attempt to install software on that machine.
That is simply not true.
Depending on the environment and security policies in place you
I thik that Mark's main point was that if you do not have root access to
a machine (physical or virtual) then it would not be ethical to attempt
to install software on that machine.
David Ashley
On 07/14/2009 08:54 AM, Mike Cowlishaw wrote:
Interesting ethics. Even when the user's access to
> > Interesting ethics. Even when the user's access to the computer is a
> > virtual machine? :-)
>
> Hmm, well maybe I don't know much about virtual machines.
>
> As far as ethics goes, it seems pretty black and white to me.
> Someone is in charge of who can install software on a machine,
On Mon, Jul 13, 2009 at 2:27 PM, René Jansen wrote:
> well, this is not practice. Plain users on all kind of machines
> install all kinds of tools to run out of their home directories every
Well, yeah, I got to admit I'm mostly a single-user system kind of guy.
I don't have any objection to ha
As I indicated earlier, you have full flexibility to decide how it
makes sense for this to operate on the Mac. There's nothing in the
daemon itself that requires root mode to operate, nor is it dependent
on being able to write out the pid filethat's just part of the
conventions for the daemon
Hi Mark,
well, this is not practice. Plain users on all kind of machines
install all kinds of tools to run out of their home directories every
day, where a root install requires a root password from some security
desk, most of the time linked to a change request or an incident
number. Then
On Mon, Jul 13, 2009 at 8:05 AM, Mike Cowlishaw wrote:
> Interesting ethics. Even when the user's access to the computer is a
> virtual machine? :-)
Hmm, well maybe I don't know much about virtual machines.
As far as ethics goes, it seems pretty black and white to me.
Someone is in charge
wrote on 13/07/2009 15:14:40:
> Mark Miesfeld
> 13/07/2009 15:14
>
> Please respond to
> Open Object Rexx Developer Mailing List
>
> To
>
> Open Object Rexx Developer Mailing List
>
> cc
>
> Subject
>
> Re: [Oorexx-devel] Only root can allow
Well, when I saw the start of this thread, I was going to make the
following point. But, I see David already touched on it.
Nevertheless, I'm going to repeat it.
Besides any technical reasons, this is an ethical problem. If you can
not get root privileges on a PC, then the computer does not belon
All -
Having rxapi run as a system daemon is an absolute necessity on *nix
systems. This is the only way to get reliable and secure communications
between processes without needless overhead.
The old shared memory communications mechanism was a disaster waiting to
happen. Not only was it CPU i
This is only an issue for the install of the package. Once installed,
the rxapi daemon is launched at system startup with the sppropriate
permissions and everything works ok.
Rick
On Mon, Jul 13, 2009 at 5:03 AM, Rony G.
Flatscher wrote:
> Relating to this conversation:
>
> -
Relating to this conversation:
- cut here ---
Rick McGuire wrote:
> On Sun, Jul 12, 2009 at 6:08 PM, René
> Jansen wrote:
>
>> (I'll paste into sf when I am at a bigger computer)
>> I cannot quite see why rxapi needs to be run by root. It seem
13 matches
Mail list logo
