From: Herbert Poetzl <herbert@13thfloor.at>
To: harry_b@mm.st
Cc: James Bourne <jbourne@hardrock.org>, linux-kernel@vger.kernel.org
Subject: Re: initrd missing TTY
Date: Tue, 7 Sep 2004 17:39:36 +0200 [thread overview]
Message-ID: <20040907153936.GD19354@MAIL.13thfloor.at> (raw)
In-Reply-To: <1B1B394B2B14C4B2DA3856C1@[192.168.1.247]>
On Wed, Sep 01, 2004 at 03:59:49PM +0200, harry_b@mm.st wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> - --On Wednesday, September 01, 2004 07:53:13 -0600 James Bourne
> <jbourne@hardrock.org> wrote:
>
> >> I am not sure where to ask this question but I hope this is the right
> >> place.
> >>
> >> I am trying to setup an encrypted root partition where the key is stored
> >> gpg-encrypted on an USB memorystick. So far everything works quite
> >> nicely but I fail to get a TTY working in the initial RAM disk.
> >>
> >> All I get is gpg complaining:
> >> gpg: cannot open '/dev/tty': No such device or address
sounds like the tty driver is either not loaded or
not compiled in at all ... but maybe I'm completely
wrong here ...
HTH,
Herbert
> >> Any idea what's necessary to get a TTY within the RAM disk? Or is there
> >> any other way to pass a passphrase to gpg without displaying it on the
> >> screen? (yes, I know about the --no-tty and --passphrase-fd options but
> >> when I use /dev/console the passphrase is visible)
> >
> > make sure /dev/tty exists on your initrd image. You can created this by
> > mounting your initrd image, changing to the dev directory on that image
> > and running mknod -m 644 tty c 5 0.
>
> I have all devices available. Right now I have udev running but I also
> tried a fully populated static /dev directory.
>
> My current tty looks quite normal like
> crw-rw-rw- 1 0 0 5, 0 Sep 1 12:10 /dev/tty
> and tty1, tty2 have
> crw-rw-rw- 1 0 0 4, 1 Sep 1 12:10 /dev/tty1
> crw-rw-rw- 1 0 0 4, 2 Sep 1 12:10 /dev/tty2
> ...
>
> Harry
>
> - --
>
> 1024D/40F14012 18F3 736A 4080 303C E61E 2E72 7E05 1F6E 40F1 4012
>
> - -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GIT/S dx s: a C++ ULS++++$ P+++ L+++$ !E W++ N+ o? K? !w !O !M
> V PS+ PE Y? PGP+++ t+ 5-- X+ R+ !tv b++ DI++ D+ G e* h r++ y++
> - ------END GEEK CODE BLOCK------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
>
> iD8DBQFBNdXVfgUfbkDxQBIRApz2AKCfReZz9d7a7XWKXqYTVG25K4pShQCfQ6jT
> ndXd09GQGN+yLNp1sizUotM=
> =QK72
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2004-09-07 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 13:07 harry_b
[not found] ` <Pine.LNX.4.58.0409010749510.6483@rio.clgy.hardrock.org>
2004-09-01 13:59 ` harry_b
2004-09-07 15:39 ` Herbert Poetzl [this message]
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=20040907153936.GD19354@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=harry_b@mm.st \
--cc=jbourne@hardrock.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®