Not to the best of my knowledge, no. It was moved to main very early on;
I think it might've been 15 years ago. Perhaps the MIR prices didn't
exist yet back then? I wouldn't know, not having heard of the whole
thing until I saw this one pass by 🙂
The client's job is to configure an NBD device in t
** Bug watch added: github.com/NetworkBlockDevice/nbd/issues #71
https://github.com/NetworkBlockDevice/nbd/issues/71
** Also affects: nbd via
https://github.com/NetworkBlockDevice/nbd/issues/71
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Correction: I stated I want NBD updatd to 3.18 in 18.04, but what I
meant was that it should be updated in 18.10 -- 18.04 contains 3.16,
which is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/178
Public bug reported:
nbd-client 3.17 suffers from the upstream bug
https://github.com/NetworkBlockDevice/nbd/issues/71, which causes the
client to disconnect too soon in some cases. It would be very
problematic for certain setups.
Additionally, nbd-client 3.18 gains the "-g" option which improves
The issue was fixed with 0.10-1, long since in Ubuntu
** Changed in: ola (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598184
Title:
olad comes wi
This is not a bug, you're using the systemd unit incorrectly. The
correct service name to use is "nbd@nbd0", not "nbd@0". You must also
make sure that the nbdtab file contains the required information about
the export.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The problem is related to the version of libmicrohttpd-dev. Versions of
ola >= 0.10.0-1 in Debian unstable have the problem fixed, by tightening
libmicrohttpd-dev version requirements.
(Debian ola maintainer here)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The nbd implementation in qemu is not related to the nbd package;
reassigning
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu (Ubuntu)
** Package changed: nbd (Ubuntu) => qemu (Ubuntu)
--
You received this bug notification because you are a
Public bug reported:
Hi,
When one plugs in a Vasco DP905v1.1 smart card reader before pcscd is
started and waits for a few moments, the green 'power' led on this
device will go off, indicating that the device is in low-power mode.
When this happens, due to an issue with the specific card reader m
On 27-06-13 21:50, Marc Gariépy wrote:
> # strace -p 16636 -f -s 1500
> Process 16636 attached - interrupt to quit
> select(5, [4], NULL, NULL, NULL)= 1 (in [4])
> accept(4, {sa_family=AF_INET, sin_port=htons(46054),
> sin_addr=inet_addr("X.X.X.X")}, [16]) = 5
> write(5, "NBDMAGIC", 8)
On Mon, Sep 03, 2012 at 04:24:35AM -, Alkis Georgopoulos wrote:
> Another idea would be for the nbd-client initscript to notify the server that
> it's about to shutdown.
> So the server would do a "delayed disconnect" after e.g. 20 seconds, long
> enough for the client to get a chance to shut
On Mon, Feb 13, 2012 at 08:49:10AM -, Alkis Georgopoulos wrote:
> Another idea to work around the problem:
> Wouldn't it be possible to somehow specify that we only want one
> nbd-server process for all the clients?
Well, one of my long-term goals is to convert nbd-server from
fork-per-process
On Fri, Dec 02, 2011 at 04:20:25AM -, Alkis Georgopoulos wrote:
> 'morning Wouter, attaching my last proposal.
> I did some more testing in the ip:port/path parsing, it should cover all
> cases now. Also, up to 2 of these parameters can be omitted.
Wonderful.
I'll give it some testing and do
Hi Alkis,
On Thu, Dec 01, 2011 at 06:14:42AM -, Alkis Georgopoulos wrote:
> While the NBDROOT environment variable would allow for some flexibility, it
> still wouldn't allow LTSP to use the nbd-client.initrd script, as some LTSP
> users need to use the nbd-proxy hack.
> Also, LTSP would need
On Wed, Oct 19, 2011 at 01:57:08PM -, Robert Lowery wrote:
> Wouter, thanks for your fast response and troubleshooting steps. It
> turns out to be an issue in the mythbuntu-diskless package, specifically
> the mythbuntu_nbd script which is calling nbd-client using the old style
> port 2000 com
On Mon, Oct 17, 2011 at 12:27:17PM -, Robert Lowery wrote:
> Public bug reported:
>
> I have been using diskless mythbuntu (based on ltsp) for several years.
> After upgrading from 11.04 -> 11.10, nbd mounting has stopped working
> from the front ends.
>
> In /var/log/syslog on the server I g
On Sun, Aug 07, 2011 at 03:01:43PM -, Schöner, Axel wrote:
> The solution is very easy:
> "update-rc.d -f nbd-client remove"
> "update-rc.d nbd-client start 41 S . stop 59 0 6 ."
The problem is this:
override_dh_installinit:
dh_installinit -p nbd-client --no-start -- start 41 S . star
On Tue, Feb 15, 2011 at 07:20:29PM -, Kees Cook wrote:
> Actually, does this patch need backporting? When was the issue
> reintroduced?
>
> nbd | 1:2.8.3-2 | dapper-updates/main
> nbd | 1:2.9.9-1ubuntu1 | hardy/main
> nbd | 1:2.9.11-2ubuntu1 | karmic/main
> nbd | 1:2.9.14-2ubuntu1 | lucid/main
On Tue, Feb 15, 2011 at 09:52:22AM -, Wouter Verhelst wrote:
> While I personally agree that having the kernel default to supporting
> partitions is a good thing, I'm not quite sure that introducing a diff
> against Debian (and therefore extra work for Ubuntu) plus a local kerne
On Tue, Feb 15, 2011 at 01:37:21AM -, Kees Cook wrote:
> Since the modprobe config file was first removed in jaunty, and an LTS
> has since carried the patch, the preinst file is not longer needed. The
> modprobe file, btw, might be not an Ubuntu-specific issue. I would
> recommend opening an u
On Thu, Jan 06, 2011 at 01:37:30AM +0100, Wouter Verhelst wrote:
> On Thu, Jan 06, 2011 at 01:36:07AM +0100, Wouter Verhelst wrote:
> > On Wed, Jan 05, 2011 at 10:59:33PM -, Alkis Georgopoulos wrote:
> > > So maybe "if root=/dev/nbdX, then fallback to ROOTSERVER",
On Thu, Jan 06, 2011 at 01:36:07AM +0100, Wouter Verhelst wrote:
> On Wed, Jan 05, 2011 at 10:59:33PM -, Alkis Georgopoulos wrote:
> > So maybe "if root=/dev/nbdX, then fallback to ROOTSERVER", to also allow
> > for the root=/dev/nfs use case that you mentioned earlie
On Wed, Jan 05, 2011 at 10:59:33PM -, Alkis Georgopoulos wrote:
> A use case is when one is unable to define ROOTPATH with DHCP (e.g. all
> Greek schools use cheap routers as their DHCP servers) and is using a
> proxyDHCP server instead
> (https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP)
On Mon, Jan 03, 2011 at 07:44:23PM -, Alkis Georgopoulos wrote:
> Public bug reported:
>
> local-top/nbd in my Lucid (2.9.14-2ubuntu1) contains the following:
> if [ -z "$nbdsrv" ]
> then
> nbdsrv=${ROOTSERVER}
> fi
>
> That allowed me to pass "root=/dev/nbd0 nbdroot=,2011" without havi
On Sun, Nov 28, 2010 at 11:02:52AM -, Alkis Georgopoulos wrote:
> Public bug reported:
>
> In /etc/init.d/nbd-client, I don't see any way that would permit me to
> use an nbd-mounted root filesystem and have a clean shutdown process.
> With the current code, "rmmod nbd" is executed and then th
Thought you might be interested to know...
I've implemented support for name-based exports in NBD 2.9.17 (though
due to a bug, you need at least 2.9.18 for it to work). There's also
been an IANA port assignment (10809) for it.
That hasn't been uploaded to Debian yet, though, and it won't be soon
Hi,
For some reason, I didn't see this until now. Since Debian is now in
freeze for squeeze, it's too late to incorporate this patch.
I'll look at it after the release of squeeze.
--
The biometric identification system at the gates of the CIA headquarters
works because there's a guard with a la
On Tue, Jun 15, 2010 at 09:59:22AM -, Alkis Georgopoulos wrote:
> Btw speaking about LTSP differences, the nbd initramfs script uses
> commas to separate the host from the port (nbdroot=*,*,*), while the
> ltsp_nbd initramfs script uses colons (nbdroot=*:*) - wouldn't it be
> better if the same
On Sun, Jun 13, 2010 at 04:50:14AM -, Alkis Georgopoulos wrote:
> Currently nbd-server and nbd-client communicate using a different port
> for each image. So if e.g. an LTSP admin wants to use a chroot for
> nvidia-based clients and a chroot for the rest of his clients, he'd need
> to use two p
On Fri, Jun 04, 2010 at 03:13:16PM -, Andrew Scott wrote:
> Could you please provide a sample config file for comparison, for use
> with LTSP on Lucid Lynx?
The output of
man 5 nbd-server
contains two at the end.
Also, if you call 'dpkg-reconfigure -plow nbd-server', you should get a
set of
On Tue, May 11, 2010 at 03:55:27PM +0200, Wouter Verhelst wrote:
> In the future, please don't send mail to me directly. Instead, use the
> bug report. That way, other people can also benefit from what I may or
> may not be able to answer.
Actually, you did do that. Never mind, so
On Mon, May 10, 2010 at 04:09:26PM -, Nicolas Roussi wrote:
> I am running Lucid 64 and there is no config file either. What should the
> correct values for the reconfigure command be?
In the future, please don't send mail to me directly. Instead, use the
bug report. That way, other people can
Could either of you please attach a network dump created with
'wireshark' (please don't use tcpdump, since that drops part of every
package, making the dump not as useful). This will help greatly in
debugging this.
Note that with its default settings, wireshark will listen for *all*
network traffi
Try "dpkg-reconfigure nbd-server". That should ask some questions and
generate a correct config file.
If it doesn't, remove the config file and try again.
--
nbd-server no config file
https://bugs.launchpad.net/bugs/381766
You received this bug notification because you are a member of Ubuntu
Bug
Managed to get past the problems I had with launchpad previously.
What's keeping this from being updated?
--
Please merge nbd 1:2.9.13-2(main) from debian unstable(main)
https://bugs.launchpad.net/bugs/399707
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
On Wed, Oct 04, 2006 at 10:29:08PM -, wouter wrote:
> Version: 2.5.9-5
>
> On Wed, Oct 04, 2006 at 11:14:44AM -, Andrew Mitchell wrote:
> > What in the 2.5.9-5 changelog fixes this bug? I can see that the bug is
> > still open in Debian & the maintainer didn't claim it fixed the bug.
>
>
36 matches
Mail list logo
