Linux-Misc Digest #60, Volume #28                 Fri, 8 Jun 01 11:13:02 EDT

Contents:
  Re: rpm build only get one source (Alien Guest)
  Re: Setup an DHCP server ! ("KW")
  Re: Setup an DHCP server ! (Kevin Croxen)
  ppp-problems with RedHat 6.2 (Lee Allen)
  Re: GROUP TAKEOVER IN PROGRESS (Shawn Michael Taub)
  Re: hardware autodetection (aykat sue)
  Re: Announce: CNCC -- Color Name Combination Center ([EMAIL PROTECTED])
  Re: X-server access problem in RH 7.1 (nordi)
  Re: Setup an DHCP server ! ("root")
  Re: "no rule to make bzimage" (Jim)
  System.map deleted by mistake ("Tom Edelbrok")
  Re: hardware autodetection ("Peter T. Breuer")
  Re: Setup an DHCP server ! ("Lam Dang")
  Re: Matt Blaze's CFS on Linux - readdir problem. (Kevin Buhr)
  linux and the modem -- a little help? (Cary Kittrell)
  Re: Replicating Linux computers ([EMAIL PROTECTED])
  Re: Print to a PDF ([EMAIL PROTECTED])
  Re: Print to a PDF (Sebastien Stormacq)
  Re: hardware autodetection (Bill Vermillion)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Alien Guest)
Subject: Re: rpm build only get one source
Date: Fri, 08 Jun 2001 13:07:54 GMT

On Fri, 08 Jun 2001 14:14:11 +0200, Christopher Albert
<[EMAIL PROTECTED]> wrote:

>Alien Guest wrote:
>> 
>> I am now to linux.
>> 
>> I am writing an installer (rpm). Follow the www.rpm.org/how-to, I have
>> three sourced in the spec:
>> 
>> Source0: some.tar
>> Source1: another.tar
>> Source2: last.tar
>> 
>> all three .tars are in the /usr/src/redhat/SOURCES/
>> 
>> however, when run "rpm -ba myspec.spec", only the source0 gets untared
>> to the BUILD dir.
>> 
>> I have read the doc, it seems very simple, and there is no need (or
>> just can not) specify how many sources I need.
>> 
>> I even tried to specify BuildRoot.
>> 
>> Any suggesion may help.
>> 
>> Thanks in advance.
>> 
>> -Alien
>> 
>> -Alien
>
>Alien,
>
>There are some complicated macros behind the setup directive in the spec
>file.
>You really should get MaximumRPM at the www.rpm.org site and read this
>book. The
>chapters on package building will take you through some examples that
>will get
>you started. There is not much more I can say, since I have no idea of
>what these
>tar files of yours do, or what kind of directory structure is necessary
>for your build.
>You probably have to have a line for each of your sources as well as the
>appropriate
>swithces to the %source macro to get them unpacked in the right places.
>
>The book is very good.
>
>
>Chris
Thanks, I think that helps. Have downloaded the ps file. :-)


-Alien



-Alien

------------------------------

From: "KW" <[EMAIL PROTECTED]>
Subject: Re: Setup an DHCP server !
Date: Fri, 08 Jun 2001 08:19:05 -0500

/var/log/messages will have some info on why DHCP is or isn't working..  

The one thing I see for sure that is different between your config and mine is
the range section...  here is what I have...

range dynamic-bootp 192.168.254.1 192.168.254.10;

Also looking at mine.. it starts out on first line...  
subnet 192.168.254.0 netmask 255.255.255.0 {

then ALL of my information is listed and then at the very end on the last line
is the closing }

I believe you need to specify the information for your subnet between the brackets....
  All in all the options look correct, I think they are just out of order for
the most part...

--
KW



In article <9fqgn0$gkq$[EMAIL PROTECTED]>, "root" <[EMAIL PROTECTED]>
wrote:

