[Bug 747888] Re: casper script 25configure_init clobbers 22serialtty, serial console nearly unusable

Stéphane Graber stgraber at stgraber.org
Tue Oct 2 21:55:19 UTC 2012


** Changed in: casper (Ubuntu)
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/747888

Title:
  casper script 25configure_init clobbers 22serialtty, serial console
  nearly unusable

Status in “casper” package in Ubuntu:
  Fix Committed

Bug description:
  Binary package hint: casper

  I am creating a custom live ubuntu image which defaults to serial console redirection. When I boot the image using a serial console, the console becomes practically unusuable, a screen shot is attached. This is because /etc/init/ttyS0.conf has been overwritten (clobbered) by a casper helper script in the initrd:
  initrd/scripts/casper-bottom/25configure_init

  The clobbering comes from these lines:
  for f in /root/etc/init/tty*; do
        sed -i -e "s|^exec.*|exec env blah=blah /bin/login -f $USERNAME </dev/$(basename $f .conf) > /dev/$(basename $f .conf) 2>\&1|" $f

  since both tty0 and ttyS0 match tty*.

  The easiest solution is if you move casper-bottom/22serialtty to
  casper-bottom/26serialtty, but this requires that the user set the
  serialtty kernel option. Personally, I think this kernel option
  "serialtty" is brilliant - it would be great if that were all you had
  to set to get full serial console redirection (or maybe from
  console=ttyS0,115200n8). But I read in the comments that serialtty is
  just for development and not really for production.

  So probably the best option is to modify 25configure_init with something like this:
  for f in $(ls /root/etc/init/tty* |grep -E tty[[:digit:]]*); do

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/747888/+subscriptions




More information about the foundations-bugs mailing list