Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-questions Digest, Vol 226, Issue 10

1 view

Skip to first unread message

freebsd-ques...@freebsd.org

unread,

Jul 30, 2008, 6:17:37 PM7/30/08

to freebsd-...@freebsd.org

Send freebsd-questions mailing list submissions to
freebsd-...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-ques...@freebsd.org

You can reach the person managing the list at
freebsd-que...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-questions digest..."

Today's Topics:

1. Re: tex, teTex, LaTeX help (dick hoogendijk)
2. Re: protecting my FreeBSD system (Roland Smith)
3. Re: tex, teTex, LaTeX help (Glyn Millington)
4. Re: valgrind (Roland Smith)
5. Problem building openssh-portable with KERBEROS, GSSAPI,
KERB_GSSAPI. (Valeriu Mutu)
6. Re: tex, teTex, LaTeX help (Polytropon)
7. Re: When gcc43 is expected to be in base? (Kris Kennaway)
8. Re: tex, teTex, LaTeX help (Roland Smith)
9. Re: question about new monitor... (Roland Smith)
10. Re: tex, teTex, LaTeX help (Roland Smith)
11. Re: tex, teTex, LaTeX help (Lowell Gilbert)
12. Re: question about new monitor... (Gary Kline)
13. Re: question about new monitor... (Chuck Robey)
14. Re: tex, teTex, LaTeX help (N. Raghavendra)
15. Re: question about new monitor... (Erik Trulsson)
16. Re: question about new monitor... (Erik Trulsson)
17. Re: tex, teTex, LaTeX help (Daniel Molina Wegener)
18. Re: tex, teTex, LaTeX help (Daniel Molina Wegener)
19. Re: seen in ports and used but dont remember the name ;)
(Daniel Molina Wegener)
20. Re: question about new monitor... (Gary Kline)
21. Re: tex, teTex, LaTeX help (Lowell Gilbert)
22. 7.0-stable snapshot (John Wilson)
23. Re: question about new monitor... (Roland Smith)
24. Building a FreeBSD based mail server (Patrick Baldwin)
25. sendmail base configuration (Tim Traver)
26. Re: SCSI RAID on FreeBSD 7.0, where is the array? (Derek Ragona)
27. Re: Building modules distributed with Apache, using ports
(Lowell Gilbert)
28. Re: When gcc43 is expected to be in base? (Jakub Lach)
29. Re: Building a FreeBSD based mail server (Jack Raats)
30. Re: setting the other end's TCP segment size (Derek Ragona)
31. Re: Mail Heading to dead.letter (Derek Ragona)
32. Bizarre Diskless Boot Behavior (Jeff Wheelhouse)
33. Group Limits (Michael Christie)
34. resume (hate to even ask) (Steve Franks)

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

Message: 1
Date: Wed, 30 Jul 2008 18:45:18 +0200
From: dick hoogendijk <di...@nagual.nl>
Subject: Re: tex, teTex, LaTeX help
To: freebsd-...@freebsd.org
Message-ID: <20080730184518...@nagual.nl>
Content-Type: text/plain; charset=US-ASCII

On Wed, 30 Jul 2008 13:00:00 -0300
"Joey Mingrone" <jo...@mingrone.org> wrote:

> Is there a guide for getting all this set up, or can some kind soul
> suggest a installation method that works well for them?

Install from the TeX Live CD and you get the latest software (FreeBSD
support is included).

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ + SunOS sxce snv94 ++

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

Message: 2
Date: Wed, 30 Jul 2008 18:56:51 +0200
From: Roland Smith <rsm...@xs4all.nl>
Subject: Re: protecting my FreeBSD system
To: DSA - JCR <jua...@dsa.es>
Cc: freebsd-...@freebsd.org
Message-ID: <20080730165...@slackbox.xs4all.nl>
Content-Type: text/plain; charset="iso-8859-15"

On Wed, Jul 30, 2008 at 09:38:26AM -0000, DSA - JCR wrote:
> HI all again
>
> I would like to know if there is a method to know how well protected is my
> system (FreeBSD 6.2) in order to not permit a user to enter as root.
> I need it because I have intellectual propierty in that box, and I know
> some people is interested on it.

Note that nothing short of disk encryption can protect the machine if
the attacker has physical access to it (e.g. he can steal the machine or
the harddisk).

Security is a never-ending road, not a destination.

- Keep the machine in a locked room/cupboard (restrict physical access).
- Subscribe to the freebsd-announce mailing list to keep on top of
security advisories.
- Keep you system patched/up-to-date in case vulnerabilities pop up in
the kernel or dæmons that you use.
- Disable dæmons that you do not use.
- Install a firewall that blocks by default.
- Disable remote root logins.
- Build a custom kernel & world that do not contain things that you do
no use. See src.conf(5), e.g. WITHOUT_RCMDS.

> I use inetd, and I have all ports disable except Samba because it is a
> repository for Windows Docs in a network. (swap is not enable).

You can use security/nmap to check if a system has open ports.

> My root password is almost 20 chars with numbers, normal and capitals
> letters, points.

That's OK, as long as it isn't on a note near the machine. :-)

> there is a user that belongs to operator with a script for (un)mounting
> USB disk in which I trap almost all signals (about 15).

