Em 24/01/2016 07:24, Olivier Cochard-Labbé escreveu:
On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote:
Hi everyone,
Could someone running FreeBSD current on a test machine try loading the
ip_mroute driver on their machine?
Hi,
no problem here:
root@lame5 # uname -a
On Saturday, 23 January 2016, Ben Woods wrote:
>
> I am running the GENERIC kernel, except with VIMAGE enabled and SCTP
> disabled.
>
> When I try to load the kernel module, I am getting an error:
> % sudo kldload -v ip_mroute
> kldload: an error occurred while loading the
On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote:
>
> Hi everyone,
>
> Could someone running FreeBSD current on a test machine try loading the
> ip_mroute driver on their machine?
>
Hi,
no problem here:
root@lame5 # uname -a
FreeBSD lame5.bsdrp.net 11.0-CURRENT FreeBSD
Unfortunately, this (and its committed successor and original for UFS)
fails to boot in some situation, like below. OTOH, gptzfsboot (and
maybe gptboot for UFS, too) is OK.
When I select Disk1 from UEFI firmware, bootx64.efi in Disk1 EFI
partition is used and it searches /boot/loader.efi from
On Fri, Jan 22, 2016 at 03:31:22PM +0100, Dag-Erling Smørgrav wrote:
> The HPN and None cipher patches have been removed from FreeBSD-CURRENT.
> I intend to remove them from FreeBSD-STABLE this weekend.
Can you do some small discurs about ssh+kerberos?
I am try to use FreeBSD with $HOME over
On Sun, Jan 24, 2016 at 03:50:45PM +0100, Dag-Erling Smørgrav wrote:
> Slawa Olhovchenkov writes:
> > Can you do some small discurs about ssh+kerberos?
> > I am try to use FreeBSD with $HOME over kerberoized NFS.
> > For kerberoized NFS gssd need to find cache file "called
> >
On Sun, Jan 24, 2016 at 04:21:17PM +0100, Dag-Erling Smørgrav wrote:
> Slawa Olhovchenkov writes:
> > OK, what about tcsh, zsh, fish and scp/sftp?
>
> I apologize for trying to help you out by suggesting a hack that works
> at least some of the time until I can get a permanent
On 24 January 2016 at 11:36, Otacílio wrote:
> Em 24/01/2016 07:24, Olivier Cochard-Labbé escreveu:
>
>> On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote:
>>
>> Hi everyone,
>>>
>>> Could someone running FreeBSD current on a test machine try loading
On 2016-01-24 07:53, Tomoaki AOKI wrote:
> Unfortunately, this (and its committed successor and original for UFS)
> fails to boot in some situation, like below. OTOH, gptzfsboot (and
> maybe gptboot for UFS, too) is OK.
>
> When I select Disk1 from UEFI firmware, bootx64.efi in Disk1 EFI
>
Slawa Olhovchenkov writes:
> Can you do some small discurs about ssh+kerberos?
> I am try to use FreeBSD with $HOME over kerberoized NFS.
> For kerberoized NFS gssd need to find cache file "called
> /tmp/krb5cc_, where is the effective uid for the RPC
> caller" (from `man
Slawa Olhovchenkov writes:
> Dag-Erling Smørgrav writes:
> > In the meantime, you can try something like this in .bashrc or
> > whatever:
> Imposible. For accessing .bashrc on kerberoized NFS need correct
> /tmp/krb5cc_.
/etc/profile, then.
DES
--
Dag-Erling
On Sun, Jan 24, 2016 at 04:09:05PM +0100, Dag-Erling Smørgrav wrote:
> Slawa Olhovchenkov writes:
> > Dag-Erling Smørgrav writes:
> > > In the meantime, you can try something like this in .bashrc or
> > > whatever:
> > Imposible. For accessing .bashrc on
Slawa Olhovchenkov writes:
> OK, what about tcsh, zsh, fish and scp/sftp?
I apologize for trying to help you out by suggesting a hack that works
at least some of the time until I can get a permanent fix in. I should
instead have hopped in my time machine, jumped back a few
On 24/01/2016 12:53, Tomoaki AOKI wrote:
Unfortunately, this (and its committed successor and original for UFS)
fails to boot in some situation, like below. OTOH, gptzfsboot (and
maybe gptboot for UFS, too) is OK.
When I select Disk1 from UEFI firmware, bootx64.efi in Disk1 EFI
partition is
14 matches
Mail list logo