Summary: | clean api for accessing stdin from init scripts needed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | roy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | test input |
Description
SpanKY
![]() Created attachment 147301 [details]
test input
This script reads user input. It works in the boot and default runlevels during a normal rc, a full system boot and a single run.
Maybe cryptsetup is doing it's own voodoo on stdin? Caveat - I have console=tty1 on the kernel commandline which may affect this.
check out 1.0.6-dm-crypt-start.sh in the files/ dir of cryptsetup ... this was working with baselayout-2.x and baselayout-1.x, but the fds it has hard coded may have changed ... It's forcing input from /dev/console, which could be the cause. I don't have the time right now to setup a test env to verify. looks like default pinentry program is broken ... it doesnt fallback to curses properly |