[Bug 176358] Re: Fails to boot with init=/bin/sh

2011-07-18 Thread Brad Figg
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu)

[Bug 176358] Re: Fails to boot with init=/bin/sh

2009-08-01 Thread necwerk
the problem is in /bin/dash. use /bin/bash! -- Fails to boot with init=/bin/sh https://bugs.launchpad.net/bugs/176358 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubun

[Bug 176358] Re: Fails to boot with init=/bin/sh

2009-07-31 Thread necwerk
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- Fails to boot with init=/bin/sh https://bugs.launchpad.net/bugs/176358 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubun

[Bug 176358] Re: Fails to boot with init=/bin/sh

2009-05-06 Thread Sergio Zanchetta
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life - http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the linux-source-2.6.22 kernel task. It would be helpful if you could test the new Jaunty Jackalope 9.04 release and confirm if this issue remains

[Bug 176358] Re: Fails to boot with init=/bin/sh

2008-10-04 Thread Gordon Goodfellow
** Changed in: linux-source-2.6.22 (Ubuntu) Sourcepackagename: None => linux-source-2.6.22 -- Fails to boot with init=/bin/sh https://bugs.launchpad.net/bugs/176358 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-

[Bug 176358] Re: Fails to boot with init=/bin/sh

2008-05-11 Thread Andrew Sayers
Confirmed in 8.04. For me, neither init=/bin/sh nor init=/bin/dash work. init=/bin/bash works, although you need to hit "enter" to actually see a command prompt - presumably the first prompt is overwritten by lines being printed by the kernel. -- Fails to boot with init=/bin/sh https://bugs.lau