Daniel Riek wrote: >The preferred solution here is to run the Desktop as a virtualized guest >on a server.
It would be great if you could talk a little bit more of this, what kind of setup you have in mind. As I said, I don't really understand how virtualization would solve this problem. For example, when using Java applets for remote access, the applets must be served from the same server that's running the desktop, due to the Java Applet security model. It might be possible to play with port forwarding etc, but that would mean extra complexity. The limited scalability of the Desktop system wrt kernels etc will also remain: The Desktop distribution doesn't scale better just because it's virtualized, right? Or do you suggest running multiple virtualized Desktops on one Server? In any case, I believe customers would prefer to maintain one system rather than two or more, so I guess they are better of running the Desktop distribution on the bare metal. Would virtualization solve the licensing problem?: >> Another problem might be >> licensing. http://www.redhat.com/rhel/desktop/compare/#note_2 >> indicates that using RHEL Desktop on a terminal server would be a >> licensing violation. I've contacted Red Hat about this, but I'm still >> waiting for an answer. If it does, would it be OK to buy one Server and one Desktop license but still run the Desktop on the bare metal? Best regards, --- Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.se Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00
Sorry for the late answer. The preferred solution here is to run the Desktop as a virtualized guest on a server. Regards, Daniel On Mon, 2007-03-26 at 08:57 +0200, Peter Åstrand wrote: > Daniel Riek wrote: > > >Yes, that channel will contain the Desktop packages not included in the > >Server tree. > > As an ISV providing a thin client product, we get a lot of questions from > our customers wrt which Linux distribution they should choose. One common > usage scenario for our product is to publish Linux desktops (possibly with > Windows applications as well) to thin clients. This requires servers with > modern applications and desktop environments, but also stability and > scalability. The trend of segmenting distributions into dedicated > "desktop" or "server" editions is a major problem with thin client setups: > > If you choose the "server" edition, you'll have to do without the > modern desktop and applications such as Evolution and OpenOffice. This > is typically not acceptable. > > If you choose the client edition, you will get other problems: Sometimes > no web server is included (which is required for accessing the desktop > from a web browser), no enterprise-kernels etc. > > Another problem might be > licensing. http://www.redhat.com/rhel/desktop/compare/#note_2 > indicates that using RHEL Desktop on a terminal server would be a > licensing violation. I've contacted Red Hat about this, but I'm still > waiting for an answer. > > > >Now, the goal is not to enable widespread client installation of the > >server variant - we have a client for that - or use as "terminal-server" > >kind-of setups - there virtualization is the recommended solution: In > >cases where these approaches do not fit, the Optional Productivity Apps > >channel will provide an alternative. > > I don't understand how virtualization could help with a > terminal-server setup. Are you suggesting that each user should have > their own, personal desktop OS running in virtual machines on the > server (VDI-style)? In most cases, this is very sub-optimal, and not very > well supported with most thin client products. > > > >The support though will be limited to maintenance (bug- and security > >fixes). The current plan is to have Customer Service give it to > >customers requiring it. I will post an announcement on this channel as > >soon as it is ready. > > Thanks. > > Regards, > --- > Peter Åstrand ThinLinc Chief Developer > Cendio AB http://www.cendio.se > Teknikringen 3 > 583 30 Linköping Phone: +46-13-21 46 00 > _______________________________________________ rhelv5-list mailing list > [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list -- Daniel Riek, Product Manager Red Hat Enterprise Linux, Red Hat Inc. E-Mail: [EMAIL PROTECTED], http://www.redhat.com/ Key-FP: 3DD7 C376 C3E0 1917 9A63 6343 5A26 2C59 6C07 6F32
signature.asc
Description: This is a digitally signed message part
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
