On 12/5/19 12:22 PM, n952162 wrote:
But, since it's included in the package, and apparently (from the name)
will use a NBD device, then I think the dependency is logical
I disagree.
QEMU itself does not use NBD. Thus QEMU does not need to depend on
qemu-nbd. QEMU uses files on mounted file
* Ian Zimmerman:
> [OpenWrt] needs one crucial bit of configuration that's kind of hidden
> (can't be done via the GUI), to let the router advertisements through.
Glad to hear that you got things working. You have probably already
filed a GUI enhancement request. ;-)
-Ralph
On 12/5/19 12:50 PM, Neil Bothwick wrote:
No, but since it is provided by the ebuild, the ebuild should check
that the target system is capable of supporting it. The qemu ebuild
already spits out warnings about missing kernel options, not all of them
essential, so why not this one too?
I
* gentoo-u...@c-14.de:
> The easiest option is if you're using stateful DHCPv6. In this case
> you just need to set up your dhcp server to notify your dns server of
> any new leases.
That's what you consider "the easiest option"? ;-)
I usually ask the following of people starting with IPv6: Do
* Peter Humphrey:
> $ ping6 vdsl
> ping: vdsl: No address associated with hostname
The outcome of ping depends on /etc/resolv.conf and /etc/hosts, and even
on the OS of the IPv6 nodes involved. Apple devices will be available as
somename.local, with "somename" being what the user configured as
On Thu, 5 Dec 2019 12:01:33 -0700, Grant Taylor wrote:
> qemu-nbd is a utility to act as a NBD server to allow the Linux kernel
> to be an NBD client to access qcow(2) image files.
>
> qemu-nbd is not /needed/ for normal QEMU operation.
No, but since it is provided by the ebuild, the ebuild
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
Very informative explanation.
On 12/05/19 20:01, Grant Taylor wrote:
On 12/4/19 11:03 PM, Walter Dnes wrote:
nbd is a "Network Block Device" driver along the lines of NFS, but it
doesn't handle concurrency. https://nbd.sourceforge.io/
I think I'd liken NBD to iSCSI more so than NFS.
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 12/4/19 11:03 PM, Walter Dnes wrote:
nbd is a "Network Block Device" driver along the lines of NFS, but
it doesn't handle concurrency. https://nbd.sourceforge.io/
I think I'd liken NBD to iSCSI more so than NFS. Primarily because both
NBD and iSCSI provide local block devices that are
On 2019-11-29 00:01, Ralph Seichter wrote:
> > The first reason [...] was that my router does _not_ assign fe80::1 to
> > itself, but rather some other arbitrary address in the fe80 prefix
>
> I found an article[1] that I first read years ago. "One method to make
> things easier is to manually
> Hello list,
Hi,
> Having been inspired by the recent discussion of IPv6, I decided to try it,
> starting with my ISP, my Billion Bipac vDSL modem-router and one host - this
> one. Of course it isn't straightforward.
>
> Zen has allocated me a /64 ND prefix and a /48 PD prefix. I found a way
Hello list,
Having been inspired by the recent discussion of IPv6, I decided to try it,
starting with my ISP, my Billion Bipac vDSL modem-router and one host - this
one. Of course it isn't straightforward.
Zen has allocated me a /64 ND prefix and a /48 PD prefix. I found a way to
tell the
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
On Thu, 5 Dec 2019 08:05:46 +0100, n952162 wrote:
> Or maybe the assumption is wrong - after emerging *nbd*, I still get
> this when I try to modprobe nbd, which is required for running
> *qemu-nbd*:
>
> modprobe: FATAL: Module ndb not found in directory
> /lib/modules/4.19.72-gentoo
The
17 matches
Mail list logo
