kfreebsd mount missing libbsd.so.0 -> it is not installed.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

kfreebsd mount missing libbsd.so.0 -> it is not installed.

Thomas Schweikle-2
Package: kfreeBSD-kernel

Booting Debian GNU/kfreeBSD fails because mount does not find
libbsd.so.0 and mount not build as static or libbsd.so.0 not part of
boot filesystem.

Any idea on how to recover?

--
Thomas

Reply | Threaded
Open this post in threaded view
|

Re: Bug#924390: kfreebsd mount missing libbsd.so.0 -> it is not installed.

James Clarke-2
Control: tags -1 moreinfo

On Tue, Mar 12, 2019 at 01:23:53PM +0100, Thomas Schweikle wrote:
> Package: kfreeBSD-kernel

This package doesn't exist. If you insist on not using reportbug, please
do ensure that you file against a valid package.

However, in this case, I don't actually know where in the stack this bug
report belongs, in part because I don't understand how it could possibly
arise (as described below).

> Booting Debian GNU/kfreeBSD fails because mount does not find
> libbsd.so.0 and mount not build as static or libbsd.so.0 not part of
> boot filesystem.

So, I'm extremely confused as to why you are having an issue, and it's
not helped by the fact that you have not provided any kind of log file.
Please provide one (or some form of error mesage that you get, with
context).

The reasons why I don't understand how this is happening are as follows:

1. There is no initrd/initramfs on GNU/kFreeBSD; the root that gets
   mounted is your real root file system.

2. This root file system gets mounted RW during boot, as configured by
   GRUB, so there should be no need to use a mount binary other than
   much later in boot for other filesystems (the root gets mounted
   directly by the kernel since there is not yet a root).

3. The mount binary itself comes from freebsd-utils, which Depends on
   libbsd0, thus pulling in libbsd.so.0

So, really, it's a mystery to me how on earth you're having issues with
a missing libbsd.so.0 that also breaks mounting the root filesystem;
none of that should matter.

> Any idea on how to recover?

Given I have no idea what your error actually is, I can't possibly hope
to tell you how to work around it.

Regards,
James