> Hi,
> 
> I want to setup an dhcp server on Redhat 7.1. I installed the
> dhcp-2.0p15-4.rpm package delivered with RedHat CDROM.
> 
> Here is my /etc/dhcpd.conf :
> #
> default-lease-time 600;
> max-lease-time 7200;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255; option routers 192.168.1.1;
> option domain-name-servers 192.168.1.2, 194.2.0.20, 194.2.0.50; option
> netbios-name-servers 192.168.1.2; option domain-name "company.com";
> 
> subnet 192.168.1.0 netmask 255.255.255.0 {
>  range 192.168.1.6 192.168.1.100;
> }
> #
> 
> I also created an /var/lib/dhcp/dhcpd.leases
> 
> The daemon started without error message, but my Windows 95/98 NT clients
> can't get their IP address !
> 
> I also started the dhcpd deamon with -d -f flags. But i didn't see anything.
> 
> Anybody have an idea ?
> Thanks for your answer.
> Minh
> 
>

------------------------------

From: [EMAIL PROTECTED] (Kevin Croxen)
Subject: Re: Setup an DHCP server !
Date: 8 Jun 2001 13:17:26 GMT

On the Linux box, use the route command to add the following route:

255.255.255.255

and see whether things suddenly get better for the windows clients. 

--Kevin



