Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish OS via SSH as root user (of course it will still ask you for a password) even when Remote connection is turned off.
| 2 | No.2 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish OS via SSH as root user (of course it will still ask you for a password) even when Remote connection is turned off.
| 3 | No.3 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a password) even when Remote connection is turned off.
| 4 | No.4 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a password) even when Remote connection is turned off.
| 5 | retagged |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a password) even when Remote connection is turned off.
| 6 | No.6 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a root password) even when Remote connection is turned off.
| 7 | No.7 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a root password) even when Remote connection is turned off.
| 8 | No.8 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a root password) even when Remote connection is turned off.
| 9 | No.9 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a root password) even when Remote connection is turned off.
| 10 | No.10 Revision |
Actually, su is already installed on Sailfish if developer mode is activated. But the password for root is not set by default so you can't use su out-of-the-box.
The steps to enable it are simple:
devel-su password prompt).devel-supasswdsu instead of devel-su to become root user.After the root user is activated, Remote connection setting becomes obsolete. You don't need to turn it on and set password for root access to use su. And you can always connect to Sailfish via SSH as root user (of course it will still ask you for a root password) even when Remote connection is turned off.