RE: Printer driver for Samsung CLP-415-NW on SL7 (solved)

2014-11-14 Thread John Rowe
Samsung's unified driver uld_v1.00.06.tar.gz, available from
http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=UNI_UKCttFileID=2041645CDCttType=DRModelType=NModelName=CLX-3175VPath=DR/201310/20131024133933517/uld_v1.00.06.tar.gz

contains a CLP-410 ppd file, I don't know if that is the same one
shipped with RH7.

John


RE: Printer driver for Samsung CLP-415-NW on SL7

2014-11-14 Thread Bill Maidment
Thanks everyone for the suggestions. I didn't try copying anything from SL6 to 
SL7; maybe I had in the past installed the Samsung Unified Linux Driver.
Anyway the newer SULD seems to have done the trick.
Two small problem with the installation was that I had to stop firewalld and 
CUPS failed to restart (probably because of the systemd changes).

Regards
Bill Maidment 
 
-Original message-
 From:Karel Lang AFD l...@afd.cz
 Sent: Friday 14th November 2014 20:52
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: Re: Printer driver for Samsung CLP-415-NW on SL7
 
 Hi Bill,
 did you just try to copy the ppd file you're using on the 6 to 7 and 
 test result?
 
 cheers,
 -- 
 *Karel Lang*
 *Unix/Linux Administration*
 l...@afd.cz | +420 731 13 40 40
 AUFEER DESIGN, s.r.o. | www.aufeerdesign.cz
 
 On 11/14/2014 05:10 AM, Bill Maidment wrote:
  Hi
  I have been using a Samsung colour printer CLP-415-NW on SL6 using the 
  recommended CLP-310 series driver with good results.
  On SL7, the driver recommended (the only one shown) is CLP-410 series, but 
  this only prints in black and white.
  Has anyone found a colour version that will work on SL7?
 
  Regards
  Bill Maidment
  Landline: +61 2 4472 9374
  Mobile: +61 418 682 993
  Web: www.maidment.me
 
 
 
 
 
 


RE: Printer driver for Samsung CLP-415-NW on SL7 (solved)

2014-11-14 Thread Bill Maidment
That should have read now i CAN print in colour.
Sorry for the confusion!!

Regards
Bill Maidment 
 
-Original message-
 From:Bill Maidment b...@maidment.me
 Sent: Friday 14th November 2014 17:39
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: RE: Printer driver for Samsung CLP-415-NW on SL7 (solved)
 
 Well I found UnifiedLinuxDriver-4.00.39.tar.gz and installed it with 
 compat-libtiff3.
 Now I can't print in colour.


Re: Printer driver for Samsung CLP-415-NW on SL7

2014-11-14 Thread Matt Lewandowsky
As the Samsung CLP series are not PCL or Postscript, you need more than just a 
PPD. 

There are really three choices:

1: Samsung model specific driver.

2: Samsung Universal Print Driver (UPD). 

3: Open source foo2qpdl driver. 

The first option is generally best, especially if your printer has a unique 
feature of some sort that you use often as the UPD will quite usually hide the 
unique options in a layer of UI. This is not an option for many models, 
especially running Linux. 

The UPD is especially great if you are printing to multiple Samsung printers. 
‎It almost always is updated more often than a model-specific driver, and that 
is the case on all supported platforms (not just Linux). It is also a better 
choice if you will be installing on a shared system where the users are 
familiar with the UPD on Windows as most of their knowledge maps cross-platform 
with this driver. 

As for the open source option… I understand foo2qpdl gives awesome output, 
especially for open source. Unfortunately, the author is actively hostile to 
packaging his drivers. As I am not a fan of leaving unpackaged files outside 
/home (ok, and maybe /etc and /opt and /var… you got me…), that makes this an 
option that is personally unpalatable. This is unfortunate, as he is 
effectively turning away patches and other development assistance. But everyone 
has their own needs and desires and approaches in open source. The foo2qpdl 
home page is at ‎http://foo2qpdl.rkkda.com/ for those who have fewer qualms 
than I do about unpackaged files and/or have a stronger need or desire to use 
an open source answer. 

I realize that this is far more than you likely hoped (or cared to receive) as 
an answer. But I am hopeful that future archive searchers will find this reply 
and that it will still be relevant. :)

Matt

-- 
Matt Lewandowsky
Big Geek
Greenviolet
m...@greenviolet.net http://www.greenviolet.net
+1 415 578 5782 (US) +44 844 484 8254 (UK)
Sent from my BlackBerry 10 smartphone.
From: Karel Lang AFD
Sent: Friday, 14 November 2014 01:49
To: Bill Maidment; SCIENTIFIC-LINUX-USERS@FNAL.GOV
Subject: Re: Printer driver for Samsung CLP-415-NW on SL7

Hi Bill,
did you just try to copy the ppd file you're using on the 6 to 7 and 
test result?

cheers,
-- 
*Karel Lang*
*Unix/Linux Administration*
l...@afd.cz | +420 731 13 40 40
AUFEER DESIGN, s.r.o. | www.aufeerdesign.cz

On 11/14/2014 05:10 AM, Bill Maidment wrote:
 Hi
 I have been using a Samsung colour printer CLP-415-NW on SL6 using the 
 recommended CLP-310 series driver with good results.
 On SL7, the driver recommended (the only one shown) is CLP-410 series, but 
 this only prints in black and white.
 Has anyone found a colour version that will work on SL7?

 Regards
 Bill Maidment
 Landline: +61 2 4472 9374
 Mobile: +61 418 682 993
 Web: www.maidment.me




