Boost logo

Boost :

Subject: Re: [boost] Getting Started Testing with Linux virtual machine on Windows host
From: Bjørn Roald (bjorn_at_[hidden])
Date: 2013-12-19 15:10:51


On 12/19/2013 10:14 AM, Jonathan Wakely wrote:
> On Dec 19, 2013 6:37 AM, "Bjørn Roald" wrote:
>>
>> On 12/19/2013 02:13 AM, Jonathan Wakely wrote:
>>>
>>> On 18 December 2013 22:22, Bjørn Roald wrote:

>>>> You would have full root access, wouldn't you?
>>>
>>>
>>> No, not as a non-root user you create. Not by default anyway.
>>
>>
>> OK, I was in the impression you tried in on a machine where you did not
> have root access as in not having the root password in your case.
>
> I have root access on my own systems, that's not the point. The
> instructions assume you are working as a non-root user.

agreed, but with root password you have access to root privileges and
thus have alternatives to using sudo that can be explained without
having separate set of instructions to various linux distros.

> If you have root
> access why use sudo at all?

Because it is convenient shorthand and it is simpler to avoid doing more
than you should with root privileges. It is also much simpler than
alternatives to document in instructions such as those that are
discussing here. I would prefer instructions to be using sudo even if I
did not have it on my system. For those that don't know sudo, provide
a note or link with information about sudo and alternatives. Such as:

For info on the sudo command see: http://en.wikipedia.org/wiki/Sudo

We are running circles around what we mean by "root access", we don't
disagree, we just misinterpret each other. Note that on many systems
including ubuntu, The system is configured so sudo users have access to
  general root privileges as they can run:

  $sudo bash

or

  $sudo -i

and thus be logged on as root in the bash shell without knowing a root
password. Just as you can with su and a password.

We are off topic and should stop.

--
Bjørn

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk