Welcome to FreeBSDFreaks.net!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

make.conf file - PLEASE HELP

 
   FreeBSD Hosting (Home) -> FreeBSD Handbook RSS
Next:  make.conf file - HELP PLEASE  
Author Message
sh4d03

External


Since: Sep 07, 2004
Posts: 2



(Msg. 1) Posted: Tue Sep 07, 2004 7:29 pm
Post subject: make.conf file - PLEASE HELP
Archived from groups: comp>unix>bsd>freebsd>misc (more info?)

I have followed the instructions as per the following url in order to
update my FreeBSD fileserver. The server is currently running FreeBSD
4.9 and I would like to update it to the latest RELEASE version. The
instructions on the following url have been followed without any
problems until it comes to:
"make buildworld"
Initially when I ran this command it would proceed correctly for some
time and then error out. (I can't remember the error any more, but when
I posted it in newsgroup I was told to clear out /usr/src and start
again. I did this and then re-cvsup'd my /usr/src files and am now
trying to do the "make buildworld" - the problem is that it now reports
"make: can't make buildworld"
After some research I initially found that my make.conf file simply
didn't exist. What I'd like to do now is replace it with a make.conf
that will work with my hardware etc. I have attempted to copy the
example file and edit it to what I beileve is correct and have placed
the file here: /etc/make.conf - however still when I run the make
buildworld command it says it doesn't know how to make buildworld. I'm
thinking there is something wrong with my make.conf but I'm not certain
how to create one that is correct for my system. I have tried following
the man pages and the comments within the file but I must admit I just
get lost.

First question - is this what I need to do to update my FreeBSD system
to the latest RELEASE?

Second question - how can I re-create my make.conf in layman's terms?

I'm not quite a newbie with Linux/BSD however the make.conf file is one
I haven't had much to do with directly. So please be gentle, and patient.

I've also included my cvs-supfile and make.conf file as they are. The
make.conf I have at the moment I have placed in the /etc folder - I did
this by copying the example file and attempting to modify it to suit my
system - I'm not sure if I've done that correctly.

http://freebsdaddicts.org/modules.p...age&artid=6





CVS-SUPFILE:


$FreeBSD: src/share/examples/cvsup/cvs-supfile,v 1.26.2.11 2003/09/12
19:01:13 ceri Exp $
#
# This file contains all of the "CVSup collections" that make up the
# CVS development tree of the FreeBSD system.
#
# CVSup (CVS Update Protocol) allows you to download the latest CVS
# tree (or any branch of development therefrom) to your system easily
# and efficiently (far more so than with sup, which CVSup is aimed
# at replacing). If you're running CVSup interactively, and are
# currently using an X display server, you should run CVSup as follows
# to keep your CVS tree up-to-date:
#
# cvsup cvs-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
# cvsup -g -L 2 cvs-supfile
#
# You may wish to change some of the settings in this file to better
# suit your system:
#
# host=CHANGE_THIS.FreeBSD.org
# This specifies the server host which will supply the
# file updates. You must change it to one of the CVSup
# mirror sites listed in the FreeBSD Handbook at
# http://www.freebsd.org/doc/handbook/mirrors.html.
# You can override this setting on the command line
# with cvsup's "-h host" option.
#
# base=/usr
# This specifies the root where CVSup will store information
# about the collections you have transferred to your system.
# A setting of "/usr" will generate this information in
# /usr/sup. Even if you are CVSupping a large number of
# collections, you will be hard pressed to generate more than
# ~1MB of data in this directory. You can override the
# "base" setting on the command line with cvsup's "-b base"
# option. This directory must exist in order to run CVSup.
#
# prefix=/home/ncvs
# This specifies where to place the requested files. A
# setting of "/home/ncvs" will place all of the files
# requested in /home/ncvs (e.g., "/home/ncvs/src/bin",
# "/home/ncvs/ports/archivers"). The prefix directory
# must exist in order to run CVSup.

# Defaults that apply to all the collections
#
# IMPORTANT: Change the next line to use one of the CVSup mirror sites
# listed at http://www.freebsd.org/doc/handbook/mirrors.html.
*default host=cvsup.au.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
#*default compress

## Main Source Tree.
#
# The easiest way to get the main source tree is to use the "src-all"
# mega-collection. It includes all of the individual "src-*" collections.
src-all

# These are the individual collections that make up "src-all". If you
# use these, be sure to comment out "src-all" above.
#src-base
#src-bin
#src-contrib
#src-etc
#src-games
#src-gnu
#src-include
#src-kerberos5
#src-kerberosIV
#src-lib
#src-libexec
#src-release
#src-sbin
#src-share
#src-sys
#src-tools
#src-usrbin
#src-usrsbin
# These are the individual collections that make up FreeBSD's crypto
# collection. They are no longer export-restricted and are a part of
# src-all
#src-crypto
#src-eBones
#src-secure
#src-sys-crypto

## Ports Collection.
#
# The easiest way to get the ports tree is to use the "ports-all"
# mega-collection. It includes all of the individual "ports-*"
# collections,
ports-all

# These are the individual collections that make up "ports-all". If you
# use these, be sure to comment out "ports-all" above and always include
# "ports-base" if you use any of the other individual collections below.
# Your ports may not build correctly without an up-to-date "ports-base".
#
#ports-base
#
#ports-archivers
#ports-astro
#ports-audio
#ports-benchmarks
#ports-biology
#ports-cad
#ports-chinese
#ports-comms
#ports-converters
#ports-databases
#ports-deskutils
#ports-devel
#ports-dns
#ports-editors
#ports-emulators
#ports-finance
#ports-french
#ports-ftp
#ports-games
#ports-german
#ports-graphics
#ports-hebrew
#ports-hungarian
#ports-irc
#ports-japanese
#ports-java
#ports-korean
#ports-lang
#ports-mail
#ports-math
#ports-mbone
#ports-misc
#ports-multimedia
#ports-net
#ports-news
#ports-palm
#ports-picobsd
#ports-polish
#ports-portuguese
#ports-print
#ports-russian
#ports-science
#ports-security
#ports-shells
#ports-sysutils
#ports-textproc
#ports-ukrainian
#ports-vietnamese
#ports-www
#ports-x11
#ports-x11-clocks
#ports-x11-fm
#ports-x11-fonts
#ports-x11-servers
#ports-x11-toolkits
#ports-x11-wm

## Documentation
#
# The easiest way to get the doc tree is to use the "doc-all"
# mega-collection. It includes all of the individual "doc-*"
# collections,
doc-all

## CVSROOT control files
#
# This is to get the control files that cvs(1) needs and the commit logs.
cvsroot-all

# These are the individual collections that make up "cvsroot-all" If you
# use these, be sure to comment out "cvsroot-all" above. "cvsroot-common"
# is a synthetic CVSROOT that has all the modules from the other CVSROOT-*
# directories merged into one, and merged commitlogs via symlinks.
#cvsroot-common
#cvsroot-src
#cvsroot-ports
#cvsroot-doc


****************************************************************************************************
********************
****************************************************************************************************
********************
****************************************************************************************************
********************

MAKE.CONF



# $FreeBSD: src/etc/defaults/make.conf,v 1.97.2.81 2003/07/12 23:22:51
gshapiro Exp $
#
# NOTE: Please would any committer updating this file also update the
# make.conf(5) manual page, if necessary, which is located in
# src/share/man/man5/make.conf.5.
#
# This file, if present, will be read by make (see /usr/share/mk/sys.mk).
# It allows you to override macro definitions to make without changing
# your source tree, or anything the source tree installs.
#
# This file must be in valid Makefile syntax.
#
# You have to find the things you can put here in the Makefiles and
# documentation of the source tree.
#
#
# The CPUTYPE variable controls which processor should be targeted for
# generated code. This controls processor-specific optimizations in
# certain code (currently only OpenSSL) as well as modifying the value
# of CFLAGS to contain the appropriate optimization directive to gcc.
# The automatic setting of CFLAGS may be overridden using the
# NO_CPU_CFLAGS variable below.
# Currently the following CPU types are recognized:
# Intel x86 architecture:
# (AMD CPUs) k7 k6-2 k6 k5
# (Intel CPUs) p4 p3 p2 i686 i586/mmx i586 i486 i386
# Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4
#
# If you experience any problems after setting this flag, please unset
# it again before submitting a bug report or attempting to modify code.
# It may be that certain types of software will become unstable after being
# compiled with processor-specific (or higher - see below) optimization
flags.
# If in doubt, do not set CPUTYPE or CFLAGS to non-default values.
#
CPUTYPE=i586
#NO_CPU_CFLAGS= true # Don't add -march=<cpu> to CFLAGS automatically
#NO_CPU_COPTFLAGS=true # Don't add -march=<cpu> to COPTFLAGS automatically
#
# CFLAGS controls the compiler settings used when compiling C code.
# Note that optimization settings above -O (-O2, ...) are not recommended
# or supported for compiling the world or the kernel - please revert any
# nonstandard optimization settings to "-O" before submitting bug reports
# to the developers.
# Note also that at this time the -O2 setting is known to produce BROKEN
# CODE on the Alpha platform.
#
CFLAGS= -O -pipe
#
# CXXFLAGS controls the compiler settings used when compiling C++ code.
# Note that CXXFLAGS is initially set to the value of CFLAGS. If you wish
# to add to CXXFLAGS value, "+=" must be used rather than "=". Using "="
# alone will remove the often needed contents of CFLAGS from CXXFLAGS.
#
CXXFLAGS+= -fmemoize-lookups -fsave-memoized
#
# BDECFLAGS are a set of gcc warning settings that Bruce Evans has suggested
# for use in developing FreeBSD and testing changes. They can be used by
# putting "CFLAGS+=${BDECFLAGS}" in /etc/make.conf. -Wconversion is not
# included here due to compiler bugs, e.g., mkdir()'s mode_t argument.
#
BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
-Wcast-qual -Wchar-subscripts -Winline \
-Wmissing-prototypes -Wnested-externs -Wpointer-arith \
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
#
# WARNS_WERROR causes -Werror to be added when WARNS is in effect.
#
#WARNS_WERROR= yes
#
# To compile just the kernel with special optimizations, you should use
# this instead of CFLAGS (which is not applicable to kernel builds anyway).
# There is very little to gain by using higher optimization levels, and
doing
# so can cause problems.
#
COPTFLAGS= -O -pipe
#
# Compare before install
INSTALL=install -C
#
# To enable installing suidperl with the setuid bit turned on
#ENABLE_SUIDPERL= true
#
# To build ppp with normal permissions
PPP_NOSUID= true
#
# To enable installing ssh(1) with the setuid bit turned on
ENABLE_SUID_SSH= true
#
# To avoid building various parts of the base system:
#NO_CVS= true # do not build CVS
#NO_BIND= true # do not build BIND
#NO_FORTRAN= true # do not build g77 and related libraries
#NO_I4B= true # do not build isdn4bsd package
#NO_IPFILTER= true # do not build IP Filter package
#NO_LPR= true # do not build lpr and related programs
#NO_MAILWRAPPER=true # do not build the mailwrapper(Cool MTA selector
#NO_MODULES= true # do not build modules with the kernel
#NO_OBJC= true # do not build Objective C support
#NO_OPENSSH= true # do not build OpenSSH
#NO_OPENSSL= true # do not build OpenSSL (implies NO_OPENSSH)
#NO_SENDMAIL= true # do not build sendmail and related programs
#NO_SHAREDOCS= true # do not build the 4.4BSD legacy docs
#NO_TCSH= true # do not build and install /bin/csh (which is tcsh)
#NO_X= true # do not compile in XWindows support (e.g. doscmd)
#NOCRYPT= true # do not build any crypto code
#NOGAMES= true # do not build games (games/ subdir)
#NOINFO= true # do not make or install info files
#NOLIBC_R= true # do not build libc_r (re-entrant version of libc)
#NOMAN= true # do not build manual pages
#NOPERL= true # do not build perl. Disables OpenSSL optimizations
#NOPROFILE= true # Avoid compiling profiled libraries
#NOSECURE= true # do not build crypto code in secure/ subdir
#NOSHARE= true # do not go into the share subdir
#NOUUCP= true # do not build uucp related programs
#
# To build sys/modules when building the world (our old way of doing things)
#MODULES_WITH_WORLD=true # do not build modules when building kernel
#
# The list of modules to build instead of all of them.
#MODULES_OVERRIDE= linux ipfw
#
# The following controls building optional IDEA code in libcrypto and
# certain ports. Patents are involved - you must not use this unless
# you either have a license or fall within patent 'fair use'
# provisions.
#
# *** It is YOUR RESPONSIBILITY to determine if you can use this! ***
#
# IDEA is patented in the USA and many European countries - thought to
# be OK to use for any non-commercial use. This is optional.
#MAKE_IDEA= YES # IDEA (128 bit symmetric encryption)
#
# To avoid running MAKEDEV all on /dev during install:
#NO_MAKEDEV= true
#
# If you do not want unformatted manual pages to be compressed
# when they are installed:
#
#NOMANCOMPRESS= true
#
#
# If you want the "compat" shared libraries installed as part of your normal
# builds, uncomment these:
#
#COMPAT1X= yes
#COMPAT20= yes
#COMPAT21= yes
#COMPAT22= yes
#COMPAT3X= yes
#COMPAT4X= yes
#
#
# If you do not want additional documentation (some of which are
# a few hundred KB's) for ports to be installed:
#
#NOPORTDOCS= true
#
#
# Default format for system documentation, depends on your printer.
# Set this to "ascii" for simple printers or screen
#
PRINTERDEVICE=ascii
#
#
# How long to wait for a console keypress before booting the default kernel.
# This value is approximately in milliseconds. Keypresses are accepted
by the
# BIOS before booting from disk, making it possible to give custom boot
# parameters even when this is set to 0.
#
BOOTWAIT=0
#BOOTWAIT=30000
#
# By default, the system will always use the keyboard/video card as system
# console. However, the boot blocks may be dynamically configured to use a
# serial port in addition to or instead of the keyboard/video console.
#
# By default we use COM1 as our serial console port *if* we're going to use
# a serial port as our console at all. Alter as necessary.
#
# COM1: = 0x3F8, COM2: = 0x2F8, COM3: = 0x3E8, COM4: = 0x2E8
#
#BOOT_COMCONSOLE_PORT= 0x3F8
#
# The default serial console speed is 9600. Set the speed to a larger value
# for better interactive response.
#
#BOOT_COMCONSOLE_SPEED= 115200
#
# By default the 'pxeboot' loader retrieves the kernel via NFS. Defining
# this and recompiling /usr/src/sys/boot will cause it to retrieve the
kernel
# via TFTP. This allows pxeboot to load a custom BOOTP diskless kernel yet
# still mount the server's '/' (i.e. rather than load the server's kernel).
#
#LOADER_TFTP_SUPPORT= YES
#
# By default, the ports collection attempts to use XFree86 4.X. If
# you are running XFree86 3.3.X, uncomment this line.
#
#XFREE86_VERSION= 3
#
# By default, this points to /usr/X11R6 for XFree86 releases 3.0 or earlier.
# If you have a XFree86 from before 3.0 that has the X distribution in
# /usr/X386, you want to uncomment this.
#
#X11BASE= /usr/X386
#
#
# If you have Motif on your system, uncomment this.
#
#HAVE_MOTIF= yes
#MOTIF_STATIC= yes
#
# If the default location of the Motif library (specified below) is NOT
# appropriate for you, uncomment this and change it to the correct value.
# If your motif is in ${X11BASE}/lib, you don't need to touch this line.
#
#MOTIFLIB= -L${X11BASE}/lib -lXm
#
#
# If you're resident in the USA, this will help various ports to determine
# whether or not they should attempt to comply with the various U.S.
# export regulations on certain types of software which do not apply to
# anyone else in the world.
#
#USA_RESIDENT= YES
#
#
# Override "don't install a port that's already installed" behavior.
# One might wish to do this for ports debugging or to unconditionally
# reinstall a set of suspect/broken ports.
#
#FORCE_PKG_REGISTER= YES
#
#
# If you're behind a firewall and need FTP or HTTP proxy services for
# ports collection fetching to work, the following examples give the
# necessary syntax. See the fetch(3) man page for details.
#
#FETCH_ENV= FTP_PROXY=ftp://10.0.0.1:21
#FETCH_ENV= HTTP_PROXY=http://10.0.0.1:80
#
#
# Port master sites.
#
# If you want your port fetches to go somewhere else than the default
# (specified below) in case the distfile/patchfile was not found,
# uncomment this and change it to a location nearest you. (Don't
# remove the "/${DIST_SUBDIR}/" part.)
#
#MASTER_SITE_BACKUP?= \
# ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/
#
# If you want your port fetches to check the above site first (before
# the MASTER_SITES specified in the port Makefiles), uncomment the
# line below. You can also change the right side to point to wherever
# you want.
#
#MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP}
#
# Some ports use a special variable to point to a collection of
# mirrors of well-known software archives. If you have a mirror close
# to you, uncomment any of the following lines and change it to that
# address. (Don't remove the "/%SUBDIR%/" part.)
#
# Note: the right hand sides of the following lines are only for your
# information. For a full list of default sites, take a look at
# bsd.sites.mk.
#
#MASTER_SITE_AFTERSTEP= ftp://ftp.afterstep.org/%SUBDIR%/
#MASTER_SITE_COMP_SOURCES=
ftp://gatekeeper.dec.com/pub/usenet...urces.%SUBDIR%/
#MASTER_SITE_FREEBSD_ORG= ftp://ftp.FreeBSD.org/pub/FreeBSD/%SUBDIR%/
#MASTER_SITE_GNOME= ftp://ftp.gnome.org/pub/GNOME/%SUBDIR%/
#MASTER_SITE_GNU= ftp://ftp.gnu.org/gnu/%SUBDIR%/
#MASTER_SITE_KDE= ftp://ftp.kde.org/pub/kde/%SUBDIR%/
#MASTER_SITE_LOCAL= ftp://ftp.FreeBSD.org/pub/FreeBSD/p...files/%SUBDIR%/
#MASTER_SITE_MOZILLA= ftp://ftp.mozilla.org/pub/%SUBDIR%/
#MASTER_SITE_NETBSD= ftp://ftp.netbsd.org/pub/NetBSD/pac...files/%SUBDIR%/
#MASTER_SITE_PERL_CPAN=
ftp://ftp.digital.com/pub/plan/perl...odule/%SUBDIR%/
#MASTER_SITE_PORTS_JP= ftp://ports.jp.FreeBSD.org/pub/Free...PORTS/%SUBDIR%/
#MASTER_SITE_RINGSERVER= ftp://ftp.dnsbalance.ring.gr.jp/pub/%SUBDIR%/
#MASTER_SITE_RUBY= ftp://ftp.ruby-lang.org/pub/ruby/%SUBDIR%/
#MASTER_SITE_SOURCEFORGE=
ftp://ftp2.sourceforge.net/pub/sourceforge/%SUBDIR%/
#MASTER_SITE_SOURCEWARE= ftp://ftp.freesoftware.com/pub/sourceware/%SUBDIR%/
#MASTER_SITE_SUNSITE= ftp://metalab.unc.edu/pub/Linux/%SUBDIR%/
#MASTER_SITE_TCLTK= ftp://ftp.scriptics.com/pub/tcl/%SUBDIR%/
#MASTER_SITE_TEX_CTAN= ftp://ftp.tex.ac.uk/tex-archive/%SUBDIR%/
#MASTER_SITE_THEMES= ftp://ftp.themes.org/pub/themes/%SUBDIR%/
#MASTER_SITE_WINDOWMAKER= ftp://ftp.windowmaker.org/pub/%SUBDIR%/
#MASTER_SITE_XCONTRIB= ftp://ftp.x.org/contrib/%SUBDIR%/
#MASTER_SITE_XEMACS= ftp://ftp.xemacs.org/pub/xemacs/%SUBDIR%/
#MASTER_SITE_XFREE= ftp://ftp.xfree86.org/pub/XFree86/%SUBDIR%/source/
#
# Also it is highly recommended that you configure MASTER_SORT_REGEX
# to choose better mirror sites for you. List awk(1)-style regular
# expressions separated by space so MASTER_SITES will be sorted in
# that order. The following example is for Japanese users; change
# "jp" part to your ccTLD ("de", "ru", "uk", etc.) or the domain names
# of your nearest/upstream networks to meet your needs.
#
#MASTER_SORT_REGEX?= ://[^/]*\.jp[/.]
#
# Ports can place their working directories somewhere other than under
# /usr/ports.
#WRKDIRPREFIX= /var/tmp
#
# Kerberos IV
# If you want KerberosIV (KTH eBones), define this:
#
#MAKE_KERBEROS4= yes
#
#
# Kerberos 5
# If you want Kerberos 5 (KTH Heimdal), define this:
#
#MAKE_KERBEROS5= yes
#
# Kerberos 5 su (k5su)
# If you want to use the k5su utility, define this to have it installed
# set-user-ID.
#ENABLE_SUID_K5SU= yes
#
#
# Kerberos5
# If you want to install MIT Kerberos5 port somewhere other than /usr/local,
# define this (this is also used to tell ssh1 that kerberos is needed):
#
#KRB5_HOME= /usr/local
#
#
# CVSup update flags. Edit SUPFILE settings to reflect whichever
distribution
# file(s) you use on your site (see /usr/share/examples/cvsup/README for
more
# information on CVSup and these files). To use, do "make update" in
/usr/src.
#
#SUP_UPDATE= yes
#
#SUP= /usr/local/bin/cvsup
#SUPFLAGS= -g -L 2
#SUPHOST= cvsup.uk.FreeBSD.org
#SUPFILE= /usr/share/examples/cvsup/stable-supfile
#PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile
#DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile
#
# top(1) uses a hash table for the user names. The size of this hash
# can be tuned to match the number of local users. The table size should
# be a prime number approximately twice as large as the number of lines in
# /etc/passwd. The default number is 20011.
#
#TOP_TABLE_SIZE= 101
#
# Documentation
#
# The list of languages and encodings to build and install
#
#DOC_LANG= en_US.ISO8859-1 ru_RU.KOI8-R
#
#
# sendmail
#
# The following sets the default m4 configuration file to use at
# install time. Use with caution as a make install will overwrite
# any existing /etc/mail/sendmail.cf. Note that SENDMAIL_CF is now
# deprecated. The value should be a fully qualified path name.
#
#SENDMAIL_MC=/etc/mail/myconfig.mc
#
# The following sets the default m4 configuration file for mail
# submission to use at install time. Use with caution as a make
# install will overwrite any existing /etc/mail/submit.cf. The
# value should be a fully qualified path name.
#
#SENDMAIL_SUBMIT_MC=/etc/mail/mysubmit.mc
#
# If you need to build additional .cf files during a make buildworld,
# include the full paths to the .mc files in SENDMAIL_ADDITIONAL_MC.
#
#SENDMAIL_ADDITIONAL_MC=/etc/mail/foo.mc /etc/mail/bar.mc
#
# Setting the following variable modifies the flags passed to m4 when
# building a .cf file from a .mc file. It can be used to enable
# features disabled by default.
#
#SENDMAIL_M4_FLAGS=
#
# Setting the following variables modifies the build environment for
# sendmail and its related utilities. For example, SASL support can be
# added with settings such as:
#
# with SASLv1:
# SENDMAIL_CFLAGS=-I/usr/local/include/sasl1 -DSASL
# SENDMAIL_LDFLAGS=-L/usr/local/lib
# SENDMAIL_LDADD=-lsasl
#
# with SASLv2:
# SENDMAIL_CFLAGS=-I/usr/local/include -DSASL=2
# SENDMAIL_LDFLAGS=-L/usr/local/lib
# SENDMAIL_LDADD=-lsasl2
#
# Note: If you are using Cyrus SASL with other applications which require
# access to the sasldb file, you should add the following to your
# sendmail.mc file:
#
# define(`confDONT_BLAME_SENDMAIL',`GroupReadableSASLDBFile')
#
#SENDMAIL_CFLAGS=
#SENDMAIL_LDFLAGS=
#SENDMAIL_LDADD=
#SENDMAIL_DPADD=
#
# Setting SENDMAIL_SET_USER_ID will install the sendmail binary as a
# set-user-ID root binary instead of a set-group-ID smmsp binary and will
# prevent the installation of /etc/mail/submit.cf.
# This is a deprecated mode of operation. See etc/mail/README for more
# information.
#
#SENDMAIL_SET_USER_ID=
#
# The permissions to use on alias and map databases generated using
# /etc/mail/Makefile. Defaults to 0640.
#
#SENDMAIL_MAP_PERMS=


--
If you require more assistance or if my suggestion works please E-mail me at
sh4d03 [at] TPG [dot] com [dot] au. Additionally, if you are able to provide
assistance to me and wish to E-mail me directly please also feel free to
contact me in this manner. Please ensure you include "Newsgroup_sh4d03"
in the
subject line. Please pay attention to the capitilisation!
Thanks,
Sh4d03

 >> Stay informed about: make.conf file - PLEASE HELP 
Back to top
Login to vote
MattD..

External


Since: Jul 29, 2004
Posts: 10



(Msg. 2) Posted: Tue Sep 07, 2004 7:29 pm
Post subject: Re: make.conf file - PLEASE HELP [Login to view extended thread Info.]
Imported from groups: per prev. post (more info?)

Back to top
Login to vote
Display posts from previous:   
Related Topics:
make.conf file - HELP PLEASE - I have followed the instructions as per the following url in order to update my FreeBSD fileserver. The server is currently running FreeBSD 4.9 and I would like to update it to the latest RELEASE version. The instructions on the following url have bee...

dhclient and /etc/resolv.conf - Hi All, This is probably something thats been asked a million times, but I need to ask anyway because googling for the answer, just points me to solutions for netbsd/openbsd, and the freebsd handbook hasnt really helped either. Short question, how do...

sound works with kldload, but not /boot/loader.conf? - Hi, I just tried playing a WAV file using xmms (this is the first time I've tried anything with sound on my installation). It issued a very generic error message, telling me things like "make sure your device is installed". I did some res...

Make Install -

Make World on FreeBSD 5.1 - Hi, How do I make a make world on FreeBSD version 5, is it the same things as version 4 or is there any differences ... ? Any tutorial, web site, else as FreeBSD handbook ... ? I'm currently running FreBSD 5.1 releases thx Seb
   FreeBSD Hosting (Home) -> FreeBSD Handbook All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]