Error you cannot perform this operation unless you are root

Запуск pacman без рута

vadik
imam, тогда и pacman.conf показывайте.

arcanis так тот пакет в основную систему установился? Или так и лежит в /tmp?

Пакет лежит где и лежал

а на попытку установить говорит
error: you cannot perform this operation unless you are root.

тоесть я в отдельном каталоге из под простого юзера собираю макет дерева каталогов и файлов для образа.

imam, про расположение пакета я спрашивал у arcanis-а. А вас просил показать тот pacman.conf, на который ссылаетесь в своей команде установки (есть мысль, но надо проверить).

П.с. только уже все это завтра, пора спать.

vadik
imam, про расположение пакета я спрашивал у arcanis-а. А вас просил показать тот pacman.conf, на который ссылаетесь в своей команде установки (есть мысль, но надо проверить).

комент выше правил ))))

pacman.conf:
[options]
RootDir = /mnt/
DBPath = /mnt/var/lib/pacman/
CacheDir = /mnt/var/cache/pacman/pkg/
LogFile = /mnt/var/log/pacman.log
HoldPkg = pacman glibc
Architecture = auto
CheckSpace
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional

vadik
arcanis так тот пакет в основную систему установился? Или так и лежит в /tmp?

Отучить pacman проверять, для некоторых операций, запущен ли он от рута нельзя — это часть его логики работы определенная в исходниках. Хотя некоторые считают что так делать моветон. А вот почему suid бит на него не действует — интересный вопрос.
Наверное поэтому:

naszar
Отучить pacman проверять, для некоторых операций, запущен ли он от рута нельзя — это часть его логики работы определенная в исходниках.

Значит мне придется править исходник

Источник

Как дать пользователю права root?

Я только что установил Arch. Работает отлично. Я создал нового пользователя, вошел в систему с ним, и теперь я пытаюсь установить несколько вещей с pacman . Но я продолжаю получать сообщение об ошибке: error: you cannot perform this operation unless you are root. я могу pacman нормально работать с root, но есть ли способ разрешить моему новому пользователю выполнять эти действия?

Я попытался войти в root и использовать gpasswd:

gpasswd -a jack root

но это ничего не сделало.

Вы должны прочитать страницу Arch Wiki на sudo .

sudo («Заместитель пользователя делает») позволяет системному администратору делегировать полномочия, чтобы дать определенным пользователям (или группам пользователей) возможность выполнять некоторые (или все) команды от имени пользователя root или другого пользователя, обеспечивая при этом контрольный журнал команд и их аргументы.

Вы можете установить sudo из репозиториев, а затем настроить его, чтобы предоставить вашему пользователю jack доступ к привилегированным командам путем редактирования /etc/sudoers . Убедитесь, что вы делаете это с помощью visudo команды.

Чтобы предоставить пользователю jack полные права суперпользователя, вы должны добавить эту строку:

Обычно я включаю привилегии root для определенной группы. Таким образом, вы можете просто добавить пользователей, которым вы хотите привилегии root, в эту группу.

Редактировать /etc/sudoers с помощью visudo и добавить (или закомментировать):

Затем добавьте своего пользователя в эту группу:

Я могу использовать pacman с root’ом, но есть ли способ разрешить моему новому пользователю выполнять эти действия?

Вы можете создать свой $USER , добавив их в wheel группу в одиночку:

Затем обновите, /etc/sudoers как предложено Эриком Леннартссоном. Но если вы ищете программный подход, вы можете вместо этого создать файл в /etc/sudoers.d виде:

Описанный выше метод был предложен Борисом в Ask Ubuntu, и он вообще не требует использования visudo . При использовании с префиксом pacman команды с sudo выглядят так:

Источник

Arch Linux

You are not logged in.

#1 2013-02-10 21:26:19

Pacman refuses to run as non-root user, I don’t agree 🙂

I would like to run pacman as a user with limited rights, so it can not overwrite my personal files. In order for this to work, I would like to change the ownership of all the needed directories for pacman to a new user, and then run pacman as this new user.

