Did I mess up?
Triforce
This is where I extracted all files and there was a sendmail-8.12.3
directory. Once I got in the directory I ran sh Build. Everything looked
like it went fine. The question I have is: after I ran the build did
sendmail install in the proper directory or was I supposed to move this
someplace else? One other note I already had a version of sendmail running.
Rob MacGregor
You just might want to read the documentation that came with it all.
Particularly the one named INSTALL.
--
Rob MacGregor (MCSE)
The light at the end of the tunnel is an oncoming dragon.
Question intelligently: http://www.tuxedo.org/~esr/faqs/smart-questions.html
gaius.petronius
> I d/l sendmail Release 8 (8.12.3). I put the sendmail tar in /opt/packages.
> This is where I extracted all files and there was a sendmail-8.12.3
> directory. Once I got in the directory I ran sh Build. Everything looked
> like it went fine.
Maybe. But i guarantee you it's not that simple.
Did you read the following files?
./README
./INSTALL
./sendmail/README
./devtools/README
> The question I have is: after I ran the build did
> sendmail install in the proper directory or was I supposed to move this
> someplace else? One other note I already had a version of sendmail running.
The binary should appear in the object directory
which should match the OS name in devtools/OS unless i am mistaken
which in your case seems like SunOS
from your build dir run
find . -name sendmail -type f -ls
and see if it appears in the obj.~ dir
That's your binary
You still need to create an appropriate .mc file and put it in
/etc/mail and create the .cf file
Fortunately sendmail now comes with fairly good documentation
read those README files and INSTALL
Triforce
"gaius.petronius" <r...@linuxmail.org> wrote in message
news:188cd7b2.02043...@posting.google.com...
Thanks for the tips. The sendmail/README file says to read the document
../doc/op/op.me
cd ../doc/op;
make op.ps op.txt
# make op.ps op.txt
`op.ps' is up to date.
rm -f op.txt
pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
sh: pic: not found
sh: groff: not found
After doing the make I have those following errors. The next thing I tried
doing was finding those two utilities on my system.
find / -name groff
find / -name pic
Both of them returned no hits.
Went to sunfreeware and d/l groff 1.17.12 package. When trying to execute
groff I got these errors:
ld.so.1: groff: fatal: libstdc++.so.3: open failed: No such file or
directory
Decided I was missing a library and downloaded the new libgcc-3.0.3 package.
After library was installed I groff was working properly.
However, I can't find pic anywhere. Searched in google nothing came up that
I noticed and the sunfreeware site didn't have it unless I overlooked it.
Does anyone know where I can get this utility?
ger...@gtconnect.net
Forget about pic.
Just convert the op.ps postscript file into something like a pdf file or
read it as is... most of the devtools stuff is documented in cf/README,
not in the op.ps file. Youll want to look at SECURITY as well.
Claus Aßmann
> # make op.ps op.txt
> `op.ps' is up to date.
> rm -f op.txt
> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
> sh: pic: not found
> sh: groff: not found
If you don't have a PostScript viewer (ghostscript), then take
a look at
http://www.sendmail.org/~ca/email/doc8.VERSION/op.html
http://www.sendmail.org/~ca/email/doc8.VERSION/op.gz
(replace version with 9, 10, 11, or 12), the latter is
the plain text version (gzip'ed).
--
If you feel the urgent wish to send me a courtesy copy of a Usenet
posting, then make sure it's recognizable as such!
The FAQ: http://www.sendmail.org/faq/ Before you ask.
Thomas Schulz
>> `op.ps' is up to date.
>> rm -f op.txt
>> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
>> sh: pic: not found
>> sh: groff: not found
>>
I got a readable text file with the following command on our Solaris
system.
neqn -C -Tascii op.me | nroff -me | ul -t dumb op.part > op.txt
--
Tom Schulz
sch...@adi.com
Thomas Schulz
>> # make op.ps op.txt
>> `op.ps' is up to date.
>> rm -f op.txt
>> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
>> sh: pic: not found
>> sh: groff: not found
>>
on my Solaris system with the following command:
neqn -C -Tascii op.me | nroff -me | ul -t dumb > op.txt
--
Tom Schulz
sch...@adi.com
Triforcian
file. Boy do I need to get a grip on things. ;-)
Thanks again...
"Claus Aßmann" <ca+sendmail(-no-copies-please)@mine.informatik.uni-kiel.de>
wrote in message news:aaoupn$6f6$1...@zardoc.esmtp.org...
Triforcian
"Triforcian" <trifo...@attbi.com> wrote in message
news:2I_z8.35142$ao1.9340@rwcrnsc54...
ger...@gtconnect.net
Claus Aßmann <ca+sendmail(-no-copies-please)@mine.informatik.uni-kiel.de> writes:
> Triforce wrote:
>
>> # make op.ps op.txt
>> `op.ps' is up to date.
>> rm -f op.txt
>> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
>> sh: pic: not found
>> sh: groff: not found
>
> If you don't have a PostScript viewer (ghostscript), then take
> a look at
>
> http://www.sendmail.org/~ca/email/doc8.VERSION/op.html
> http://www.sendmail.org/~ca/email/doc8.VERSION/op.gz
> (replace version with 9, 10, 11, or 12), the latter is
> the plain text version (gzip'ed).
Why not fix the Makefile in this case? Its too GNU centric : >
Claus Aßmann
> >> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
> >> sh: pic: not found
> >> sh: groff: not found
> Why not fix the Makefile in this case? Its too GNU centric : >
$ make ROFF_CMD=nroff op.txt
rm -f op.txt
pic -C op.me | eqn -C -Tascii | nroff -Tascii -me | ul -t dumb > op.txt
ger...@gtconnect.net
Claus Aßmann <ca+sendmail(-no-copies-please)@mine.informatik.uni-kiel.de> writes:
> wrote:
>
>> >> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
>> >> sh: pic: not found
>> >> sh: groff: not found
>
>> Why not fix the Makefile in this case? Its too GNU centric : >
>
> $ make ROFF_CMD=nroff op.txt
> rm -f op.txt
> pic -C op.me | eqn -C -Tascii | nroff -Tascii -me | ul -t dumb > op.txt
Solaris doesnt have pic : > Solaris eqn does not have a -C. There is
no nroff -Tascii either. That was the guys original problem along
with not having groff and its GNU options.
cat op.me | neqn | nroff -me | ul -t dumb
produces something readable.
A separate Makefile is needed for Solaris and I would be happy to
contribute one if you like.
Thomas Schulz
Claus =?iso-8859-1?Q?A=DFmann?= <ca+sendmail(-no-copies-please)@mine.informatik.uni-kiel.de> wrote:
> wrote:
>
>> >> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
>> >> sh: pic: not found
>> >> sh: groff: not found
>
>> Why not fix the Makefile in this case? Its too GNU centric : >
>
>$ make ROFF_CMD=nroff op.txt
>rm -f op.txt
>pic -C op.me | eqn -C -Tascii | nroff -Tascii -me | ul -t dumb > op.txt
>
That would work if:
1) You have pic
2) You have an eqn that understands -C -Tascii
3) You have a nroff that understands -Tascii
4) ul did not completely mess up the equations produced by eqn
My Solaris machine has all the above problems. My Linux system has only
problem 4. I have gotten the most readable result with the following
command:
nroff -me op.me | ul -t dumb > op.txt
On Linix I can add in the -Tascii.
--
Tom Schulz
sch...@adi.com
ger...@gtconnect.net
Thats cuz Linux is GNU and GNU is Linux : <
Ideally you dont want to grope through text anyway : >
Have a look at : www.wizards.de/~frank/pstill.html
Converting the op.ps file to pdf format is ideal on Solaris
where the postscript reader isnt the greatest and acroread
works reasonably well for this purpose..