Language Selection

English French German Italian Portuguese Spanish

Yoper 3.0 Beta Tested

Filed under
Linux
Reviews
-s

Yoper is a Linux Distribution that takes the best of the best and rolls it into their own 686 optimized system. They released a beta of 3.0, dubbed Blacksand, a few days ago and someone put a little bug in my ear to test it. So we downloaded the iso linked to at Distrowatch and tested it this morning. So, how did Yoper stack up?

Yoper is said to be "a high performance computer-operating system. It has been carefully optimized for PC's with either i686 or higher processor types. The binaries that come with Yoper have been built from scratch combining the original sources with the some of the best features from other Open Source Linux distributions."

They state some of it's features are:

  • The base system is built from scratch.

  • Package management via rpm and smart-pm
  • Kudzu Hardware recognition from Red Hat.
  • as well as from KNOPPIX / KANOTIX
  • Firefox and Thunderbird from Mozilla.org.
  • Hwsetup from Knoppix.
  • KDE 3.5
  • Apt tools from Debian.

The yoper iso as downloaded is a traditional install cd. When it boots, one is given the choice of installing using text-based or gui-based. I chose the gui-base. This opens a unique install environment and starts the installer. The install environment is a drastically scaled-down kde with even a kde toolbar at the top of the screen. From there I could open a konsole and start ksnapshot to get wonderful real-time screenshots of the install.

        

The installer is also rather unique. It has some features that remind of redhat's/fedora's in a way, and some others that remind of kanotix's some. I suppose it is an original tool. It walks one through the basic setup configurations and installs the system onto your hard drive. My only problem with it was it only saw the first 9 partition on each of my hard drives. This limitation put me to a disadvantage as my swap partition is located at hda11 and the desired target partition was hda25. Well, it saw an old swap at hdb7 and I installed over a system that should have an update soon that was installed on hda7. One is given the opportunity to assign a /home and /boot partition if so desired at this same screen. Click install and off it goes.

        

The system installed in about 15 minutes and asked if we should configure a bootloader or do it manually later. I chose manually later. At that point I was asked to setup a root password. After the install one is asked for their language, to setup a new root password (yep, again), and a(n) user account. This is followed by timezone settings, alsa configuration, and X config.

Upon boot one is greeted by a graphical login screen with a lovely background of red balls stamped with an uppercase Y. I logged into kde and noticed the nice wallpaper and great looking icons. What I did not get was a kicker. I opened konsole and could get it to start with no problems. After logging out and back in, kicker still did not start with the desktop. I put a link in my .kde/Autostart folder. Not the correct or even the best method probably, but it works. It appears that we are in a complete KDE 3.5.0 desktop although not all of the kde apps are in the menu. The menu update tool tried to start from the menu, but didn't. So, I'm sure there are plenty of other apps installed that are not listed in the menu.

Besides all the usual kde applications, Yoper includes Firefox 1.5, Thunderbird, gaim, amarok, juk, koffice, xchat, gftp and smart package tool. The only problems apps I found here was the kde menu updater, kb3, and xmms, which would not open. Woefully missing even from the smart repository was OpenOffice.org and mplayer.

        

They include apt and rpm in order for their smart package manager to work and it does. It works wonderfully. My only complaint is that the repository is somewhat lacking in choice of applications. However, it appears that all of gnome is offered for installation.

        

Although I complained about mplayer being missing, kaffine is present. Upon testing, kaffine was found to play mpegs and avi without issue. There were no browser plugins available, but flash installed through firefox in a few seconds.

    

Under the hood we find Xorg-6.8.2, kernel 2.6.15, and gcc-3.4.3. They state the os is optimized for 686 machines, and it really shows here. It felt light-weight, fast and care-free. Apps opened amazingly fast. Firefox opened in about 3 seconds and rendered pages in an equally impressive manner. Of course the kde apps opened instantaneously. Despite this speed, the desktop and apps seemed remarkably stable.

