Linux must be run as root

Помогите пожалуста установить драйвер NVIDIA

Люди посмогите мне я устанавливаю драйвер NVIDIA-Linux-x86-1.0-6629-pkg1.run а мне пишеь ERROR: nvidia-installer must be run as root что это значит и как мне продолжит установку драйвера? подскажите плиззз!

Re: Помогите пожалуста установить драйвер NVIDIA

Re: Помогите пожалуста установить драйвер NVIDIA

y mena vot chto visvetilo

ERROR: An NVIDIA kernel module ‘nvidia’ appears to already be loaded in your kernel. This may be because it is in use (for example, by the X server), but may also happen if your kernel was configured without support for module unloading. Please be sure you have exited X before attempting to upgrade your driver. If you have exited X, know that your kernel supports module unloading, and still receive this message, then an error may have occured that has corrupted the NVIDIA kernel module’s usage count; the simplest remedy is to reboot your computer.

Re: Помогите пожалуста установить драйвер NVIDIA

если Xы не запущены, то rmmod nvidia от rootа.

Re: Помогите пожалуста установить драйвер NVIDIA

Откуда же вы такие лезете? У тебя словаря нет — три слова никак не прочитать?

>nvidia-installer must be run as root

Программа установки должна быть запущена под root’ом.

На сайте nvidia есть русское README.

А для альтернативно мыслящих здесь есть еще одна инструкция, прямо на сайте:

Re: Помогите пожалуста установить драйвер NVIDIA

ага я с рута ставил и вот что мне вылезло. ERROR: An NVIDIA kernel module ‘nvidia’ appears to already be loaded

in your kernel. This may be because it is in use (for example, by the X server),

but may also happen if your kernel was configured without

support for module unloading. Please be sure you have exited X

before attempting to upgrade your driver. If you have exited X, know

that your kernel supports module unloading, and still receive this

message, then an error may have occured that has corrupted the NVIDIA

kernel module’s usage count; the simplest remedy is to reboot your computer.

кто нибудь знает что это значит.

Re: Помогите пожалуста установить драйвер NVIDIA

ну тут же написано все! что неясно?

либо ты устанавливаешь модуль при запущенных иксах, либо у тя ядро собрано без поддержки выгрузки модулей

. еще там написано что если ты не из под иксов запускаешь модуль и у тя в ядре поддеривается выгрузка модулей то перегрузи комп! 🙂

а вообще сделай вот так от рута:

и запусти еще раз программу установки!

Re: Помогите пожалуста установить драйвер NVIDIA

Чую, придется еще раз инструкцию править.

Для тех, кто по-английски не разумеет и думать ленится. 🙂

Re: Помогите пожалуста установить драйвер NVIDIA

ну пишу я в руте: rmmod nvidia и ничё незапускается command not found! даже комады такой незнает

Re: Помогите пожалуста установить драйвер NVIDIA

ну помогите мне поставит этот драйвер уже 3 дня с ним парюсь и каждый раз онди ошибки! как правильно его установить посдкажить?

Re: Помогите пожалуста установить драйвер NVIDIA

нужно выполнить установку с правами суперпользователя root

Re: Помогите пожалуста установить драйвер NVIDIA

Источник

Thread: «This script must be run as root»

Thread Tools

Display

«This script must be run as root»

I am trying to install a program, but when I enter «./install» in the terminal, I get the message:

«This script must be run as root»

How can I run it as root, and what does that mean ?

Re: «This script must be run as root»

root is the privileged adiminstrator’s account in Linux. It’s usually needed for example to install software outside your home folder.

Be careful what you do and run as root. Only run programs and scripts from trustworthy sources that way as the can harm your system.

Re: «This script must be run as root»

I used the «sudo ./install» command and it asked me for my password, which I entered. Then I got the message «command not found», though I navigated exactly to the directory where it is inside.

I am trying to install Avira Antivir Personal for Linux, if that helps. I unzipped the gz package to the /tmp folder in the main drive, where Linux is installed. I renamed it to «antivir» since the original name was long and complicated.

Yet I cannot get it to install.

Re: «This script must be run as root»

Do I have to enter «sudo ./install» exactly or something like «sudo cd /tmp/antivir/install» ?

Re: «This script must be run as root»

I quote from the Terminal with translations in bold, since it is the German version:

So first it asks me for permission, and when I enter «sudo» before the «./install» it suddenly does not find the command anymore ?!

But when I open the folder with the file manager, the install command/file is clearly there !

Re: «This script must be run as root»

Could it be that the program, though written for Linux, is not compatible with Ubuntu ?

It’s quite annoying that such a simple task like installing a downloaded program is so complicated under Linux. I’m not a computer illiterate, i have been working with Windows computers extensively since 1996 and some would call me a power-user with some reason. But Linux beats me.

Last edited by Ali_Barba; June 15th, 2012 at 11:38 PM .

Re: «This script must be run as root»

Maybe somebody could download the program, too, and see whether it works ? The source is definitely trustworthy, one of the major antivirus companies. But maybe they made some mistake while writing the installer and it is corrupted ?

Re: «This script must be run as root»

