Hi, Anthony DeRobertis wrote:
> ctrl-c probably doesn't work due to the terminal not being set up (wild
> guess). Maybe you could make it work with "stty intr ^C"
>
Basically, it doesn't work because there's no controlling TTY set.
Opening a TTY usually sets the controlling TTY, but the linuxrc
co
Hi, Anthony DeRobertis wrote:
> ctrl-c probably doesn't work due to the terminal not being set up (wild
> guess). Maybe you could make it work with "stty intr ^C"
>
Basically, it doesn't work because there's no controlling TTY set.
Opening a TTY usually sets the controlling TTY, but the linuxrc
co
On Tue, 2003-12-16 at 11:22, e-bone wrote:
> I've tried:
> 1
> calling cryptcat in the linuxrc script. this works, but then i can't
> enter passwords at the tty ! apparently signals (ctrl-c) cannot be caught in
> the linuxrc script either ? i tried a script that catches this signal
> then asked fo
On Tue, 2003-12-16 at 11:22, e-bone wrote:
> I've tried:
> 1
> calling cryptcat in the linuxrc script. this works, but then i can't
> enter passwords at the tty ! apparently signals (ctrl-c) cannot be caught in
> the linuxrc script either ? i tried a script that catches this signal
> then asked fo
Hi,
this question does not pertain specifically to debian-boot,
but it deals with things which i think the readers of this list have a
particular knowledge of, so here goes:
My main root partition is /dev/hda2, and it is encrypted via ppdd.
I have a "maintenance"/"fake" root partition at /dev/hda6
Hi,
this question does not pertain specifically to debian-boot,
but it deals with things which i think the readers of this list have a
particular knowledge of, so here goes:
My main root partition is /dev/hda2, and it is encrypted via ppdd.
I have a "maintenance"/"fake" root partition at /dev/hda6
6 matches
Mail list logo
