Sponsored Content
Full Discussion: Driver for Lexmark PRO901
Operating Systems Linux Debian Driver for Lexmark PRO901 Post 302514573 by shamused on Saturday 16th of April 2011 07:30:03 PM
Old 04-16-2011
Driver for Lexmark PRO901

I just bought a Lexmark PRO901 printer, for I was told that it was debian compliant.
Upon unpacking I saw mention of Ubuntu.
I thought of returning it but found a site that had
Printer Driver with JRE for 64-bit Debian Package Manager based Distros


What I downloaded was
lexmark-inkjet-legacy-wJRE-1.0-1.amd64.deb.sh_Pro900.tar.gz

edhe@hebrews:~$ file lexmark-inkjet-legacy-wJRE-1.0-1.amd64.deb.sh_Pro900.tar.gz
lexmark-inkjet-legacy-wJRE-1.0-1.amd64.deb.sh_Pro900.tar.gz: gzip compressed data, from Unix, last modified: Thu Dec 16 08:50:19 2010

Can I use it?t
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Lexmark Z22-Z32 desktop inkjet printer installation problem under solaris8

Hello There, I have problem with installing my printer in solaris8, i have Lexmark Z22-Z32 series inkjet printer and i download its driver for solaris from the internet. I got driver file like that... drivers-linux-glibc2-x86.tar.gz first i copy this on my temporary folder and use these... (3 Replies)
Discussion started by: abidmalik
3 Replies

2. Post Here to Contact Site Administrators and Moderators

To Driver

Driver, Are you an admin? I got banned from the board two times! Is this authorized? (13 Replies)
Discussion started by: Computekwes
13 Replies

3. UNIX for Dummies Questions & Answers

Epson Driver

hi i'm new here and my first problem ( and not the last) that i acquired a network laser printer epson epl 6200n and i can't print on it with unix sco5. is there a driver that allow this? thanx (1 Reply)
Discussion started by: zapping
1 Replies

4. SCO

pseudo driver

explain differences between a device driver & a pseudo driver...???? thanks in advance (1 Reply)
Discussion started by: areef4u
1 Replies

5. SCO

Lexmark T632 printer settings

My Lexmark T632 printer is attached to Unix system. Somtimes user change the printer settings. I want to be able to get access the printer setting file. If a user changes the settings and I need to restore the settings to original value, then I can ftp the standard menu setting file. Can anyone... (0 Replies)
Discussion started by: nasirgondal
0 Replies

6. Solaris

SUNWglmr -- rasctrl environment monitoring driver for i2c or SCSI device driver ?

I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies

7. UNIX for Dummies Questions & Answers

boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd

Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
3 Replies

8. Hardware

Difference between platform driver,codec driver and Machine driver

In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

9. Solaris

Database driver

Dear Gurus, I have to install oracle gateway 11g on solaris 10.5 , can any body let me know what is the path for ODBC.ini file in solaris and does solaris provide any generic database driver for all the database or i need to download the odbc driver for particular database. I have to connect... (0 Replies)
Discussion started by: guddu_12
0 Replies
deb(5)								    dpkg suite								    deb(5)

NAME
deb - Debian binary package format SYNOPSIS
filename.deb DESCRIPTION
The .deb format is the Debian binary package file format. It is understood since dpkg 0.93.76, and is generated by default since dpkg 1.2.0 and 1.1.1elf (i386/ELF builds). The format described here is used since Debian 0.93; details of the old format are described in deb-old(5). FORMAT
The file is an ar archive with a magic value of !<arch>. Only the common ar archive format is supported, with no long file name extensions, but with file names containing an optional trailing slash, which limits their length to 15 characters (from the 16 allowed). File sizes are limited to 10 ASCII decimal digits, allowing for up to approximately 9536.74 MiB member files. The tar archives currently allowed are, the old-style (v7) format, the pre-POSIX ustar format, a subset of the GNU format (new style long pathnames and long linknames, supported since dpkg 1.4.1.17; large file metadata since dpkg 1.18.24), and the POSIX ustar format (long names supported since dpkg 1.15.0). Unrecognized tar typeflags are considered an error. Each tar entry size inside a tar archive is limited to 11 ASCII octal digits, allowing for up to 8 GiB tar entries. The GNU large file metadata support permits 95-bit tar entry sizes and negative timestamps, and 63-bit UID, GID and device numbers. The first member is named debian-binary and contains a series of lines, separated by newlines. Currently only one line is present, the format version number, 2.0 at the time this manual page was written. Programs which read new-format archives should be prepared for the minor number to be increased and new lines to be present, and should ignore these if this is the case. If the major number has changed, an incompatible change has been made and the program should stop. If it has not, then the program should be able to safely continue, unless it encounters an unexpected member in the archive (except at the end), as described below. The second required member is named control.tar. It is a tar archive containing the package control information, either not compressed (supported since dpkg 1.17.6), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since 1.17.6) or zstd (with .zst extension, supported since 1.19.0.5ubuntu2), as a series of plain files, of which the file control is mandatory and contains the core control information, the conffiles, triggers, shlibs and symbols files contain optional control information, and the preinst, postinst, prerm and postrm files are optional maintainer scripts. The control tarball may optionally contain an entry for '.', the current directory. The third, last required member is named data.tar. It contains the filesystem as a tar archive, either not compressed (supported since dpkg 1.10.24), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since dpkg 1.15.6), zstd (with .zst extension, supported since 1.19.0.5ubuntu2), bzip2 (with .bz2 extension, supported since dpkg 1.10.24) or lzma (with .lzma extension, supported since dpkg 1.13.25). These members must occur in this exact order. Current implementations should ignore any additional members after data.tar. Further members may be defined in the future, and (if possible) will be placed after these three. Any additional members that may need to be inserted after debian-binary and before control.tar or data.tar and which should be safely ignored by older programs, will have names starting with an underscore, '_'. Those new members which won't be able to be safely ignored will be inserted before data.tar with names starting with something other than underscores, or will (more likely) cause the major version number to be increased. MEDIA TYPE
Current application/vnd.debian.binary-package Deprecated application/x-debian-package application/x-deb SEE ALSO
deb-old(5), dpkg-deb(1), deb-control(5), deb-conffiles(5) deb-triggers(5), deb-shlibs(5), deb-symbols(5), deb-preinst(5), deb-postinst(5), deb-prerm(5), deb-postrm(5). 1.19.0.5 2018-04-16 deb(5)
All times are GMT -4. The time now is 02:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy