|
From: Sean D. <se...@du...> - 2007-10-19 20:36:22
|
I just ran into this project today and am looking to start using it (or at least testing it out). Before I delve into packaging it up, is there anyone out there that's already made packages for RHEL 4/5? Or anyone who is in the process of making them? Thanks, Sean |
|
From: Johannes K. <oj...@gm...> - 2007-11-07 09:29:48
Attachments:
signature.asc
|
Sean Dilda schrieb: > I just ran into this project today and am looking to start using it (or= =20 > at least testing it out). Before I delve into packaging it up, is ther= e=20 > anyone out there that's already made packages for RHEL 4/5? Or anyone = > who is in the process of making them? Im not sure how the usage of this project ist planned, but it would be nice to have packages for more distributions, RHEL 4/5 or Fedora, openSUSE 10.x, Debian, Ubuntu,... Then one could just install them from within the vm via the normal mechanism (apt, yum, smart,...). OJ --=20 As sure as night is dark and day is light, I keep you on my mind both day and night. And happiness I've known proves that it's right, because you're mine, I walk the line. (Johnny Cash: I walk the line) |
|
From: Elliot L. <el...@vm...> - 2007-11-08 01:23:30
|
On 11/7/07 1:29 AM, "Johannes Kastl" <oj...@gm...> wrote: > Sean Dilda schrieb: >> I just ran into this project today and am looking to start using it (or >> at least testing it out). Before I delve into packaging it up, is there >> anyone out there that's already made packages for RHEL 4/5? Or anyone >> who is in the process of making them? > > Im not sure how the usage of this project ist planned, but it would be > nice to have packages for more distributions, RHEL 4/5 or Fedora, > openSUSE 10.x, Debian, Ubuntu,... > > Then one could just install them from within the vm via the normal > mechanism (apt, yum, smart,...). > OJ I agree 100% that it'd be nice to get more packages made. Here's what I know about distro packages so far: . Debian has a package in contrib/experimental ( http://packages.debian.org/open-vm-tools ) . Ubuntu has a page for it at https://launchpad.net/open-vm-tools , but doesn't seem to have packaged it yet. They may wind up getting in there via Debian. . Gentoo is working on a package ( http://bugs.gentoo.org/show_bug.cgi?id=192377 ) . Fedora won't include the kernel modules unless they're included in the upstream Linux kernel, but someone has started packaging things in Livna. See http://bugzilla.livna.org/show_bug.cgi?id=1664 and http://bugzilla.livna.org/show_bug.cgi?id=1665 . Don't know what's going on with OpenSUSE. . Any other distros people care about? Heiko, how is DevilLinux going? :) Please also note the packaging guidelines at http://open-vm-tools.wiki.sourceforge.net/Packaging Sean, unless someone else pops up soon, don't feel like you need permission to build RHEL packages on your own. Do you know of an existing repository of unofficial RHEL packages that is in wide use? Anything I can do to help anyone move things forward with distro packaging? Best, -- Elliot |
|
From: Sean D. <se...@du...> - 2007-11-08 01:34:39
|
Elliot Lee wrote: > On 11/7/07 1:29 AM, "Johannes Kastl" <oj...@gm...> wrote: > Sean, unless someone else pops up soon, don't feel like you need permission > to build RHEL packages on your own. Do you know of an existing repository of > unofficial RHEL packages that is in wide use? > I found the packages that were submitted to Fedora and ran with them. I ended up splitting out an extra subpackage (in case you don't want to install X-libs). I also modified the init script (there are some things ESX doesn't need). If anyone wants, you can find my packages here: http://www.duke.edu/~sean/rpms/open-vm-tools/ They're compiled against CentOS 5 Thanks, Sean |
|
From: Justin M. F. <jmf...@li...> - 2007-11-08 03:10:09
|
On Wed, 2007-11-07 at 17:23 -0800, Elliot Lee wrote: > I agree 100% that it'd be nice to get more packages made. Here's what I know > about distro packages so far: > > . Debian has a package in contrib/experimental ( > http://packages.debian.org/open-vm-tools ) > . Ubuntu has a page for it at https://launchpad.net/open-vm-tools , but > doesn't seem to have packaged it yet. They may wind up getting in there via > Debian. > . Gentoo is working on a package ( > http://bugs.gentoo.org/show_bug.cgi?id=192377 ) > . Fedora won't include the kernel modules unless they're included in the > upstream Linux kernel, but someone has started packaging things in Livna. > See http://bugzilla.livna.org/show_bug.cgi?id=1664 and > http://bugzilla.livna.org/show_bug.cgi?id=1665 > . Don't know what's going on with OpenSUSE. > . Any other distros people care about? Heiko, how is DevilLinux going? :) rPath Linux has open-vm-tools packaged and is shipping it enabled by default on vmware flavors of the distro (and many users appliances). Foresight Linux is coming soon. Justin |
|
From: Ragavan S <rag...@gm...> - 2007-11-09 17:52:07
|
> rPath Linux has open-vm-tools packaged and is shipping it enabled by > default on vmware flavors of the distro (and many users appliances). > Foresight Linux is coming soon. I've started a wiki page to start keeping track of this information. http://open-vm-tools.wiki.sourceforge.net/Distro+Package+Status By the way, I am curious to see if you or the other packagers found the packaging guidelines doc helpful. http://open-vm-tools.wiki.sourceforge.net/Packaging Are there any other pieces of information we can provide that would make your jobs easier? Ragavan |
|
From: Sean D. <se...@du...> - 2007-11-09 18:07:01
|
Ragavan S wrote: >> rPath Linux has open-vm-tools packaged and is shipping it enabled by >> default on vmware flavors of the distro (and many users appliances). >> Foresight Linux is coming soon. > > I've started a wiki page to start keeping track of this information. > http://open-vm-tools.wiki.sourceforge.net/Distro+Package+Status > Thanks for keeping track of that. > By the way, I am curious to see if you or the other packagers found > the packaging guidelines doc helpful. > http://open-vm-tools.wiki.sourceforge.net/Packaging > > Are there any other pieces of information we can provide that would > make your jobs easier? > I did find the packaging page to be quite useful. However, there are a couple pieces of extra information that would be useful. For a lot of the components, I'm not really sure what they do, which makes it hard to know how to package them. For instance, I made the guess that 'vmblock' is used for drag-and-drop (something ESX users don't have to use). However, its not clear to me if its used for anything else. Likewise, most of the other components don't have what they're used for specified. I'd also like to note that the Packaging page references vmware-xferlogs, which isn't actually available in the source download. Thanks, Sean |
|
From: Andrew B. <big...@vm...> - 2007-11-09 18:20:26
|
Sean Dilda <se...@du...> wrote: > For instance, I made the guess that 'vmblock' is used for > drag-and-drop (something ESX users don't have to use). However, its > not clear to me if its used for anything else. To answer just this question, vmblock is used for drag and drop and file copy/paste in the host to guest direction. The same module is used on the host for the same features but in the guest to host direction. Neither of those features are available on ESX, as you mentioned, and vmblock is not used for anything else. |
|
From: Elliot L. <el...@vm...> - 2007-11-09 18:49:32
|
On 11/9/07 10:06 AM, "Sean Dilda" <se...@du...> wrote: > I'd also like to note that the Packaging page references > vmware-xferlogs, which isn't actually available in the source download. It'll be in the next release. :) Best, -- Elliot |
|
From: Ragavan S <rag...@gm...> - 2007-11-09 23:01:32
|
> > For a lot of the components, I'm not really sure what they do, which > makes it hard to know how to package them. For instance, I made the > guess that 'vmblock' is used for drag-and-drop (something ESX users > don't have to use). However, its not clear to me if its used for > anything else. Likewise, most of the other components don't have what > they're used for specified. Good idea. I've started a new page to document this on the wiki. http://open-vm-tools.wiki.sourceforge.net/ComponentFunctionality Right now it is sparse - I copied Andrew's description of where vmblock is used. We'll start adding similar descriptions for the other components as well. > > I'd also like to note that the Packaging page references > vmware-xferlogs, which isn't actually available in the source download. This was missed due to an oversight on our part. As Elliot said, it will be in the next release. Regards, Ragavan |