From: jidanni@jidanni.org
To: grub-devel@gnu.org
Cc: bug-grub@gnu.org
Subject: forgot passwd, cannot login, [rd]init=/bin/sh don't work
Date: Thu, 09 Oct 2008 05:40:32 +0800 [thread overview]
Message-ID: <87skr6935b.fsf_-_@jidanni.org> (raw)
In-Reply-To: 20081007095652.GD7127@fencepost.gnu.org
Gentlemen, last time I forgot my password and couldn't log into my
machine here on my far away rural mountaintop, I ended up digging up an
old Debian "potato" CDROM and installing it into some free space on my
disk, from which I could edit /etc/passwd and zero out the password.
These days that would no longer necessarily work, see man mkfs.ext3 -I.
> Presuming Linux, you can add "init=/bin/sh" to the kernel command line. This
> will give you a shell without asking for a password. From this shell you can
> edit your password file.
Didn't work.
>Initrd scripts might change everything.
OK, I then tried linux-doc-2.6.26/Documentation/kernel-parameters.txt.gz:
rdinit= [KNL]
Format: <full_path>
Run specified binary instead of /init from the ramdisk,
used for early userspace startup. See initrd.
So in grub2 I chose "e" to edit, and changed the lines to
linux /boot/vmlinuz-2.6.26-1-686 root=UUID=... rdinit=/bin/sh
initrd /boot/initrd.img-2.6.26-1-686
hit ESC then RET, and alas it was like I didn't type anything at
all but just hit RET, booting proceeded as usual, and /proc/cmdline
shows that my changes to that command line were thrown away.
next parent reply other threads:[~2008-10-08 21:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081007095652.GD7127@fencepost.gnu.org>
2008-10-08 21:40 ` jidanni [this message]
2008-10-08 23:09 ` forgot passwd, cannot login, [rd]init=/bin/sh don't work walt
2008-10-09 18:19 ` Niels Böhm
2008-10-11 2:46 ` jidanni
2008-10-15 18:41 ` jidanni
2008-12-26 18:57 ` [PATCH] menu.c clearer instructions jidanni
2008-12-26 19:48 ` cmdline.c: ESC at any time exits: only mentioned once jidanni
2009-01-24 20:11 ` Vesa Jääskeläinen
2009-01-25 9:42 ` Carles Pina i Estany
2008-12-26 20:46 ` [PATCH] menu.c clearer instructions Carles Pina i Estany
2008-12-26 22:54 ` jidanni
2008-12-27 6:53 ` Pavel Roskin
2008-12-27 22:49 ` jidanni
2008-12-30 1:09 ` jidanni
2008-12-30 8:12 ` Jerone Young
2009-01-01 0:18 ` jidanni
2009-01-05 5:31 ` Jerone Young
2009-01-05 23:53 ` jidanni
2009-01-23 20:05 ` patches not acted upon jidanni
2009-01-24 20:02 ` Vesa Jääskeläinen
2009-01-25 3:24 ` Jerone Young
2009-01-26 19:27 ` jidanni
2008-12-26 19:10 ` [semi-PATCH] grub.texi: emergency booting without root passwd jidanni
2008-12-26 20:42 ` Carles Pina i Estany
2009-01-24 20:06 ` Vesa Jääskeläinen
[not found] <4728c15d0810081751i57cfe910x9aa321f25f89495a@mail.gmail.com>
2008-10-09 1:09 ` forgot passwd, cannot login, [rd]init=/bin/sh don't work jidanni
2008-10-17 12:26 James Shewey
2008-10-18 3:44 ` Cameron Braid
2008-10-18 12:20 ` Steven Trotter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skr6935b.fsf_-_@jidanni.org \
--to=jidanni@jidanni.org \
--cc=bug-grub@gnu.org \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.