Re: Import of DragonFly Mail Agent
Thomas Mueller wrote There needs to be better documentation of sendmail if it is to be kept, and the option to compile sendmail for fuller function including SSL and TLS Apparently sendmail is compiled with ssl/tls support in FreeBSD, standard. This is what i get by sending mail from my freshly installed FreeBSD-10 machine niobe to the lab's mailhub (running postfix) Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN niobe.lpthe.jussieu.fr, Issuer niobe.lpthe.jussieu.fr (not verified)) by parthe.lpthe.jussieu.fr (Postfix) with ESMTPS id 18143E4DE9 and indeed i see niobe% telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 niobe.lpthe.jussieu.fr ESMTP Sendmail 8.14.7/8.14.7; Tue, 25 Feb 2014 16:41:11 +0100 (CET) ehlo lpthe.jussieu.fr 250-niobe.lpthe.jussieu.fr Hello localhost [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-STARTTLS 250-DELIVERBY 250 HELP There is a directory /etc/mail/certs with various certs, presumably self signed, which has been created at installation. -- Michel Talon ta...@lpthe.jussieu.fr smime.p7s Description: S/MIME cryptographic signature
Re: removing libreadline from base system
The only problem I see is from the ports lots of them relies on base libreadline, so we need to first run an exp-run without libreadline, to determine the impact and fix the related ports, before we can fully drop libreadline. One of the first port to consider, i think, is rlwrap. Some time ago i had to compile it on a mac (which is equipped with libedit in place of libreadline) and it had problems since it calls functions in libreadline not in libedit . So i was forced to also compile libreadline. -- Michel Talon ta...@lpthe.jussieu.fr ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: DHCP server in base
David DEMELIER said: I agree that for some people it will be completely useless, but if we can disable it in src.conf everyone will be happy. Since FreeBSD is great for a router it's really fast to make a full working server without installing anything else. What is the problem of installing something else? You are probably ignoring that many people are complaining about the presence of sendmail, bind, perl etc. in the base system from ages, indeed X and perl have been removed, and it is clear that the consensus is to make the base smaller not bigger. And frankly i have *very* hard time to think that a DHCP server in the base has any utility. why not maxima for example? I am interested in formal computation, you are interested in routers, another one likes images and would want gimp, and so on. -- Michel TALON ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)
Jeez, it's been broken a year and it's almost 5.2-RELEASE now. See for example the page for the FreeBSD eagle driver: http://damien.bergamini.free.fr/ueagle/ end notably the OHCI patches in http://damien.bergamini.free.fr/ueagle/download.html At least for the eagle USB ADSL modem, these patches solve the ohci problems. -- Michel TALON ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Really no one knows ?!
Now, leaving apart that my lest backup dated a month ago, and it's really stupid to lost all your data from a HDD without suffering any hardware or software crash, I would really apreciate some ideas, links whatever about what it is to do to avoid this to happend if the future. Just an idea. This occurred to me once that the superblock and primary alternate were corrupted. Hence i was in the same unfortunate situation as you, fsck was not working. The situation was solved by running newfs with the -N flag on the slice. This printed the location of other copies of the superblock. Feeding that to fsck allowed to recover the filesystem, without losing anything. -- Michel TALON ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
