** Patch added: "lucid-proposed patch"
   http://launchpadlibrarian.net/52315085/512253.patch

** Description changed:

  SRU justification:
  
  IMPACT: If /etc/network/interfaces contains a typo (e.g. 'iface eth0
  inet statuc') then the system will fail to reach runlevel 2, including
  recovery mode (although gdm will start fine, since it's started by an
  Upstart job).
  
  DEVELOPMENT BRANCH: Fixed in ifupdown 0.6.10ubuntu2 by manually bringing
  up lo before ifup -a.  I consulted with Scott James Remnant on the
  correct implementation here.
  
- PATCH: to-do
+ PATCH: http://launchpadlibrarian.net/52315062/512253.patch (karmic),
+ http://launchpadlibrarian.net/52315085/512253.patch (lucid)
  
  TEST CASE: Make a deliberate syntax error in /etc/network/interfaces
  (see example above) and try to boot to recovery mode.
  
  REGRESSION POTENTIAL: Take care to ensure that runlevel switching
  continues to work normally both with valid and invalid
  /etc/network/interfaces.
  
  Original report follows:
  
  Binary package hint: ifupdown
  
  I apparently made some mistake in /etc/network/interfaces. When I rebooted, 
the computer hung with a blank black screen
  with just a blinking cursor in the upper left corner. When pressing 
Ctrl-Alt-Del shutdown messages appear. Trying a few imes,
  there seems to be a couple of lines of output that is cleared off the screen. 
Perhaps it has something to do with the
  following line in /var/log/syslog:
  
   syslog:Jan 25 10:07:36 emmaline4 init: networking main process (762)
  terminated with status 1
  
  ProblemType: Bug
  Architecture: amd64
  Date: Mon Jan 25 10:41:48 2010
  DistroRelease: Ubuntu 9.10
  Package: ifupdown 0.6.8ubuntu21
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-server
  SourcePackage: ifupdown
  Uname: Linux 2.6.31-17-server x86_64

-- 
Mistake in /etc/network/interfaces keeps the system from booting
https://bugs.launchpad.net/bugs/512253
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to