Novell Linux Desktop
Welcome to the SUSE Linux Enterprise Desktop Wiki!!
As already mentioned on the wiki main page, please feel free to join in. You can read anything in here without logging in, but if you feel like commenting on something, or starting a new topic, you'll need to use a Novell Login account (which you'll be prompted to create if you don't already have one). If you are unfamiliar with using Wiki's in general, please visit Novell Wiki or the grandaddy wiki info site www.wiki.org for some background info.
- 1 Laptop
- 2 Desktop
- 3 Management
- 4 Remote Desktop Control
- 5 Other
For the Qosmio G25 Laptop with NVIDIA GEForce 6xxx graphic card: when you install the updated NVIDIA driver (necessary to use XGL features), the resolution available goes down to 1024x768, as opposed to the native 1280x768. If you click on the Display Information icon and select "Configure Display Settings" and change the setting to 1440x900, the option to use 1280x768 appears on the "Configure Display Settings" menu, allowing you to use native resolution (the option for 1440x900 does not appear, however).
Did a install yesterday of SLED10.1 SP1 on a MSI K9N Platinum M/B; 4GB Memory; 320GB SATA2 HDD; Samsung SATA2 DVD Writer; AMD AM2 DuoCore 3800+ CPU and an nVidia 7300GT Video Card. Installation constantly stalled at about 30-45 seconds into the installation. Had to abandon the SLED10 SP1. Tried the same using SLES10 SP1, same results, but after several tries it finally completed the installation. Have not been able to figure out why. We installed Xen so that we could install WXPPSP2 as the guest OS. After the installation was complete and the Xen installed, we installed WXPPSP2. The preformance was not to my satisfaction, Windows runs fairly slow. Looking into the memory monitor shows that Windows used 1GB memory while SLED was using the remainder. We set the guest OS size to 50GB. We also upgraded the video driver which gave us some performance improvement but not a lot. Questions: Is the size of the guest OS too large to run on Xen? Does anyone know of pending issues using the hardware we used? Is there a difference in the kernel between the desktop and the server that would cause the installation to fail on one and complet on the other although on the server initially it was doing the same. Can I get some of the desktop features and functions on the SLES installation? Any suggestions on tweaking the setup?
Desktop 10 RC3 have ATI 9250 card can't enable 3D without system crashing
Anyone hving problems with wifi cards that used to work with Desktop Version 9 which do not work with Desktop 10 RC 3?
Red Carpet Client
ZENworks Linux Management
Remote Desktop Control
SSH Background: How is an X session established?
1) The X windows server and window manager software must be running on your local machine and the remote machine does not need to at run level 5 for you to launch an X application locally.
2) Configure the local machine's X windows server to allow the remote machine to DISPLAY on the local machine
3) Connect to the remote machine
4) Configure the remote machine's X windows client software applications to display on your local machine
5) Start the X windows client software on the remote machine
b) From your local machine connect to the remote system using either X terminal (xterm) or terminal: ssh -X <ip_addr or hostname>
The "-X" option sets up points 2 & 4 above on the remote system for you.
c) Launch the application, e.g. xeyes or "/apps/eclipse/eclipse" or "./eclipse"
Using NX (nomachine)
Although there are a number of ways to control a Linux GUI, give nomachine a go.
1. NX is good because there is only one session to establish. This is especially helpful on VPN connections. If it dies it's a lot less work to get going.
2. NX allows you to resume a session. So you can leave 2-3 terminal windows, browers, apps like Eclipse or other tools as-is and simply continue later.
3. There are other ways to get remote X sessions, e.g. vnc
a. Download the three rpms and EXE if using Windows as the client
b. Install ALL three on the server rpm -i nxclient-3.0.0-89.i386.rpm rpm -i nxnode-3.0.0-93.i386.rpm rpm -i nxserver-3.0.0-79.i386.rpm
c. Install "nxclient-3.0.0-89.i386.rpm" on the Linux workstation or the EXE for Windows
d. Connect to the server. (No config required on the server)
e. The nomachine session will not allow "root" user access, you need to create/use a non-root user account on the Linux machine you need to access, then once connected, use "su" to switch to root IF required.
It's a great way to get at you Lab servers if you're not using a VM Server/XEN and console.
Omni - Desktop Multiplier Turn 1 PC into 10 with the Desktop Multiplier. Ideal for computer labs and classrooms.
How do you think we should break up the articles?