Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 99703 - Baselayout- 1.11.13 gives weird boot script messages
Summary: Baselayout- 1.11.13 gives weird boot script messages
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-20 10:47 UTC by Stig Mogensen
Modified: 2005-08-02 00:30 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
output from rc-update show boot (rcupdate.txt,1.73 KB, text/plain)
2005-07-20 10:47 UTC, Stig Mogensen
Details
Output from dmesg (bootmessages.txt,12.22 KB, text/plain)
2005-07-20 10:48 UTC, Stig Mogensen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stig Mogensen 2005-07-20 10:47:03 UTC
I upgraded to the new stable baselayout-1.1.13 from the previous stable version.
Ran etc-update as requested, and now I can't boot. Whenever a script is starting
up, say alsasound, bootmisc, or clock, I get the errors;

Command not found2
Command not found6
Command not found8
Command not found11
Command not found13
Command not found18
Command not found38
Command not found40 

This is happens also, if I run
/etc/init.d/alsasoun stop
and
/etc.initd./alsasound stop

or any other bootscript.



Reproducible: Always
Steps to Reproduce:
1. It happens on boot - every time
2. It happens on shutdown - every time
3. It happens on /etc/init.d/<bootscript> start and /etc/init.d/<bootscript> stop
Comment 1 Stig Mogensen 2005-07-20 10:47:54 UTC
Created attachment 63904 [details]
output from rc-update show boot
Comment 2 Stig Mogensen 2005-07-20 10:48:36 UTC
Created attachment 63905 [details]
Output from dmesg
Comment 3 SpanKY gentoo-dev 2005-07-20 17:50:12 UTC
sounds like maybe an error in one of your config files

if you run `depscan.sh` do you get the error ?
Comment 4 Stig Mogensen 2005-07-21 00:23:34 UTC
(In reply to comment #3)
> sounds like maybe an error in one of your config files
> 
> if you run `depscan.sh` do you get the error ?

Yes.....depscan.sh fills up my screen with "Command not found2, Command not
found6, ..." and so on. 
Comment 5 Martin Schlemmer (RETIRED) gentoo-dev 2005-07-21 01:46:44 UTC
Edit /sbin/runscript.sh, add an ' -x' to the end of the first line
(#!/bin/bash), and then start/stop something that fails, and attach the output here.
Comment 6 Stig Mogensen 2005-07-21 02:56:27 UTC
(In reply to comment #5)
> Edit /sbin/runscript.sh, add an ' -x' to the end of the first line
> (#!/bin/bash), and then start/stop something that fails, and attach the output
here.
> 

Did that. I don't think it did much good though. Here's what happened;

/etc/init.d/ntpd stop
: invalid option
Usage: /bin/bash [GNU long option] [option]...
       /bin/bash [GNU long option] [scriptfile]
GNU long options:

and so it continues, with a list of options.  
Comment 7 SpanKY gentoo-dev 2005-07-21 07:04:07 UTC
edit depscan.sh and add the -x to the first line
Comment 8 Stig Mogensen 2005-07-22 03:08:24 UTC
(In reply to comment #7)
> edit depscan.sh and add the -x to the first line

Same error. But more fatal.....nothing in Gentoo works, with an andded '-x' in
depscan.sh
Comment 9 SpanKY gentoo-dev 2005-07-22 06:57:12 UTC
so edit depscan.sh and put this on the 2nd line:
set -x
Comment 10 Martin Schlemmer (RETIRED) gentoo-dev 2005-07-26 02:45:52 UTC
Attach you modified /sbin/runscript.sh here please.
Comment 11 Martin Schlemmer (RETIRED) gentoo-dev 2005-08-02 00:30:06 UTC
Reopen if you have time to respond, thanks.