ebiso is needed by Relax-and-Recover (abbreviated ReaR)
to create bootable ISO images with enabled UEFI boot
on 64-bit x86_64 architecture.

ebiso only works for systems with UEFI boot.
ebiso cannot create legacy bootable ISOs.

See project pages at https://gitlab.com/gozora/ebiso

Relax-and-Recover (abbreviated rear) is the leading
Free Software disaster recovery framework.

Relax-and-Recover is written entirely in the native
language for system administration: as bash scripts.

Experienced users and system admins can adapt or extend
the rear scripts to make it work for their particular
cases.

Relax-and-Recover is a modular framework with
ready-to-go workflows for common situations.

The basic workflow is as follows:
Specify its configuration in /etc/rear/local.conf
(cf. /usr/share/rear/conf/examples) and run
"rear mkbackup" to create a backup.tar.gz on
a NFS server and a bootable recovery ISO image
for your system.
A recovery medium which is made from the ISO image
boots a special rear recovery system.
Log in as root and run "rear recover" which does
the following steps:
It runs the rear installer that recreates the basic
system, in particular the system disk partitioning
with filesystems and mount points, then it restores
the backup from the NFS server and finally it
installs the boot loader.
Finally remove the recovery medium and reboot the
recreated system.

Relax-and-Recover supports various kind of boot media
for the recovery system (incl. ISO, PXE, OBDR tape,
USB or eSATA storage), a variety of network protocols
(incl. sftp, ftp, http, nfs, cifs) for storage and backup
as well as various external third-party backup methods
(incl. IBM Tivoli Storage Manager, HP DataProtector,
Symantec NetBackup, EMC NetWorker, FDR/Upstream,
NovaBACKUP DC, Bareos, Bacula, rsync, rbme).

Warning for users who like to upgrade Relax-and-Recover:
Users who already use it must re-validate that their
particular disaster recovery procedure still works.

Additionally when you already use Relax-and-Recover and
you upgrade software that is related to the basic system
(e.g. kernel, storage, bootloader, init, networking) or
you do other changes in your basic system, you must also
re-validate that your particular disaster recovery
procedure still works for you.

You must test in advance that it works in your particular
case to recreate your particular system with your
particular recovery medium and that the recreated system
can boot on its own and that the recreated system with
all its system services still work as you need it in your
particular case.

You must have replacement hardware available on which your
system can be recreated and you must try out if it works
to recreate your system with your recovery medium on your
replacement hardware.

Be prepared that your system recovery fails to recreate
your system. When it fails to recreate your system
it is usually a dead end. Be prepared for a manual
recreation from scratch. Always have all information
available that you need to recreate your particular
system manually. Manually recreate your system on your
replacement hardware as an exercise.

For more information see
http://en.opensuse.org/SDB:Disaster_Recovery

Relax-and-Recover comes with ABSOLUTELY NO WARRANTY;
for details see the GNU General Public License.

Relax-and-Recover is the leading Open Source disaster recovery and system migration solution, and successor to mkcdrec. It comprises of a modular framework and ready-to-go workflows for many common situations to produce a bootable image and restore from backup using this image. As a benefit, it allows to restore to different hardware and can therefore be used as a migration tool as well.

ebiso is needed by Relax-and-Recover (abbreviated ReaR)
to create bootable ISO images with enabled UEFI boot
on 64-bit x86_64 architecture.

ebiso only works for systems with UEFI boot.
ebiso cannot create legacy bootable ISOs.

See project pages at https://gitlab.com/gozora/ebiso

This project hosts all graphics related software, such as viewers, tools for manipulating images, capturing and such stuff.

It is a devel project for openSUSE:Factory.

Home Project of Johannes Meixner
http://en.opensuse.org/User:Jsmeix

This is my personal playground where
packages could be severely incompatible
with official openSUSE packages.

Do not somehow add the whole "home:jsmeix"
repository to be used by your package
installer (e.g. via zypper or YaST).
Using the whole "home:jsmeix" repository
could be a perfect way to mess up your
system.
Instead only download the packages
of your particular interest which match
your exact system from the appropriate
sub-directory in
http://download.opensuse.org/repositories/home:/jsmeix/
and install them manually
(e.g. using plain "rpm").
If you are unexperienced with manual
installation, do not install any package
from "home:jsmeix".

Packages in the "home:jsmeix" project might
neither be in usable state nor fit into
currently installed systems.
Have this in mind if you think about to
install packages from "home:jsmeix" into
your currently running system.
Do not use "Factory" if your system is
not "Factory".
Use the matching packages for your
particular system.
The packages in the "home:jsmeix" project
are only for testing, without any guarantee
or warranty, and without any support.
As an extreme example, this means if your
complete computer center crashes because
of those packages, it is only your problem.
On the other hand this does not mean that
all those packages are known to be terrible
broken (but some of those packages could
be really broken) and none of those packages
are thoroughly tested so that any unexpected
issue can happen.

This project was created for package dockerfile-application-container via attribute OBS:Maintained

