Bug 561231

Summary:	Skipping cryptodisk mounting in parallel boot causes no hostname set
Product:	[openSUSE] openSUSE 11.2	Reporter:	B. B. <bradavka>
Component:	Other	Assignee:	Dr. Werner Fink <werner>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	lnussel, werner
Version:	Final
Target Milestone:	---
Hardware:	PC
OS:	openSUSE 11.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description B. B. 2009-12-06 22:33:01 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090410 SUSE/1.1.16-1.1 SeaMonkey/1.1.16

I switched to opensuse 11.2 and continue to use cryptopartition mounted in boot.crypto.

I don't want to mount the partition every time I use the computer. In previous versions of opensuse I used to press ^C at password promt to skip mounting of the partition. In 11.2 ^C works if parallel boot is set to no. If parallel boot is set to yes, the ^C prevented the script boot.localnet from running and the machine ends with '(none') hostname, that prevents other services from running.

Is it possible to handle the ^C in parallel boot process? I know I can giv bad/empty password several times and the boot finish ok, but the ^C is faster.

Reproducible: Always

Steps to Reproduce:
1. create cryptopartion mounted in boot.crypto
2. check that you have RUN_PARALLEL=yes in /etc/sysconfig/boot
3. boot the PC and press ^C at crypto partition password prompt
Actual Results:  
The boot process finish, but the script boot.localnet (and maybe others) is not run, so the hostname is set to '(none)'

Expected Results:  
^C should kill only the waiting interactive process, other boot scripts should be finished

Comment 1 Ruediger Oertel 2009-12-08 11:21:37 UTC

trying maintainer of boot.crypto

Comment 2 Ludwig Nussel 2009-12-08 12:12:36 UTC

I don't know what I could do in boot.crypto against this. My advise would be to use ctrl-d at the prompt instead which makes boot.crypto exit gracefully.

Comment 3 Dr. Werner Fink 2009-12-11 16:54:59 UTC

I'm not maintainer of boot.crypto

Comment 4 Ludwig Nussel 2009-12-14 07:52:23 UTC

Yeah, and I as maintainer of boot.crypto can't fix the problem :) The bug seems to be that if the user presses ctrl-c at the cryptsetup prompt not only boot.crypo is terminated but also other, unrelated scripts which could indicate a problem e.g. in startpar.

Comment 5 Dr. Werner Fink 2009-12-14 08:35:13 UTC

Ctrl-C is not supported and it will not be supported
The correct answer is EOF aka Ctrl-D if the prompt
is visible.  Beside this boot.crypto is nont handled by
startpar as startpar handled boot.crypto as interactive
script.  And hopefully boot.crypto reconnects to the
physical device as provided by the environment variable
REDIRECT then it should be easy to use modify to stty
command ... nevertheless we're talking about /dev/console
that is we do not have any controlling terminal and
therefore without any controlling terminal Ctrl-C will
not work.