In article <9fqgn0$gkq$[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
>Hi,
>
>I want to setup an dhcp server on Redhat 7.1.
>I installed the dhcp-2.0p15-4.rpm package delivered with RedHat CDROM.
>
>Here is my /etc/dhcpd.conf :
>#
>default-lease-time 600;
>max-lease-time 7200;
>option subnet-mask 255.255.255.0;
>option broadcast-address 192.168.1.255;
>option routers 192.168.1.1;
>option domain-name-servers 192.168.1.2, 194.2.0.20, 194.2.0.50;
>option netbios-name-servers 192.168.1.2;
>option domain-name "company.com";
>
>subnet 192.168.1.0 netmask 255.255.255.0 {
> range 192.168.1.6 192.168.1.100;
>}
>#
>
>I also created an /var/lib/dhcp/dhcpd.leases
>
>The daemon started without error message, but my Windows 95/98 NT clients
>can't get their IP address !
>
>I also started the dhcpd deamon with -d -f flags. But i didn't see anything.
>
>Anybody have an idea ?
>Thanks for your answer.
>Minh
>
>

------------------------------

From: [EMAIL PROTECTED] (Lee Allen)
Subject: ppp-problems with RedHat 6.2
Reply-To: [EMAIL PROTECTED]
Date: Fri, 08 Jun 2001 13:33:27 GMT

I am having problems establishing a ppp connection under RedHat 6.2.
I used linuxconf to configure the ppp interface.
I connect using: 'ifup ppp0'
Sometimes (maybe one time out of three, or four) it connects okay.
Other times I get this sequence in /var/log/messages:

chat[2093]:  -- got it 
I am having problems establishing a ppp connection under RedHat 6.2.
I used linuxconf to configure the ppp interface.
I connect using: 'ifup ppp0'
Sometimes (maybe one time out of three, or four) it connects okay.
Other times I get this sequence in /var/log/messages:

chat[2093]: send (^M)
chat[2093]:  -- got it 
chat[2093]: send (^M)
pppd[2084]: Serial connection established.
pppd[2084]: Using interface ppp0
pppd[2084]: Connect: ppp0 <--> /dev/modem
pppd[2084]: local  IP address 204.32.178.109
pppd[2084]: remote IP address 163.179.93.14
pppd[2084]: local  IP address 204.32.178.109
pppd[2084]: remote IP address 163.179.93.14
pppd[2084]: Hangup (SIGHUP)
pppd[2084]: Modem hangup
pppd[2084]: Connection terminated.
pppd[2084]: Connect time 0.2 minutes.
pppd[2084]: Sent 292 bytes, received 387 bytes.
pppd[2084]: Exit.

See the 2 sets of local & remote IP addressess?  When it succeeds, I
see only one set.

Any ideas?

-Lee Allen


------------------------------

From: [EMAIL PROTECTED] (Shawn Michael Taub)
Crossposted-To: alt.drugs.pot,comp.lang.javascript,comp.lang.perl.misc,comp.lang.python
Subject: Re: GROUP TAKEOVER IN PROGRESS
Date: 8 Jun 2001 06:35:42 -0700

The mere fact you don't know makes me want to take of every 'zig'.  A
little help, you need.

http://hubert.retrogames.com/article.php?sid=1
http://members.nbci.com/finagler/base/
http://www.newgrounds.com/frames.php?location=/collections/ayb.html

For Great Justice.

------------------------------

From: [EMAIL PROTECTED] (aykat sue)
Crossposted-To: alt.os.linux,comp.unix.bsd.freebsd.misc
Subject: Re: hardware autodetection
Date: 8 Jun 2001 06:38:21 -0700

[EMAIL PROTECTED] wrote in message news:<9fq1je$uud$[EMAIL PROTECTED]>...
> Wroot <[EMAIL PROTECTED]> wrote:
> > Hi
>  
> > How come Debian and FreeBSD do not autodetect hardware the way Windows, Mandrake
> > and Redhat do? How am I supposed to know which cryptic kernel modules I should
> > enable and with which parameters?
> 
> This is false. I dont know Debian, but FreeBSD autodetects hardware.
> If i do ifconfig xl0 IP number, the xl driver will be loaded automatically.
> Without having to edit an /etc/module.conf.
> Redhat uses a special program kudzu which probes hardware at boot and
> writes the modules.conf file. This program i think can be compiled on Debian 
> and used to the same goal.
> But not knowing you have a 3Com card in your box is plain stupid. As for
> Windows, i can say you i have spent hours to make it use a 3com card.
> So saying that their autodetection is the best thing in the world is
> also plain false.
> 

What hardware are you trying to detect? ISA or PCI
If you want help give more "Information"  :-(

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: comp.lang.tcl,comp.os.linux.x,comp.windows.x,comp.emacs
Subject: Re: Announce: CNCC -- Color Name Combination Center
Date: 8 Jun 2001 13:37:33 GMT
Reply-To: [EMAIL PROTECTED]


According to * Tong *  <[EMAIL PROTECTED]>:
:Have you ever wondered what the standard X-window color names are?
:Have you been bothered by the fact that the color combination you
:picked was not what you were imaging? Then worry no more. The color
:mysteries terminator is here: the CNCC -- "Color Name Combination
:Center", my free X-window color picker.

Neat.  Also, were you aware that if you do a look up of the Tk man page
"colors" in section n, you also get the information?

-- 
-- 
"See, he's not just anyone ... he's my son."  Mark Schultz
<URL: mailto:[EMAIL PROTECTED]> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting

------------------------------

From: nordi <[EMAIL PROTECTED]>
Subject: Re: X-server access problem in RH 7.1
Date: Fri, 8 Jun 2001 15:51:55 +0200

Andrew wrote:

> In our xinetd.conf everything seems to be okay - What are some possible or
> likely candidates for mistakes in this file? We CAN telnet into the box
> from itself, this is why I think telnetd is installed and running. How can
> I check if it is running or not?
> 
If you can telnet into your box with "telnet localhost" then telnetd is 
running. You can always check with "ps ax | grep telnetd" which will show 
the command itself and the telnetd if its running.
With telnet you have to login as a normal user, not root, maybe that's the 
problem?

> No, both machines are on the LAN behind the firewall. Is it possible
> RedHat is setting up its own firewall and not allowing telnet access from
> a remote computer?

I don't think RH sets up a firewall by default. Maybe you have played 
around with the /etc/hosts.* files and messed something up. Does the 
"connection failed" message appear when using the remote X-server or telnet?

Why don't you simply try ssh, maybe that works.

nordi

-- 
Linux - Less bugs for less bucks!

Visit http://private.addcom.de/nordi

------------------------------

From: "root" <[EMAIL PROTECTED]>
Subject: Re: Setup an DHCP server !
Date: Fri, 8 Jun 2001 15:50:10 +0200

I followed everything explained in the howto !
And i also did this command before starting dhcpd server.
But it's still not work !

Minh

Kevin Croxen <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On the Linux box, use the route command to add the following route:
>
> 255.255.255.255
>
> and see whether things suddenly get better for the windows clients.
>
> --Kevin
>
>
>
> In article <9fqgn0$gkq$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
wrote:
> >Hi,
> >
> >I want to setup an dhcp server on Redhat 7.1.
> >I installed the dhcp-2.0p15-4.rpm package delivered with RedHat CDROM.
> >
> >Here is my /etc/dhcpd.conf :
> >#
> >default-lease-time 600;
> >max-lease-time 7200;
> >option subnet-mask 255.255.255.0;
> >option broadcast-address 192.168.1.255;
> >option routers 192.168.1.1;
> >option domain-name-servers 192.168.1.2, 194.2.0.20, 194.2.0.50;
> >option netbios-name-servers 192.168.1.2;
> >option domain-name "company.com";
> >
> >subnet 192.168.1.0 netmask 255.255.255.0 {
> > range 192.168.1.6 192.168.1.100;
> >}
> >#
> >
> >I also created an /var/lib/dhcp/dhcpd.leases
> >
> >The daemon started without error message, but my Windows 95/98 NT clients
> >can't get their IP address !
> >
> >I also started the dhcpd deamon with -d -f flags. But i didn't see
anything.
> >
> >Anybody have an idea ?
> >Thanks for your answer.
> >Minh
> >
> >



------------------------------

From: [EMAIL PROTECTED] (Jim)
Subject: Re: "no rule to make bzimage"
Date: 8 Jun 2001 13:51:39 GMT

In article <3b205478$0$62143$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
>Also, kernel 2.2.14 is a few months behind the times.  The latest stable
>version is kernel 2.2.19, and the 2.4 series is just about ready for
>prime time.  (Just MHO, 2.4.5 has so far shown none of the weird
>joystick, sound, or VIA chipset problems that plagued earlier 2.4
>kernels for me.)

Which Via chipsets have had problems? I'm running the Via Apollo chipset
on an Abit KT7A-RAID motherboard using kernel 2.4.2. So far, anyway, it
seems well behaved ...

Jim
remove not for email


------------------------------

From: "Tom Edelbrok" <[EMAIL PROTECTED]>
Subject: System.map deleted by mistake
Date: Fri, 08 Jun 2001 14:03:08 GMT

I accidentally wiped out my /boot/System.map file, (it was size 196625, and
dated April 19, 1999). It is for kernel 2.2.5-15 (Redhat 6.0).

The system was still up and running however, so I did a locate on
"System.map" and found another one labelled /boot/System.map-2.2.5-15 of
size 180770 and dated with today's date. So I copied this file into
/boot/System.map.

I then rebooted and the system came up successfully, but complained many
times along the way that /boot/System.map pointed to a wrong kernel version.

So far everything seems to run OK.

Is there some way I can regenerate a proper System.map without rebuilding
the kernel?

Thanks,
Tom



------------------------------

From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.unix.bsd.freebsd.misc
Subject: Re: hardware autodetection
Date: Fri, 8 Jun 2001 15:58:13 +0200

In comp.os.linux.misc Wroot <[EMAIL PROTECTED]> wrote:
> How come Debian and FreeBSD do not autodetect hardware the way Windows, Mandrake

Why should they?

> and Redhat do? How am I supposed to know which cryptic kernel modules I should
> enable and with which parameters?

No parameters, and the module for your hardware, whoch you'll find out
because you know what your hardware is, and you can read the names of
the supported hardware in the kernel code comments, or else the
manufacturer supplied a driver with the card. If the manufacturer
didn't, complain to him! What is this? You buy a card without
researching whether it's supported by anyone? Huh!

Peter

------------------------------

From: "Lam Dang" <[EMAIL PROTECTED]>
Subject: Re: Setup an DHCP server !
Date: 08 Jun 2001 09:57:16 -0400

>From "root" <[EMAIL PROTECTED]> on Fri, 8 Jun 2001 14:33:42 +0200:

> Hi,
> 
> I want to setup an dhcp server on Redhat 7.1.
> I installed the dhcp-2.0p15-4.rpm package delivered with RedHat CDROM.

[...]

> The daemon started without error message, but my Windows 95/98 NT clients
> can't get their IP address !

One possibility is your RH 7.1 firewall.
Check your ipchains for ports 67 and 68 and
try opening them up as follows:

# bootp & dhcp
-A input -s 0/0 67:68 -d 0/0 67:68 -p udp -i eth0 -j ACCEPT

-- 
Lam Dang
dangit AT ix DOT netcom DOT com

------------------------------

From: [EMAIL PROTECTED] (Kevin Buhr)
Crossposted-To: 
comp.os.linux.security,comp.os.linux.development.apps,comp.os.linux.development.system
Subject: Re: Matt Blaze's CFS on Linux - readdir problem.
Date: 08 Jun 2001 09:10:33 -0500

"Binesh Bannerjee" <[EMAIL PROTECTED]> writes:
>
>       if you read a large CFS directory with readdir it doesn't get
> all of the files, but readdir64 will work... Has anyone else
> had this problem, and if so, how do I go about fixing it?

It's a kernel/C-library bug that's difficult to fix completely.  The C
library does some fancy double-buffering in getdents(2) and so must
occassionally lseek on directories behind the scenes.  When reading
from NFS filesystems whose files have large (>0x8000000) NFS cookies,
it will occassionally issue directory lseeks to negative offsets
without checking for an error return value.  This is highly dependent
on internal C library buffer sizes, and will result in silently
disappearing files that vary from application to application.  For
NFSv2, you can fix this particular problem by having the C library
llseek in this situation; for NFSv3---where the cookies are 64 bits,
it'll still be broken

Note that this isn't normally a data-destroying bug---your files are
still there; it's just that some applications won't "see" some files.
"rm -rf" might give you a mysterious "directory not empty"; or after a
"mv * elsewhere", you might be surprised to discover the current
directory is still full of files that were missed on the first pass.

There's more on this in a "linux-kernel" thread with subject:

        negative NFS cookies: bad C library or bad kernel?

dated December 2, 2000.

The easiest fix is to modify CFS to use small NFS cookies.  CFS
actually uses small host-endian cookies that, on little-endian
architectures, become large cookies in NFS space.  This isn't a CFS
*bug*: cookies are supposed to be arbitrary.  However, it just happens
to tickle this Linux bug, and we can "fix" it by having CFS convert
cookie values to network byte order.

I've enclosed a patch against Debian CFS 1.3.3-9; it will apply
against vanilla CFS 1.3.3 with some fuzz.  Note that this modification
won't introduce any compatibility problems with existing or new CFS
directories---it only changes the values of the temporary cookies
passed between the CFS server and the kernel, not anything to do with
the CFS storage format.  As always, test on a trash CFS directory
before trying it on your pr0n collection or anti-government tract
archive.

Kevin <[EMAIL PROTECTED]>

                        *       *       *

diff -ru cfs-1.3.3/cfs_nfs.c cfs-1.3.3-new/cfs_nfs.c
--- cfs-1.3.3/cfs_nfs.c Wed Jun  6 00:37:40 2001
+++ cfs-1.3.3-new/cfs_nfs.c     Wed Jun  6 00:34:34 2001
@@ -873,7 +873,7 @@
        ne=0;
        prev= &ret.readdirres_u.reply.entries;
        *prev=NULL;
-       bcopy(ap->cookie,&cookie,sizeof(cookie));
+       cookie = ntohl(*(unsigned long*)(ap->cookie));
        eof=TRUE;
        
        key=keyof(h);
@@ -910,7 +910,7 @@
                else if (strcmp(s,"..")==0)     /* parent */
                        entrytab[ne].fileid=fhpid(h);
                else entrytab[ne].fileid=dent->d_fileno;
-               bcopy(&cookie,entrytab[ne].cookie,sizeof(long));
+               *(unsigned long*)entrytab[ne].cookie = htonl(cookie);
                *prev = &entrytab[ne];
                prev = &entrytab[ne].nextentry;
                entrytab[ne].nextentry=NULL;
@@ -1127,7 +1127,7 @@
        ne=0;
        prev= &ret.readdirres_u.reply.entries;
        *prev=NULL;
-       bcopy(ap->cookie,&cookie,sizeof(long));
+       cookie = ntohl(*(unsigned long*)(ap->cookie));
        eof=1;
        
        ret.status=NFS_OK;
@@ -1146,7 +1146,7 @@
                else entrytab[ne].fileid=dent->d_fileno;
                cookie=dent->d_reclen;  /* may not work everywhere */
                *prev = &entrytab[ne];
-               bcopy(&cookie,entrytab[ne].cookie,sizeof(long));
+               *(unsigned long*)entrytab[ne].cookie = htonl(cookie);
                prev = &entrytab[ne].nextentry;
                entrytab[ne].nextentry=NULL;
                ne++;

------------------------------

From: [EMAIL PROTECTED] (Cary Kittrell)
Crossposted-To: comp.os.linux,linux.redhat.misc
Subject: linux and the modem -- a little help?
Date: 8 Jun 2001 13:20:32 GMT

I'm having to do some remote development work for a client
who, for reasons of security, will only permit me access
via modem, no ethernet connections allowed (oh, don't
even ask...).  They know nothing of Unix or Linux
at their end -- NOTHING -- and so set up a PC for
me to log onto via modem, a PC running Windoze NT.

I, a decades-long Unix user, screamed long enough
and piteously enougth that they finally found someone at 
their facility who had actually heard of Linux, and who 
will be installing Redhat Linux on this PC for me.

My question: can someone tell me of any software out
there which will drive a modem under Linux?  Though,
as mentioned, I have been using Unix since the 
late Ordivician, we have Sun stations around here,
and so I myself have not used Linux yet.  Thus
the naivte of my question.  Please be gentle.

And thanks in advance.




--
cary kittrell                         the truth is out there
steward mirror lab                    but the X-files are more fun.
university of arizona



------------------------------

From: [EMAIL PROTECTED]
Subject: Re: Replicating Linux computers
Date: 08 Jun 2001 22:24:59 +0800

>>>>> "Peter" == Peter T Breuer <[EMAIL PROTECTED]> writes:

    Peter> The point is that ghost does it via broadcast, so you can
    Peter> do 50 at once. You'd need 50 helpers to do it at once the
    Peter> way I just described.  Mind you, you could race round the
    Peter> room with the floppy. I once wrote the /etc/rc file to do
    Peter> all that while installing a room full of clients.  As I
    Peter> recall, it took me the first two rows (about 8 machines) to
    Peter> get it right. The trouble is that one has to program in a
.................................................^^^^^^
    Peter> reboot in order that the kernel sees the new partition
    Peter> table ..

Wrong!  You don't need a reboot.

Firstly,  most, if  not all,  fdisk utilities  on Linux  will  use the
appropriate ioctl() calls to tell  the kernel to re-read the partition
table.   This feature  has  been there  since  the first  time I  used
Linux...  that  was 8 years  ago.  For a shell-script  friendly fdisk,
look for 'sfdisk'.

Secondly, as  mentioned above, there is  an ioctl() call  to cause the
kernel to re-read the partition  table.  It's not difficult to do this
in a C program.  So, you can write a tiny C program to do that.


    Peter> either that or you have to hope that all the
    Peter> bioses and all the disks are exactly alike (they never are)
    Peter> and dd the whole disk (which is how ghost does it,
    Peter> usually).

If all  the machines are identical,  that's not a  problem.  Having to
configure different  IP addresses for the machines  is more difficult.
So, if the machines are to be networked together, you would eventually
want to  set up  BOOTP or even  better: DHCP  (but I prefer  DHCP with
statistically  assigned IP  addresses).  If  you have  set up  DHCP or
BOOTP, then  network booting is  just a few  steps away.  So,  why not
network-boot the  machines?  Why  not have one  server serve  the file
system to all  other machines (NFS root-mount)?  That  would save much
maintenance work  in the  long run.  (Imagine  having to  apply distro
patches!)



-- 
Lee Sau Dan                     ���u��(Big5)                    ~{@nJX6X~}(HZ) 
.----------------------------------------------------------------------------.
| e-mail: [EMAIL PROTECTED]                     http://www.csis.hku.hk/~sdlee |
`----------------------------------------------------------------------------'

------------------------------

From: [EMAIL PROTECTED]
Subject: Re: Print to a PDF
Date: 08 Jun 2001 22:32:35 +0800

>>>>> "Sebastien" == Sebastien Stormacq <[EMAIL PROTECTED]> writes:

    Sebastien> ps2pdf is a great tool to convert PS files to PDF.
    Sebastien> What we would like to have is printer definition in
    Sebastien> /etc/printcap that "prints to PDF", i.e. which use a
    Sebastien> filter that converts the data on the fly to PDF and
    Sebastien> save it somewhere on your disk, much like the PDF
    Sebastien> Writer Windows printer driver.

    Sebastien> Example of usage :

    Sebastien> lpr myfile.ps -PPDFWriter

    Sebastien> creates myfile.pdf in a special dir

    Sebastien> I think this should be possible using the filter
    Sebastien> capabilities of lpd (if:...)  and the gs program

"man printcap" and pay attention  to the "if" parameter.  There should
be some HOWTO's which teaches you how to use 'gs' as a filter to print
Postscript  on ANY printer.   The idea  is the  same, except  that you
replace 'gs' with 'ps2pdf'.

(If you  know more  about 'gs',  you can study  the ps2pdf  script and
discover  how  to  do  it  more directly  with  "gs  -sDEVICE=pdfwrite
-sOutputFile=/tmp/printout.pdf  ...", bypassing  the  overhead of  the
shell script.)


-- 
Lee Sau Dan                     ���u��(Big5)                    ~{@nJX6X~}(HZ) 
.----------------------------------------------------------------------------.
| e-mail: [EMAIL PROTECTED]                     http://www.csis.hku.hk/~sdlee |
`----------------------------------------------------------------------------'

------------------------------

From: Sebastien Stormacq <[EMAIL PROTECTED]>
Subject: Re: Print to a PDF
Date: Fri, 08 Jun 2001 16:48:07 +0200

I totally agree with you... What I was looking for was someone who 
already did the job and who has the correct printcap entry :-)
I am sooo lazy :-)

