Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#19311 - [initscripts] inittab uses bashism who prevents slim to start when /bin/sh is not bash
Attached to Project:
Arch Linux
Opened by Benoit Izac (benizac) - Saturday, 01 May 2010, 13:21 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 04 May 2010, 17:38 GMT
Opened by Benoit Izac (benizac) - Saturday, 01 May 2010, 13:21 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 04 May 2010, 17:38 GMT
|
DetailsAfter replacing /bin/sh by /bin/dash insteed of /bin/bash, slim doesn't start anymore.
I have the following errors: /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number /bin/sh: Syntax error: Bad fd number INIT: Id "x" respawning too fast: disabled for 5 minutes I /etc/inittab the syntax is: x:5:respawn:/usr/bin/slim >& /dev/null which is a bashism and should be written: x:5:respawn:/usr/bin/slim >/dev/null 2>&1 to be POSIX compliant. |
This task depends upon
Comment by Dan McGee (toofishes) -
Tuesday, 04 May 2010, 17:37 GMT
Easy enough to fix, I pushed this small change.