Re: [gentoo-user] nbd ebuild incomplete? [SOLVED]
On 12/05/19 20:01, Grant Taylor wrote: On 12/5/19 12:33 AM, n952162 wrote: The emerge should have checked for this and failed. I don't think it should fail. I've routinely seen emerge check for various kernel / network / other parameters and issue warnings about things not being the way that the ebuild wants. But the ebuild does successfully emerge. IMHO emerge / ebuild should not refuse to do what I tell it to do just because it doesn't like my custom kernel. The lack of kernel support is /my/ problem. The emerge / ebuild is capable of compiling perfectly fine without the kernel support. Perhaps I'm compiling on a fast machine that is running a different kernel and then copying the utilities to another system that does have the kernel support. Then you set the appropriate USE variable for that special situation. You could your argument for any dependency.
Re: [gentoo-user] nbd ebuild incomplete? [SOLVED]
On 12/5/19 12:33 AM, n952162 wrote: The emerge should have checked for this and failed. I don't think it should fail. I've routinely seen emerge check for various kernel / network / other parameters and issue warnings about things not being the way that the ebuild wants. But the ebuild does successfully emerge. IMHO emerge / ebuild should not refuse to do what I tell it to do just because it doesn't like my custom kernel. The lack of kernel support is /my/ problem. The emerge / ebuild is capable of compiling perfectly fine without the kernel support. Perhaps I'm compiling on a fast machine that is running a different kernel and then copying the utilities to another system that does have the kernel support. -- Grant. . . . unix || die -- Grant. . . . unix || die
Re: [gentoo-user] nbd ebuild incomplete? [SOLVED]
On Thursday, 5 December 2019 12:52:41 GMT n952162 wrote: > where do I start? By not top-posting. > On 12/05/19 09:56, Neil Bothwick wrote: > > On Thu, 5 Dec 2019 08:33:08 +0100, n952162 wrote: > >> Okay, I see from /proc/config.gz that NBD probably needs to be > >> configured with the kernel > >> > >> # CONFIG_BLK_DEV_NBD is not set > >> > >> Bummer. At work, I could just do a apt-get install qemu-nbd (or > >> similar) without any more effort. > > > > That's because generic distro kernels already have BLK_DEV_NBD enabled. > > > >> The emerge should have checked for this and failed. > > > > Yes, it sounds like it. Have you filed a bug report? Have ready the output of 'emerge --info' in a file. Then go to bugs.gentoo.org, create an account and log in. Search for existing bugs against the ebuild you're interested in, including its version. If there is one, you could add yourself to its CC list (top right corner) to be notified of changes. Otherwise, create a new bug report, giving as much detail as you can. Attach your --info file to the bug. Job done. -- Regards, Peter.
Re: [gentoo-user] nbd ebuild incomplete? [SOLVED]
where do I start? On 12/05/19 09:56, Neil Bothwick wrote: On Thu, 5 Dec 2019 08:33:08 +0100, n952162 wrote: Okay, I see from /proc/config.gz that NBD probably needs to be configured with the kernel # CONFIG_BLK_DEV_NBD is not set Bummer. At work, I could just do a apt-get install qemu-nbd (or similar) without any more effort. That's because generic distro kernels already have BLK_DEV_NBD enabled. The emerge should have checked for this and failed. Yes, it sounds like it. Have you filed a bug report?
Re: [gentoo-user] nbd ebuild incomplete? [SOLVED]
On Thu, 5 Dec 2019 08:33:08 +0100, n952162 wrote: > Okay, I see from /proc/config.gz that NBD probably needs to be > configured with the kernel > > # CONFIG_BLK_DEV_NBD is not set > > Bummer. At work, I could just do a apt-get install qemu-nbd (or > similar) without any more effort. That's because generic distro kernels already have BLK_DEV_NBD enabled. > The emerge should have checked for this and failed. Yes, it sounds like it. Have you filed a bug report? -- Neil Bothwick Taglines are like cars - You get a good one, then someone nicks it. pgpFv_NDOpbcL.pgp Description: OpenPGP digital signature
Re: [gentoo-user] nbd ebuild incomplete? [SOLVED]
Okay, I see from /proc/config.gz that NBD probably needs to be configured with the kernel # CONFIG_BLK_DEV_NBD is not set Bummer. At work, I could just do a apt-get install qemu-nbd (or similar) without any more effort. The emerge should have checked for this and failed. On 12/05/19 08:23, n952162 wrote: The documentation emerged with sys-block/nbd includes this: /usr/share/doc/nbd-3.19/README.md.bz2: # modprobe nbd but there's no module emerged by nbd-3.19.ebuild. There doesn't seem to be any relevant USE flags to cause it to be generated. How can I get nbd.ko?
