On 11/17/09, Albert Hopkins wrote:
> On Tue, 2009-11-17 at 20:46 -0700, Maxim Wexler wrote:
>> Any one see a way past this impasse? I'm using ext2 with the journal
>> option.
>
> Why didn't you mount/fsck all the filesystems from outside the chroot?
>
Yeah, that's what I ended up doing. Something
2009/11/18 Maxim Wexler :
> Hi group,
>
> I ran emerge -avuDN world and came up with blocked packages which I
> eliminated by un-merging device-mapper and e2fsprogs-libs. When I
> rebooted was greeted by a maintenance console and the message
> "libblkid.so.1 cannot open shared object file". A lit
On Tue, 2009-11-17 at 20:46 -0700, Maxim Wexler wrote:
> Any one see a way past this impasse? I'm using ext2 with the journal
> option.
Why didn't you mount/fsck all the filesystems from outside the chroot?
I had a similar problem before and I solved it by start my computer
using boot CD then reemerge e2fsprogs-libs and sys-fs/e2fsprogs.
Hung
Maxim Wexler wrote:
> Hi group,
>
> I ran emerge -avuDN world and came up with blocked packages which I
> eliminated by un-merging device-mapper and e2fsprog
Hi group,
I ran emerge -avuDN world and came up with blocked packages which I
eliminated by un-merging device-mapper and e2fsprogs-libs. When I
rebooted was greeted by a maintenance console and the message
"libblkid.so.1 cannot open shared object file". A little googling
later I realized that e2
5 matches
Mail list logo