So, all in all I found Yoper to be a great little system and even in this early beta state offers great usability, stability and performance. It's great looking with some wonderful artwork and icons. It could use a few more apps and plugins, but overall, I liked it a lot. Yoper 3.0 is gonna be a fantastic desktop system, I can tell already. More Screenshots.


Yoper

This is a very important release for Yoper, as it marks the transition from what was essentially a one-person (Andreas) project to a community driven distro, since Andreas seems to have moved on to Suse special projects instead. This, and the large number of changes (such as the new installer) explain the long time between releases. There might be a few rough edges at the moment, but remember this is only the first beta. I hope Yoper 3 will be a good one!

re: Yoper

Interesting tidbit! Thanks for contributing.

That would have made a great paragraph in the article. Big Grin

----
You talk the talk, but do you waddle the waddle?

re: Why you can and me no?

Well, my first boot looked for livecd and switched to runlevel 6, but when I asked in the forum how to get around it, I was told to rm /etc/rc5.d/S99Yoper. And that fixed it.

Other notes: I do my own lilo from my gentoo install and I installed onto ext3 filesystem. So, I didn't have some of the issue I saw reported.

----
You talk the talk, but do you waddle the waddle?

re: Thanks

Thank you for the extra info.

gcc --version reported the 3.4.3. In smart, nothing showed installed. Tongue So, I went with the gcc --version. info.

Wonderful KDE news as well! That's great.

Thanks again for the input.

----
You talk the talk, but do you waddle the waddle?

Yoper 3.0 CD

Hi guys,

I am quite amazed with the reviews and like to test yoper 3.0
Does anyone has the link for that?

Another thing whereever I find yoper3.0 ftp server, I get versions like rocketfuel, velocity , and all.
I awant to know what is it all about. Does it mean that separate teams are building yoper and testing them???

My hardware system is Pentium IV 3.0 GHz, with D101 MotherBoard, and currently I am using Suse 10.0, I would like to know if Yoper ll perform better on my machine or Suse in terms of speed.

I need only kdewebdev, gftp, openoffice/koffice, thunderbrd, audio/video, apache, MySql packages and dont need those long list of packages of Suse.

So my Yoper system with only these packages ll perform better I think.

Whjat do you guys say???

Thanks in Advance.