Please post back if you have any further questions or comments.

Источник

How to run a .run file as root?

I downloaded a .run file for a Nvidia driver, but when I run it in the terminal it tells me it must be run as root.

I’m a complete noob and I barely even know what root is. I think it’s somewhere around the equivalent of admin in windows.

Well, I got the file to run but it turns out that the driver will not recognize my card. I’ve heard about other problems with Nvidia cards not working right with 64 bit versions of 12.04.

4 Answers 4

You need to do two things; both from a Terminal prompt:

1. Change to the directory where you have the .run file stored.
2. Type: chmod 755 filename.run
3. Type: sudo ./filename.run

The above commands will make the file executable and will launch the executable with root-level permissions.

Add the command «sudo» before the command. For example: sudo blah.sh

After you enter your password the command will run as root. Be careful to verify the trustworthiness of a package or command before running it with sudo.

root is the master account in Ubuntu; every account has limited privileges but the root account has no limitations. The reason for hiding root is that in most cases you don’t need root access. The analog in Windows would be having to authenticate when you want to install a driver; in Ubuntu you have to be root or have root privileges.

There are two ways for you to get access as root. You can type:

sudo and Ubuntu will ask you for your password and then execute that command as root.

Источник

How to run applications as root?

I am having some strange issue with Kate and Kwrite. When I click on Open File, it crashes with segmentation fault.

I am a complete newbie to Linux, and I think the issue is that I am not running the application as root.

How do I run applications as root in Ubuntu? Is it bad practice to do this? What is the purpose of the whole root thing, where even though we need to use root so frequently, it is not utilized as default?

4 Answers 4

It is pretty simple to run a program as root.

For a console program use

If it is a GUI application use

UNIX-like operating systems (including Linux) use a concept called privilege separation to ensure that the system stays safe. UNIX was designed as a multi-user system from the ground up — that is, it was designed so that many people could use one computer running UNIX at once. Because most users don’t need to be able to modify the core system only the system administrator should have that privilege. That privileged user is traditionally called root. (Root is a lot like Administrator in Windows.)

This makes sense on several levels. Commonly, a web server or other process that exposes a port to other (possibly malicious) computers will run as its own user (Apache runs as the user nobody ), so that even if the web server program is hacked, the attacker can’t trash the entire machine quite so easily. It even makes sense for mostly single-user machines such as desktops: if other members of your family, for example, somehow manage to run rm -rf / (do NOT run that), they won’t have permission to delete every file on the system, like they would if there were no such thing as privilege separation.

There are several commands you can use to elevate your privileges. The sudo command exists to temporarily give you root-level privileges when you need them to administer the system. You can also use the commands gksudo or su . The latter can be used only if you know root’s password and is a good option if your account doesn’t have permission to use sudo .

The root user can do anything on a system, with almost no exceptions. So even if you request something by accident, it will be carried out with little or no warning, even if it’s bad for the health of your system. This is why it’s good practice to do most of your activities as a normal user, and use root only when needed, like when you’re installing a program.

You shouldn’t need to use root to get rid of a segmentation fault. If root is the only thing that fixes a segfault, then the program has a bug. Programs should not fail like that just because they don’t have root.

Источник

How to run Terminal as root?

When we want to run a programs as root we use sudo , gksu , gksudo and etc. Now my question is how do we can run a Terminal as the root user in Terminal?

I tried with using gksudo terminal and gksu terminal but nothing happens. and by running sudo terminal I get error sudo: terminal: command not found .

7 Answers 7

The default terminal emulator on Ubuntu is the GNOME Terminal. It’s located at /usr/bin/gnome-terminal and can be run with the gnome-terminal command.

What You Really Want

What you probably want is a shell running as root, as though it were produced from a root login (for example, with all the environment variables set for root rather than for your user).

Assuming that’s what you want, as steeldriver has suggested, just run:

You’ll have a root shell in which commands you enter will be run as root (without having to precede them with sudo ).

But if you really want to run the graphical terminal emulator application as root, read on. I present two ways: with gksu / gksdo , and with the sudo command.

With gksu / gksudo

Since you have the gksu package installed, you can run gnome-terminal as root with either of:

(Since gksu is set to sudo-mode in Ubuntu by default, these should be equivalent.)

Running gnome-terminal as root without a controlling non-root terminal:

Virtually every desktop environment provides a facility to run a command without having to open a terminal (which would then, if closed, usually cause the command to be terminated).

This is usually achieved with Alt + F2 . A textbox labeled Run command (or similar) will appear and you can enter your command.

For example, it looks like this in Unity:

And like this in MATE (GNOME Flashback/Fallback, Xfce, LXDE are similar):

Note that this works with gksu and gksudo because they use a graphical authentication dialog. If you were to press Alt + F2 and run sudo . , you would then be unable to interact with the password prompt.

With sudo

If you don’t have the gksu package and you won’t want to install it, you can use:

The -H flag is important because it sets the HOME environment variable to /root instead of your own user’s home directory. You should not use sudo gnome-terminal as it can break the gnome-terminal configuration belonging to the non-root user. For more information about this, see:

( sudo -i gnome-terminal is also okay.)

Getting rid of the controlling non-root terminal:

If you (1) open a graphical terminal, (2) run something like sudo -H gnome-terminal in it, to create a new graphical root terminal, and (3) quit the original non-root graphical terminal . then the root graphical terminal quits as well.

This is because the root graphical terminal is sent SIGHUP when the terminal that owns it is exited.

To prevent this, you might think you could instead launch the graphical root terminal with:

But this will only work if sudo doesn’t have to prompt for a password. If it does, you won’t see the password prompt.

One way to work around this is to use:

sudo -v exists for just this purpose. As explained in man sudo , it «update[s] the user’s cached credentials, authenticating the user if necessary.»

Note that this will still not work if run directly from your desktop environment’s Alt + F2 «run command» box, because you still need a terminal to enter your password for sudo -v .

Or you can do it in what might be called the traditional way, by suspending the job after it starts:

1. Run sudo -H gnome-terminal from the original non-root graphical terminal.
2. Enter your password as prompted by sudo . The graphical terminal will start.
3. Still in the non-root terminal, press Ctrl + Z to suspend the root terminal. While the root terminal is suspended, you can’t use it; its interface will not respond to your actions.
4. Quit the controlling non-root terminal with exit . The graphical root terminal job will be both unsuspended and disowned by the non-root terminal, automatically.

But suppose you wanted to keep using the original, non-root terminal too. Then you could run bg N , where N is the graphical root terminal’s job number, to resume the job in the background. You can run jobs to find N but you probably won’t have to—that number was shown as [N] when you pressed Ctrl + Z . For example:

opens a terminal as root:

No need to explain that you can use this to open any terminal as root like this; like Vala ( gksudo vala-terminal ), Xterm ( gksudo xterm ), Termit ( gksudo termit ), UXTerm ( gksudo uxterm ), Konsole ( gksudo konsole ) and so on.

As previously stated, you ask how to run Terminal as root, but more likely you actually want to run the graphical Terminal application as your normal user, and start a root shell inside it where you are logged on as root. In this way the graphical terminal application is not granted root privileges. The previous answers don’t seem to give clear command lines to use so here’s what I use.

With xterm

xterm -bg black -fg red -e sudo -i

The ‘-e sudo -i’ tells xterm to switch to root in the session, and the colours are just to make it very obvious that it’s a root shell.

With Gnome Terminal

gnome-terminal — sudo -i

Personally, I bind Gnome keybindings to launch terminals easily

Go to Keyboard settings, add a custom shortcut with Shortcut Super+X and command ‘xterm -bg black -fg white -sb -sl 5000’, and root xterm with Shortcut Super+Z and command ‘xterm -bg black -fg red -sb -sl 5000 -e sudo -i’.

In the past I have tended to prefer xterm over Gnome Terminal because the font is small and simple, but I’m coming round to Terminal now I run high DPI big screens. Colour coding your terminals is a very good idea once you start to run different profiles with dangerous consequences to avoid accidents (e.g. local root, remote client’s machine, remote client root).

That question sounds so simple that there must be a simple solution, right?
Of course you can use gksudo or similar tools but there may be environments where you don’t want to depend on GTK. It’s confusing but a terminal is not a shell !

The terminal is that thing what shows you stuff, where the shell is the thing that has those fancy features like environment variables, conditionals and all that scripting stuff. That’s why x-terminal-emulator -e . just expects a program to run. No scripts possible here, it just starts a new process. When a terminal starts it just knows that there’s some kind of screen showing you stuff and the input of your keyboard which pours directly in there. A shell delivers all the logic of a script language like eg. sh, bash, ash, zsh, .

The other important distinction is who is running the terminal and what shell is running inside it. You may run a terminal in the context of an ordinary user which runs a root shell inside of it but this has some disadvantages eg. when you start a new tab a new shell is spawned but it falls back to the privileges of an ordinary user. Your command of a ‘New shell please’ goes to the terminal and not the shell!
A disappointment when you realize that you have to enter all those sudo stuff once again for every tab you open. Now, is there a way to open a terminal and not a shell as root without using packages like gksudo? Expecting a debian context:

bash -c «xhost +si:localuser:root; ssh-askpass | sudo -S -Hb /usr/bin/xfce4-terminal —default-working-directory=/root»

Although it looks simple a lot stuff is happening here:

• allow root to access the X desktop of the current user.
• since sudo requires a tty, we avoid that by running ssh-askpass which runs in the context of the current user and asks for your pass.
• sudo now reads that pass from the stdin (-S), it set’s the home folder (-H) and spawns a new process detaching from our context (-b).
• and finally sets the terminal process’ default home folder to root to avoid landing in the home of the current user.

et voilà! You have a terminal running as root spawned in the context of the current user. Now when you spawn a new tab it’s happening inside the root terminal instead of the user who spawned it.

Attention! There’s is a reason why this stuff is so complicated. Keep in mind in whatever X|VNC|RDP session you are running it. It just keeps a terminal open. That’s the downside! If someone is able to capture your session (however likely it may be), root access is for free! Your decision.

Источник