Open Printing



  • works on the development of new printing architectures, technologies, printing infrastructure, and interface standards for Linux and UNIX-style operating systems.
  • collaborates with IEEE-ISTO Printer Working Group (PWG) on IPP projects.
  • is working with SANE to make IPP scanning a reality.
  • maintains cups-filters which allows CUPS to be used on any Unix-based (non-macOS) system.
  • is responsible for the Foomatic database.
  • is working on Common Print Dialog Backends project.

Installing Plex Media Server on openSUSE Leap 15

Unfortunatelly, there is no version of openSUSE that is supported by the Plex Media Server.

This tutorial assumes the following:

  1. you have a current version of openSUSE Leap 15
  2. have basic knowledge of Linux systems

Steps to take to install PlexMediaServer(PMS) on openSUSE Leap 15:

  1. download PMS for CentOS 64 bit from
  2. verify the file is not corrupted
    1. run sha1sum on the downloaded file and compare it with the SHA-1 Checksum provided
  3. download the gpg key from
    1. $ wget
  4. move the gpg key to the /var/cache/zypp/pubkeys
    1. $ sudo mv PlexSign.key /var/cache/zypp/pubkeys
  5. install PMS using zypper
    1. $ sudo zypper in plexmediaserver-
  6. installation will fail with an error specifying chown: invalid group: ‘plex:plex’
    1. the installation fails because the plex group does not exit
    2. the group plex is missing and before we continue, we must create it
    3. before we create a new plex group, lets make sure that:
      1. plex group indeed does not exist
      2. we have a plex user available
      3. ## list all users 
        $ cat /etc/passwd 
        plex:x:458:100:RPM Created PlexUser:/var/lib/plexmediaserver:/sbin/nologin
        ## list all groups 
        $cat /etc/groups
    4. if you don’t see a plex group, lets create one
      1. ## in this case I am explicitly giving the plex group 
        ## a group ID of 458, to match the user ID.
        ## if the group ID is not available, you can choose to
        ## omit the -g option, and have the OS pick a new ID.
        $ sudo groupadd -g 458 plex
    5. verify that the plex user and group exist
    6. add plex user to the plex group
      1. $ usermod -aG plex plex
    7. PMS needs to have access to the following directory:
      1. /var/lib/plexmediaserver
      2. we are going to change the ownership tp plex:plex
        1. $ sudo chown -R plex:plex /var/lib/plexmediaserver
          ## by default, the plex user has write permission to the directory
          ## by default, the plex group has no rite permission, only read and execute
    8. now the installation is complete, we can enable and start the plex service
        1. ## enable the plex service
          $ sudo systemctl enable plexmediaserver.service
          ## start the plex service
          $ sudo systemctl start plexmediaserver.service
          ## check to make sure the service is running
          $ sudo systemctl status plexmediaserver.service
    9. configure your new Plex Media Server
    10. go to http://localhost:32400/web
    11. congratulations!

Note: openSUSE Leap 15 “server” mode (no GUI)

If you install Plex Media Server on openSUSE Leap 15 in “server” mode you might get the following error when trying to enable the plex service:

/sbin/insserv: No such file or directory

If that happens install the following package:

$ sudo zypper in insserv-compat-0.1-lp150.2.1.noarch


Enable root login via SSH on Linux/Unix systems

Most Linux/Unix systems have root login disabled by default.

It is a huge security risk to allow root login via SSH, so if for some particular reason you need root login via SSH, enable it temporarily to perform need tasks, then disable it right away to secure your system.


  • go to Services -> SSH config
  • enable Login as Root with password
  • OK to save


  • edit the /etc/ssh/sshd_config file
    • $ sudo nano /etc/ssh/sshd_config
  • set PermitRootLogin yes
  • restart sshd
    • $ systemctl restart sshd

For more information on sshd_config settings read the man page.

Firmware update for iDRAC6 on Dell PowerEdge R710

This tutorial is for iDRAC on a Dell PowerEdge R710.

Get the latest firmware for the iDRAC from Dell Support.

Go to -> Support -> Drivers & Downloads -> Choose from all Products -> View Products -> Servers, Storage, & Networking -> PowerEdge -> PowerEdge R710 -> Category -> Embedded Server Management -> Dell iDRAC Monolithic Release.

The latest version as of May 18th, 2018 is 2.90.

Click on the latest driver to expand the view and then click on View full driver details.

From Available formats download the:

  • Release Notes — read this before updating the firmware
  • Application format file: iDRAC6_2.90_A00_FW_IMG.exe

Note: if you run Microsoft Windows on your server, you can download the ESM_Firmware file designed to run on MS Window 64-bit Operating Systems

For this tutorial iDRAC6 is being upgraded via the iDRAC Web GUI.

Run the file to unzip. The firmware file is called firmimg.d6. Read the release notes before upgrading the firmware.

Login into the iDRAC.

Go to iDRAC Settings -> Update -> Firmware Update and click on the Browse button to select the firmware file, then click on Upload.

Screen will display File upload in progress … (wait until completed!; it will take a while)

Make sure the Current Version is lower than the New Version.

Preserve iDRAC Configuration Settings checkbox should be checked.

Click Next button to proceed with the firmware upgrade or Cancel to cancel the upgrade. Click Yes to confirm.

Wait until the upgrade is complete at 100%.

You don’t have to reboot the server. Close the browser window and reconnect to the iDRAC using a new browser session.

Congratulations! You are done.



Java error: Unsigned application requesting unrestricted access to sytem

Starting with Java version 8 Update 131, Oracle decided to treat applications that are signed with the MD5withRSA or MD5withDSA algorithms as unsigned, therefore JNLP (Java Network Launch Protocol) with not run them.

When I try to access one of my Dell servers via the iDRAC interface, I get this error:

The reason for this is that the application was signed with a weak cryptographic algorithm (such as MD5witRSA ) and Java will not run the application due to security reasons since it sees it as unsigned.

To allow applications signed with a weak cryptographic algorithm to run, you need to disable jdk.jar.disabledAlgorithms property in the Java master security properties file, called Do this at your own risk!

The file is located in C:\Program Files\Java\jre1.8.0_171\lib\security folder for the 64-bit systems and C:\Program Files (x86)\Java\jre1.8.0_171\lib\security folder for the 32-bit systems.

To edit the file you must Run as administrator your favorite text editor, then open the file. Comment out the jdk.jar.disabledAlgorithms property and save the file.

Restart your browser and connect again. This time, the JNLP should run the application.