of course interesting work, but unfortunately, and as you know me,
what would i say next
cc -target x86_64-unknown-freebsd12.0
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe
-I/usr/src/sys/cddl/compat/opensolaris
-I/usr/src/cddl/compat/opensolaris/
Yes. I _just_ rebased and broke world in the process. Fix coming up
momentarily.
-M
On Wed, Aug 22, 2018 at 12:06 AM Outback Dingo
wrote:
> of course interesting work, but unfortunately, and as you know me,
> what would i say next
>
> cc -target x86_64-unknown-freebsd12.0
> --sysroot=/usr/obj/us
Fixed. Pull.
bc2b257d1082112cc27e56db793f5c569f603bec
On Wed, Aug 22, 2018 at 12:10 AM Matthew Macy wrote:
> Yes. I _just_ rebased and broke world in the process. Fix coming up
> momentarily.
> -M
>
> On Wed, Aug 22, 2018 at 12:06 AM Outback Dingo
> wrote:
>
>> of course interesting work, but u
> That's exactly why I keep the following in my /boot/loader.rc:
I meant "in my /boot/loader.conf"...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curren
HP EliteBook 8570p with AMD 'Thames' Radeon HD 7570M.
If neither drm-stable-kmod nor drm-next-kmod is used – commenting out
# kld_list="/boot/modules/radeonkms.ko"
in /etc/rc.conf
and if boot is pure UEFI, without CSM,
then the notebook can reliably resume from suspend. There's a
distinctive singl
On 22 Aug 2018, at 04:01, Mark Millard wrote:
>
> Brooks Davis brooks at freebsd.org wrote on
> Tue Aug 21 20:29:45 UTC 2018 :
>
>> On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote:
>>> . . .
>>>
>>> I have attached a patch for most of the llvm ports, which sets the
>>> LLVM_PARAL
As of r338192 the command line option "-use-udpsock" no longer exists,
since r320757 has been reverted.
The behaviour is now back to always using a UDP socket the same as stable/11.
In other words, if you are using the nfsuserd with the "-use-udpsock" option,
just
get rid of the "-use-udpsock" op
On 22/08/2018 05:29, Manfred Antar wrote:
On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote:
On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
Перенаправленное сообщение
Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
Дата: Tue, 21 Aug 2018 16:41:
On 08/22/2018 08:48, tech-lists wrote:
> On 22/08/2018 05:29, Manfred Antar wrote:
>>
>>> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev
>>> wrote:
>>>
>>> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
Перенаправленное сообщение
Тема: nvidia-driver buil
On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote:
>
>
> > On 20. Aug 2018, at 17:09, Konstantin Belousov wrote:
> >
> >> On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote:
> >>
> >> See here for a screenshot (also including the output of "show pte
> >> 0xf8000100
Hello!
What do these lines in my dmesg mean?
I am on amd64.
/usr/src Revision: 338177
/usr/ports Revision: 43
P.S
I got Fatal trap 12 with this revision after installing several fusefs
modules from ports.
After removing fuse from my loader.conf, things booted again.
Regards,
Per Gunnar
> On Aug 21, 2018, at 10:10 PM, Alan Cox wrote:
>
> On 08/21/2018 23:29, Manfred Antar wrote:
>>
>>> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote:
>>>
>>> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
Перенаправленное сообщение
Тема: nvidi
On 8/22/18 2:11 AM, Graham Perrin wrote:
HP EliteBook 8570p with AMD 'Thames' Radeon HD 7570M.
If neither drm-stable-kmod nor drm-next-kmod is used – commenting out
# kld_list="/boot/modules/radeonkms.ko"
in /etc/rc.conf
and if boot is pure UEFI, without CSM,
then the notebook can reliably res
On 22/08/2018 17:50, Pete Wright wrote:
> not sure this will address this specific issue - but have you tested setting
> this sysctl knob and seeing if that fixes your resume issues:
> hw.acpi.reset_video=1
Thanks, I'll be away for around three weeks, I'll test some time in September.
__
On Wed, Aug 22, 2018 at 6:00 PM Graham Perrin
wrote:
> On 22/08/2018 17:50, Pete Wright wrote:
> > not sure this will address this specific issue - but have you tested
> setting this sysctl knob and seeing if that fixes your resume issues:
> > hw.acpi.reset_video=1
>
> Thanks, I'll be away for ar
On 22/08/2018 16:29, Alan Cox wrote:
All of kmem_alloc_attr(), kmem_alloc_contig(), and kmem_malloc() should
have their first parameter, typically kernel_arena, but sometimes
kmem_arena, removed in FreeBSD 12.
There is still one more pending change to kmem_free() that has not hit
HEAD yet. That
On Wed, Aug 22, 2018 at 7:20 PM, Per Gunnarsson
wrote:
Hello!
What do these lines in my dmesg mean?
I am on amd64.
/usr/src Revision: 338177
/usr/ports Revision: 43
P.S
I got Fatal trap 12 with this revision after installing several fusefs
modules from ports.
After removing fuse f
On Aug 21, 2018, at 8:16 PM, Alan Somers wrote:
>
> > The last time I looked (which was a long time ago), Oracle's ZFS encryption
> > looked extremely vulnerable to watermarking attacks. Did anybody ever fix
> > that?
This is the comment about dedup in zio_crypt.c:
* CONSIDERATIONS FOR DEDU
I'm just using this move as an example for some more
general questions.
After this change when I look at:
https://www.freebsd.org/cgi/man.cgi?query=devfs.conf&apropos=0&sektion=5&manpath=FreeBSD+12-current&arch=default&format=html
I see in the man page:
FILES
/etc/devfs.conf
/usr/shar
Only encrypting L0 blocks also leaks a lot of information. That means
that, if encryption is set to anything but "off", watermarking attacks will
still be possible based on the size and sparsity of a file. Because I
believe that with any encryption mode, ZFS turns continuous runs of zeros
into ho
On Wed, Aug 22, 2018 at 12:30 PM Sean Fagan wrote:
> On Aug 21, 2018, at 8:16 PM, Alan Somers wrote:
> >
> > > The last time I looked (which was a long time ago), Oracle's ZFS
> encryption looked extremely vulnerable to watermarking attacks. Did
> anybody ever fix that?
>
> This is the comment
Hi,
I recently reinstalled my old Thinkpad T410 with ZFS and -CURRENT, but I
cannot get my VGA adapter working. It worked before and it also works
with Linux from a memory stick. The notebook has NVIDIA Optimus, but it
is disabled and set to discrete graphics in the BIOS, using the
x11/nvidia-dri
On Aug 22, 2018, at 12:35 PM, Alan Somers wrote:
> Only encrypting L0 blocks also leaks a lot of information. That means that,
> if encryption is set to anything but "off", watermarking attacks will still
> be possible based on the size and sparsity of a file. Because I believe that
> with an
> On 22. Aug 2018, at 17:46, Konstantin Belousov wrote:
>
>> On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote:
>>
>>
On 20. Aug 2018, at 17:09, Konstantin Belousov wrote:
On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote:
See here for a
On Aug 22, 2018, at 12:20 PM, Alan Somers wrote:
> ]That doesn't answer the question about what happens when dedup is turned
> off. In that case, is the HMAC still used as the IV? If so, then
> watermarking attacks are still possible. If ZFS switches to a random IV when
> dedup is off, then
Yesterday I installed a server from scratch from image
FreeBSD-12.0-ALPHA2-amd64-20180816-r337934-memstick.img,
then I updated sources with svn and did make buildworld, buildkernel,
installkernel, installworld, mergemaster. Upon reboot I can no longer
talk to the server on IPv4 but it works on IP
On Wed, Aug 22, 2018 at 1:25 PM Andreas Ott wrote:
> Yesterday I installed a server from scratch from image
> FreeBSD-12.0-ALPHA2-amd64-20180816-r337934-memstick.img,
> then I updated sources with svn and did make buildworld, buildkernel,
> installkernel, installworld, mergemaster. Upon reboot I
On Tue, Aug 21, 2018 at 3:15 PM Bjoern A. Zeeb <
bzeeb-li...@lists.zabbadoz.net> wrote:
> On 21 Aug 2018, at 12:31, Olivier Cochard-Labbé wrote:
>
>
> Do you have a last-good revision?
>
>
> Hi,
Since VIMAGE was enabled by default on GENERIC
(r327969).
So perhaps VIMAGE+carp never works on i38
On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote:
>
>
> > On 22. Aug 2018, at 17:46, Konstantin Belousov wrote:
> >
> >> On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote:
> >>
> >>
> On 20. Aug 2018, at 17:09, Konstantin Belousov
> wrote:
>
>
Hi,
On Wed, Aug 22, 2018 at 01:30:37PM -0700, Freddie Cash wrote:
> There's nothing wrong with the timing. Your rc.conf is incorrect.
>
> The second ifconfig_em1 line overrides the former. These are variable
> declarations, not commands. The last setting for a variable is the only
> one that ta
> On 22. Aug 2018, at 23:15, Konstantin Belousov wrote:
>
>> On Wed, Aug 22, 2018 at 10:03:54PM +0200, Michael Gmelin wrote:
>>
>>
On 22. Aug 2018, at 17:46, Konstantin Belousov wrote:
On Tue, Aug 21, 2018 at 12:14:35AM +0200, Michael Gmelin wrote:
>> On 20. A
Hi Thomas,
Alan believes that, even with dedup disabled, the ZFS native encryption
support is vulnerable to watermarking attacks. I don't have enough exposure
to crypto to pass any judgement and was hoping that you'd share your point
of view. Thanks in advance.
-M
On Wed, Aug 22, 2018 at 12:42
Sorry for possibly mentioning this twice.
FreeBSD konjak 12.0-ALPHA2 FreeBSD 12.0-ALPHA2 #0 r338177: Wed Aug 22
08:46:40 CEST 2018
root@konjak:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
/usr/src Revision: 338177
/usr/ports Revision: 43
When I try to boot with the fuse module in /bo
On 18. 8. 3., Warner Losh wrote:
> On Sun, Jul 29, 2018 at 6:35 AM, O. Hartmann wrote:
> 'efibootmgr -v' output:
>
> BootCurrent: 0004
> Timeout: 1 seconds
> BootOrder : 0001, 0002, 0003, 0004
> Boot0001* Hard Drive BBS(HD,,0x0)
> Boot0002* Network Card BBS(Net
> On 23. Aug 2018, at 01:02, Per Gunnarsson wrote:
>
> Sorry for possibly mentioning this twice.
>
> FreeBSD konjak 12.0-ALPHA2 FreeBSD 12.0-ALPHA2 #0 r338177: Wed Aug 22
> 08:46:40 CEST 2018
> root@konjak:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
>
> /usr/src Revision: 338177
>
>
On Tue, Aug 21, 2018 at 06:47:19PM -0700, Mark Millard wrote:
>
> I've used a SSD both directly via SATA and via a USB enclosure,
> the same partitions/file systems across the uses. Only when it
> was SATA-style-use did TRIM work.
>
This is likely the key to my question. If USB blocks the TRIM se
On 8/22/18 8:37 PM, Mark Millard wrote:
> I'm just using this move as an example for some more
> general questions.
>
> After this change when I look at:
>
> https://www.freebsd.org/cgi/man.cgi?query=devfs.conf&apropos=0&sektion=5&manpath=FreeBSD+12-current&arch=default&format=html
>
> I see in
37 matches
Mail list logo