Pacman however refuses to run as the root user:

$ pacman -Suy
error: you cannot perform this operation unless you are root.

Is it a good idea to change pacman so it does work as a non-root user? Please also tell me if this is a terrible idea 🙂

#2 2013-02-10 21:30:39

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

How do you intend to update your system, which is almost entirely root-owned? And no, it doesn’t overwrite your personal files unless they somehow belong to an installed package, which they shouldn’t. In case of configs in /etc, pacman just creates new config as .pacnew files to be reviewed by user.

Last edited by kaszak696 (2013-02-10 21:32:31)

‘What can be asserted without evidence can also be dismissed without evidence.’ — Christopher Hitchens
‘There’s no such thing as addiction, there’s only things that you enjoy doing more than life.’ — Doug Stanhope
GitHub Junkyard

#3 2013-02-10 21:33:07

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

What «personal» files do you think pacman is overwriting?

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

#4 2013-02-10 21:50:02

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

This is a terrible idea. Use «pacman -Qii » and look at the bottom of the output. It is smart enough to be told to treat config files differently. Ergo, if they are changed and an update occurs, you will end up with a *.pacnew file. If you remove the package, these files stay unless specifically told to remove them.

#5 2013-02-10 21:50:51

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

How do you intend to update your system, which is almost entirely root-owned?

I would first change the ownership of the files pacman needs access to, then run pacman as that user. I don’t know exactly yet what files they are, but I guess it’s everything below /usr, and the /var/cache/pacman, and probably some other places.

And no, it doesn’t overwrite your personal files unless they somehow belong to an installed package, which they shouldn’t. In case of configs in /etc, pacman just creates new config as .pacnew files to be reviewed by user.

You are absolutely right. This should not happen. But why not make it impossible to happen? Adding the new user, and chowning the needed files/directories only has to be done once, after that the system is more secure.

#6 2013-02-10 21:54:04

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

Chowning everything in /usr is a giant gaping security hole, you are just asking for trouble. Even if not, files in packages are owned by root by default, so i don’t thing chowning would be permament.

Last edited by kaszak696 (2013-02-10 21:58:29)

‘What can be asserted without evidence can also be dismissed without evidence.’ — Christopher Hitchens
‘There’s no such thing as addiction, there’s only things that you enjoy doing more than life.’ — Doug Stanhope
GitHub Junkyard

#7 2013-02-10 21:55:42

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

I don’t know exactly yet what files they are, but I guess it’s everything below /usr, and the /var/cache/pacman, and probably some other places.

This is what is commonly refrerred to in the literature as the «fatal flaw».

Registered Linux User #482438

#8 2013-02-10 21:57:04

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

This is a terrible idea. Use «pacman -Qii » and look at the bottom of the output. It is smart enough to be told to treat config files differently. Ergo, if they are changed and an update occurs, you will end up with a *.pacnew file. If you remove the package, these files stay unless specifically told to remove them.

In order for this to work, pacman still does not need to be run as root, it only needs write access to some files under /etc.

#9 2013-02-11 00:03:48

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

You asked «is this a terrible idea?» and several people have told you, yes, this is a terrible idea, and have even told you why. Yet you persist. Why did you ask for opinions in the first place if you already knew what you were going to do? This begins to look like trolling. Go ahead, do whatever you want. It’s your system.

Last edited by 2ManyDogs (2013-02-11 00:40:36)

How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.

#10 2013-02-11 00:53:11

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

chown all the files pacman needs access to? OK, pacman is the package manager. It manages all packages. All files installed in a fresh install are owned by packages. Pacman needs access to all of them; ALL of them. The only files pacman should not need access to are your personal files which are stored under /home/, and perhaps any files you have independently placed under /opt/.

Pacman needs access to /usr and /var as already noted, but also to /boot . you do get kernel upgrades, right? It also needs access to /bin /sbin and /etc. That only really leaves /opt, /root and /home as real (i.e., on disk) directories. The first of those could well be empty (mine is) and the second can be pretty darn close to empty. The third contains those personal files you don’t want pacman to touch . which it doesn’t anyways.

