1 |
On Thursday, 5 December 2019 12:52:41 GMT n952162 wrote: |
2 |
> where do I start? |
3 |
|
4 |
By not top-posting. |
5 |
|
6 |
> On 12/05/19 09:56, Neil Bothwick wrote: |
7 |
> > On Thu, 5 Dec 2019 08:33:08 +0100, n952162 wrote: |
8 |
> >> Okay, I see from /proc/config.gz that NBD probably needs to be |
9 |
> >> configured with the kernel |
10 |
> >> |
11 |
> >> # CONFIG_BLK_DEV_NBD is not set |
12 |
> >> |
13 |
> >> Bummer. At work, I could just do a apt-get install qemu-nbd (or |
14 |
> >> similar) without any more effort. |
15 |
> > |
16 |
> > That's because generic distro kernels already have BLK_DEV_NBD enabled. |
17 |
> > |
18 |
> >> The emerge should have checked for this and failed. |
19 |
> > |
20 |
> > Yes, it sounds like it. Have you filed a bug report? |
21 |
|
22 |
Have ready the output of 'emerge --info' in a file. Then go to |
23 |
bugs.gentoo.org, create an account and log in. Search for existing bugs |
24 |
against the ebuild you're interested in, including its version. If there is |
25 |
one, you could add yourself to its CC list (top right corner) to be notified |
26 |
of changes. Otherwise, create a new bug report, giving as much detail as you |
27 |
can. Attach your --info file to the bug. |
28 |
|
29 |
Job done. |
30 |
|
31 |
-- |
32 |
Regards, |
33 |
Peter. |