Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Operating System
No login screen: mistakes with permissions and deleting /usr/bin/login
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Biogeek" data-source="post: 798506" data-attributes="member: 85226"><p>I have not been able to find a case close enough to mine to be of use, so I'm posting here in the hopes that someone might have some internal understanding of the system and be able to help...</p><p></p><p>So I recently got a MacBook with an intel processor and 10.5.5 (I believe it is 10.5.5, but I can only be certain that it is 10.5) installed (having previously used an eMac with 10.4.11 and a PPC processor), but it went through a university's tech department and had some excess baggage that I wanted to get rid of. I managed to remove most of it, rename my home folder and reshape the users to a more sensible configuration, but every time I deleted, moved, or modified a file in Applications (and some other folders), it required that I put in the administrator's password, which got rather irritating.</p><p></p><p>Having gone into the info of folders previously and set the desired permissions ("Read & Write") and applied to all enclosed items with success, I attempted to do the same for the entirety of my hard drive. However, afterwards (almost half an hour later), I was unable to delete, move, or modify any files at all, and a number of programs did not work (including Terminal, which spat out a terrible three-line error involving the failure of login, and DiskUtility, which proclaimed that it had a failure on exit when I attempted to verify disk permissions). As I was probably justified in worrying about the possibility of not being able to log in again, I enabled the root user and logged out, and into root. From root, the programs worked, and I was able to run verify and repair disk permissions—but this was projected to take over 5 days, so, after giving it a good 7 hours, I switched to Terminal and repaired them through "applejack", which took under an hour.</p><p></p><p>I logged back into my normal admin account (I only recently discovered that it is recommended that one as inexperienced as I am should not routinely administer the computer), and attempted to resume sorting through and getting rid of excess files. However, the permissions were still wacky, and I while I was able to delete things, I was unable to move them, even to transfer over a firewire cable (that may seem random but it makes sense in context). So, following some advice I found on other forums that applied to the earlier problems with Terminal, now empowered with the knowledge of how to find it, I deleted /usr/bin/login... and that led me to my current state. I am unable to reach the login screen, and the computer loads for about a minute and a half before restarting and resuming the process. I can start up in single-user mode, but have been unable to boot from any install discs. In single user mode, I employed applejack yet again, and after a couple of tries, succeeded (really only through increasing patience on each attempt) in getting it to run through repairing the disk, repairing permissions (which threw several errors in the process:</p><p>kextd[206] <Error>: bootstrap_check_in(): Unkown service name</p><p>configd[231]: allow_crash_reports bootstrap_look_up() failed: Unknown service name</p><p>and the most irritating,</p><p>(username) configd[231]: InterfaceNamer: timed out waiting for IOKit to quiesce</p><p>after which many, many dots were printed before it moved on), and so on. However, doing this (even several times) has not helped at all, and I'm still stuck with the normal login loop and the single-user mode.</p><p>Any suggestions/insight?</p></blockquote><p></p>
[QUOTE="Biogeek, post: 798506, member: 85226"] I have not been able to find a case close enough to mine to be of use, so I'm posting here in the hopes that someone might have some internal understanding of the system and be able to help... So I recently got a MacBook with an intel processor and 10.5.5 (I believe it is 10.5.5, but I can only be certain that it is 10.5) installed (having previously used an eMac with 10.4.11 and a PPC processor), but it went through a university's tech department and had some excess baggage that I wanted to get rid of. I managed to remove most of it, rename my home folder and reshape the users to a more sensible configuration, but every time I deleted, moved, or modified a file in Applications (and some other folders), it required that I put in the administrator's password, which got rather irritating. Having gone into the info of folders previously and set the desired permissions ("Read & Write") and applied to all enclosed items with success, I attempted to do the same for the entirety of my hard drive. However, afterwards (almost half an hour later), I was unable to delete, move, or modify any files at all, and a number of programs did not work (including Terminal, which spat out a terrible three-line error involving the failure of login, and DiskUtility, which proclaimed that it had a failure on exit when I attempted to verify disk permissions). As I was probably justified in worrying about the possibility of not being able to log in again, I enabled the root user and logged out, and into root. From root, the programs worked, and I was able to run verify and repair disk permissions—but this was projected to take over 5 days, so, after giving it a good 7 hours, I switched to Terminal and repaired them through "applejack", which took under an hour. I logged back into my normal admin account (I only recently discovered that it is recommended that one as inexperienced as I am should not routinely administer the computer), and attempted to resume sorting through and getting rid of excess files. However, the permissions were still wacky, and I while I was able to delete things, I was unable to move them, even to transfer over a firewire cable (that may seem random but it makes sense in context). So, following some advice I found on other forums that applied to the earlier problems with Terminal, now empowered with the knowledge of how to find it, I deleted /usr/bin/login... and that led me to my current state. I am unable to reach the login screen, and the computer loads for about a minute and a half before restarting and resuming the process. I can start up in single-user mode, but have been unable to boot from any install discs. In single user mode, I employed applejack yet again, and after a couple of tries, succeeded (really only through increasing patience on each attempt) in getting it to run through repairing the disk, repairing permissions (which threw several errors in the process: kextd[206] <Error>: bootstrap_check_in(): Unkown service name configd[231]: allow_crash_reports bootstrap_look_up() failed: Unknown service name and the most irritating, (username) configd[231]: InterfaceNamer: timed out waiting for IOKit to quiesce after which many, many dots were printed before it moved on), and so on. However, doing this (even several times) has not helped at all, and I'm still stuck with the normal login loop and the single-user mode. Any suggestions/insight? [/QUOTE]
Verification
Name this item. 🏈
Post reply
Forums
Apple Computing Products:
macOS - Operating System
No login screen: mistakes with permissions and deleting /usr/bin/login
Top