smime.p7s
Description: S/MIME cryptographic signature


Scientific Linux LiveCD/DVD 6.6 officially released

2014-11-14 Thread Urs Beyerle

Hi,

Scientific Linux 6.6 LiveCD, LiveMiniCD and LiveDVD are officially released.
They are available for 32-bit and 64-bit and come with following window manager

LiveMiniCD icewm
LiveCD gnome
LiveDVDgnome, kde, icewm

Software was added from rpmforge, epel and elrepo (see EXTRA SOFTWARE) to 
include
additional filesystem support (ntfs, reiserfs), secure network connection 
(openvpn,
vpnc, pptp), filesystem tools (dd_rescue, ddrescue, gparted, gdisk), and better
multimedia support (gstreamer-ffmpeg, flash-plugin)


DOWNLOAD

- http://ftp.scientificlinux.org/linux/scientific/6.6/i386/iso
- http://ftp.scientificlinux.org/linux/scientific/6.6/x86_64/iso
Or
- http://ftp.scientificlinux.org/linux/scientific/livecd/66/i386
- http://ftp.scientificlinux.org/linux/scientific/livecd/66/x86_64

Alternatively use a public mirror
http://www.scientificlinux.org/downloads/sl-mirrors/


CHANGES SINCE SL6.5 LIVE

- software based on SL6.6
- gnome-applets, gnome-utils, evince, ghostscript, poppler and some fonts
were removed from LiveCD(still available on the LiveDVD)


NOTES

- For SL6 the way how the LiveCD was built has completely changed. It is
  now based on the Fedora LiveCD tools.
- If you install the LiveCD to hard drive, the installation of the live
  image is done by anaconda similar to the normal SL6 installation.
  All changes done during LiveCD usage are lost!
- You can install the LiveCD on an USB stick with persistent changes using
  liveusb-creator included in sl-addons:
yum --enablerepo=sl-addons install liveusb-creator
- To build your own LiveCD use livecd-tools from sl-addons:
yum --enablerepo=sl-addons install livecd-tools


EXTRA SOFTWARE (repo sl-livecd-extra)

- fuse-sshfs
- ntfs-3g
- ntfsprogs
- dd_rescue
- ddrescue
- iperf
- flash-plugin
- gstreamer-ffmpeg
- rxvt-unicode (only MiniCD)
- gparted
- gdisk
- NetworkManager-openvpn
- NetworkManager-vpnc
- NetworkManager-pptp
- vpnc-consoleuser
- kmod-reiserfs
- reiserfs-utils


BOOT PARAMETERS

- live_ram copy entire Live image to RAM (takes a few minutes)
- noswap   do not use SWAP partition found on hard drive
- pw=any_password  set password
- noautologin  disable auto login
- automountenable auto mounting (rw) of all found hard drives
- user=usernameusername of local user, default is liveuser
- cups=server  set CUPS server
- hostname=nameset hostname
- checkverify LiveCD before booting
- liveinst directly start graphical installation to hard drive
- textinst directly start text based installation to hard drive
- overlay=UUID=defines the UUID of the USB device used for persistent 
overlay
- rdinitdebug  debug dracut boot process
- ejecteject LiveCD/DVD at shutdown


More information can be found at http://www.livecd.ethz.ch

Urs Beyerle


Re: SL 7 install network drivers

2014-11-14 Thread Konstantin Olchanski
On Wed, Nov 12, 2014 at 09:35:47AM -0600, Stephen Berg (Contractor) wrote:
 I have a desktop system with Nvidia MCP55 ethernet chipset. ...

Yes, I noticed this, too.

SL7 installer did not see the network on an ASUS A8N-E based
machine (NVidia chipset and NVidia 1GigE ethernet).

We still have several of these machines and no plans to retire them,
they work just fine. Replacement could be $300 AMD socket AM1 machines.

Lack of driver in the installer is not a big deal - I do the installations
from USB flash, no need for network.

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada


Re: Anyone want my Wine compile notes?

2014-11-14 Thread David Sommerseth
On 13/11/14 21:30, ToddAndMargo wrote:
 Do you know how to use 'mock'? Can you RPM
 wrap it, or work from the older RPM's to update them and build them
 with 'mock', so you get a clean list of the dependencies in the .spec
 file?
 
 Hi Nico,
 
 Sadly, I don't know how.

A very quick and rough mock crash course, purely from my memory and it
may contain some errors.

yum install mock

Then ensure you become member of the new 'mock' group.

rpm -hvi $SRC_RPM

Then edit ~/rpmbuild/SPECS/$package.spec file with your modifications.
Look for the %setup section, where %configure often is a macro for
running ./configure.  But arguments to %configure are passed on further
to ./configure.

rpmbuild -bs  ~/rpmbuild/SPECS/$package.spec

This should give you a src.rpm in ~/rpmbuild/SRPMS/$package

To run a mock build, do this:

  mock --rebuild $SRC_RPM -r $CONFIGNAME

$CONFIGNAME can for example be epel-7-x86_64.  When it has completed (or
failed), you can find the results in /var/lib/mock/ with complete
build logs and all packaged RPMs if it was successful.

All defalt configs packaged with mock can be found in /etc/mock.  You'll
see an extensive list of Fedora and EPEL here.  Might even find
addtional ones for CentOS or SL other places too.  The point is that
using this method you can easily build packages for many distros in a
safe and correct manner, without too much worries.  All builds happens
in a mock chroot with the proper compiler and libraries installed for
that distro.

For anyone who haven't played with mock, I can highly recommend it!


-- 
kind regards,

David Sommerseth