![]() If you leave the laptop unattended for a moment. USB, and you password protect grub, someone could easily get root access So, even if you lock down the bios to not allow booting from CD-Rom or The grub boot loader generates a boot entry for rescue mode. Having been in this business for 25 years, I cannot help but entirely disagree with the Michael Biebl's argument in message #31 in that thread:Ĭonsider this: You have a laptop with a locked root account. There was a discussion on the Debian bug report about this very problem, and, as far as understand, this was decided a feature and not a bug, which I judge to have been rather a mistake. All modern journaling filesystems like ext4, xfs and btrfs recover themselves quickly (a few seconds for a journal check at most, if synced before the reset), and you'll be all set. In case the exec fails, simply reset the machine and let it boot normally. A reboot is recommended, as (although very rarely) init may be passed additional parameters during a normal boot, and that we did not do. sudo reboot-you should have gotten your sudo privilege back. The system will most likely continue to boot normally (no recovery mode). Sync just in case anything goes wrong, to save all changes to disk, and the exec to replace the shell with the real init (which can be systemd, upstart or System V init, but it's always called /sbin/init). So the next two command you must issue are: sync reboot, halt or poweroff won't work, and exit from the shell will lead to a kernel panic, as the PID 1 process is not expected to just exit. You cannot shutdown or reboot the system cleanly at this point. In case you get a "command not found" error, use /sbin/usermod and /bin/id. Confirm with id -a YOURUSERID that you've got your sudo membership back.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |