Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well, you are not the first in the history of computing to do this.
You have borked the file permissions - so you will be spending quite sometime in the root account fixing the problems.
You cannot su to root because the su program now only allows the root user to execute it.
It is possible to bring the system back to life or you do a reinstall.
If you want a lesson in permissions that will last a lifetime, but take a day or so to do I would opt for the 'system back to life' approach.
Some people make a permission script after they do this - and I do think it is not a bad idea, others try to nerf chown -R, but often after doing this you tend to make sure you pause and reread the command before entering commands that contain recursion especially rm.
I like banging my head against walls. So I would opt for the 'system back to life' option. However, since I have no backup or other linux box to compare to (slapping self) I will be reinstalling Slack. And then preparing a script for the future.
You are correct, Zention. There is a long heritage of chmod/chown mishaps. I was unable to find a time it happened and the person did not opt for a reinstall.
Distribution: O.A.M. (Overmonitoring Address Matrix) Release 2.2 with 2120 Patch
Posts: 37
Rep:
Can't you boot into single-user mode (run-level 1)?
Or just boot with a live cd, mount your partion and
do your repair that way. Let us know how it works
out for you. Good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.