Better to make that user member of a new group (e.g. usb) and (assuming
that you're using umass(4)) give that group read/write rights on the da
devices in /etc/devfs.rules: "add path 'da*' mode 0660 group usb"

Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20080730/5fc7688f/attachment-0001.pgp

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

Message: 3
Date: Wed, 30 Jul 2008 18:05:59 +0100
From: Glyn Millington <gl...@millingtons.org>
Subject: Re: tex, teTex, LaTeX help
To: "Joey Mingrone" <jo...@mingrone.org>
Cc: freebsd-...@freebsd.org
Message-ID: <86ej5bs...@nowhere.org>
Content-Type: text/plain; charset=us-ascii

"Joey Mingrone" <jo...@mingrone.org> writes:

> I've been told that LaTeX is probably the best solution for creating
> scientific papers with math fonts, so I'm trying to get a working
> installation.

A noble ambition!

> fonts, but it seems they are in the teTex port, but that port
> conflicts with the tex port and it seems teTex is no longer being
> updated.

Alas the news about teTeX is true.

> Is there a guide for getting all this set up, or can some kind soul
> suggest a installation method that works well for them?

Have you had a look at TeXLive?

http://www.tug.org/texlive/

For FreeBSD that means downloading the iso, mounting it like this

mount_cd9660 -o ro /dev/`mdconfig -a -t vnode -f /path/to/file.iso` /mount-point

cd to the mount point and look out for script entitled install-tl.sh

the script pretty well takes you through the installation

Good luck!

atb

Glyn

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

Message: 4
Date: Wed, 30 Jul 2008 19:06:59 +0200
From: Roland Smith <rsm...@xs4all.nl>
Subject: Re: valgrind
To: Andrea Venturoli <m...@netfence.it>
Cc: freebsd-...@freebsd.org, bar...@freebsd.org
Message-ID: <20080730170...@slackbox.xs4all.nl>
Content-Type: text/plain; charset="us-ascii"

On Wed, Jul 30, 2008 at 05:12:39PM +0200, Andrea Venturoli wrote:
>
> ** Port marked as IGNORE: devel/valgrind:
> is only for i386, while you are running amd64
> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> - devel/valgrind
>
> Same holds for valgrind-snapshot.
>
> On it's website I see it supports AMD64 on Linux, so I guess this is a
> FreeBSD specific problem.
>
> Is there ongoing work to get this on amd64?
>
> Out of curiosity, what is the reason it does not work right now?

Read http://valgrind.org/info/platforms.html, especially 'Porting Plans'.

Or remove the line 'ONLY_FOR_ARCHS= i386' from the port Makefile, try it
and see where it breaks. :-) I'm guessing it need some support code in
the OS.

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

Message: 5
Date: Wed, 30 Jul 2008 12:40:32 -0400
From: Valeriu Mutu <vm...@pcbi.upenn.edu>
Subject: Problem building openssh-portable with KERBEROS, GSSAPI,
KERB_GSSAPI.
To: FreeBSD-questions list <freebsd-...@freebsd.org>
Message-ID: <2008073016...@snowball.pcbi.upenn.edu>
Content-Type: text/plain; charset=us-ascii

Hi all,

I am trying to build 'openssh-portable' from ports (security/openssh-portable/) with the following configuration options:

PAM=on "Enable pam(3) support"
TCP_WRAPPERS=on "Enable tcp_wrappers support"
LIBEDIT=on "Enable readline support to sftp(1)"
KERBEROS=on "Enable kerberos (autodetection)"
SUID_SSH=off "Enable suid SSH (Recommended off)"
GSSAPI=on "Enable GSSAPI support (req: KERBEROS)"
KERB_GSSAPI=on "Enable Kerberos/GSSAPI patch (req: GSSAPI)"
OPENSSH_CHROOT=off "Enable CHROOT support"
OPENSC=off "Enable OpenSC smartcard support"
OPENSCPINPATCH=off "Enable OpenSC PIN patch"
HPN=off "Enable HPN-SSH patch"
LPK=off "Enable LDAP Public Key (LPK) patch"
OVERWRITE_BASE=off "OpenSSH overwrite base"

and get the following error on 'make':
-----------------------------------------------------------------------
...
if test ! -z ""; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi
(cd openbsd-compat && make)
cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o -L. -Lopenbsd-compat/ -L/usr/local/lib -rpath=/usr/local/lib -L/lib -lssh -lopenbsd-compat -lcrypto -lutil -lz -lcrypt -lgssapi -lkrb5 -lk5crypto -lcom_err
./libssh.a(gss-genr.o)(.text+0xa8c): In function `ssh_gssapi_import_name':
/usr/ports/security/openssh-portable/work/openssh-5.0p1/gss-genr.c:369: undefined reference to `gss_nt_service_name'
*** Error code 1

Stop in /usr/ports/security/openssh-portable/work/openssh-5.0p1.
*** Error code 1

Stop in /usr/ports/security/openssh-portable.
*** Error code 1

Stop in /usr/ports/security/openssh-portable.

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

I am running a GENERIC kernel on FreeBSD 7.0-RELEASE (i386).

ps: Searched the internet and found some hints that the problem might be caused by the definition of GSS_C_NT_HOSTBASED_SERVICE . Any ideas as to what is causing this problem and how could this be fixed?

Thanks,
Valeriu

--
Valeriu Mutu

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

Message: 6
Date: Wed, 30 Jul 2008 19:17:26 +0200
From: Polytropon <fre...@edvax.de>
Subject: Re: tex, teTex, LaTeX help
To: freebsd-...@freebsd.org
Message-ID: <20080730191726....@edvax.de>
Content-Type: text/plain; charset=US-ASCII

On Wed, 30 Jul 2008 18:05:59 +0100, Glyn Millington <gl...@millingtons.org> wrote:
> "Joey Mingrone" <jo...@mingrone.org> writes:
> > fonts, but it seems they are in the teTex port, but that port
> > conflicts with the tex port and it seems teTex is no longer being
> > updated.
>
> Alas the news about teTeX is true.

I'm very sad to hear this, allthough I'm always installing teTeX
via pkg_add -r, and I never found something not working anymore.
Is there any consideration to remove teTeX completely from the
ports tree, or is it still valid to keep using it?