So you would want to chown your entire root and boot partitions to some user so pacman could have access to everything that it currently has access to but does not have access to what it wouldn’t touch anyways?

EDIT: if my sarcasm burried the point, the point is this new user that you’d create would effectively be a root account. The only differences is that the new user could access your home directory(ies) — that’s it. If this is your end goal, to protect your home partition from pacman (which as an aside has no code that would have it touch your home directory), then you could just unmount your home partition every time you run pacman. This would be far easier . though no less pointless.

Last edited by Trilby (2013-02-11 00:56:31)

«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

Online

#11 2013-02-11 01:19:36

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

I’ve heard a lot of crazy things about package management in my time, but nothing could top the damage done by doing what you are proposing. On my system with

600 packages, pacman is right now managing 131840 files. That’s a lot of things that chowning can break. If you want to keep personal configs, then keep them in your $HOME directory. If they’re system configuration files, pacman will not overwrite them anyway becuase it’s not dumb. If the file has been modified, it will install a `file.pacnew` file next to `file`. Unless you somehow manage to trick pacman into thinking you didn’t modify the file, then you have nothing to worry about. If there is a package that is having configs overwritten, then contact the maintainer, because there’s something missing in their PKGBUILD. (Hell, systemd has a whole infrastructure for user and system configs, with three different places for them so that even dumb package managers con’t break things.)

I thought that the reason for not wanting to run pacman as root was for a good reason, like you want to just download files to a user owned directory, but no. Not even a valid reason.

As other people have said, try running `pacman -Qii

` and looking at the output on the bottom. It will tell you which config files pacman is tracking and which ones have been modified since the package was installed.

Thinkpad T420 | Intel 3000 | systemd
PKGBUILDs I use | pywer AUR helper

Запуск pacman без рута

vadik
imam, тогда и pacman.conf показывайте.

arcanis так тот пакет в основную систему установился? Или так и лежит в /tmp?

Пакет лежит где и лежал

а на попытку установить говорит
error: you cannot perform this operation unless you are root.

тоесть я в отдельном каталоге из под простого юзера собираю макет дерева каталогов и файлов для образа.

imam, про расположение пакета я спрашивал у arcanis-а. А вас просил показать тот pacman.conf, на который ссылаетесь в своей команде установки (есть мысль, но надо проверить).

П.с. только уже все это завтра, пора спать.

vadik
imam, про расположение пакета я спрашивал у arcanis-а. А вас просил показать тот pacman.conf, на который ссылаетесь в своей команде установки (есть мысль, но надо проверить).

комент выше правил ))))

pacman.conf:
[options]
RootDir = /mnt/
DBPath = /mnt/var/lib/pacman/
CacheDir = /mnt/var/cache/pacman/pkg/
LogFile = /mnt/var/log/pacman.log
HoldPkg = pacman glibc
Architecture = auto
CheckSpace
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional

vadik
arcanis так тот пакет в основную систему установился? Или так и лежит в /tmp?

Отучить pacman проверять, для некоторых операций, запущен ли он от рута нельзя — это часть его логики работы определенная в исходниках. Хотя некоторые считают что так делать моветон. А вот почему suid бит на него не действует — интересный вопрос.
Наверное поэтому:

naszar
Отучить pacman проверять, для некоторых операций, запущен ли он от рута нельзя — это часть его логики работы определенная в исходниках.

Значит мне придется править исходник

Источник

Как дать пользователю права root?

Я только что установил Arch. Работает отлично. Я создал нового пользователя, вошел в систему с ним, и теперь я пытаюсь установить несколько вещей с pacman . Но я продолжаю получать сообщение об ошибке: error: you cannot perform this operation unless you are root. я могу pacman нормально работать с root, но есть ли способ разрешить моему новому пользователю выполнять эти действия?

Я попытался войти в root и использовать gpasswd:

gpasswd -a jack root

но это ничего не сделало.

Вы должны прочитать страницу Arch Wiki на sudo .

