On 6/3/19 10:44 PM, Baptiste Daroussin wrote:
> On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote:
>> Hello List,
>>
>> lately I ran into a serious problem installing packages in a nanoBSD
>> environment, in which the package repository server is "remotely" on site.
>> The
>> issue as
> On 04/06/2019 06:32, O. Hartmann wrote:
> > As far as I know,, the package installation is performed via "chroot'ed"
> > environment and somehow /dev/null is out of a sudden not accessible anymore
> > while pkg tries to delegate some output to /dev/null.
>
> Assuming you're chroot'd to /chroot,
On Tue, Jun 4, 2019 at 8:16 AM Warner Losh wrote:
>
>
> On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI
> wrote:
>
>> Hi.
>>
>> Try attached patch for stand/efi/boot1/boot1.c.
>> This partially reverts r347193 and works at least for me.
>>
>> Without this, boot1.efi (bootx64.efi) forcibly boot from
On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI
wrote:
> Hi.
>
> Try attached patch for stand/efi/boot1/boot1.c.
> This partially reverts r347193 and works at least for me.
>
> Without this, boot1.efi (bootx64.efi) forcibly boot from
> first physical HDD/SSD, even if forcibly booted from other
>
FreeBSD Project Quarterly Status Report - 1st Quarter 2019
As spring leads into summer, we reflect back on what the FreeBSD
project has accomplished in the first quarter of 2019. Events included
FOSDEM and AsiaBSDCon, the FreeBSD Journal is now free to everyone,
ASLR is available in
Hi.
Try attached patch for stand/efi/boot1/boot1.c.
This partially reverts r347193 and works at least for me.
Without this, boot1.efi (bootx64.efi) forcibly boot from
first physical HDD/SSD, even if forcibly booted from other
physical drive via BIOS (UEFI firmware) menu.
Remaining parts of
On Tue, 4 Jun 2019 07:44:09 +0200
Baptiste Daroussin wrote:
> On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote:
> > Hello List,
> >
> > lately I ran into a serious problem installing packages in a nanoBSD
> > environment, in which the package repository server is "remotely" on site.
>
> On 4 Jun 2019, at 04:38, Johannes Lundberg wrote:
>
> Hi
>
> I'm using poudriere-image to create usb memstick images. The images are
> identical except OS version. They are tested on a laptop with 13-CURRENT
> installed as only OS, having UEFI boot and root on zfs.
>
> 12-STABLE memstick
On 04/06/2019 06:32, O. Hartmann wrote:
> As far as I know,, the package installation is performed via "chroot'ed"
> environment and somehow /dev/null is out of a sudden not accessible anymore
> while pkg tries to delegate some output to /dev/null.
Assuming you're chroot'd to /chroot, then:
