Hello All!

I have installed this distro via raspberry website and have been installing extra s/w as sources and have got to the point where one of them needs to be installed as root (su). This is not sudo or sudo su etc as that will not work.

So doing su asks for a password and the one used for user pi does not work.

What is it or failing that how say having issued sudo -s
can I change it?

Now I did think of using usermod -p password root

but the docs specify :

-p, --password PASSWORD
The encrypted password, as returned by crypt(3).

Note: This option is not recommended because the password (or
encrypted password) will be visible by users listing the processes.

You should make sure the password respects the system's password
policy.

So I am guessing I need to try and install crypt assuming it is available via the distro file repos but the only one I can see is as shown on doing a
man crypt which is a library routine and not a program so how on earth do you do it ?

Bye the bye I decided to change the system name via the GUI app that you can change the pi password and on reboot it stops during the boot sequence and will
not go any further so I guess Debian is not a happy camper doing a change :(

I must admit I do not recall trying to do the same with any other distro but find it hard to understand why it should not like it, or am I having another senior moment ?


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Re: Pi 4 Bullseye Desktop x64
By: Vincent Coen to All on Thu Mar 03 2022 01:04 am

What is it or failing that how say having issued sudo -s
can I change it?

Now I did think of using usermod -p password root

$ sudo passwd root

Job done.

Curious to know why 'sudo su' is not working though. If it isn't setting your environment correctly, there is always:

$ sudo su -

Tristan.
--- SBBSecho 3.14-Linux
* Origin: Extricate BBS - bbs.extricate.org (2:250/11)

On 02/03/2022 18:57, Tristan Greaves wrote:

Re: Pi 4 Bullseye Desktop x64
By: Vincent Coen to All on Thu Mar 03 2022 01:04 am

VC> What is it or failing that how say having issued sudo -s
VC> can I change it?

VC> Now I did think of using usermod -p password root

$ sudo passwd root

Job done.

Curious to know why 'sudo su' is not working though. If it isn't setting your
environment correctly, there is always:

$ sudo su -

Tristan.

I think that until you set a root password, you cannot operate a root
shell *at all*

I always set the root password. There are times when it saves multiple
uses of sudo

--
“The fundamental cause of the trouble in the modern world today is that
the stupid are cocksure while the intelligent are full of doubt."

- Bertrand Russell

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 02/03/2022 13:04, Vincent Coen wrote:

So doing su asks for a password and the one used for user pi does not work.

What is it or failing that how say having issued sudo -s
can I change it?

to set a root password I tend to use:
sudo bash
passwd root

--
Nev
It causes me a great deal of regret and remorse
that so many people are unable to understand what I write.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Thu, 3 Mar 2022 10:20:34 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

I always set the root password. There are times when it saves multiple
uses of sudo

On a personal/home system with one admin, set a root password and
use root when needed (don't run browsers etc. as root).

On a business system with multiple admins do not permit root access, have a controlled list of sudoers with an audited sudoers configuration and
log everything that happens under sudo against the real user.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello Tristan!

Thursday March 03 2022 06:57, you wrote to me:

Re: Pi 4 Bullseye Desktop x64
By: Vincent Coen to All on Thu Mar 03 2022 01:04 am

What is it or failing that how say having issued sudo -s
can I change it?

Now I did think of using usermod -p password root

$ sudo passwd root

Job done.

Curious to know why 'sudo su' is not working though. If it isn't
setting your environment correctly, there is always:

$ sudo su -

Within the Makefile there is :

@if [ "`id -un`" != "root" ] ; then \
echo; echo " Must be root to install!"; echo; exit 3;
fi

So if not using su this test will fail.

Although trying echo `id -un` returns root for su, sudo -s
So do not understand why it fails the test.

Never less still need to fix the password issue with su
Clearly something to do with Debian at least as far as Raspberry version is concerned but think I have had similar issue with another distro using Debian.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello nev!

Thursday March 03 2022 10:39, you wrote to me:

On 02/03/2022 13:04, Vincent Coen wrote:

So doing su asks for a password and the one used for user pi does
not work.

What is it or failing that how say having issued sudo -s
can I change it?

to set a root password I tend to use:
sudo bash
passwd root

Is that with no options to passwd other than passing 'root' ?

Thanks for the method though I will try it after re-installing the O/S as it is
failing to boot.

I did set up Trim as suggested by another posters reference to a blog and that appeared to work even after I rebooted so may have something to do with changing the system name but cannot understand why it should be the case.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Ahem!

Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:

On Thu, 3 Mar 2022 10:20:34 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

I always set the root password. There are times when it saves
multiple uses of sudo

On a personal/home system with one admin, set a root password and
use root when needed (don't run browsers etc. as root).

On a business system with multiple admins do not permit root
access, have a controlled list of sudoers with an audited sudoers configuration and log everything that happens under sudo against the
real user.

To install specific software after compiling using 'make install' must be made using su and sudo -s does not work.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

On Thu, 03 Mar 2022 13:08:21 +1200
nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

Hello Ahem!

Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:

On Thu, 3 Mar 2022 10:20:34 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

I always set the root password. There are times when it saves
multiple uses of sudo

On a personal/home system with one admin, set a root password and
use root when needed (don't run browsers etc. as root).

On a business system with multiple admins do not permit root
access, have a controlled list of sudoers with an audited sudoers configuration and log everything that happens under sudo against the
real user.

To install specific software after compiling using 'make install' must be made using su and sudo -s does not work.

Home system log in as root and run make install - commercial system don't do that use package management all the way probably backed by a CMS
like ansible or puppet.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello Ahem!

Thursday March 03 2022 14:19, you wrote to me:

On Thu, 03 Mar 2022 13:08:21 +1200 nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

Hello Ahem!

Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:

On Thu, 3 Mar 2022 10:20:34 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

I always set the root password. There are times when it saves
multiple uses of sudo

On a personal/home system with one admin, set a root password

and

use root when needed (don't run browsers etc. as root).

On a business system with multiple admins do not permit root
access, have a controlled list of sudoers with an audited sudoers
configuration and log everything that happens under sudo against

the

real user.

To install specific software after compiling using 'make install'
must be made using su and sudo -s does not work.

Home system log in as root and run make install - commercial
system don't do that use package management all the way probably
backed by a CMS like ansible or puppet.

That's the problem - I can't log in as root using su or su - as I do not know the password.



Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

On 03/03/2022 05:03, Vincent Coen wrote:

Hello Ahem!

Thursday March 03 2022 14:19, you wrote to me:

> On Thu, 03 Mar 2022 13:08:21 +1200
> nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

>> Hello Ahem!
>>
>> Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:
>>
>> > On Thu, 3 Mar 2022 10:20:34 +0000
>> > The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>> >> I always set the root password. There are times when it saves
>> >> multiple uses of sudo
>>
>> > On a personal/home system with one admin, set a root password
>> and
>> > use root when needed (don't run browsers etc. as root).
>>
>> > On a business system with multiple admins do not permit root
>> > access, have a controlled list of sudoers with an audited sudoers
>> > configuration and log everything that happens under sudo against
>> the
>> > real user.
>>
>> To install specific software after compiling using 'make install'
>> must be made using su and sudo -s does not work.

> Home system log in as root and run make install - commercial
> system don't do that use package management all the way probably
> backed by a CMS like ansible or puppet.

That's the problem - I can't log in as root using su or su - as I do not know the password.

Vincent

On a Raspbian fresh install, I have always found:
sudo -i
[yourpassword]
works.

Then 'visudo' to fix any problems, and
passwd to set root password.

I.e. sudo uses your password, su uses root password

--
Chris Elvidge
England

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Thu, 03 Mar 2022 13:08:21 +1200, Vincent Coen wrote:

Hello Ahem!

Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:

On Thu, 3 Mar 2022 10:20:34 +0000 The Natural Philosopher <tnp@invalid.invalid> wrote:

I always set the root password. There are times when it saves
multiple uses of sudo

On a personal/home system with one admin, set a root password and
use root when needed (don't run browsers etc. as root).

On a business system with multiple admins do not permit root
access, have a controlled list of sudoers with an audited sudoers configuration and log everything that happens under sudo against the
real user.

To install specific software after compiling using 'make install' must
be made using su and sudo -s does not work.

sudo won't work until until you've configured it. To do that, log in as
root and run 'visudo', which edits /etc/sudoers - beware that this will
want to use vi as its editor unless you've set the EDIT global variable,
to the name of your preferred editor. I normally set that by editing /etc/ profile.d/less.sh, which takes effect next time you log in.

However ymmv.

Vincent

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello Ahem!

Thursday March 03 2022 14:19, you wrote to me:

On Thu, 03 Mar 2022 13:08:21 +1200 nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

Hello Ahem!

Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:

On Thu, 3 Mar 2022 10:20:34 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

I always set the root password. There are times when it saves
multiple uses of sudo

On a personal/home system with one admin, set a root password

and

use root when needed (don't run browsers etc. as root).

On a business system with multiple admins do not permit root
access, have a controlled list of sudoers with an audited sudoers
configuration and log everything that happens under sudo against

the

real user.

To install specific software after compiling using 'make install'
must be made using su and sudo -s does not work.

Home system log in as root and run make install - commercial
system don't do that use package management all the way probably
backed by a CMS like ansible or puppet.

The trick was to use passwd root

and change it BUT what the devil was it originally - no docs on this needless to say :(


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

On Thu, 03 Mar 2022 22:51:00 +1200
nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

The trick was to use passwd root

and change it BUT what the devil was it originally - no docs on this
needless to say :(

It wasn't set at all originally so root could not log in.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 03/03/2022 01:03, Vincent Coen wrote:

Hello nev!

Thursday March 03 2022 10:39, you wrote to me:

> On 02/03/2022 13:04, Vincent Coen wrote:

>> So doing su asks for a password and the one used for user pi does
>> not work.
>>
>> What is it or failing that how say having issued sudo -s
>> can I change it?
>>
> to set a root password I tend to use:
> sudo bash
> passwd root

Is that with no options to passwd other than passing 'root' ?

Yes.
sudo bash starts a new bash shell as root. Then passwd root will let you
set a new root passwd. As you're now root it doesn't ask for the
old/existing one.

--
Nev
It causes me a great deal of regret and remorse
that so many people are unable to understand what I write.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello Vincent!

03 Mar 22 17:03, you wrote to Ahem A Rivet's Shot:

That's the problem - I can't log in as root using su or su - as I do not know the password.

Where is your problem?. It is only a rasberry system, zo it is stored
on a USB drive or a Micro SSD. Take ik to the system where you put
this image on de datacarrier. Mount the secon partition (rootfs) and
look for the shadow file. In the line for root remove the gibberish
between the first and second colon, with any editor.

Root will now have no password, so you should set one as soon as you have
logged in.

But to be serious, it should not be possible to login on root with a password.
There should be a '*' in the shadow files and access should be given in the
sudo config.

So instead of my first suggestion to edit the shadow file, edit sudoers,
maybe adding your login account to the group sudo is sufficient.
That file can also be edited while the rootfs in mounted on the host system.

Kees

--- GoldED+/LNX 1.1.5--b20180707
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

Den 2022-03-02 kl. 14:04, skrev Vincent Coen:

Hello All!

I have installed this distro via raspberry website and have been installing extra s/w as sources and have got to the point where one of them needs to be installed as root (su). This is not sudo or sudo su etc as that will not work.

So doing su asks for a password and the one used for user pi does not work.

I never enable root user on macos or debian-derivatives
If I need a root prompt, I

sudo su -

and gives the pi user's passwd.

the prompt is from sudo - and it is run by use r pi (or whoever is
logged in)

The only system I tried that do not allow this is
centos/rocky (and probably RHEL as well then) - in which the
installation guide requires a root pwd to be set
and AIX.


--
Björn

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 03/03/2022 05:03, Vincent Coen wrote:

Hello Ahem!

Thursday March 03 2022 14:19, you wrote to me:

> On Thu, 03 Mar 2022 13:08:21 +1200
> nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

>> Hello Ahem!
>>
>> Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:
>>
>> > On Thu, 3 Mar 2022 10:20:34 +0000
>> > The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>> >> I always set the root password. There are times when it saves
>> >> multiple uses of sudo
>>
>> > On a personal/home system with one admin, set a root password
>> and
>> > use root when needed (don't run browsers etc. as root).
>>
>> > On a business system with multiple admins do not permit root
>> > access, have a controlled list of sudoers with an audited sudoers
>> > configuration and log everything that happens under sudo against
>> the
>> > real user.
>>
>> To install specific software after compiling using 'make install'
>> must be made using su and sudo -s does not work.

> Home system log in as root and run make install - commercial
> system don't do that use package management all the way probably
> backed by a CMS like ansible or puppet.

That's the problem - I can't log in as root using su or su - as I do not know the password.

If you can su you can exhange/set the root password

sudo passwd root

Vincent

--
Any fool can believe in principles - and most of them do!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 03/03/2022 01:08, Vincent Coen wrote:

Hello Ahem!

Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:

> On Thu, 3 Mar 2022 10:20:34 +0000
> The Natural Philosopher <tnp@invalid.invalid> wrote:

>> I always set the root password. There are times when it saves
>> multiple uses of sudo

> On a personal/home system with one admin, set a root password and
> use root when needed (don't run browsers etc. as root).

> On a business system with multiple admins do not permit root
> access, have a controlled list of sudoers with an audited sudoers
> configuration and log everything that happens under sudo against the
> real user.

To install specific software after compiling using 'make install' must be made
using su and sudo -s does not work.

Vincent

Yes. business use you need root and a password, but it should be one
person alone that knows it


--
Any fool can believe in principles - and most of them do!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 03/03/2022 10:51, Vincent Coen wrote:

Hello Ahem!

Thursday March 03 2022 14:19, you wrote to me:

> On Thu, 03 Mar 2022 13:08:21 +1200
> nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

>> Hello Ahem!
>>
>> Thursday March 03 2022 10:39, you wrote to The Natural Philosopher:
>>
>> > On Thu, 3 Mar 2022 10:20:34 +0000
>> > The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>> >> I always set the root password. There are times when it saves
>> >> multiple uses of sudo
>>
>> > On a personal/home system with one admin, set a root password
>> and
>> > use root when needed (don't run browsers etc. as root).
>>
>> > On a business system with multiple admins do not permit root
>> > access, have a controlled list of sudoers with an audited sudoers
>> > configuration and log everything that happens under sudo against
>> the
>> > real user.
>>
>> To install specific software after compiling using 'make install'
>> must be made using su and sudo -s does not work.

> Home system log in as root and run make install - commercial
> system don't do that use package management all the way probably
> backed by a CMS like ansible or puppet.

The trick was to use passwd root

and change it BUT what the devil was it originally - no docs on this needless to say :(

often it does not exist so it is not possible to login to a shell as
root at all until it is set

'sudo bash' was suggested by someone else - that should work I guess.

Vincent

--
Any fool can believe in principles - and most of them do!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Den 2022-03-04 kl. 10:58, skrev Björn Lundin:

I never enable root user on macos or debian-derivatives
If I need a root prompt, I

sudo su  -

and gives the pi user's passwd.

I forgot to mention that the sudoers file is setup to allow this for the
first created user on these systems



--
Björn

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 3.3.2022 02:56 AM, Vincent Coen wrote:

Within the Makefile there is :

@if [ "`id -un`" != "root" ] ; then \
echo; echo " Must be root to install!"; echo; exit 3;
fi

So if not using su this test will fail.

Your example is missing a backslash at the end of the second line,
after 'exit 3;'.

After adding it, the example worked with straight sudo and
changing to root with 'sudo bash'. It works on Raspbian and
Raspi OS.

You are doing ther change to superuser too complicated. The
installation should work with single 'sudo make install'.

--

-TV

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 04/03/2022 13:45, Tauno Voipio wrote:

The
installation should work with single 'sudo make install'.

All of my root ownership compiled binaries are installed with that.

--
Any fool can believe in principles - and most of them do!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello Ahem!

Friday March 04 2022 05:27, you wrote to me:

On Thu, 03 Mar 2022 22:51:00 +1200 nospam.Vincent.Coen@f1.n250.z2.fidonet.org (Vincent Coen) wrote:

The trick was to use passwd root

and change it BUT what the devil was it originally - no docs on this
needless to say :(

It wasn't set at all originally so root could not log in.

So using blank would not have worked - I did wonder afterwards.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello nev!

Friday March 04 2022 09:04, you wrote to me:

On 03/03/2022 01:03, Vincent Coen wrote:

Hello nev!

Thursday March 03 2022 10:39, you wrote to me:

> On 02/03/2022 13:04, Vincent Coen wrote:

>> So doing su asks for a password and the one used for user pi
does
>> not work.
>>
>> What is it or failing that how say having issued sudo -s
>> can I change it?
>>
> to set a root password I tend to use:
> sudo bash
> passwd root

Is that with no options to passwd other than passing 'root' ?

Yes.
sudo bash starts a new bash shell as root. Then passwd root will let
you set a new root passwd. As you're now root it doesn't ask for
the old/existing one.

Thanks all done now ---- hopefully.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Kees!

Friday March 04 2022 00:19, you wrote to me:

Hello Vincent!

03 Mar 22 17:03, you wrote to Ahem A Rivet's Shot:

That's the problem - I can't log in as root using su or su - as I
do not know the password.

Where is your problem?. It is only a rasberry system, zo it is stored
on a USB drive or a Micro SSD. Take ik to the system where you put
this image on de datacarrier. Mount the secon partition (rootfs) and
look for the shadow file. In the line for root remove the gibberish
between the first and second colon, with any editor.

Root will now have no password, so you should set one as soon as you
have logged in.

But to be serious, it should not be possible to login on root with a password. There should be a '*' in the shadow files and access should
be given in the sudo config.

So instead of my first suggestion to edit the shadow file, edit
sudoers, maybe adding your login account to the group sudo is
sufficient. That file can also be edited while the rootfs in mounted
on the host system.

As explained before - the installation tool will not allow a install unless logged in as root via su - sudo or sudo -s does not work.

All fixed now that I have set the root password.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Tauno!

Friday March 04 2022 15:45, you wrote to me:

On 3.3.2022 02:56 AM, Vincent Coen wrote:

Within the Makefile there is :

@if [ "`id -un`" != "root" ] ; then \
echo; echo " Must be root to install!";
echo; exit 3;
fi

So if not using su this test will fail.

Your example is missing a backslash at the end of the second line,
after 'exit 3;'.

After adding it, the example worked with straight sudo and
changing to root with 'sudo bash'. It works on Raspbian and
Raspi OS.

You are doing ther change to superuser too complicated. The
installation should work with single 'sudo make install'.

Seems my cut and paste across two editors messed up this is what is there :

--
all depend:
@if [ -z ${MBSE_ROOT} ] ; then \
echo; echo " MBSE_ROOT is not set!"; echo; exit 3; \
else \
for d in ${SUBDIRS}; do (cd $$d && ${MAKE} $@) || exit;
done; \
fi


--

I will retry that as sudo bash and see if it works as I may not have tried
that one.

Nope that fails, so will stick to the install doc.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)