sudo («Заместитель пользователя делает») позволяет системному администратору делегировать полномочия, чтобы дать определенным пользователям (или группам пользователей) возможность выполнять некоторые (или все) команды от имени пользователя root или другого пользователя, обеспечивая при этом контрольный журнал команд и их аргументы.

Вы можете установить sudo из репозиториев, а затем настроить его, чтобы предоставить вашему пользователю jack доступ к привилегированным командам путем редактирования /etc/sudoers . Убедитесь, что вы делаете это с помощью visudo команды.

Чтобы предоставить пользователю jack полные права суперпользователя, вы должны добавить эту строку:

Обычно я включаю привилегии root для определенной группы. Таким образом, вы можете просто добавить пользователей, которым вы хотите привилегии root, в эту группу.

Редактировать /etc/sudoers с помощью visudo и добавить (или закомментировать):

Затем добавьте своего пользователя в эту группу:

Я могу использовать pacman с root’ом, но есть ли способ разрешить моему новому пользователю выполнять эти действия?

Вы можете создать свой $USER , добавив их в wheel группу в одиночку:

Затем обновите, /etc/sudoers как предложено Эриком Леннартссоном. Но если вы ищете программный подход, вы можете вместо этого создать файл в /etc/sudoers.d виде:

Описанный выше метод был предложен Борисом в Ask Ubuntu, и он вообще не требует использования visudo . При использовании с префиксом pacman команды с sudo выглядят так:

Источник

Arch Linux

You are not logged in.

#1 2013-02-10 21:26:19

Pacman refuses to run as non-root user, I don’t agree 🙂

I would like to run pacman as a user with limited rights, so it can not overwrite my personal files. In order for this to work, I would like to change the ownership of all the needed directories for pacman to a new user, and then run pacman as this new user.

Pacman however refuses to run as the root user:

$ pacman -Suy
error: you cannot perform this operation unless you are root.

Is it a good idea to change pacman so it does work as a non-root user? Please also tell me if this is a terrible idea 🙂

#2 2013-02-10 21:30:39

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

How do you intend to update your system, which is almost entirely root-owned? And no, it doesn’t overwrite your personal files unless they somehow belong to an installed package, which they shouldn’t. In case of configs in /etc, pacman just creates new config as .pacnew files to be reviewed by user.

Last edited by kaszak696 (2013-02-10 21:32:31)

‘What can be asserted without evidence can also be dismissed without evidence.’ — Christopher Hitchens
‘There’s no such thing as addiction, there’s only things that you enjoy doing more than life.’ — Doug Stanhope
GitHub Junkyard

#3 2013-02-10 21:33:07

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

What «personal» files do you think pacman is overwriting?

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

#4 2013-02-10 21:50:02

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

This is a terrible idea. Use «pacman -Qii » and look at the bottom of the output. It is smart enough to be told to treat config files differently. Ergo, if they are changed and an update occurs, you will end up with a *.pacnew file. If you remove the package, these files stay unless specifically told to remove them.

#5 2013-02-10 21:50:51

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

How do you intend to update your system, which is almost entirely root-owned?

I would first change the ownership of the files pacman needs access to, then run pacman as that user. I don’t know exactly yet what files they are, but I guess it’s everything below /usr, and the /var/cache/pacman, and probably some other places.

And no, it doesn’t overwrite your personal files unless they somehow belong to an installed package, which they shouldn’t. In case of configs in /etc, pacman just creates new config as .pacnew files to be reviewed by user.

You are absolutely right. This should not happen. But why not make it impossible to happen? Adding the new user, and chowning the needed files/directories only has to be done once, after that the system is more secure.

#6 2013-02-10 21:54:04

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

Chowning everything in /usr is a giant gaping security hole, you are just asking for trouble. Even if not, files in packages are owned by root by default, so i don’t thing chowning would be permament.

Last edited by kaszak696 (2013-02-10 21:58:29)

‘What can be asserted without evidence can also be dismissed without evidence.’ — Christopher Hitchens
‘There’s no such thing as addiction, there’s only things that you enjoy doing more than life.’ — Doug Stanhope
GitHub Junkyard

