[Pkg-kbd-devel] Bug#549317: sed: can't read /etc/inittab: No such file or directory

Michael Schutte michi at uiae.at
Sun Oct 4 10:55:39 UTC 2009


tag 549317 + patch
thanks

Hi Jussi!

On Fri, Oct 02, 2009 at 03:05:53PM +0300, Jussi Myllykoski wrote:
> I get this message on boot:
> 
> ....
> Setting console screen modes
> sed: can't read /etc/inittab: No such file or directory
> ....
> 
> This is on a system where sysvinit has been replaced with upstart,
> so if I understand correctly the data that used to be in /etc/inittab
> is now in several files found at /etc/init/
> 
> This isn't a showstopper by any means, just something that I thought
> might be good to bring to your attention (if it isn't already).

Thanks a lot for your report.  Init systems seem to be kbd’s greatest
enemy :-)

May I ask you to apply the attached patch to your local copy of
/etc/init.d/kbd and confirm that it works?  The solution isn’t perfect
since it’s theoretically possible that gettys are started from files
other than /etc/init/tty*.conf, but I guess it is good enough for most
cases.

Cheers,
-- 
Michael Schutte <michi at uiae.at>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 549317.patch
Type: text/x-diff
Size: 668 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-kbd-devel/attachments/20091004/e4f9ac6a/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-kbd-devel/attachments/20091004/e4f9ac6a/attachment.pgp>


More information about the Pkg-kbd-devel mailing list