> Are you using zvols to back the VMs? Make sure they are in 'volmode=dev'
> not 'geom' (the default), or GEOM will lock the device when it detects a
> partition table being written to the zvol (from the installer inside the
> VM)
>
> Note that this setting requires you to export/import the pool
I'm converting some Xen/Debian/Windows domain servers to
FreeBSD/Bhyve/Samba domain servers. Windows is still required for a couple
of applications, but I've recently had enough success with Samba4 to try
this. Not the problem.
The machines have two disks (was RAID-1 before, will be RAID-1
On Fri, Sep 16, 2016 at 1:06 AM, Allan Jude <allanj...@freebsd.org> wrote:
> On 2016-09-16 01:04, Zaphod Beeblebrox wrote:
> >
> >
> >
> > Are you using zvols to back the VMs? Make sure they are in
> 'volmode=dev'
> > not 'geom' (the d
>From the information that was leaked by AMD claiming that their processors
didn't have the flaws, it would seem any OS in which the kernel occupies
the same address space as the userland would be vulnerable. The AMD post
implied that Intel's speculative execution of code did not check the
As I said I would, I put the contents of /boot onto the FAT-formated EFI
partition. This is suboptimal. The default is to use "kernel.old" ...
etc ... which cannot be done on a FAT partition... at least not with our
filesystem driver ...
... but with all of /boot on the EFI partition, simply
I've booted that image on my zbook 15. I show in the boot that I can
deliberately load efirt.ko ... and it doesn't help. I also show that I can
"type blind" after the system boots ... so everything but the screen is
working.
In case you can't quite make it out, I hit right cursor twice (move to
the 80x25 text
mode emulated on a bitmapped screen?
On Mon, Apr 2, 2018 at 9:07 PM, Kyle Evans <kev...@freebsd.org> wrote:
> On Mon, Apr 2, 2018 at 5:51 PM, Zaphod Beeblebrox <zbee...@gmail.com>
> wrote:
> > On Sun, Apr 1, 2018 at 7:41 PM, David NewHamlet <whe
If you're thinking on it, you should know that the DVD version works. The
difference, AFAICT, is that it simply calls loader.efi directly. Ie:
bootx64.efi is loader.efi, not boot1.efi.
Loader.efi doesn't seem to change the screen mode when it starts. When the
kernel starts afterwards, this
Are there any plans to support AMD RAID?
AMD RAID is _like_ Intel RAID, but has a number of differences. One is
that it requires UEFI (without UEFI it does not boot, at least). It comes
on/with AMD motherboards for Zen and Threadripper processors. It also only
supports RAID 0/1/10, that is: no
As someone who controls both ends of the link (runs the ISP, has service
from the ISP), so far (a bit out of laziness) I have the following
solution...
Now... of note is that we statically assign addresses. This is not just
being nice, but being practical. We deal out IPv4 addresses vi IPCP,
Hrm. Maybe what I hear others saying, tho, and not entirely being replied
to is just a nice concise document of the why. What I hear you saying is
that GIT has momentum and that it's popular... (and I accept that --- it is
evidently true), but then I hear handwaving about features, but no list
Actually, frankly, yes. Nearly the first cogent summary I've found so far.
On Sat, Sep 19, 2020 at 2:22 AM Warner Losh wrote:
>
>
> On Fri, Sep 18, 2020, 11:31 PM Zaphod Beeblebrox
> wrote:
>
>> Hrm. Maybe what I hear others saying, tho, and not entirely being
>>
I'm not posting as someone in-the-know about the state of the FreeBSD stack
--- I trust the security team to divulge things as required,
BUT ...
... the examples of vulnerable things in that article to reference lead me
to conclude that the stacks in question are "libraries" ... likely, but not
IIRC, isn't the postgresql-server's default install on FreeBSD, from ports,
have TCP turned off? IE: try editing the config (in the database
directory) to uncomment the listen directive?
On Sun, Aug 8, 2021 at 5:21 AM FreeBSD User wrote:
> Hello,
>
> on all(!) of my home systems based on
Is the NFS mounted filesystem NFS? I've found NFS mounted ZFS has several
pathologies like this when there is no SSD cache and/or log vdevs attached.
On Wed, Oct 6, 2021 at 10:18 PM Felix Palmen wrote:
> Hi all,
>
> I use a -CURRENT bhyve vm for testing port builds with poudriere. As
> this vm
One thing, that I'm sure the developers know, but that might be
underappreciated at the user level:
These things are little computers ... with their own little operating
systems and as such, their own little bugs. This means that the quality
can swing very wildly between different examples of
Just in case it's relevant, I'm carrying around this patch on my fairly
busy little RISC-V machine.
diff --git a/sys/fs/nfsclient/nfs_clvnops.c b/sys/fs/nfsclient/nfs_clvnops.c
index 0b8c587a542c..85c0ebd7a10f 100644
--- a/sys/fs/nfsclient/nfs_clvnops.c
+++ b/sys/fs/nfsclient/nfs_clvnops.c
@@
101 - 117 of 117 matches
Mail list logo