(I use LaTeX for nearly everything: work, documentation, literature,
even for letters (dinbrief class), so I'm interested in this topic.)

Many thanks for pointing out how to get \LaTeX{} from TeXLive.

--
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0

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

Message: 7
Date: Wed, 30 Jul 2008 19:18:21 +0200
From: Kris Kennaway <kr...@FreeBSD.org>
Subject: Re: When gcc43 is expected to be in base?
To: Jakub Lach <jakub...@mailplus.pl>
Cc: freebsd-...@freebsd.org
Message-ID: <4890A25D...@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Jakub Lach wrote:
>
>
> Kris Kennaway-3 wrote:
>> Jakub Lach wrote:
>>> I'm eager to have core2 march, but don't want to mess system forcing
>>> gcc43 as
>>> base.
>> I don't think it is planned to update to gcc 4.3 since it is covered by
>> the GPLv3.
>
> Thanks for fast answer, is there any chance that licensing stuff is going to
> be omitted?

There is basically no chance the GCC developers will reconsider their
decision to relicense GCC 4.3 to GPLv3.

> If not, will then FreeBSD move to another compiler?

The existing gcc 4.2 will be supported for some time by the gcc
developers. In the meantime hopefully llvm/clang will mature enough to
provide an alternative. It is already quite far along and has
significant resources behind it (apple, etc).

Kris

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

Message: 8
Date: Wed, 30 Jul 2008 19:31:24 +0200
From: Roland Smith <rsm...@xs4all.nl>
Subject: Re: tex, teTex, LaTeX help
To: dick hoogendijk <di...@nagual.nl>
Cc: freebsd-...@freebsd.org
Message-ID: <20080730173...@slackbox.xs4all.nl>
Content-Type: text/plain; charset="us-ascii"

On Wed, Jul 30, 2008 at 06:45:18PM +0200, dick hoogendijk wrote:
> On Wed, 30 Jul 2008 13:00:00 -0300
> "Joey Mingrone" <jo...@mingrone.org> wrote:
>
> > Is there a guide for getting all this set up, or can some kind soul
> > suggest a installation method that works well for them?
>
> Install from the TeX Live CD and you get the latest software (FreeBSD
> support is included).

The latest CD (2007) only has i386 6.x binaries. I've built from source
on amd64, but that needs some Makefile hacking to work. Those who are
interested can mail me.

The advantage of TeXLive is that it is very complete.

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

Message: 9
Date: Wed, 30 Jul 2008 18:29:01 +0200
From: Roland Smith <rsm...@xs4all.nl>
Subject: Re: question about new monitor...
To: Gary Kline <kl...@thought.org>
Cc: FreeBSD Mailing List <freebsd-...@freebsd.org>
Message-ID: <20080730162...@slackbox.xs4all.nl>
Content-Type: text/plain; charset="us-ascii"

On Tue, Jul 29, 2008 at 06:46:33PM -0700, Gary Kline wrote:
>
> I've changed my mind:: if I go to 20" i can get widescreen
> with 1680x1050, so my current 1284x1024 would fit. IFF
> xorg know what kind of beast this is:-)

Xorg can "talk" to modern monitors using the ddc2 protocol (but only
with a DVI connection, AFAICT). Effectively the monitor tells Xorg what
it's capable of WRT resolutions, rehresh rates etc. It's pretty neat.

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

Message: 10
Date: Wed, 30 Jul 2008 19:38:12 +0200
From: Roland Smith <rsm...@xs4all.nl>
Subject: Re: tex, teTex, LaTeX help
To: Polytropon <fre...@edvax.de>
Cc: freebsd-...@freebsd.org
Message-ID: <20080730173...@slackbox.xs4all.nl>
Content-Type: text/plain; charset="us-ascii"

On Wed, Jul 30, 2008 at 07:17:26PM +0200, Polytropon wrote:
> On Wed, 30 Jul 2008 18:05:59 +0100, Glyn Millington <gl...@millingtons.org> wrote:
> > "Joey Mingrone" <jo...@mingrone.org> writes:
> > > fonts, but it seems they are in the teTex port, but that port
> > > conflicts with the tex port and it seems teTex is no longer being
> > > updated.
> >
> > Alas the news about teTeX is true.
>
> I'm very sad to hear this, allthough I'm always installing teTeX
> via pkg_add -r, and I never found something not working anymore.
> Is there any consideration to remove teTeX completely from the
> ports tree, or is it still valid to keep using it?

I expect that teTeX will be removed as soon as TeXLive is ported. IIRC,
some people are working on that. A problem is that TeXLive has an
interactive install script. I'm not sure how well that matches with ports.

> (I use LaTeX for nearly everything: work, documentation, literature,
> even for letters (dinbrief class), so I'm interested in this topic.)
>
> Many thanks for pointing out how to get \LaTeX{} from TeXLive.

Basic installation is very easy, just use the install script on the
CD. If you have to build you own binaries (only i386 6.x binaries are
supplied on the CD), it is somewhat more involved. Basically, you need
to patch a makefile to remove some omega stuff that won't build. I have
some notes from my last build that I could send you if you like.

If more people are interested I could post them on the list.

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

Message: 11
Date: Wed, 30 Jul 2008 13:42:01 -0400
From: Lowell Gilbert <freebsd-que...@be-well.ilk.org>
Subject: Re: tex, teTex, LaTeX help
To: Polytropon <fre...@edvax.de>
Cc: freebsd-...@freebsd.org
Message-ID: <44ej5bg...@be-well.ilk.org>
Content-Type: text/plain; charset=us-ascii

Polytropon <fre...@edvax.de> writes:

> On Wed, 30 Jul 2008 18:05:59 +0100, Glyn Millington <gl...@millingtons.org> wrote:
>> "Joey Mingrone" <jo...@mingrone.org> writes:
>> > fonts, but it seems they are in the teTex port, but that port
>> > conflicts with the tex port and it seems teTex is no longer being
>> > updated.
>>
>> Alas the news about teTeX is true.
>
> I'm very sad to hear this, allthough I'm always installing teTeX
> via pkg_add -r, and I never found something not working anymore.
> Is there any consideration to remove teTeX completely from the
> ports tree, or is it still valid to keep using it?
>
> (I use LaTeX for nearly everything: work, documentation, literature,
> even for letters (dinbrief class), so I'm interested in this topic.)
>
> Many thanks for pointing out how to get \LaTeX{} from TeXLive.

teTeX still works fine; well enough that I haven't been tempted to try
porting TeXLive yet...

--
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/

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

Message: 12
Date: Wed, 30 Jul 2008 10:44:32 -0700
From: Gary Kline <kl...@thought.org>
Subject: Re: question about new monitor...
To: Roland Smith <rsm...@xs4all.nl>
Cc: FreeBSD Mailing List <freebsd-...@freebsd.org>
Message-ID: <20080730174...@thought.org>
Content-Type: text/plain; charset=us-ascii

On Wed, Jul 30, 2008 at 06:29:01PM +0200, Roland Smith wrote:
> On Tue, Jul 29, 2008 at 06:46:33PM -0700, Gary Kline wrote:
> >
> > I've changed my mind:: if I go to 20" i can get widescreen
> > with 1680x1050, so my current 1284x1024 would fit. IFF
> > xorg know what kind of beast this is:-)
>
> Xorg can "talk" to modern monitors using the ddc2 protocol (but only
> with a DVI connection, AFAICT). Effectively the monitor tells Xorg what
> it's capable of WRT resolutions, rehresh rates etc. It's pretty neat.
>

So in effect, since all my connections are going thru mt old,
analog KVM switch, this won't work. Not only that, but my two
desktops would need two new video cards. So best to stick with
the
older standard ... until

So in effect, since all my connections are going thru mt
old, analog KVM switch, this won't work. Not only that,
but my two desktops would need two new video cards. So
best to stick with the older standard.

gary

> Roland
> --
> R.F.Smith http://www.xs4all.nl/~rsmith/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)

--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org

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

Message: 13
Date: Wed, 30 Jul 2008 13:45:56 -0400
From: Chuck Robey <chu...@telenix.org>
Subject: Re: question about new monitor...
To: Roland Smith <rsm...@xs4all.nl>
Cc: Gary Kline <kl...@thought.org>, FreeBSD Mailing List
<freebsd-...@freebsd.org>
Message-ID: <4890A8D4...@telenix.org>
Content-Type: text/plain; charset=ISO-8859-1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roland Smith wrote:
> On Tue, Jul 29, 2008 at 06:46:33PM -0700, Gary Kline wrote:
>> I've changed my mind:: if I go to 20" i can get widescreen
>> with 1680x1050, so my current 1284x1024 would fit. IFF
>> xorg know what kind of beast this is:-)
>
> Xorg can "talk" to modern monitors using the ddc2 protocol (but only
> with a DVI connection, AFAICT). Effectively the monitor tells Xorg what
> it's capable of WRT resolutions, rehresh rates etc. It's pretty neat.
>
> Roland