Seb

[EMAIL PROTECTED] wrote:

>>>>>>"Sebastien" == Sebastien Stormacq <[EMAIL PROTECTED]> writes:
>>>>>>
> 
>     Sebastien> ps2pdf is a great tool to convert PS files to PDF.
>     Sebastien> What we would like to have is printer definition in
>     Sebastien> /etc/printcap that "prints to PDF", i.e. which use a
>     Sebastien> filter that converts the data on the fly to PDF and
>     Sebastien> save it somewhere on your disk, much like the PDF
>     Sebastien> Writer Windows printer driver.
> 
>     Sebastien> Example of usage :
> 
>     Sebastien> lpr myfile.ps -PPDFWriter
> 
>     Sebastien> creates myfile.pdf in a special dir
> 
>     Sebastien> I think this should be possible using the filter
>     Sebastien> capabilities of lpd (if:...)  and the gs program
> 
> "man printcap" and pay attention  to the "if" parameter.  There should
> be some HOWTO's which teaches you how to use 'gs' as a filter to print
> Postscript  on ANY printer.   The idea  is the  same, except  that you
> replace 'gs' with 'ps2pdf'.
> 
> (If you  know more  about 'gs',  you can study  the ps2pdf  script and
> discover  how  to  do  it  more directly  with  "gs  -sDEVICE=pdfwrite
> -sOutputFile=/tmp/printout.pdf  ...", bypassing  the  overhead of  the
> shell script.)
> 
> 
> 


------------------------------

Crossposted-To: alt.os.linux,comp.unix.bsd.freebsd.misc
From: [EMAIL PROTECTED] (Bill Vermillion)
Subject: Re: hardware autodetection
Reply-To: [EMAIL PROTECTED]
Date: Fri, 8 Jun 2001 14:14:44 GMT

In article <[EMAIL PROTECTED]>,
Gregory Bond  <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] (Wroot) writes:
>
>> How come Debian and FreeBSD do not autodetect hardware the way Windows, Mandrake
>> and Redhat do? How am I supposed to know which cryptic kernel modules I should
>> enable and with which parameters?
>
>Becuase there is in general no way to do this that will boot and
>detect with all possible combinations of hardware.  This is because
>the probe for nonexistent device A may well freeze a system containing
>device B.  The FreeBSD GENERIC kernel has very careful ordering of ISA
>ethernet probes for exactly this reason.

>And have you ever actually seen how badly this works in Windows?

Complete with the message that indicates that if your computer does
nothing for a long period of time turn it off and back on.  
Working 'badly' is almost a compliment.

-- 
Bill Vermillion -   bv @ wjv . com

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list by posting to comp.os.linux.misc.

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to