Permission denied from /boot
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
when I typed less /boot/grub2/grub.cfg in tty2 i get permission denied an I did su - password and that did not work I am in fedora 20 64 bit 
fedora boot grub2 tty less
asked Mar 7 at 18:08
cinemassacres
32
add a comment |Â
up vote
0
down vote
favorite
when I typed less /boot/grub2/grub.cfg in tty2 i get permission denied an I did su - password and that did not work I am in fedora 20 64 bit
fedora boot grub2 tty less
asked Mar 7 at 18:08
cinemassacres
32
The$should indicate that the command was run a regular user.
– Christopher
Mar 7 at 18:10
Could you please expand upon "that did not work" - did you receive the same permission denied error? Was your password not accepted? It's difficult to answer without the full details.
– aliceinpalth
Mar 7 at 18:11
@aliceinpalth Christopher helped me I was not in root
– cinemassacres
Mar 7 at 18:13
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
when I typed less /boot/grub2/grub.cfg in tty2 i get permission denied an I did su - password and that did not work I am in fedora 20 64 bit
fedora boot grub2 tty less
asked Mar 7 at 18:08
cinemassacres
32
when I typed less /boot/grub2/grub.cfg in tty2 i get permission denied an I did su - password and that did not work I am in fedora 20 64 bit
fedora boot grub2 tty less
asked Mar 7 at 18:08
cinemassacres
32
asked Mar 7 at 18:08
cinemassacres
32
asked Mar 7 at 18:08
cinemassacres
32
asked Mar 7 at 18:08
cinemassacres
32
32
The$should indicate that the command was run a regular user.
– Christopher
Mar 7 at 18:10
Could you please expand upon "that did not work" - did you receive the same permission denied error? Was your password not accepted? It's difficult to answer without the full details.
– aliceinpalth
Mar 7 at 18:11
@aliceinpalth Christopher helped me I was not in root
– cinemassacres
Mar 7 at 18:13
add a comment |Â
The$should indicate that the command was run a regular user.
– Christopher
Mar 7 at 18:10
Could you please expand upon "that did not work" - did you receive the same permission denied error? Was your password not accepted? It's difficult to answer without the full details.
– aliceinpalth
Mar 7 at 18:11
@aliceinpalth Christopher helped me I was not in root
– cinemassacres
Mar 7 at 18:13
The
$ should indicate that the command was run a regular user.– Christopher
Mar 7 at 18:10
The
$ should indicate that the command was run a regular user.– Christopher
Mar 7 at 18:10
Could you please expand upon "that did not work" - did you receive the same permission denied error? Was your password not accepted? It's difficult to answer without the full details.
– aliceinpalth
Mar 7 at 18:11
Could you please expand upon "that did not work" - did you receive the same permission denied error? Was your password not accepted? It's difficult to answer without the full details.
– aliceinpalth
Mar 7 at 18:11
@aliceinpalth Christopher helped me I was not in root
– cinemassacres
Mar 7 at 18:13
@aliceinpalth Christopher helped me I was not in root
– cinemassacres
Mar 7 at 18:13
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You failed to change into the root user.
To view that file, you must have root privileges.
You get that by using sudo:
sudo less /boot/grub2/grub.cfg
assuming sudo has been set up and that you have permission to use it. The password that sudo asks for is your unprivileged user's password, not the root password.
If sudo has not been set up, then change into root with
su -
This will also ask for a password, but in this case it's the root account's password.
Once you are root, you should configure your other user so that it can use sudo. You do this using visudo. See the sudo and visudo (and sudoers) manuals.
answered Mar 7 at 18:14
Kusalananda
103k13202318
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You failed to change into the root user.
To view that file, you must have root privileges.
You get that by using sudo:
sudo less /boot/grub2/grub.cfg
assuming sudo has been set up and that you have permission to use it. The password that sudo asks for is your unprivileged user's password, not the root password.
If sudo has not been set up, then change into root with
su -
This will also ask for a password, but in this case it's the root account's password.
Once you are root, you should configure your other user so that it can use sudo. You do this using visudo. See the sudo and visudo (and sudoers) manuals.
answered Mar 7 at 18:14
Kusalananda
103k13202318
add a comment |Â
up vote
2
down vote
accepted
You failed to change into the root user.
To view that file, you must have root privileges.
You get that by using sudo:
sudo less /boot/grub2/grub.cfg
assuming sudo has been set up and that you have permission to use it. The password that sudo asks for is your unprivileged user's password, not the root password.
If sudo has not been set up, then change into root with
su -
This will also ask for a password, but in this case it's the root account's password.
Once you are root, you should configure your other user so that it can use sudo. You do this using visudo. See the sudo and visudo (and sudoers) manuals.
answered Mar 7 at 18:14
Kusalananda
103k13202318
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You failed to change into the root user.
To view that file, you must have root privileges.
You get that by using sudo:
sudo less /boot/grub2/grub.cfg
assuming sudo has been set up and that you have permission to use it. The password that sudo asks for is your unprivileged user's password, not the root password.
If sudo has not been set up, then change into root with
su -
This will also ask for a password, but in this case it's the root account's password.
Once you are root, you should configure your other user so that it can use sudo. You do this using visudo. See the sudo and visudo (and sudoers) manuals.
answered Mar 7 at 18:14
Kusalananda
103k13202318
You failed to change into the root user.
To view that file, you must have root privileges.
You get that by using sudo:
sudo less /boot/grub2/grub.cfg
assuming sudo has been set up and that you have permission to use it. The password that sudo asks for is your unprivileged user's password, not the root password.
If sudo has not been set up, then change into root with
su -
This will also ask for a password, but in this case it's the root account's password.
Once you are root, you should configure your other user so that it can use sudo. You do this using visudo. See the sudo and visudo (and sudoers) manuals.
answered Mar 7 at 18:14
Kusalananda
103k13202318
edited Mar 7 at 18:52
answered Mar 7 at 18:14
Kusalananda
103k13202318
answered Mar 7 at 18:14
Kusalananda
103k13202318
answered Mar 7 at 18:14
Kusalananda
103k13202318
103k13202318
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428816%2fpermission-denied-from-boot%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The
$should indicate that the command was run a regular user.– Christopher
Mar 7 at 18:10
Could you please expand upon "that did not work" - did you receive the same permission denied error? Was your password not accepted? It's difficult to answer without the full details.
– aliceinpalth
Mar 7 at 18:11
@aliceinpalth Christopher helped me I was not in root
– cinemassacres
Mar 7 at 18:13