FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Edubuntu Development

 
 
LinkBack Thread Tools
 
Old 06-13-2010, 04:50 AM
Alkis Georgopoulos
 
Default feature request: add a root-path parameter

Public bug reported:

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 ports. And he wanted nbd swapping a third port would be
needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
* A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
* A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.

** Affects: ltsp (Ubuntu)
Importance: Undecided
Status: New

** Affects: nbd (Ubuntu)
Importance: Undecided
Status: New

** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New

--
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
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 ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
* A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
* A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.



--
edubuntu-devel mailing list
edubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel







References:

[Bug 593227] [NEW] feature request: add a root-path parameter
From: Alkis Georgopoulos <alkisg@gmail.com>
 
Old 06-15-2010, 06:54 AM
Alkis Georgopoulos
 
Default feature request: add a root-path parameter

Στις 14-06-2010, ημ*ρα Δευ, και ώρα 20:35 +0000, ο/η Wouter Verhelst
*γραψε:
> NBD has a "virtual host" feature that allows you to change the served
> file based on (part of) the IP address of the client that's
> connecting.

That would indeed work for some use cases, but unfortunately fixed IP
addresses would be required, which isn't always an option.

> I'd prefer that the client would be able to specify a name of an
> export, with the server using the section name in the config file as
> the name of the export, rather than having the ability to specify a
> path; the latter would have some security ramifications that I'd
> prefer not to deal with.

I was thinking something like /etc/exports, with one entry per line,
which would make it easier for postinst/postrm scripts to handle. In
essence the two methods are the same except that the whole "section" is
in one line, and the full path is used as the "section name" - I can't
see any differences security-wise. But sure, the configuration file
format (or config.d directory if implemented) is not an issue at all.

Thank you very much,
Alkis

--
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
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 ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
* A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
* A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.



--
edubuntu-devel mailing list
edubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
 
Old 06-15-2010, 08:12 AM
Oliver Grawert
 
Default feature request: add a root-path parameter

hi,
Am Dienstag, den 15.06.2010, 06:54 +0000 schrieb Alkis Georgopoulos:
> Στις 14-06-2010, ημ*ρα Δευ, και ώρα 20:35 +0000, ο/η Wouter Verhelst
> *γραψε:
> > NBD has a "virtual host" feature that allows you to change the served
> > file based on (part of) the IP address of the client that's
> > connecting.
>
> That would indeed work for some use cases, but unfortunately fixed IP
> addresses would be required, which isn't always an option.
just add an info function to the client and query it from the script
(ldminfo in reverse ...)

ciao
oli

--
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
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 ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
* A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
* A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.



--
edubuntu-devel mailing list
edubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
 
Old 06-15-2010, 09:59 AM
Alkis Georgopoulos
 
Default feature request: add a root-path parameter

Στις 15-06-2010, ημ*ρα Τρι, και ώρα 08:12 +0000, ο/η Oliver Grawert
*γραψε:
> just add an info function to the client and query it from the script
> (ldminfo in reverse ...)

Hi Oli,

if nbd-client was to be modified independently from nbd-server, we could
just make it send any info we want, and have our nbdrootd daemon read it
from stdin (inetd) before chaining to nbd-server. There's no need for
scripts and callback functions.
But I'd really prefer a clean upstream solution if it's possible, rather
than maintaining an nbd-client fork just for LTSP.

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 conventions were used in both cases?

--
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
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 ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
* A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
* A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.



--
edubuntu-devel mailing list
edubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
 
Old 06-15-2010, 01:34 PM
Alkis Georgopoulos
 
Default feature request: add a root-path parameter

Στις 15-06-2010, ημ*ρα Τρι, και ώρα 10:26 +0000, ο/η Wouter Verhelst
*γραψε:
> Having said that, I don't think it would hurt to support the ltsp_nbd
> syntax as an alternative, provided it does not break anything in my
> current scripts. I would need a pointer to how that works then, however.

I thought it'd be better if I filed a separate feature request for that:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/594595

Kind regards,
Alkis

--
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
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 ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
* A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
* A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.



--
edubuntu-devel mailing list
edubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
 

Thread Tools




All times are GMT. The time now is 01:35 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org