similar to: FreeBSD Quarterly Status Report, January-March 2013

Guus The mdoc warnings (on FreeBSD 8) are getting a little bit annoying at times: anywi at lcrproxy:/usr/ports/security/tinc/work/tinc-1.0.19/doc % man tinc.conf 2>&1 | head -5 mdoc warning: Empty input line #6 mdoc warning: Empty input line #10 mdoc warning: Empty input line #15 mdoc warning: Empty input line #22 mdoc warning: Empty input line #30 There are hundreds. Ctrl-L refreshes

In preparation for 7.3-RELEASE, the ports tree is now in feature freeze. Normal upgrade, new ports, and changes that only affect other branches are allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commts to ports with unusually high number of dependent ports,

As of June 1, 2008 00:00:00 UTC, FreeBSD 5.X support in the ports tree is End Of Life. This means that a ports tree checked out after this date is not guaranteed to produce usable packages on 5.X. Additionally, 5.X package builds on the cluster will cease. Users are encouraged to upgrade to 6.3 or 7.0 if they wish to continue to track the latest ports tree. A tag, RELEASE_5_EOL, has been laid

On Sat, 11 Mar 2017 08:18:26 +0100 "Niels Dettenbach \(Syndicat IT & Internet\) via samba" <samba at lists.samba.org> wrote: > Am 11. März 2017 00:04:13 MEZ schrieb Andrew Walker via samba > <samba at lists.samba.org>: > >I don't believe that ZFS on FreeBSD supports acltype=posixacl and > >sa-based > > If you want to see a working samba / zfs

I don't believe that ZFS on FreeBSD supports acltype=posixacl and sa-based xattrs. For the record, the latest version of samba that I've been successfully able to compile on FreeBSD 10.3 is Samba 4.5.5. On Mon, Mar 6, 2017 at 11:09 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 6 Mar 2017 17:17:07 +0100 > Klaus Hartnegg via samba <samba at

Hi all, Sorry for the delay - three business trips abroad and LOTS of head scratching with USB Keys and DVD's of SuSE and FreeBSD... The question about the USB reports from Windows is still unanswered (I am abroad again !), but *think* the Liebert driver had been stopped. I can report the following updates for my linux setups; SuSE/FreeBSD/FreeNAS [remember here I am trying to make nut

Hi all, I’m new to NUT and have some trouble getting my new UPS to work. Since the HCL listed Powercom UHID models as „green“ I thought buying a Roline (German rebranded Powercom) model would be a good idea. The OS is FreeBSD: FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at

I believe that iXsystems recently patched Samba 4.6 in FreeNAS so that it can act as an AD DC. https://bugs.freenas.org/issues/23566 As is mentioned here: https://lists.samba.org/archive/samba/2017-June/209021.html I imagine that maybe a fix for vanilla FreeBSD is coming soon. As things stand, if you want to use FreeBSD as an AD DC on ZFS, I believe that FreeNAS is the only option. On Mon, Jul

Hello;I just came across NUT, testing FreeNAS/FreeBSD. I?m running at home a APC UPS connected to another computer, running apcupsd. I found out that NUT didn't talk by default to apcupsd, and there was a driver created relatively recently (apcupsd-ups), which filled in that gap. The version I found on my FreeBSD/FreeNAS system seems to imply that there is more to come to that driver (0.04)

please reply to the list. thanks! See below. On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > thanks for your reply. I'm running the latest version of FreeNAS based on 9.2 with NUT 2.7.1 > > [root at archivio ~]# uname -a > FreeBSD archivio.dannyb78.home 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+ > 38751c8: Thu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 FreeBSD Project Quarterly Status Report - 3rd Quarter 2016 As focused as we are on the present and what is happening now, it is sometimes useful to take a fresh look at where we have come from, and where we are going. This quarter, we had our newest doc committer working to trace through the tangled history of many utilities, and we

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 FreeBSD Project Quarterly Status Report - 3rd Quarter 2016 As focused as we are on the present and what is happening now, it is sometimes useful to take a fresh look at where we have come from, and where we are going. This quarter, we had our newest doc committer working to trace through the tangled history of many utilities, and we

But if Samba AD does not work on the ZFS filesystem, then why bundle it with the NAS4Free OS? What filesystems does the Samba AD support? On Thu, Jul 6, 2017 at 10:54 AM, Andrew Walker via samba < samba at lists.samba.org> wrote: > Yes. I imagine that's why Andrew Bartlett commented: "There may be some > good news in the future, as I've had one of the developers at

Greetings! I''ve got a FreeBSD-based (FreeNAS) appliance running as an HVM DomU. Dom0 is Debian Squeeze on an AMD990 chipset system with IOMMU enabled. The DomU sees six physical drives: one of them is a USB stick that I''ve passed through in its entirety as a block device. The other five are SATA drives attached to a controller that I''ve handed to the DomU with PCI

Hi, I've installed a FreeBSD (stable 9.2) as a guest on ESXi 5.5. I've added Adaptec Controller via passthrough. Unfortunately FreeBSD does not show hard drives. Any clue? aac0: <Adaptec RAID 5805> mem 0xfd200000-0xfd3fffff irq 18 at device 0.0 on pci3 aac0: Enabling 64-bit address support aac0: Enable Raw I/O aac0: Enable 64-bit array aac0: New comm. interface enabled aac0:

On 9/21/2013 5:49 AM, Bryan Drewery wrote: > Ports now support enabling Stack Protector [1] support on FreeBSD 10 > i386 and amd64, and older releases on amd64 only currently. > > Support may be added for earlier i386 releases once all ports properly > respect LDFLAGS. > > To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports. > > The default

On 9/21/2013 5:49 AM, Bryan Drewery wrote: > Ports now support enabling Stack Protector [1] support on FreeBSD 10 > i386 and amd64, and older releases on amd64 only currently. > > Support may be added for earlier i386 releases once all ports properly > respect LDFLAGS. > > To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports. > > The default

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

I've noticed that the samba-tool ntacl sysvolreset --use-s3fs command does not work on a ZFS filesystem on FreeBSD. It does work if sysvol is moved to a volume that is able to be mounted with the acls flag. I will reference a ticket I started with FreeNAS here: https://bugs.freenas.org/issues/4351 As of version 9.2.1.1 s3fs is now the default using the workaround known for FreeBSD.

Hello, I need help configuring my USB connected UPS "Emerson Power Liebert PowerSure PSI 1440" to my freebsd machine, using NUT. here's the manufacturer's product page http://www.emersonnetworkpower.com/en-US/Products/ACPower/Pages/LiebertPowerSurePSILineInteractiveUPS10003000VA.aspx I'm not a BSD expert, so please ask me for any information you need. regards Daniele