#7 2013-02-10 21:55:42

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

I don’t know exactly yet what files they are, but I guess it’s everything below /usr, and the /var/cache/pacman, and probably some other places.

This is what is commonly refrerred to in the literature as the «fatal flaw».

Registered Linux User #482438

#8 2013-02-10 21:57:04

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

This is a terrible idea. Use «pacman -Qii » and look at the bottom of the output. It is smart enough to be told to treat config files differently. Ergo, if they are changed and an update occurs, you will end up with a *.pacnew file. If you remove the package, these files stay unless specifically told to remove them.

In order for this to work, pacman still does not need to be run as root, it only needs write access to some files under /etc.

#9 2013-02-11 00:03:48

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

You asked «is this a terrible idea?» and several people have told you, yes, this is a terrible idea, and have even told you why. Yet you persist. Why did you ask for opinions in the first place if you already knew what you were going to do? This begins to look like trolling. Go ahead, do whatever you want. It’s your system.

Last edited by 2ManyDogs (2013-02-11 00:40:36)

How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.

#10 2013-02-11 00:53:11

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

chown all the files pacman needs access to? OK, pacman is the package manager. It manages all packages. All files installed in a fresh install are owned by packages. Pacman needs access to all of them; ALL of them. The only files pacman should not need access to are your personal files which are stored under /home/, and perhaps any files you have independently placed under /opt/.

Pacman needs access to /usr and /var as already noted, but also to /boot . you do get kernel upgrades, right? It also needs access to /bin /sbin and /etc. That only really leaves /opt, /root and /home as real (i.e., on disk) directories. The first of those could well be empty (mine is) and the second can be pretty darn close to empty. The third contains those personal files you don’t want pacman to touch . which it doesn’t anyways.

So you would want to chown your entire root and boot partitions to some user so pacman could have access to everything that it currently has access to but does not have access to what it wouldn’t touch anyways?

EDIT: if my sarcasm burried the point, the point is this new user that you’d create would effectively be a root account. The only differences is that the new user could access your home directory(ies) — that’s it. If this is your end goal, to protect your home partition from pacman (which as an aside has no code that would have it touch your home directory), then you could just unmount your home partition every time you run pacman. This would be far easier . though no less pointless.

Last edited by Trilby (2013-02-11 00:56:31)

«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

#11 2013-02-11 01:19:36

Re: Pacman refuses to run as non-root user, I don’t agree 🙂

I’ve heard a lot of crazy things about package management in my time, but nothing could top the damage done by doing what you are proposing. On my system with

600 packages, pacman is right now managing 131840 files. That’s a lot of things that chowning can break. If you want to keep personal configs, then keep them in your $HOME directory. If they’re system configuration files, pacman will not overwrite them anyway becuase it’s not dumb. If the file has been modified, it will install a `file.pacnew` file next to `file`. Unless you somehow manage to trick pacman into thinking you didn’t modify the file, then you have nothing to worry about. If there is a package that is having configs overwritten, then contact the maintainer, because there’s something missing in their PKGBUILD. (Hell, systemd has a whole infrastructure for user and system configs, with three different places for them so that even dumb package managers con’t break things.)

I thought that the reason for not wanting to run pacman as root was for a good reason, like you want to just download files to a user owned directory, but no. Not even a valid reason.

As other people have said, try running `pacman -Qii

` and looking at the output on the bottom. It will tell you which config files pacman is tracking and which ones have been modified since the package was installed.

Thinkpad T420 | Intel 3000 | systemd
PKGBUILDs I use | pywer AUR helper

Ответы:

jack ALL=(ALL) ALL

%wheel      ALL=(ALL) ALL

gpasswd -a jack wheel

useradd -Ng wheel --create-home --no-log-init $USER

echo "$USER ALL=(ALL:ALL) NOPASSWD: ALL" | sudo tee /etc/sudoers.d/dont-prompt-$USER-for-password

sudo pacman -S docker docker-compose