That 2408 of mine, when it came via freight, had a flyer inside it telling me
that they'd included a new interface, over and above the specs, but I forget if
it was the HDMI or DisplayPort. I'd never used either before. Really tiny and
tight interfaces, both, and probably requiring a protocol like ddc2. There's
actually 8 different switchable interfaces (well, seven really, it's got 2
different DVI's.) You can bring in broadcast video by either RCA jack, SVideo,
or the component video.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiQqNQACgkQz62J6PPcoOkVgwCeN2of6fc8KX3gK8hBag+9RrLI
wIgAniKaNVoNzZAw9Z1j4N2fjUJXEi7z
=QOfG
-----END PGP SIGNATURE-----

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

Message: 14
Date: Wed, 30 Jul 2008 23:47:21 +0530
From: "N. Raghavendra" <ra...@mri.ernet.in>
Subject: Re: tex, teTex, LaTeX help
To: "Joey Mingrone" <jo...@mingrone.org>
Cc: freebsd-...@freebsd.org
Message-ID: <868wvj1...@riemann.mri.ernet.in>
Content-Type: text/plain; charset=us-ascii

At 2008-07-30T13:00:00-03:00, Joey Mingrone wrote:

> My first attempt was to install the latex2e-2003.12_1 port, which
> installed the tex-3.14159_3 port as a dependency. This seemed to
> work, but there were some things referenced in the documentation that
> seemed to be missing. For example, the amsmath package wasn't
> available. I thought there must be a port specifically for these
> fonts, but it seems they are in the teTex port, but that port
> conflicts with the tex port

Just deinstall the `tex' and `latex' ports, and install the metaport
`print/teTeX', which will pull in all the standard stuff, including
AMSLaTeX packages like `amsmath'. Also, install `print/gv' for
viewing PostScript files, and `print/acroread8' to view PDF files.

After installing these ports, you can view documentation using the
command texdoc(1). Here are a few examples for starters:

% texdoc lshort

will display the `Not So Short Introduction to LATEX2e', a useful
primer on LaTeX.

% texdoc symbols

will show you a list of symbols and their control sequences in LaTeX.

% texdoc usrguide

will display `LaTeX2e for authors'.

% texdoc amsldoc

will show you the `User's Guide for the amsmath Package'.

% texdoc `texdoc -s 'hyperref.*manual'`

will display the manual for the `hyperref' package.

Generally, it is worth browsing through `/usr/local/share/texmf-dist/doc'.
As for print references, the `LaTeX Companion' by Mittelbach, et al,
is very useful, as also is the LaTeX book by Lamport.

> Is there a guide for getting all this set up, or can some kind soul
> suggest a installation method that works well for them?

FWIW, I am a mathematician and have been typesetting mathematics for
more than a decade using the teTeX distribution, and have found it
sufficient for my needs. I've used TeXLive too, but have not found
any need to do so. YMMV.

HTH,
Raghavendra.

--
N. Raghavendra <ra...@mri.ernet.in> | http://www.retrotexts.net/
Harish-Chandra Research Institute | http://www.mri.ernet.in/
See message headers for contact and OpenPGP information.

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

Message: 15
Date: Wed, 30 Jul 2008 20:26:45 +0200
From: Erik Trulsson <ertr...@student.uu.se>
Subject: Re: question about new monitor...
To: Roland Smith <rsm...@xs4all.nl>
Cc: Gary Kline <kl...@thought.org>, FreeBSD Mailing List
<freebsd-...@freebsd.org>
Message-ID: <20080730182...@owl.midgard.homeip.net>
Content-Type: text/plain; charset=us-ascii

No, ddc/ddc2b works just fine over a standard analog VGA-connector as well
(assuming both monitor and graphics card supports it, which just about all
devices you can buy today does.)

Effectively the monitor tells Xorg what
> it's capable of WRT resolutions, rehresh rates etc. It's pretty neat.
>
> Roland

--
<Insert your favourite quote here.>
Erik Trulsson
ertr...@student.uu.se

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

Message: 16
Date: Wed, 30 Jul 2008 20:31:31 +0200
From: Erik Trulsson <ertr...@student.uu.se>
Subject: Re: question about new monitor...
To: Gary Kline <kl...@thought.org>
Cc: Roland Smith <rsm...@xs4all.nl>, FreeBSD Mailing List
<freebsd-...@freebsd.org>
Message-ID: <20080730183...@owl.midgard.homeip.net>
Content-Type: text/plain; charset=us-ascii

On Wed, Jul 30, 2008 at 10:44:32AM -0700, Gary Kline wrote:
> On Wed, Jul 30, 2008 at 06:29:01PM +0200, Roland Smith wrote:
> > On Tue, Jul 29, 2008 at 06:46:33PM -0700, Gary Kline wrote:
> > >
> > > I've changed my mind:: if I go to 20" i can get widescreen
> > > with 1680x1050, so my current 1284x1024 would fit. IFF
> > > xorg know what kind of beast this is:-)
> >
> > Xorg can "talk" to modern monitors using the ddc2 protocol (but only
> > with a DVI connection, AFAICT). Effectively the monitor tells Xorg what
> > it's capable of WRT resolutions, rehresh rates etc. It's pretty neat.
> >
>
>
> So in effect, since all my connections are going thru mt old,
> analog KVM switch, this won't work. Not only that, but my two
> desktops would need two new video cards. So best to stick with
> the
> older standard ... until
>
>
> So in effect, since all my connections are going thru mt
> old, analog KVM switch, this won't work. Not only that,
> but my two desktops would need two new video cards. So
> best to stick with the older standard.

It should actually work fine over an analog connection (including via a
KVM, assuming the KVM is not too old.) It works fine for me anyway.

One thing to watch out for when using a KVM is if a computer can get
information from the monitor even it is is not the active unit on the KVM.
Many newer KVM switches caches the response from the monitor, so all
attached computers can get information about the monitor.
Older KVM switches typically do not do this, so then you need to have each
attached computer be active when it starts to get information from the
monitor.

--
<Insert your favourite quote here.>
Erik Trulsson
ertr...@student.uu.se

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

Message: 17
Date: Wed, 30 Jul 2008 14:25:25 -0400
From: Daniel Molina Wegener <d...@unete.cl>
Subject: Re: tex, teTex, LaTeX help
To: Joey Mingrone <jo...@mingrone.org>
Cc: freebsd-...@freebsd.org
Message-ID: <4890B215...@unete.cl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Joey Mingrone escribió:
> Hello,
>
> I've been told that LaTeX is probably the best solution for creating
> scientific papers with math fonts, so I'm trying to get a working
> installation.
>
> My first attempt was to install the latex2e-2003.12_1 port, which
> installed the tex-3.14159_3 port as a dependency. This seemed to
> work, but there were some things referenced in the documentation that
> seemed to be missing. For example, the amsmath package wasn't
> available. I thought there must be a port specifically for these
> fonts, but it seems they are in the teTex port, but that port
> conflicts with the tex port and it seems teTex is no longer being
> updated.
>
> Is there a guide for getting all this set up, or can some kind soul
> suggest a installation method that works well for them?
>
> Thanks,
>
> Joey Mingrone
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>
Try teTex and other packages regarding it.

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

Message: 18
Date: Wed, 30 Jul 2008 14:27:11 -0400
From: Daniel Molina Wegener <d...@unete.cl>
Subject: Re: tex, teTex, LaTeX help
To: Polytropon <fre...@edvax.de>
Cc: freebsd-...@freebsd.org
Message-ID: <4890B27F...@unete.cl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Polytropon escribió:
> On Wed, 30 Jul 2008 18:05:59 +0100, Glyn Millington <gl...@millingtons.org> wrote:
>
>> "Joey Mingrone" <jo...@mingrone.org> writes:
>>
>>> fonts, but it seems they are in the teTex port, but that port
>>> conflicts with the tex port and it seems teTex is no longer being
>>> updated.
>>>
>> Alas the news about teTeX is true.
>>
>
> I'm very sad to hear this, allthough I'm always installing teTeX
> via pkg_add -r, and I never found something not working anymore.
> Is there any consideration to remove teTeX completely from the
> ports tree, or is it still valid to keep using it?
>
> (I use LaTeX for nearly everything: work, documentation, literature,
> even for letters (dinbrief class), so I'm interested in this topic.)
>
> Many thanks for pointing out how to get \LaTeX{} from TeXLive.
>
>
>
Try:

portinstall -PP teTex

Regards,
DMW

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

Message: 19
Date: Wed, 30 Jul 2008 14:19:20 -0400
From: Daniel Molina Wegener <d...@unete.cl>
Subject: Re: seen in ports and used but dont remember the name ;)
To: DSA - JCR <jua...@dsa.es>
Cc: freebsd-...@freebsd.org
Message-ID: <4890B0A8...@unete.cl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

DSA - JCR escribió:
> Hi all
>
Hi
> FreeBSD 6.2
>
> I have used in the past year an utility for terminal that permit me to
> split the terminal in several sesions vertically/horizontally and also
> save and restore the sesion, letting it doing some commands.
>
> I installed from ports, but I dont remember its name. ;-)
>
window(1), screen -- in the ports collection and as terminal emulators,
you have yakuake.
> Can anyone help me?
>
>
> Thanks in advance
>
> Juan Coruña
> Desarrollo de Software Atlantico
>
>
>
>
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>

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

Message: 20
Date: Wed, 30 Jul 2008 11:49:19 -0700
From: Gary Kline <kl...@thought.org>
Subject: Re: question about new monitor...
To: Erik Trulsson <ertr...@student.uu.se>
Cc: Roland Smith <rsm...@xs4all.nl>, FreeBSD Mailing List
<freebsd-...@freebsd.org>
Message-ID: <20080730184...@thought.org>
Content-Type: text/plain; charset=us-ascii

On Wed, Jul 30, 2008 at 08:26:45PM +0200, Erik Trulsson wrote:
> On Wed, Jul 30, 2008 at 06:29:01PM +0200, Roland Smith wrote:
> > On Tue, Jul 29, 2008 at 06:46:33PM -0700, Gary Kline wrote:
> > >
> > > I've changed my mind:: if I go to 20" i can get widescreen
> > > with 1680x1050, so my current 1284x1024 would fit. IFF
> > > xorg know what kind of beast this is:-)
> >
> > Xorg can "talk" to modern monitors using the ddc2 protocol (but only
> > with a DVI connection, AFAICT).
>
> No, ddc/ddc2b works just fine over a standard analog VGA-connector as well
> (assuming both monitor and graphics card supports it, which just about all
> devices you can buy today does.)
>

This is the "gotcha." I bought a new, high-end SoundBlaster for
my Dell; it didn't fit. Dell only works with certain,
proprietary cards -- I don't know which ones. So whether or not
my Dell 8200 can even be upgraded is a question.

(My Ubuntu desktop is the only new computer; it was custom built in
'05; I have never popped the cover. It is strictly generic. ...)

>
> Effectively the monitor tells Xorg what
> > it's capable of WRT resolutions, rehresh rates etc. It's pretty neat.
> >
> > Roland
>
>
> --
> <Insert your favourite quote here.>
> Erik Trulsson
> ertr...@student.uu.se

--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org

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

Message: 21
Date: Wed, 30 Jul 2008 15:13:24 -0400
From: Lowell Gilbert <freebsd-que...@be-well.ilk.org>
Subject: Re: tex, teTex, LaTeX help
To: freebsd-...@freebsd.org
Message-ID: <44myjzf...@be-well.ilk.org>
Content-Type: text/plain; charset=us-ascii

Lowell Gilbert <freebsd-que...@be-well.ilk.org> writes:

> Polytropon <fre...@edvax.de> writes:
>
>> On Wed, 30 Jul 2008 18:05:59 +0100, Glyn Millington <gl...@millingtons.org> wrote:
>>> "Joey Mingrone" <jo...@mingrone.org> writes:
>>> > fonts, but it seems they are in the teTex port, but that port
>>> > conflicts with the tex port and it seems teTex is no longer being
>>> > updated.
>>>
>>> Alas the news about teTeX is true.
>>
>> I'm very sad to hear this, allthough I'm always installing teTeX
>> via pkg_add -r, and I never found something not working anymore.
>> Is there any consideration to remove teTeX completely from the
>> ports tree, or is it still valid to keep using it?
>>
>> (I use LaTeX for nearly everything: work, documentation, literature,
>> even for letters (dinbrief class), so I'm interested in this topic.)
>>
>> Many thanks for pointing out how to get \LaTeX{} from TeXLive.
>
> teTeX still works fine; well enough that I haven't been tempted to try
> porting TeXLive yet...

I forgot to mention that the FreeBSD documentation project
(textproc/docproj*) still uses teTeX, so I keep that installed anyway.

--
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/

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

Message: 22
Date: Wed, 30 Jul 2008 15:21:42 -0400
From: "John Wilson" <jmw...@panix.com>
Subject: 7.0-stable snapshot
To: <freebsd-...@freebsd.org>
Message-ID: <4C564DCD5031485291A5A59BCE1F9637@JohnPC>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original

Good day.

I recently attempted to install the most recent AMD64 7.0-snapshot onto
another system. I chose a minimal install with all of the source
distributions as well as ports. Unfortunately, the install fails when
attempting to install the scompat tarball. Upon looking at the install CD,
it appears that the scompat tarball is not listed in the src directory.

src/scompat does seem to appear on a 7.0-release CD. I've attempted to
reburn the snapshot with the same results. Naturally, if I omit scompat
from the src install options, the install proceeds normally and without
error.

I'm just curious as to where the problem actually resides. Are the
7.0-snapshots leaving out scompat for some reason? Since I've attempted to
download and burn multiple snaps with the same issue, I can't see that I've
a corrupt ISO.

Thank you for your time.

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

Message: 23
Date: Wed, 30 Jul 2008 21:43:52 +0200
From: Roland Smith <rsm...@xs4all.nl>
Subject: Re: question about new monitor...
To: FreeBSD Mailing List <freebsd-...@freebsd.org>
Message-ID: <20080730194...@slackbox.xs4all.nl>
Content-Type: text/plain; charset="us-ascii"

I forgot to check on Wikipedia. :) For those who are interested, see
http://en.wikipedia.org/wiki/Display_Data_Channel and
http://en.wikipedia.org/wiki/VESA_Display_Data_Channel for more in-depth info.

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

Message: 24
Date: Wed, 30 Jul 2008 15:57:29 -0700
From: Patrick Baldwin <Patrick...@studsvik.com>
Subject: Building a FreeBSD based mail server
To: freebsd-...@freebsd.org
Message-ID: <4890F1D9...@studsvik.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I posted a few weeks ago about being interested in building a FreeBSD based
mail server, and got a lot of good input. In my research since then, I
found
this:

http://www.purplehat.org/?page_id=4

Which seems to me to be a pretty good guide to building a FreeBSD based
Postifx/SpamAssassin
mailserver. However, never having done this before myself, I was
wondering if anyone here
had any useful comments about this guide, particularly if you think it's
missing any key points
that will leave me cursing at my monitor late one night.

I'm currently planning on using FreeBSD 7.0-RELEASE, although I'm
certainly open to
sugegstions if people think a different version would serve better.

--
Patrick Baldwin
Systems Administrator
Studsvik Scandpower
617-965-7455

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

Message: 25
Date: Wed, 30 Jul 2008 12:08:11 -0700
From: Tim Traver <tt-...@simplenet.com>
Subject: sendmail base configuration
To: bsd <freebsd-...@freebsd.org>
Message-ID: <4890BC1B...@simplenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi all,

I know this isn't exactly the right place for a sendmail question, but
it has to do with the system configuration, and I'm trying to find some
help to create a relatively simple solution (I think)...

ok, here is what I want to do, which I have done in the past, but now it
doesn't seem to be working...

I simply want any submitted email using sendmail to be relayed to
another mta for distribution. I want this to happen both from submitted
mail from the command line, and from any queues, if the mail is
submitted to the running daemon.

I use FreeBSD 7.0, and all of the configuration is in /etc/mail/. From
what I understand, if I simply set the DS variable to a hostname, it is
supposed to use that as the smart relay host, but it is not working. For
some reason, it is ignoring that hostname, and attempting to contact the
MX record host for the domain name of the machine, which is really weird.

So, I tried setting the DS and the MTAHost variables to the IP of the
machine I want it to go to, and that seems to work, but oddly enough,
sendmail replaces the Rcpt To: variable with my current logged in
username@machine host instead of the address that I gave on the command
line to send the mail to...

So, for instance, I would do a command like this :

/usr/sbin/sendmail -v t...@domain.com
Subject:test from command line

test

.
tt... Connecting to [209.132.x.xx] via relay...
220 relayhost.scaledsystems.com ESMTP
>>> EHLO script5.scaledsystems.com
250-scriptmail.scaledsystems.com
250-PIPELINING
250 8BITMIME
>>> MAIL From:<>
250 ok
>>> RCPT To:<t...@script5.scaledsystems.com>
>>> DATA
250 ok
354 go ahead
>>> .
250 ok 1217444220 qp 69963
tt... Sent (ok 1217444220 qp 69963)
Closing connection to [209.132.x.xx]
>>> QUIT
221 relayhost.scaledsystems.com

I've checked DNS, etc...but I find it strange that it replaces the RCPT
To to be my local user...

Is this a bounce or something??? Is it bouncing the message based on
some sort of new relaying rules or something?

Cause I haven't seen this on older FreeBSD hosts...

the version of sendmail is 8.14.2

Thanks,

Tim.

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

Message: 26
Date: Wed, 30 Jul 2008 15:23:52 -0500
From: Derek Ragona <de...@computinginnovations.com>
Subject: Re: SCSI RAID on FreeBSD 7.0, where is the array?
To: "ghost...@gmail.com" <ghost...@gmail.com>,
freebsd-...@freebsd.org
Message-ID:
<6.0.0.22.2.200807...@mail.computinginnovations.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 07:56 AM 7/30/2008, ghost...@gmail.com wrote:
>Hi all,
>
>
>I am fighting the following hardware:
>
>MB: ASUS p5b-plus (NON vista edition)
>Cpu: Core 2 duo 4600
>SCSI Card: Adaptec 39320 (Unused Dell OEM bought from ebay)
>HDDs: 2xSeagate Cheetah 73.4 GB Ultra320 SCSI (posibly Dell OEM)
>
>Nb. The MB does not support PCI-X, but is backwards compatible to a
>standard PCI slot. On recommendations I have limited the throughput on the
>channels to 160mb.
>
>If you think any other pieces relevant let me know.
>
>
>I think this is probably just an issue with my not knowing wtf I'm doing,
>but to be optimistic lets assume the ahd module worked as there are no
>errors in dmesg; which device do I install to? I can not see see ahd0 in fdisk.
>
>There are alot of posts over the years reporting trouble with the
>Dell(Adaptec/Seagate) combiniation. The funny thing is that I am having
>none of these troubles; There are no panics, no dumps and no lengthy
>pauses. It all seems fine, until I try to select the disk to install to
>and I only have da0 or da1.
>
>
>
>Thanks for your time

Have you defined an array?

If you create the array in the adaptec BIOS you will see one large hard
disk in FreeBSD. If you do not define an array in the adaptec BIOS you
will see the individual SCSI drives as da0, da1, etc.

The GENERIC kernel has all the typical SCSI and RAID adapters compiled in,
so look at the dmesg output when you boot FreeBSD.

-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Message: 27
Date: Wed, 30 Jul 2008 16:25:51 -0400
From: Lowell Gilbert <freebsd-que...@be-well.ilk.org>
Subject: Re: Building modules distributed with Apache, using ports
To: Jonathan McKeown <jonathan+free...@hst.org.za>
Cc: freebsd-...@freebsd.org
Message-ID: <44r69b1...@be-well.ilk.org>
Content-Type: text/plain; charset=us-ascii

Jonathan McKeown <jonathan+free...@hst.org.za> writes:

> This may be a daft question. I freely admit it's a lazy one - I'm hoping
> someone has a quick answer that'll save me a couple of hours building a test
> server and experimenting.
>
> I built apache 2.0 from ports, using WITH_LDAP - but not WITH_LDAP_MODULES, as
> the Makefile.doc says it's implied by WITH_LDAP. As far as I can tell it's
> actually the other way round, that WITH_LDAP_MODULES triggers the WITH_LDAP
> options (either that or I didn't set it properly).
>
> Be that as it may, I now have an installation of Apache to which I need to add
> mod_auth_ldap and mod_ldap from the Apache 2.0 distribution.
>
> Is it possible to use the www/apache20 port to build these, or additional
> modules generally, without rebuilding/reinstalling Apache itself?

Not really, no.

--
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/

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

Message: 28
Date: Wed, 30 Jul 2008 13:29:21 -0700 (PDT)
From: Jakub Lach <jakub...@mailplus.pl>
Subject: Re: When gcc43 is expected to be in base?
To: freebsd-...@freebsd.org
Message-ID: <187422...@talk.nabble.com>
Content-Type: text/plain; charset=us-ascii

Kris Kennaway-3 wrote:
>
> Jakub Lach wrote:
>>
>>
>> Kris Kennaway-3 wrote:
>>> Jakub Lach wrote:
>>>> I'm eager to have core2 march, but don't want to mess system forcing
>>>> gcc43 as
>>>> base.
>>> I don't think it is planned to update to gcc 4.3 since it is covered by
>>> the GPLv3.
>>
>> Thanks for fast answer, is there any chance that licensing stuff is going
>> to
>> be omitted?
>
> There is basically no chance the GCC developers will reconsider their
> decision to relicense GCC 4.3 to GPLv3.
>
>> If not, will then FreeBSD move to another compiler?
>
> The existing gcc 4.2 will be supported for some time by the gcc
> developers. In the meantime hopefully llvm/clang will mature enough to
> provide an alternative. It is already quite far along and has
> significant resources behind it (apple, etc).
>
> Kris
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questi...@freebsd.org"
>
>

Thank you very much for all answers.

--
View this message in context: http://www.nabble.com/When-gcc43-is-expected-to-be-in-base--tp18736784p18742235.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

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

Message: 29
Date: Wed, 30 Jul 2008 22:33:29 +0200
From: "Jack Raats" <ja...@jarasoft.net>
Subject: Re: Building a FreeBSD based mail server
To: "Patrick Baldwin" <Patrick...@studsvik.com>,
<freebsd-...@freebsd.org>
Message-ID: <EECBBBDCA33846E5...@jarasoft.net>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=response

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick Baldwin" <Patrick...@studsvik.com> schreef in bericht
news:4890F1D9...@studsvik.com...

>I posted a few weeks ago about being interested in building a FreeBSD based
> mail server, and got a lot of good input. In my research since then, I
> found
> this:
>
> http://www.purplehat.org/?page_id=4
>
> Which seems to me to be a pretty good guide to building a FreeBSD based
> Postifx/SpamAssassin
> mailserver. However, never having done this before myself, I was
> wondering if anyone here
> had any useful comments about this guide, particularly if you think it's
> missing any key points
> that will leave me cursing at my monitor late one night.

I should add postgrey and clamsmtp.
Postgrey is a very good greylisting filter for postfix and clamsmtp I use
for the interface between postfix and clamav.
I never heard of Maia-Mailguard but it look like clamsmtp.

Jack

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32) - GPGrelay v0.959

iD8DBQFIkNAaPh5RwW/NzC4RAh9xAJsGuUOYbjIqohoHwlpYJ6BnvabGaACgx0Qp
iZpmNJTW5DhO0n3bnS55+aY=
=+kzI
-----END PGP SIGNATURE-----

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

Message: 30
Date: Wed, 30 Jul 2008 16:20:06 -0500
From: Derek Ragona <de...@computinginnovations.com>
Subject: Re: setting the other end's TCP segment size
To: per...@pluto.rain.com, kera...@ceid.upatras.gr
Cc: freebsd-...@freebsd.org
Message-ID:
<6.0.0.22.2.200807...@mail.computinginnovations.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:04 PM 7/29/2008, per...@pluto.rain.com wrote:
> > [TCP] splits traffic to 'segments' using its own logic ...
>
>Is there a simple way for a FreeBSD system to cause its peer
>to use a transmit segment size of, say, 640 bytes -- so that
>the peer will never try to send a packet larger than that?
>
>I'm trying to get around a network packet-size problem.
>In case it matters, the other end is SunOS 4.1.1 on a sun3, and
>I've been unable to find a way to limit its packet size directly.
>_______________________________________________
>freebsd-...@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>
>--

Just as an FYI, you might want to do:
man setsockopt
ro
man getsockopt

Each tcp conversation can have it's own size set along with a bunch of
other params.

-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Message: 31
Date: Wed, 30 Jul 2008 16:22:36 -0500
From: Derek Ragona <de...@computinginnovations.com>
Subject: Re: Mail Heading to dead.letter
To: "Andy Christianson" <andy.chri...@gmail.com>, "Ruben de
Groot" <mai...@bzerk.org>
Cc: freebsd-...@freebsd.org
Message-ID:
<6.0.0.22.2.200807...@mail.computinginnovations.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 07:52 AM 7/30/2008, Andy Christianson wrote:
>Sendmail is running & DNS is working. See the following output:
>
>[root@fbsd /home/andy]# /etc/rc.d/sendmail status
>sendmail_submit is running as pid 71703.
>sendmail_clientmqueue is running as pid 675.
>[root@fbsd /home/andy]# ping gmail.com
>PING gmail.com (64.233.161.83): 56 data bytes
>64 bytes from 64.233.161.83: icmp_seq=0 ttl=239 time=19.943 ms
>64 bytes from 64.233.161.83: icmp_seq=1 ttl=239 time=22.096 ms
>64 bytes from 64.233.161.83: icmp_seq=2 ttl=239 time=22.568 ms
>64 bytes from 64.233.161.83: icmp_seq=3 ttl=239 time=19.368 ms
>^C
>--- gmail.com ping statistics ---
>4 packets transmitted, 4 packets received, 0.0% packet loss
>round-trip min/avg/max/stddev = 19.368/20.994/22.568/1.364 ms
>[root@fbsd /home/andy]# mail andy.chri...@gmail.com
>Subject: Test
>This is a test!!
>EOT
>[root@fbsd /home/andy]# exit
>exit
>[andy@fbsd ~]$ mail andy.chri...@gmail.com
>Subject: Another test!!
>Test sent from a normal user
>EOT
>[andy@fbsd ~]$ /home/andy/dead.letter... Saved message in
>/home/andy/dead.letter
>

Check perms on /var/mail that it is set to 775

-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Message: 32
Date: Wed, 30 Jul 2008 17:15:40 -0400
From: Jeff Wheelhouse <freebsd-...@wheelhouse.org>
Subject: Bizarre Diskless Boot Behavior
To: freebsd-...@freebsd.org
Message-ID: <6C89B0E1-5309-4C27...@wheelhouse.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

I have a number of diskless FreeBSD servers. Usually, they work
fine. But sometimes when I reboot one, I get weird messages on the
console like this:

FreeBSD/i386 bootstrap loader, Revision 1.1
(root@e2, Sat Jan 19 16:41:40 MST 2008)
pxe_open: server addr: 1.2.3.4
pxe_open: server path: /path/to/NFS/Root
pxe_open: gateway ip: 1.2.3.1
\
Insert disk labelled Loader.rc and press any key...

It isn't always "Loader.rc" though, it seems quasi-random. I've also
seen:

Insert disk labelled ELF and press any key...
Insert disk labelled boot.nfsroot.options="nfsv3,soft,intr,tcp" and
press any key...

(The latter being the first line of loader.conf.)

I think these incidents correspond to the following strange xferlog
entries from tftpd on the boot server:

Jul 30 20:15:03 xx tftpd[86096]: 1.2.3.11: read request for \.split:
File not found
Jul 30 20:15:03 xx tftpd[86098]: 1.2.3.11: read request for \.split:
File not found
Jul 30 20:15:03 xx tftpd[86100]: 1.2.3.11: read request for
\.gz.split: File not found
Jul 30 20:15:03 xx tftpd[86102]: 1.2.3.11: read request for \.gz: File
not found
Jul 30 20:15:03 xx tftpd[86104]: 1.2.3.11: read request for \: File
not found

Rebooting generally makes it go away, so it's not a *big* deal, but I
wouldn't want this to happen in the event of an unattended panic/
reboot or something. Does anyone have any ideas what might cause this?

Thanks!

Jeff

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

Message: 33
Date: Thu, 31 Jul 2008 07:32:23 +1000
From: Michael Christie <mic...@powerzone.net.au>
Subject: Group Limits
To: freebsd-...@freebsd.org
Message-ID: <4890DDE7...@powerzone.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi there,

I am running webmin and virtualmin on freebsd 7.0, I have found when
i add a number of domains using virtualmin and restart apachie i get the
following error.

[alert] (22)Invalid argument: initgroups: unable to set groups for User
www and Group 80... Apachie will not start..

it happens when the 'apache' or 'httpd' user is a member of too many groups. By default,
Virtualmin adds the user Apache runs as to each domain's group, which
eventually triggers this problem.

Can any one advise me how to expand the number of groups allow on freebsd I think my default it is 16, I need to make it 50 to 100

Thank you

Michael

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

Message: 34
Date: Wed, 30 Jul 2008 15:17:23 -0700
From: "Steve Franks" <steve...@ieee.org>
Subject: resume (hate to even ask)
To: "FreeBSD Mailing List" <freebsd-...@freebsd.org>
Message-ID:
<539c60b90807301517v6c5...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Ok,

I have too many systems with varying degrees of working freebsd on
them, and I can't seem to leave well enough alone. I hear lots of
people having sucess with suspend, and I can't get it to work on a
single system.

My current strongest desire is to get it running on my hp ze4500
laptop. I've played with the stuff in the handbook, but that just
took me from having a blank screen and no responses from Ctl-Alt-F(x)
to now the fan comes on for a moment on resume, then the system powers
off....doesn't seem to matter if X is up or not.

I've kldunloaded usb, radeon, sound, drm, what else should I try?
Also, rc.resume has a typo, right? I'm susposed to change the
#kldunload usb section to add kldload usb (and friends) right?

Steve

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

End of freebsd-questions Digest, Vol 226, Issue 10
**************************************************

0 new messages