CUPS
Posted: Mon 12 Sep 2005, 14:11
Hi Rarsa,
I
I
READ-ONLY Archive
https://oldforum.puppylinux.com/
Sorry, I didn't read this part.dewdrop wrote:If you could start me out with a step by step after the CD install I'd appreciate it.
There was some missunderstanding here. So. Lets start over... To do the step by step I need the answer to some questions:dewdrop wrote:I know you want me to not load the entire usr.dev file,
Oh, this is not a solved/unsolved kind fo thread, this is a 'working thread' and this 1.0.5 experiment is part of if. Hopefully the last one for this round.dewdrop wrote:I thought you might like to handle the contact with the Moderators to switch this over to the Solved Threads.
It will be some combination of 16 choices I guess (4 items x 4 combinations)...I think that's how it works. That might be a bit tiresome expecially if they have the space on their machines. You might suggest that they download and install all 4 - giving the space requirements as part of the posting.The difficult part for most people will be understanding which drivers to use.
Do you think it would be beneficial to do some kind of step by step? I kind of get the impression that the linux community at large feels that people don't need or want the step by steps. Your guidance to me was invaluable. I would have never figured out how to do some of the steps you were asking me to do, without you telling me "how to" do each step. At least the first time.Looking back the steps are really quite simple, it was just a matter of understanding what they were.
I take it that each of these components is located inside the usr.devx.sfs file - and that whatever Developers need, it is included in that file, or can be included. And that...the existence of the usr.devx.sfs file is what really sets 1.0.5 apart from previous versions of Puppy.I am planning to create one DotPup per component as not everyone will require all of them:
- CUPS
- ESP Gohstscript
- HPIJS drivers
- Perl
No, What the usr_devx.sfs contains are the development tools and libraries to compile programs for Puppy. Some of the tools included in Usr_devx.sfs require Perl, thus it was included.dewdrop wrote:I take it that each of these components is located inside the usr.devx.sfs file
Right now there is a step by step. The DotPups will only put then installers in a Puppy standard format.dewdrop wrote:Do you think it would be beneficial to do some kind of step by step?
Actually the nice part is that the testers are actual users for the most part.dewdrop wrote: and anyone who wanted to act as a tester for the Developers
I did it a long time ago ... You still have to include some perl libs and the program generated isn't small.BarryK wrote:Gee, I wonder if CC can be used to convert ndiswrapper, a Perl program for
setting up wireless networking, to C code?.... I'm probably being too hopeful.
Where is the CUPS-install.tar.gz (site)rarsa wrote:Well,
Finally here it is. I found that it would take me the same time to write the instructions as to write the scritp. I'd recommend you to read the script to understand what I'm doing and maybe find a better way of doing it.
I still need to package all of this in a DotPup.
Notes:
- I will put new versions of the installer in this post. If you have tried a previous version check the change log before trying again.
- I tested this script booting from a chubby puppy 1.0.4 live CD.
- Currently the each of the install scripts download the required files from a slackware mirror. I'm thinking that's the best option for now.
- The configuration files are already configured to work with puppy.
- The script modifies rc.local to start cups at boot time.
- You need about 25 MB of free space to install all the components
- This instructions include the hpijs printer driver as an example. Before proceeding make sure that you have available CUPS printer drivers for your particular printer. You can google to find out.
For a list of printers supported by hpij go to this page http://www.linuxprinting.org/show_drive ... iver=hpijs
The scripts downloads the required packages to /root/tmp
It extracts them to /tmp . This means the following:
- Installation is faster as /tmp is in RAMDISK
- You need enough ram or enough swap space (about 30 MB)
- All temporary files will be lost when you reboot.
Disclaimer
This script is working for me using a pristine pup001 file.
I highly recommend testing with a pristine pup001 file. Don't test in your regular pup001. I am not responsible if you corrupt your pup001 file. An alternative is to backup your pup001 file to test on an already configured and non pristine pup001.
Instructions:
1. Download the cups-install.tar.gz file
2. Open a console terminal and change folders to the folder where you downloaded the file.
3. Untar the cups-install.tar.gz with "tar -xvzf cups-install.tar.gz". This tar file includes the scripts to install cups. ESP Ghostscript and the hpijs driver.
4. From the console execute "sh cups-install.sh"
5. If you are printing to a remote CUPS server go to step 9, otherwise continue with step 6.
6. If your print drivers require ESP Ghost script, execute ""sh espgs-install.sh". (the hpijs driver needs it).
7. Install the CUPS drivers for the printers connected to your puppy computer according to your driver's instructions. Check in http://www.linuxprinting.org to find out the drivers required by your printer. These instructions include the hpijs, if your printer is suported just execute "sh hpijs-install.sh".
8. If your driver requires foomatic, you also need to install Perl. Don't use the Perl PupGet as it is a stripped down version. If you are using puppy 1.0.5 download the usr_devx.sfs file. If you are using a puppy version prior to 1.0.5 downlad the attached perl installer, untar it and instal with "sh perl-5.8.6-install.sh"
9. Restart cups with "sh /etc/rc.d/rc.cups restart"
10. Open your browser and go to the following address http://localhost:631
11. Add your printer following the links on that page. If you already have a CUPS server that allow browsing you will see the shared printers there.
12. Print the test page
It's THAT easy. I took dewdrop and my self about 80 hours to get to this point but we are finally here!
The main problems I encountered were the following:
- Understanding what I was doing as I did not have previous CUPS experience.
- Find a version that ran OK under puppy. (this took almost 15 hours)
- Finding the correct access rights combination for the config files.
- Understanding that I needed ESP Ghostscript.
- Learning that the Perl PupGet did not include all the components required by foomatic.
========== Change log ==========
Oct 6, 2005 11:51 pm EST
- Added comment to use usr_devx.sfs in puppy 1.0.5 to access perl.
Sept 12, 2005 11:22 pm EST
- Added Full Perl Installation. Final instructions.
Sept 8, 2005 11:22 pm EST
- Inserted new step to install Perl when the driver requires foomatic.
Sept 4, 2005 8:31 pm EST
- Cleaned up the configuration file cupsd.conf
Sept 3, 2005 2:37 pm EST
- Added the hpijs printer driver which supports hundreds of printers from many brands.
- Created separate scripts for CUPS, ESP Ghostscript and the hpijs driver.
- Packaged all the scripts and configuration files in one download.
- Changed the protocol for the wget from HTTP to FTP. Now the download is faster.
- The scripts now download the packages to /root/tmp so you don't have to redownload them every time.
- The script will continue with a failed download when you re-run it.
Sept 3 ,2005 2:19 am EST
- First post
Ok .rarsa wrote:It is not a site. It is a file I created with the scripts to install CUPS.
The file is an attachment in the post that you just quoted.
Unfortunately, although the downloaded packages are saved locally, re-running the scripts will download them once again instead of using the local copies. The scripts should look first to see if local copies are present (e.g. in the same directory as the scripts) before ftp'ing once again.rarsa wrote: - The scripts now download the packages to /root/tmp so you don't have to redownload them every time.