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

From: Joseph Ward <jbwlists_at_hilltopgroup.com>
Date: Tue, 11 Jun 2019 20:22:40 -0400
Thank you!  I only added the mount line, but it seemed to work.

On 2019-06-11 14:52, Johannes Lundberg wrote:
> Hi
>
> This is probably overkill but I've attached a diff that show my patches
> to image.sh. It's just a hack so far to make it do what I want and not
> meant as general purpose. Use the changes you need for your application.
>
> Changes (only meant to work for building usb images on amd64 and i386)
>
> - mount devfs so pkg will work properly
> - add "install packages from official repo" option so you won't have to
> build your own packages for each jail
> - downloaded packages from official repo is cached locally to avoid
> excessive downloads
> - hack for i386 so packages are installed properly
> - increase swap space to allow for kernel core dumps (for usb image)
> - execute post-install script "overlay.sh" in the jail if provided in
> the overlay folder
>
> Bapt: Maybe you'll find some of these changes useful? :)
>
> /Johannes
>
> On 6/11/19 8:52 AM, jbwlists_at_hilltopgroup.com wrote:
>> I'm having the same issue with poudriere image; could you please let
>> me know what you did to fix it?  I'm assuming the image.sh you're
>> referring to is /usr/local/share/poudriere/image.sh, but I'm not sure
>> where the change would need to be made.
>>
>> Thanks in advance,
>> Joseph
>>
>>
>> On 2019-06-04 13:02, Johannes Lundberg wrote:
>>> 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 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.
>>> Hi
>>>
>>> Same things applies to poudriere-image. I had to add a mount devfs
>>> command to the image.sh script.
>>>
>>>> Best regards,
>>>> Bapt
>>> _______________________________________________
>>> freebsd-current_at_freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to
>>> "freebsd-current-unsubscribe_at_freebsd.org"
Received on Tue Jun 11 2019 - 22:22:45 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:20 UTC