This project was created for package ipp-usb via attribute OBS:Maintained

The Common UNIX Printing System provides a portable printing layer for
UNIX operating systems like BSD lp or lprng. CUPS provides some
additional features.

http://www.cups.org

This package contains free additional backends for CUPS.

The print filter "foomatic-rip" is used
by print spoolers (in particular by CUPS)
to convert PostScript print job data into
the printer's native format as described
by a printer/driver-specific Foomatic PPD file.

GNU awk is upwardly compatible with the System V Release 4 awk. It is
almost completely POSIX 1003.2 compliant.

This package contains all start-up files for calling gs (GNU
Ghostscript).

Find some useful documentation about a few printer drivers in the
directory:

/usr/share/doc/packages/ghostscript-library/doc/

For mor informations please read the files Use.htm and Devices.htm.

SuSE internal replacement for ghostscript-library and ghostscript-any
(Ghostscript)

The grep command searches one or more input files
for lines containing a match to a specified pattern.
By default, grep prints the matching lines.

The Gutenprint (formerly Gimp-Print) printer drivers for CUPS.
See the user's manual at /usr/share/gutenprint/doc/gutenprint-users-manual.pdf

The Hewlett-Packard Linux Imaging and Printing project (HPLIP) provides
a unified single and multifunction connectivity solution for HP
printers and scanners (in particular, HP all-in-one devices).

HPLIP provides unified connectivity for printing, scanning, sending
faxes, photo card access, and device management and is designed to work
with CUPS.

It includes the Ghostscript printer driver HPIJS for HP printers and a
special "hp" CUPS back-end that provides bidirectional communication
with the device (required for HP printer device management).

It also includes the SANE scanner driver "hpaio" for HP all-in-one
devices. Basic PC send fax functionality is supported on a number of
devices.

The special "hpfax" CUPS back-end is required to send faxes. Direct
uploading (i.e. without print and scan) of received faxes from the
device to the PC is not supported.

The "hp-toolbox" program is provided for device management.

The "hp-sendfax" program must be used to send faxes.

The "hp-setup" program can be used to set up HP all-in-one devices.

The HPLIP project is open source software and uses GPL-compatible
licenses. For more information, see:

http://hplipopensource.com

/usr/share/doc/packages/hplip/index.html

This version of the Image Scan for Linux software contains only
the free software parts of what Avasys provides.

In particular this version of the Image Scan for Linux software
neither contains any proprietary driver library nor firmware files
nor proprietary software to support scanner network interfaces
nor the proprietary "libesmod" library which would be required
by the "/usr/bin/iscan" frontend which is also not provided.

This package contains only the epkowa driver for SANE, which compiles
and runs natively even on non-i386 platforms. For documentation, see
"man sane-epkowa".

The frontend /usr/bin/iscan was removed because it requires the
proprietary "libesmod" library. This should cause no problem
because the driver epkowa in this version of the Image Scan
for Linux software runs natively even on non-i386 platforms
so that the usual frontends (like scanimage and xsane)
can be used even on non-i386 platforms.

Drawbacks:

The free version of the epkowa driver cannot work for those scanners
that require a proprietary driver library (and a firmware file).
As of this writing (June 2010), those scanners are the following models:

ES-D400, GT-1500, GT-7200U, GT-7300U, GT-9400UF, GT-D1000, GT-F500,
GT-F520, GT-F550, GT-F570, GT-F600, GT-F650, GT-F670, GT-F700,
GT-F720, GT-S50, GT-S80, GT-S600, GT-S620, GT-X750, GT-X770, GT-X820,
Perfection 1250, Perfection 1250 PHOTO, Perfection 1260,
Perfection 1260 PHOTO, Perfection 2480 PHOTO, Perfection 2580 PHOTO,
Perfection 3170 PHOTO, Perfection 3490 PHOTO, Perfection 3590 PHOTO,
Perfection 4180 PHOTO, Perfection 4490 PHOTO, Perfection V10,
Perfection V30, Perfection V100 Photo, Perfection V200 Photo,
Perfection V300 Photo, Perfection V350 Photo, Perfection V500 Photo,
Perfection V600 Photo, Stylus CX4300, Stylus CX4400, Stylus CX5500,
Stylus CX5600, Stylus DX4400

Those models do not work with the free iscan version.
The third-party Image Scan driver software from Avasys
is required for those models.
The Image Scan driver software is made and provided by Avasys
at http://avasys.jp/eng/linux_driver/ where RPM packages
for 32-bit (i386) and 64-bit (x86_64) architecture can be downloaded
(provided you accept the Avasys and Epson license agreements).
The Image Scan driver from Avasys contains proprietary binary-only software.
For some models it is only available for 32-bit (i386) architecture
which does not work when you have a 64-bit system installation.
Some scanners are also supported by another (free-software) driver.
When your scanner model requires a non-free (proprietary) module,
you have to download and install two packages from Avasys:
The 'iscan' package for the base software and an additional
model dependant 'iscan-plugin' package with the proprietary module.

