Jump to content

Talk:Linux-VServer: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Removed duplicate of fair use template
Removing outdated "fair use" template - image has an explicit license.
Line 20: Line 20:


Vservers as a whole can be migrated easily as long as the filesystems it depends on are able to be mounted on different hosts. Fail over is described [http://linux-vserver.org/Fail-over| here]
Vservers as a whole can be migrated easily as long as the filesystems it depends on are able to be mounted on different hosts. Fail over is described [http://linux-vserver.org/Fail-over| here]
==Fair use rationale for Image:Linux-VServer-logo.png==
[[Image:Nuvola apps important.svg|70px|left]]
'''[[:Image:Linux-VServer-logo.png]]''' is being used on this article. I notice the image page specifies that the image is being used under [[Wikipedia:Fair use|fair use]] but there is no [[Wikipedia:Fair use rationale guideline|explanation or rationale]] as to why its use in '''this''' Wikipedia article constitutes fair use. In addition to the [[Wikipedia:Image copyright tags/Fair use|boilerplate fair use template]], you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with [[WP:FU|fair use]].

Please go to [[:Image:Linux-VServer-logo.png|the image description page]] and edit it to include a [[Wikipedia:Fair use rationale guideline |fair use rationale]]. Using one of the templates at [[Wikipedia:Fair use rationale guideline]] is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on [[Wikipedia:Criteria for speedy deletion#Images.2FMedia|criteria for speedy deletion]]. If you have any questions please ask them at the [[Wikipedia:Media copyright questions|Media copyright questions page]]. Thank you.<!-- Template:Missing rationale2 -->[[User:BetacommandBot|BetacommandBot]] 00:21, 6 June 2007 (UTC)

== Two items: 1) terminology, 2) the "Advantages" section is inaccurate ==
== Two items: 1) terminology, 2) the "Advantages" section is inaccurate ==



Revision as of 02:09, 25 January 2014

WikiProject iconLinux Unassessed
WikiProject iconThis article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

origin

Does this derive from the similar project years ago out of Quebec by the author of linuxconf? I've lost track of where that went...

Dan Shearer 19:48, Nov 20, 2004 (UTC)

Do you talk about Jacques Gélinas ? If so, yes, this project replaces the "contexts" project launched by Jacques.

Xen does process migration, doesn't it?

"No clustering or process migration capability is included, so the host kernel and host computer is still a single point of failure for all virtual servers (similar to Xen and UML)." I don't know about UML, but I know Xen does allow migration from one hardware node to another.

When it started?

Can anybody clarify of when exactly the "contexts" project was started, and when the first working version of Linux-VServer (or "contexts") was available? Just curious. --K001 22:47, 19 June 2006 (UTC)[reply]

Vserver Can Be Migrated!

Vservers as a whole can be migrated easily as long as the filesystems it depends on are able to be mounted on different hosts. Fail over is described here

Two items: 1) terminology, 2) the "Advantages" section is inaccurate

1) The phrase "whole system emulation" is used in several places. Is this intended to refer to virtualization in general, to actual emulation such as is provided by Bochs (http://bochs.sourceforge.net/)? Assuming it's virtualization that's intended, my second question (below) becomes relevant.

2) The "Advantages" section says that VServer's approach is "somewhat more memory-efficient and I/O-efficient than whole-system emulation, which cannot return "unused" memory or share a disk cache with the host and other virtual servers.". This is incorrect. For example, VMware supports memory ballooning as a mechanism to return unused memory to the host, and Oracle's Transcendent Memory project (http://oss.oracle.com/projects/tmem/) can provide even greater gains with suitably modified Linux guests.

-klode — Preceding unsigned comment added by Klode (talkcontribs) 16:13, 11 August 2011 (UTC)[reply]

Does it support file descriptor passing across isolation contexts?

Most unices support a mechanism to 'pass' a file descriptor through a socket. (http://archives.neohapsis.com/archives/postfix/2000-09/1476.html) For example, you might have a virus scanning daemon running as an unpriviledge user, and then to scan a file, a client can pass an open file descriptor over the socket to the virus scanning daemon. The scanning daemon can then read that file to search for viruses, even though it is running under a user that normally cannot access the file.

Does Linux-VServer allow file descriptor passing of this type between security contexts?

PS- I've asked the same question about Talk:LXC, Talk:Linux-VServer and Talk:OpenVZ 128.112.139.195 (talk) 20:42, 11 November 2012 (UTC)[reply]