General TC > General TC Talk
sudo'd out
jpeters:
--- Quote from: mikshaw on February 11, 2009, 08:28:08 AM ---I think it really helps to use a file manager which has the ability to display the file permissions at all times. A quick glance will let you know what needs to be done if you have a permissions-related problem. Personally, mc with mode:3 (or 4,5,6,or 7) as part of the file listing mode is great
--- End quote ---
For the uninitiated, one is still faced with the problem of what to do with them. For example, I quickly tried out "find . | cpio -o -H newc | gzip -9 > tinycore.gz " from files unpacked in /tmp, only to receive errors about not having permission to read /usr/bin/sudo and vsudo files....which are ---s--x--x 1 root root. I didn't spend much time looking at it, but didn't notice any mention of this issue where the instructions were listed. Not knowing what execute means for a dir vs a file can become a crisis fairly quickly...
mikshaw:
There are several files in the base system which are rightly not readable by anyone but root, so when creating a new tinycore, it should be done only as root.
jpeters:
--- Quote from: mikshaw on February 11, 2009, 08:12:41 PM ---There are several files in the base system which are rightly not readable by anyone but root, so when creating a new tinycore, it should be done only as root.
--- End quote ---
Last night, even in root I got read permission errors for /usr/bin/sudo and vsudo with "find . | cpio -o -H newc | gzip -9 > tinycore.gz" . Tonight, it worked perfectly. Either there's an astrological aspect required (i.e., the planets have to be aligned correctly to get permission) or it just needed your blessing. If it's the latter, I hope you'll be available for the next remaster......
mikshaw:
Considering file permissions don't limit what root can do I have to guess that the issue is something else. Are you sure it's a "read permission" error, and not a "read" error? If it's the latter, it might be a corrupted file.
jpeters:
--- Quote from: mikshaw on February 12, 2009, 06:30:24 AM ---Considering file permissions don't limit what root can do I have to guess that the issue is something else. Are you sure it's a "read permission" error, and not a "read" error? If it's the latter, it might be a corrupted file.
--- End quote ---
I reproduced the error. If I use "sudo find . | cpio -o -H newc | gzip -9 > tinycore.gz" I get:
--- Code: ---cpio: ./usr/sbin/visudo: Cannot open: Permission denied
cpio: ./usr/bin/sudo: Cannot open: Permission denied
--- End code ---
If I go into root with sudo su first and run the command, it works fine. I thought they were the same thing, but guess not.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version