Other scanners may only work via USB but require a proprietary
software package which supports the network interface.
As of this writing (June 2010), those scanners are the following models:

Artisan 710 Series, Artisan 810 Series, EP-702A, EP-802A, EP-902A,
ES-H7200, GT-20000, PX-602F, Stylus Office BX610FW Series,
Stylus Office TX610FW Series, Stylus Photo PX650 Series,
Stylus Photo PX710W Series, Stylus Photo PX810FW Series,
Stylus Photo TX650 Series, Stylus Photo TX710W Series,
Stylus SX610FW Series, WorkForce 610 Series

To use those models via the network interface, you need the above
mentioned third-party Image Scan driver software from Avasys
plus an additional iscan-network-nt package from Avasys
which provides support for the network interface.

Note that the iscan-network-nt package from Avasys does not
provide support for the network interface for all models.
As of this writing (June 2010), the network interface
of the following models is not supported:

AcuLaser CX11NF, AcuLaser CX21, Artisan 700, Artisan 800, EP-801A,
EP-901A, EP-901F, ES-H300, Expression 10000XL,
Expression 10000XL Graphic Arts, Expression 10000XL Photo, GT-2500,
LP-A500, LP-M5000, LP-M5500, LP-M5500F, LP-M5600, LP-M6000,
ME Office 700FW, PM-A840S, PX-501A, PX-601F, Stylus Office BX600FW,
Stylus Office TX600FW, Stylus Photo PX700W, Stylus Photo PX800FW,
Stylus Photo TX700W, Stylus Photo TX800FW, Stylus NX400,
Stylus NX410 Series, Stylus SX400, Stylus SX410 Series,
Stylus SX600FW, Stylus TX400, Stylus TX410 Series, WorkForce 600

This library is intended to be used by applications that need to
communicate with (or at least identify) devices that are attached via a
parallel port.

For Linux, there are some wrinkles in communicating with devices on
parallel ports (see /usr/share/doc/packages/libieee1284/README). The
aim of this library is to take all the worry about these wrinkles from
the application. It figures out which method is appropriate for the
currently running kernel. For instance, if the application wants to
know the device ID of a device on a particular port, it asks the
library for the the device ID. The library then figures out if it is
available via /proc (in any of the possible locations) and, if not,
tries asking the device itself. If /dev/parport0 is not available for
use, it tries ioperm; if that fails, it tries /dev/port. The
application does not have to care.

This is an open source Linux printer driver for the Konica Minolta
magicolor 2300W and 2400W color laser printers. It requires Ghostscript
and foomatic-filters. It is recommended to use this driver with CUPS.

The current version 0.51 was released 2005-10-16 and
the m2300w driver is no longer actively maintained
which means that help, a workaround, or a bugfix
is rather unlikely if there are issues with this driver.

PPD files from printer manufacturers that are under a free license.

For example, the original MIT license, shown for example under
http://www.opensource.org/licenses/mit-license.php, is okay but not an
often used modified MIT license, which does not allow redistribution if
the file was altered in any way from its original form.

If you have a PostScript printer and there is no PPD file included in
this package, ask your printer manufacturer for a PPD file or visit
http://www.linuxprinting.org/ppd-doc.html.

To set up a printer configuration a printer description file
(PPD file) is required.

A printer description file is not a driver.

For non-PostScript printers a driver is needed
together with a PPD file which matches exactly
to the particular driver.

For PostScript printers, a PPD file alone is sufficient
(except for older PostScript level 1 printer models).

The PPD files are provided in the following sub-packages
depending on which kind of driver software is needed:

OpenPrintingPPDs-ghostscript provides PPDs
which use Ghostscript built-in drivers.

OpenPrintingPPDs-hpijs provides PPDs
which use the hpijs driver from HPLIP.

OpenPrintingPPDs-postscript provides PPDs
which need no driver.

This software is a Python library which can prepare IPP requests with
the help of a somewhat high level API. These requests can then be sent
to an IPP printer or print server (e.g. CUPS).

This library can also parse IPP answers received, and create high level
Python objects from them.

Both of these actions can be done through an IPPRequest class and its
instance methods.

Finally, a CUPS class can be leveraged to easily deal with CUPS print
servers.

All of this library being written in the Python language, there is no
need to link the code with the CUPS' API, which makes it independant of
the CUPS version being installed.

Nevertheless some features require an appropriate CUPS version which
supports the functionality (e.g. IPP subscriptions require CUPS 1.2.x).

Python Bindings for CUPS, the Common Unix Printing System

The software consists of SANE scanner drivers, "scanimage," and the
"saned" daemon.

A SANE scanner driver is used via a SANE front-end. This package
contains the command line front-end "scanimage". There are various
graphical front-ends like "xscanimage" (package sane-frontends), XSane
(package xsane), and the KDE front-end Kooka (package
kdegraphics3-scan).

The "saned" daemon provides the service "sane-port" to access scanners
that are connected to a server via network from client hosts that run
the "net" meta driver.