[Bug 61361] Re: [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix

2008-03-14 Thread Richard Johnson
Marking as fix released due to comment. Thanks! ** Changed in: klibc (Ubuntu) Status: New = Fix Released -- [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix https://bugs.launchpad.net/bugs/61361 You received this bug notification because you are

[Bug 61361] Re: [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix

2008-01-05 Thread Daniel Karlsson
So I take it that this bug has been fixed since Edgy? If so perhaps we should mark this bug as fixed? -- [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix https://bugs.launchpad.net/bugs/61361 You received this bug notification because you are a member of

[Bug 61361] Re: [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix

2006-10-18 Thread Michael Ellerman
It's not fixed in Dapper (klibc-utils 1.1.16-1ubuntu5), but is fixed in Edgy (klib-utils 1.4.10-0ubuntu3). -- [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix https://launchpad.net/bugs/61361 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 61361] Re: [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix

2006-10-13 Thread towsonu2003
** Summary changed: - Machine won't boot because fstype misidentifies ext3 filesystem as minix + [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix -- [patch attached] Machine won't boot because fstype misidentifies ext3 filesystem as minix