FreeBSD « CopperEgg. Ports — freebsd tips v1.0 documentation. Updating available port list csup -L 2 -h cvsup1.fr.FreeBSD.org /usr/share/examples/cvsup/ports-supfile Installing portmaster cd /usr/ports/ports-mgmt/portmaster make install clean Deleting one program/lib (and force in case of unmet dependencies) pkg_delete xf86bigfontproto-1.2.0 pkg_delete -f xf86bigfontproto-1.2.0 Using portmaster portmaster -L #list installed ports and available updates.
Clean stale files cd /usr/ports && make -DNOCLEANDEPENDS clean yes|portmaster -t --clean-distfiles #usually without -t In case of missing dependencies, you might get errors like these : pkg_info: corrupted record (pkgdep line without argument), ignoring Search for missing dependencies cd /usr/ports/cat/portname make missing Search for all missing dependencies grep -A1 "^@pkgdep $" /var/db/pkg/*/+CONTENTS Search ports cd /usr/ports && make index make search name=<port-name> make search key=<keyword> Display the port who has installed a specified file: Display the files that where installed by a specific port: Portversion « Yet Another Sysadmin Blog … Le but de ce post est de détailler comment réaliser une authentification double pile sur Postfix pour envoyer des mails.
Les utilisateurs pourront à la fois se connecter via la GSSAPI ou un simple bind sur l'annuaire LDAP. Le choix de la méthode doit se faire au niveau du MUA, SMTP ne prévoie pas de mécanismes de négociation. 1) smtpd en SSL Ca se passe dans le master.cf : smtps inet n - - - - smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_sasl_local_domain=REALM -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING Puis on configure les certificats dans le main.cf : smtpd_tls_cert_file=/etc/postfix/ssl/server.crt smtpd_tls_key_file=/etc/postfix/ssl/server.key 2) Kerberos Pour Kerberos, il faut déja créer un principal smtp/fqdn@REALM et l'exporter sous forme de keytab. Enfin, le fichier /etc/postfix/sasl/smtpd.conf doit aussi être configuré : log_level: 5 pwcheck_method: saslauthd mech_list: GSSAPI PLAIN START=yes. Le Projet FreeBSD. Setting Up Network Interface Cards.
First, determine the model of the NIC and the chip it uses. FreeBSD supports a wide variety of NICs. Check the Hardware Compatibility List for the FreeBSD release to see if the NIC is supported. If the NIC is supported, determine the name of the FreeBSD driver for the NIC. Refer to /usr/src/sys/conf/NOTES and /usr/src/sys/arch/conf/NOTES for the list of NIC drivers with some information about the supported chipsets. When in doubt, read the manual page of the driver as it will provide more information about the supported hardware and any known limitations of the driver. The drivers for common NICs are already present in the GENERIC kernel, meaning the NIC should show up during boot.
In this example, two NICs using the dc(4) driver are present on the system: If the driver for the NIC is not present in GENERIC, but a driver is available, the driver will need to be loaded before the NIC can be configured and used. 12.5.1.1. To use ndisgen(8), three things are needed: # kldload . FreeBSD Server Administration.