This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27
userid in NiChrome does not match with userid of the build machine, leading to permission denied error #65
Comments
Root should definitely not be 700! I wonder why that happened ... |
It shows root as 700 |
My / is 0700 in the repo. I think you need to work your way back to why the original uinit dologin() function is failing. |
So do this: |
I changed cmds/uinit.go to not run the dologin command.
|
well this is a good first step. The permissions on / are wrong and we need to know why. So let's focus on that. |
thienhoang23
changed the title
usb cmd builds an initramfs cpio file with a wrong userid owner and/or wrong permission bits for some programs resulting in permission denied errors when boot
userid in NiChrome does not match with userid of the build machine, leading to permission denied error
Feb 12, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Commit id: 511cf6f
Build Machine Configurations:
Steps for reproduction:
Ctrl-U
Ctrl-Alt-backspace
to exit X11X11 user startup: fork/exec /bbin/uinit: permission denied
The following are results of some further investigation after the above reproduction steps:
ls -a -l /
in the test Chromebook show that /, /go, /lib, /tcz, /usr owned by the user who built the usb stick on the build machine (in this case, userid: 533858, groupid: 5762). Furthermore, the permission on / is 700When I did
chmod 755 /
as a root and ranuinit -login
, I got the following output:Upon entering
ls -a -l /src/github.com/u-root/wingo
, I found cmd_hacks.go and a lot other .go files all have permission 640Upon changing the permissions in all the files in the /src/github.com/u-root/wingo directory tree to 755, running
uinit -login
again generated the following message:uinit -login
again, generate the following message:uinit -login
will not generate the installcommand error anymore.The text was updated successfully, but these errors were encountered: