From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A1CC21381F3 for ; Tue, 2 Jul 2013 16:59:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D21E8E0AEA; Tue, 2 Jul 2013 16:54:57 +0000 (UTC) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by pigeon.gentoo.org (Postfix) with ESMTP id F18A8E0ADB for ; Tue, 2 Jul 2013 16:54:56 +0000 (UTC) Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta09.westchester.pa.mail.comcast.net with comcast id vUPU1l0080EZKEL59UuwmT; Tue, 02 Jul 2013 16:54:56 +0000 Received: from ajax ([24.11.47.14]) by omta01.westchester.pa.mail.comcast.net with comcast id vUuw1l00J0JMh7c3MUuwpv; Tue, 02 Jul 2013 16:54:56 +0000 Date: Tue, 2 Jul 2013 12:54:54 -0400 From: Frank Peters To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: Kernel-3.10 Nvidia Emerge Failure And Other Stuff Message-Id: <20130702125454.161f55f908460aedaabf030a@comcast.net> In-Reply-To: References: <20130701153542.eedab9994a52502121e7e8e5@comcast.net> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; x86_64-unknown-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372784096; bh=6pGb0OqK1b8PBu5iwPHDxq7u7KTWUa9++rVwi0mZ3xw=; h=Received:Received:Date:From:To:Subject:Message-Id:Mime-Version: Content-Type; b=AHNBbrCZdbTft+kWRGXOD6lg1Rf+xlnL6FozJlsZBnTS5JpblTHTdB7Zj61YwO1lM Zur7BqUBKrRBLGFOQ5sV6PzYQYZcVUpwulLIZPGDyPBnhdX241XPGoc9YPkORydnHO Slg55NYxSCgHwaIQy8nzvnLaRl93uF1wiCQClBcs3J8bvubSUT+8mW9AfDvklXpIb8 K1mrJeiY5ufRu/LgKI/OLtDIQlbC02bBMpqirOQAjjkqGtjUeWlxKtpp0GSRem/7VB FYJc4YtKwAfykMbufmgM1TU3gJkksPurXO6oi/Xy3CKF9jW0wqcPMnD1xarpOFkfqH WhGkZk0o1Q7nw== X-Archives-Salt: daea2d39-af65-4d5d-915c-88ee1d622823 X-Archives-Hash: b78841c4f55d468073659c0b179a6080 On Tue, 2 Jul 2013 11:29:47 +0000 (UTC) Duncan <1i5t5.duncan@cox.net> wrote: > > > > First, there is a new kernel option called "Kernel support for scripts > > starting with #!." > > > And no, as you found out it's *NOT* initramfs-only. It's basic kernel > functionality that been assumed for (I guess) decades now. > > But as you may have noticed, openrc, gentoo's default init system, uses > #!/sbin/runscript to point to runscript (part of openrc), as its script > interpreter, and it may well be that turning off kernel shebang support > screwed you up that way. > I am entirely sure what is happening with this kernel "#!" option. My boot scripts are very simple and customized for my specific machine (as opposed to having a complex set of highly generalized scripts that attempt to account for every possible situation). Basically, once the kernel loads itself, it invokes the init binary which then uses parameters in /etc/inittab to invoke appropriate scripts (or other binaries). From my inittab, only a single bash script is called for system initialization and this bash script runs just fine _without_ the kernel "#!" option. However, after this bash initialization script executes, the console login process then begins. My inittab contains this line for login: agetty -n -l /sbin/autologin 38400 tty1 Now /sbin/autologin is another bash script and it is *only at this point* that the boot fails to complete without the kernel "#!" option. IOW, my bash boot scripts succeed but the bash autologin script fails w/o the kernel "#!" option. I suspect, although I have not tested it, that if I substitute a normal binary login (i.e. /bin/login) for the bash /sbin/autologin then the boot will be completely successful w/o the kernel "#!" option. So what does the "#!" option accomplish? Does it allow the kernel to effect redirection based on "#!?" This should only be necessary if bash itself is not invoked, but in boot-up based on init and inittab, bash, I believe, is automatically invoked for all scripts. But yet the agetty program, after boot-up is essentially complete, fails to execute the bash script in its parameter list. At this point is it agetty, or the kernel, that is responsible for executing the autologin script? I need to study this more. Frank Peters