On Wed, Mar 02, 2016 at 11:54:29PM +, Glen Barber wrote:
> For those who have missed the initial email surrounding this topic, we
> are planning on packaging the base system with pkg(8) for 11.0-RELEASE.
>
> https://lists.freebsd.org/pipermail/freebsd-pkgbase/2016-January/00.html
>
> At
Does FreeBSD's mount_smbfs(8) support for Microsoft's SMBv3 protocol introduced
with Windows 8 and Windows Server 2012/R2?
I tried to find informations/documentation for the kernel options
NETSMB
SMBFS
which I suspect to maintain this aspect, but I couldn't find anything regarding
NETSMB or SMBFS
On 03/02/16 23:54, Glen Barber wrote:
> Also note (as repeated below), running 'pkg delete -a' will implicitly
> remove base system packages after they are installed.
This has the potential for many feet to be shot, given that up to now,
'pkg delete -a' would always leave you with a viable system.
First of all, thanks to everyone who got FreeBSD's UEFI + ZFS boot
working, I'm now triple-booting FreeBSD, Kubuntu Linux and my HP
laptop's native Windows 10 (all 3 spread among about 13 GPT partitions
including an EFI partition). I have a couple issues - an EFI
configuration disables some device
Hi,
On Thu, March 3, 2016 14:46, Anthony Jenkins wrote:
> The other issue is just me being jealous of EFI Linux showing up in a
> toplevel BIOS boot menu:
>
> Selecting "F9 - Boot Device Options" goes to the "Boot Manager" screen:
>
>
> Boot Option Menu
>
>
> - OS boot Manager
> - ubuntu (MKNSSDR
On Wed, 02 Mar 2016 23:00:44 -0800 "Chris H" wrote
> On Wed, 02 Mar 2016 21:49:39 -0800 "Chris H" wrote
>
> > Hello all,
> > I just finished an install off of the
> > 11.0-CURRENT-i386-20160206-r295345-bootonly iso image burnt to DVD.
> > After rebooting to the fresh install; shutting down the
On 03/03/2016 09:39 AM, Jakob Alvermark wrote:
> Hi,
>
> On Thu, March 3, 2016 14:46, Anthony Jenkins wrote:
>
>> The other issue is just me being jealous of EFI Linux showing up in a
>> toplevel BIOS boot menu:
>>
>> Selecting "F9 - Boot Device Options" goes to the "Boot Manager" screen:
>>
>>
>
Building a custom kernel fails when bpf(4) is disabled as suggested in
security(7) due to the error shown below.
I also tried to define in make.conf
WITHOUT_MODULES="lmc" or
WITHOU_MODULES="if_lmc"
assuming I could avoid building the culprit module/device, but it did not work
as expected!
I ne