Rohit Arora
Xaprio Solutions
http://xaprio.com

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Programming: WebAssembly, Mozilla GFX, Qt and Python

  • WebAssembly for speed and code reuse

    Imagine translating a non-web application, written in a high-level language, into a binary module ready for the web. This translation could be done without any change whatsoever to the non-web application's source code. A browser can download the newly translated module efficiently and execute the module in the sandbox. The executing web module can interact seamlessly with other web technologies—with JavaScript (JS) in particular. Welcome to WebAssembly. As befits a language with assembly in the name, WebAssembly is low-level. But this low-level character encourages optimization: the just-in-time (JIT) compiler of the browser's virtual machine can translate portable WebAssembly code into fast, platform-specific machine code. A WebAssembly module thereby becomes an executable suited for compute-bound tasks such as number crunching. Which high-level languages compile into WebAssembly? The list is growing, but the original candidates were C, C++, and Rust. Let's call these three the systems languages, as they are meant for systems programming and high-performance applications programming. The systems languages share two features that suit them for compilation into WebAssembly. The next section gets into the details, which sets up full code examples (in C and TypeScript) together with samples from WebAssembly's own text format language.

  • Mozilla GFX: moz://gfx newsletter #47

    Hi there! Time for another mozilla graphics newsletter. In the comments section of the previous newsletter, Michael asked about the relation between WebRender and WebGL, I’ll try give a short answer here. Both WebRender and WebGL need access to the GPU to do their work. At the moment both of them use the OpenGL API, either directly or through ANGLE which emulates OpenGL on top of D3D11. They, however, each work with their own OpenGL context. Frames produced with WebGL are sent to WebRender as texture handles. WebRender, at the API level, has a single entry point for images, video frames, canvases, in short for every grid of pixels in some flavor of RGB format, be them CPU-side buffers or already in GPU memory as is normally the case for WebGL. In order to share textures between separate OpenGL contexts we rely on platform-specific APIs such as EGLImage and DXGI. Beyond that there isn’t any fancy interaction between WebGL and WebRender. The latter sees the former as a image producer just like 2D canvases, video decoders and plain static images.

  • The Titler Revamp: QML Producer in the making

    At the beginning of this month, I started testing out the new producer as I had a good, rough structure for the producer code, and was only facing a few minor problems. Initially, I was unclear about how exactly the producer is going to be used by the titler so I took a small step back and spent some time figuring out how kdenlivetitle worked, which is the producer in use. Initially, I faced integration problems (which are the ones you’d normally expect) when I tried to make use of the QmlRenderer library for rendering and loading QML templates – and most of them were resolved by a simple refactoring of the QmlRenderer library source code. To give an example, the producer traditionally stores the QML template in global variables which is taken as a character pointer argument (which is, again, traditional C) The QmlRenderer lib takes a QUrl as its parameters for loading the Qml file, so to solve this problem all I had to do was to overload the loadQml() method with one which could accommodate the producer’s needs – which worked perfectly fine. As a consequence, I also had to compartmentalise (further) the rendering process so now we have 3 methods which go sequentially when we want to render something using the library ( initialiseRenderParams( ) -> prepareRenderer( ) -> renderQml( ) ) [...] The problem was resolved (thank you JB) finally and it was not due to OpenGL but it was simply because I hadn’t created an QApplication for the producer (which is necessary for qt producers). The whole month’s been a steep curve, definitely not easy, but, I enjoyed it! Right now, I have a producer which is, now, almost complete and with a little more tweaking, will be put to use, hopefully. I’m still facing a few minor issues which I hope to resolve soon and get a working producer. Once we get that, I can start work on the Kdenlive side. Let’s hope for the best!

  • How to Make a Discord Bot in Python

    In a world where video games are so important to so many people, communication and community around games are vital. Discord offers both of those and more in one well-designed package. In this tutorial, you’ll learn how to make a Discord bot in Python so that you can make the most of this fantastic platform.

  • Qt Visual Studio Tools 2.4 RC Released

    The Visual Studio Project System is widely used as the build system of choice for C++ projects in VS. Under the hood, MSBuild provides the project file format and build framework. The Qt VS Tools make use of the extensibility of MSBuild to provide design-time and build-time integration of Qt in VS projects — toward the end of the post we have a closer look at how that integration works and what changed in the new release. Up to this point, the Qt VS Tools extension managed its own project settings in an isolated manner. This approach prevented the integration of Qt in Visual Studio to fully benefit from the features of VS projects and MSBuild. Significantly, it was not possible to have Qt settings vary according to the build configuration (e.g. having a different list of selected Qt modules for different configurations), including Qt itself: only one version/build of Qt could be selected and would apply to all configurations, a significant drawback in the case of multi-platform projects. Another important limitation that users of the Qt VS Tools have reported is the lack of support for importing Qt-related settings from shared property sheet files. This feature allows settings in VS projects to be shared within a team or organization, thus providing a single source for that information. Up to now, this was not possible to do with settings managed by the Qt VS Tools.

Screenshots/Screencasts: 10 GNU/Linux Distros (Screenshots) and New Screencast/Video of Endeavour OS 2019.08.17

  • 10 Linux distros: From different to dangerous

    One of the great benefits of Linux is the ability to roll your own. Throughout the years, individuals, organizations, and even nation states have done just that. In this gallery, we're going to showcase some of those distros. Be careful, though. You may not want to load these, or if you do, put them in isolated VMs. We're not kidding when we say they could be dangerous.

  • Endeavour OS 2019.08.17 Run Through

    In this video, we are looking at Endeavour OS 2019.08.17.

A Cycle of Renewal, Broken: How Big Tech and Big Media Abuse Copyright Law to Slay Competition

