Oracle linux ��������� gnome
Your search did not match any results.
We suggest you try the following to help find what you’re looking for:
- Check the spelling of your keyword search.
- Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
- Try one of the popular searches shown below.
- Start a new search.
Oracle Linux is free to download, use and distribute and is provided in a variety of installation and deployment methods.
- Installation media (ISO images) for Oracle Linux are freely available from Oracle Linux yum server or Oracle Software Delivery Cloud.
- Individual RPM packages for released versions of Oracle Linux as well as update/errata packages can be obtained from the Oracle Linux yum server. Learn What’s New.
- Follow the instructions to verify Oracle Linux downloads.
- For troubleshooting and analysis of system workloads, you can use DTrace for Oracle Linux.
Developer Preview
- Oracle Container Runtime for Docker and Oracle Container Service for use with Kubernetes have been frequently updated with preview builds available on the ol7_preview repository.
- Developer Previews of Oracle Linux 7 and Oracle Linux 8 are periodically updated
- An Oracle Linux 7 and Oracle Linux 8 Arm disk image for use on Raspberry Pi™ 4 Model B and Raspberry Pi™ 3 Model B/B+ hardware is available for developers who may not have access to alternate Arm hardware.
The developer preview releases are for development and test purposes only and are not covered by Oracle Linux support. Oracle does not recommended using preview releases in production. If you have any questions, please visit Oracle Linux Community.
Additional Downloads
- Oracle Linux Docker images on the Docker Hub
- Oracle Linux Vagrant Boxes
- Pre-Built Developer VMs for Oracle VM VirtualBox for development and evaluation purposes
- Thousands of EPEL packages, signed and built by Oracle, have been added to Oracle Linux yum server. Learn What’s New.
Related Solutions and Features
For Linux system administrators
For Developers
For Database Administrators
Источник
A few questions about Gnome 3 in OEL 7
The default desktop environment in OEL 7 is Gnome 3 (gnome-session and gnome-classic-session). Working with Gnome 3 however is very frustrating and distracting. Putting aside the fact that Linux is more and more windowizing every day, to me Gnome 3 looks like a sadistic spartan edition of Windows 8. Unbelievable! They changed everything what worked before. Unless I am badly missing something, it can be said that Gnome 3 is almost useless for any serious work on OEL 7 server and it shouldn’t have taken the place in RHEL 7 and RHEL 7 based server distributions anyway.
Is there any way to customize and setup one decent, usable and functional desktop? How to create application launchers on desktop without writing .desktop files manually? How to create application launchers on menu and taskbar panels? How to create additional panels?
I would like to make this clear before getting rid of Gnome 3 from the system and installing MATE-Desktop instead.
Thanks a lot in advance.
Best Answer
Wow, that’s quite a post. Oracle Linux ships with all the packages provided by the upstream distribution from which we are derived. This includes both the GNOME and KDE Desktop Environments. There are no plans on Oracle’s part to remove these packages, but we cannot forsee the roadmap of the upstream distribution.
I don’t quite understand what you mean about «Oracle’s policy» — we have no policy about the purpose of our distro. We have an engineering focus to provide the best possible server distribution, but that doesn’t preclude you from using Oracle Linux as a desktop, if that’s what you chose.
So yes, you’re right: Oracle Linux can be used as a desktop/workstation or server. In fact, within Oracle itself, Oracle Linux is one of the supported desktop environments for Oracle employees. However, from an Oracle Linux engineering perspective, the majority of our testing is done with Oracle Linux running without a GUI as a pure server, as this is how it is deployed at the vast majority of our customers. There is no such thing as «Oracle Linux Server», it’s all Oracle Linux. The role completely depends on the packages you install.
However, the Oracle Unbreakble Enterprise Kernel (UEK) is designed for server-class hardware, not desktops or laptops. Therefore, it is missing several graphics and network interface drivers that are specific to desktop/laptop hardware, e.g. wifi and embedded GPUs. If you are running on this sort of hardware, you would probably have better luck running the RHCK instead, because the drivers are either more likely to be included or are more likely to be available from the hardware vendor.
On the other hand, if you DO have server-class hardware, the UEK is more aligned with the mainline Linux kernel, therefore it has improvements for server-style workloads, including better scheduling, memory support, filesystem scaling, network throughput, etc. Things that are not as critical for desktop/workstation workloads.
At the end of the day, you have a choice: you can absolutely run Oracle Linux as a desktop (I do, and I have for a while). You can also run it as a server (I do, and have for a while). But you need to understand that our focus from an engineering perspective is to make Oracle Linux the best possible server operating system, because that’s what our customers want. If you want a Linux-based desktop or workstation, there are far better options available.
Answers
Linux Enterprise never had an extremely useful or attractive GUI Desktop interface. Whether it is Gnome 2 or 3 or anything else, it always seems minimalistic and incomplete. If you wish to rely on a sophisticated and complete graphical desktop interface to manage your server, then Enterprise Linux is not your best option. The strengths and primary focus of Unix and Linux servers are not the user interface, but to maximize resource utilization and processing power, while relying on most versatile and minimalistic administration tools. I’m not saying this cannot be done with a graphical user interface, but it requires a different skills.
I would not suggest to install a GUI destkop other than what comes with the system or what is supported by the vendor. It depends on your purpose and IT background, but you won’t find a lot of useful and reliable GUI admin tools in the end. You can however run GUI tools and applications without installing a graphical desktop system, and instead execute X-Window applictions using SSH with X forwarding or VNC.
Really? And what are you supposed to run to get the GUI if you don’t run KDE or Gnome?
Since I’ve installed Oracle’s Linux 7 — Gnome doesn’t run, KDE has problems, no Xfce, and R (which took forever to install) does not work (can’t install packages).
To us it is no good.
In order to run a GUI application you do not need KDE or Gnome. GUI applications under Linux and Unix are based on the X-Window client/server architecture. To run a GUI application the system needs access to a X-Window server. You do not need a GUI Desktop. The X-Window server needs to be physically connected to your screen and keyboard when using SSH with X11 forwarding, or you can use VNC, which provides a minimal X Window system and works similar to screen sharing.
You may find the following previous posts interesting, which should help you to understand the various concepts:
Unlike the Windows world, a Linux server (as Catch-22 says) doesn’t need a GUI. All of the graphical tools are still usable, either via VNC or via X11 forwarding. By not running the GUI on the server, you’re significantly reducing your overall install footprint, which makes ongoing maintenance easier (less packages to update) and overall security better (less potential security flaws).
I strongly recommend investigating VNC in the first instance (which requires some X running on the server) and X11 forwarding (which requires far less running on the server).
Also note that R installs just fine on OL7 and I answered your question about that in another thread. It just requires the enabling of a non-default channel (ol7_optional_latest).
Certainly pure text console and a few ncurses/readline command line utilities to manage the server would be an ideal environment from the “low footprint” point of view. But even that is not possible anymore with modern kernel implementations utilizing Kernel Modesetting (KMS) and frame buffer console. Starting with kernel 2.6.29 we definitely lost the good old pure text console and even when we talk about “text mode”, we are talking about graphics. The fb console is significantly slower than pure text console that can still be seeing only when grub is loaded or when the BIOS setup screen is entered. With introduction of systemd and awfully confusing, distracting and non-unix-like systemctl syntax, and by getting rid of System V, the daemons are gone, the units-targets-services are here. Welcome on the board. Linux is desperately windowized and we are all in Redmond’s balloons now. In two or three years, I guess, we will have to deal with “registry” or something alike.
All in all, the questions like – whether the VNC is recommended solution for server or not — are a little bit misleading in this context. Gnome 3 is the legal Redhat’s choice for default desktop in RHEL 7 server and is legally shipped with it. It has many ‘pros’ and only one ‘cons’ – it is useless. In order to please myself, I’ve just installed MATE-Desktop and right now I am customizing it. MATE is fast, fully functional and looking awesome. You can see three screenshots of my MATE desktop on top of OL7.1 server attached to this post.
Kernel mode setting is required for displaying a high resolution startup screen, but you can disable it by adding the «nomodeset» kernel parameter. You can also change the startup screen to see all text if you prefer. Regarding your comments about the text console, the Linux console traditionally used the hardware VGA-compatible text mode. I haven’t tried recently, but you can most likely still change your console using some vga=xxx kernel parameter. But why would you want to? I hardly remember using the Linux console and always connect using SSH.
The concept of the sysv init obviously had it’s limits and was modernized by upstart in RHEL 6 and systemd in RHEL 7. For the better or worse, things change, but I do not share your opinion about Linux getting «windowized». I’m used to command line, but I would not despise a useful GUI. Unfortunately however you won’t find many GUI enthusiasts in the Linux or Unix community. Oracle Linux, like all RHEL based Linux systems is a server system and I would not see a good reason to use such OS for a desktop purpose — there are certainly better options.
I agree with both Avi and Catch-22. Remote X over ssh or vnc are the better options for servers even if a GUI is needed.
Something to keep in mind as well about server hardware. Due to the fact that servers spend most of their time in racks with no video output connected the chipsets in the video cards are often not as cutting edge as the ones found in a workstation class machine. This alone is a good reason not to run a GUI directly on the server and to use a workstation to remote display graphics as needed.
I would still like to be able to log onto my server with my X-windows software and have the same experience I do from the console. Unfortunately, in Oracle 7, when connected to my server via X-windows, gnome fails completely with an composite acceleration problem and in KDE the pointer does not work properly.
These all worked fine in other installations, so I don’t want her hear discussions about how I don’t want to have a GUI interface. What I would like are real solutions.
Thanks in advance,
Are you aware of the reasons and purpose why there are different Linux distributions? Why did you install Enterprise Linux if you want a Desktop system? Perhaps you will have a better time if you use the right tool for the right purpose.
The ‘nomodeset’ parameter? It is not working for my card. I was already tired and sick of experimenting with those video/vga kernel/grub boot parameters in my OL6 period. The ‘nomodeset’ and ‘vga=normal’ do not satisfy my requirements. Here is why.
I have AMD/ATI workstation video card and 24” monitor with 1920×1200 pixels resolution (16 : 10 aspect ratio, not 16 : 9). The best and most appropriate driver for this card is vendor’s legacy fglrx driver maintained regularly and downloadable from vendor’s site as the source package that builds the driver on user’s machine and generates rpm binary package for installation on various linux distros (for RHEL7 as well). As the driver is built as kernel .ko module, it must be rebuilt with each and every one kernel update for both uek and rhel compatible kernels. During the installation the package automatically blacklists the default X.Org radeon driver as it interferes with fglrx. They are mutually exclusive. If fglrx driver is installed, the system boots in native VGA 80×25 text mode as the driver is not loaded during the boot. It is loaded only at runtime when X11 is started and the screen appears in full 1920×1200 resolution. When I exit X11, the driver is unloaded and I am again in native vga text mode console that is extremely fast compared to KMS/radeon frame buffer console. Although both drivers works fine in X11 (radeon only with KMS), fglrx graphics is evidently faster and X11 starts and exits faster with fglrx. Unfortunately, these advantages (native vga text console and faster graphics) are not worth of wasting the time on rebuilding the driver for both kernels each time when one or both kernels are updated, keeping that in mind and thinking about it. That’s the reason I permanently switched to system’s X.Org radeon driver and KMS.
Unlike fglrx however, the radeon driver is loaded immediately at boot time, regardless of whether the ‘nomodeset’ and ‘vga=normal’ are put in the kernel command line or not. If they are, the KMS is off and the system boots in normal text mode, but when I ‘startx’, the desktop screen appears in 1280×1024 resolution mode that is maximal resolution if KMS is off, with deformed and extremely slow desktop graphics. That’s because X.Org doesn’t have appropriate driver to be loaded at X11 runtime as the development of those drivers has been abandoned to the care of kernel KMS development. So, those parameters are useless and the system is always booted with KMS. In order to at least simulate the normal text mode, the ‘video’ parameter is set to ‘video=DVI-I-2:720×400’.
Well, was I right? Is the good old native vga text console definitely lost for linux world? They certainly can change that in the future, but I don’t think so.
Источник
