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
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
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
>
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
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
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,
6 matches
Mail list logo