In 1950, a television salesman named Robert Tarlton put together a consortium of TV merchants in the town of Lansford, Pennsylvania to erect an antenna tall enough to pull down signals from Philadelphia, about 90 miles to the southeast. The antenna connected to a web of cables that the consortium strung up and down the streets of Lansford, bringing big-city TV to their customers — and making TV ownership for Lansfordites far more attractive. Though hobbyists had been jury-rigging their own "community antenna television" networks since 1948, no one had ever tried to go into business with such an operation. The first commercial cable TV company was born. The rise of cable over the following years kicked off decades of political controversy over whether the cable operators should be allowed to stay in business, seeing as they were retransmitting broadcast signals without payment or permission and collecting money for the service. Broadcasters took a dim view of people using their signals without permission, which is a little rich, given that the broadcasting industry itself owed its existence to the ability to play sound recordings over the air without permission or payment. The FCC brokered a series of compromises in the years that followed, coming up with complex rules governing which signals a cable operator could retransmit, which ones they must retransmit, and how much all this would cost. The end result was a second way to get TV, one that made peace with—and grew alongside—broadcasters, eventually coming to dominate how we get cable TV in our homes. By 1976, cable and broadcasters joined forces to fight a new technology: home video recorders, starting with Sony's Betamax recorders. In the eyes of the cable operators, broadcasters, and movie studios, these were as illegitimate as the playing of records over the air had been, or as retransmitting those broadcasts over cable had been. Lawsuits over the VCR continued for the next eight years. In 1984, the Supreme Court finally weighed in, legalizing the VCR, and finding that new technologies were not illegal under copyright law if they were "capable of substantial noninfringing uses." Read more

Software, HowTos and Storage

  • Pause Music When Locking The Screen And Resume On Unlock For Spotify, Rhythmbox, Others

    When you lock your computer screen (without suspending the system), most desktop audio players continue playback in the background, sometimes not emitting any sound ¹. Due to this you may unintentionally skip parts of podcasts or songs in a playlist, etc. Enter pause-on-lock, a Bash script that pauses your music player when you lock the screen and resumes playback once the screen is unlocked. pause-on-lock works on Unity, GNOME, Cinnamon and MATE desktop environments, and by default it supports Spotify and Rhythmbox. With the help of playerctl (a command line controller for controlling media players that support the MPRIS D-Bus interface), this script can extend its supported music players to many others, including Audacious, VLC, Cmus, and others.

  • Easy Way to Screen Mirroring Android on Ubuntu!

    Screen Mirroring is one of the features found on smartphones, one of which is on Android. This feature serves to display the smartphone to a computer. This is very useful for example when used for demo applications that you make, or maybe for other things related to smartphones. In Ubuntu, we can do screen mirroring with applications available on Android, for example is AirDroid which can be used for screen mirroring through a browser. But I feel less optimal when using this instant method. Because there is a lag between activity on the smartphone and on the monitor screen on the computer, and the results are less than optimal. What might be the cause because it is opened through a browser and uses wi-fi? (Personal question). I am looking for another application for screen mirroring on Ubuntu, and one of the very good applications is Scrcpy. This application can be used for screen mirroring without a root device.

  • Command line quick tips: Searching with grep
  • How to Install Cezerin on Debian 9
  • How to Create a Bootable USB Stick from the Ubuntu Terminal
  • How to Install Git on Debian 10
  • How to Copy/Move a Docker Container to Another Host
  • Six practical use cases for Nmap
  • The Next Stage of Flash Storage: Computational Storage
  • NAS upgrade

    At some point in the future I hope to spend a little bit of time on the software side of things, as some of the features of my set up are no longer working as they should: I can't remote-decrypt the main disk via SSH on boot, and the first run of any backup fails due to some kind of race condition in the systemd unit dependencies. (The first attempt does not correctly mount the backup partition; the second attempt always succeeds).

  • Storage Concepts And Technologies Explained In Detail