Re: pkg: Cannot open /dev/null:No such file or directory

On Tue, 4 Jun 2019 07:44:09 +0200
Baptiste Daroussin <bapt_at_FreeBSD.org> 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 documented below occurs on both 12-STABLE r348529 and CURRENT
> > r348600 and must have been introduced shortly, since the last known good
> > installation with the environment of ours was on 21st May 2019.
> >
> > 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.
> >
> > What happened here?
> >
> > Kind regards and thanks in advance,
> >
> > oh
> >
> > [...]
> > All repositories are up to date.
> > The following 10 package(s) will be affected (of 0 checked):
> >
> > New packages to be INSTALLED:
> >         python3: 3_3 [zeit4]
> >         sudo: 1.8.27_1 [zeit4]
> >         devcpu-data: 1.22 [zeit4]
> >         python36: 3.6.8_2 [zeit4]
> >         readline: 8.0.0 [zeit4]
> >         indexinfo: 0.3.1 [zeit4]
> >         libffi: 3.2.1_3 [zeit4]
> >         gettext-runtime: 0.19.8.1_2 [zeit4]
> >         openldap-sasl-client: 2.4.47 [zeit4]
> >         cyrus-sasl: 2.1.27 [zeit4]
> >
> > Number of packages to be installed: 10
> >
> What is new is that pkg is using /dev/null as input when running script? this
> is new since pkg 1.11 . Somehow this does not seems to be avaalaible in your
> environement.
>
> Best regards,
> Bapt

Hello,

thanks for the hint!

Packages are installed via the pkg -c ${WORLD_ROOT_DIR} option, chroot'ed, as
far as I can see and therefore, there is no /dev/null device.

Mathew's hint solved the problem.

Greetings,

oh