On 9/4/20, O. Hartmann wrote:
> On Tue, 1 Sep 2020 19:21:36 +0200
> Mateusz Guzik wrote:
>
>> It's not my bug but i'll make sure it is taken care of.
>
> Oh, I'm sorry. But I grasp for every help I can get ...
>
> The problem is that I do not know whether the process "make installkernel"
> does
>
On Tue, 1 Sep 2020 19:21:36 +0200
Mateusz Guzik wrote:
> It's not my bug but i'll make sure it is taken care of.
Oh, I'm sorry. But I grasp for every help I can get ...
The problem is that I do not know whether the process "make installkernel" does
silently proceed and drop the error message an
It's not my bug but i'll make sure it is taken care of.
On 8/30/20, Hartmann, O. wrote:
> On Fri, 28 Aug 2020 13:16:05 +0200
> Mateusz Guzik wrote:
>
>> On 8/28/20, Hartmann, O. wrote:
>> > On Fri, 28 Aug 2020 12:31:21 +0200
>> > Mateusz Guzik wrote:
>> >
>> >> Can you show more of the log?
>>
On Fri, 28 Aug 2020 13:16:05 +0200
Mateusz Guzik wrote:
> On 8/28/20, Hartmann, O. wrote:
> > On Fri, 28 Aug 2020 12:31:21 +0200
> > Mateusz Guzik wrote:
> >
> >> Can you show more of the log?
> >>
> >> When you installkernel you should see:
> >> mkdir -p /boot/kernel
> >> install -p -m 555 -
On 8/28/20, Hartmann, O. wrote:
> On Fri, 28 Aug 2020 12:31:21 +0200
> Mateusz Guzik wrote:
>
>> Can you show more of the log?
>>
>> When you installkernel you should see:
>> mkdir -p /boot/kernel
>> install -p -m 555 -o root -g wheel kernel /boot/kernel/
>
> These lines are seen right after the
On Fri, 28 Aug 2020 12:31:21 +0200
Mateusz Guzik wrote:
> Can you show more of the log?
>
> When you installkernel you should see:
> mkdir -p /boot/kernel
> install -p -m 555 -o root -g wheel kernel /boot/kernel/
These lines are seen right after the beginning of "make installkernel".
> mkdir -
Can you show more of the log?
When you installkernel you should see:
mkdir -p /boot/kernel
install -p -m 555 -o root -g wheel kernel /boot/kernel/
mkdir -p /usr/lib/debug/boot/kernel
install -p -m 555 -o root -g wheel kernel.debug /usr/lib/debug/boot/kernel/
Did these succeed? Do these dirs exist
Mark Johnston wrote:
On Wed, Apr 29, 2020 at 08:49:00AM +0300, Yuri Pankov wrote:
I'm trying to replace the kernel on memstick image with the help of
mdconfig, and installkernel runs out of space despite
WITHOUT_DEBUG_FILES= added to /etc/src.conf.
/usr/src$ make -V MK_DEBUG_FILES
no
/usr/src$
On Wed, Apr 29, 2020 at 08:49:00AM +0300, Yuri Pankov wrote:
> I'm trying to replace the kernel on memstick image with the help of
> mdconfig, and installkernel runs out of space despite
> WITHOUT_DEBUG_FILES= added to /etc/src.conf.
>
> /usr/src$ make -V MK_DEBUG_FILES
> no
> /usr/src$ sudo rm
In message: <001601c19bf8$04c1f7e0$ae60dacb@joannaraman>
"Raman Ng" <[EMAIL PROTECTED]> writes:
: I have cvsup the source (current) yesterday that is about 14 hours ago.
: Buildworld and buildkernel without any problem. However, when I tried to
: installkernel the following error is f
James Johnson wrote:
> Having to specify
> which kernel to build with the KERNEL= parameter seems to indicate that
> people should be running GENERIC kernels all the time as it is the default.
No, it seems to indicate that you should specify KERNEL=YOURKERNEL in
make.conf.
--
Ben Smithurst / [
From: "James Johnson" <[EMAIL PROTECTED]>
> The method of building and installing a kernel to me seems a bit off.. Both
> the buildworld and installworld targets default to GENERIC, yet GENERIC is a
> file checked into the -CURRENT CVS repository.. Any changes to this file
> will get blown away if
On Wed, Jul 26, 2000 at 10:02:40AM -0700, Marcel Moolenaar wrote:
> Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The
> installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV
> was changed to have the very restricted path that broke the
> installkernel target as you d
Bill Fumerola wrote:
>
> > WORLDTMP is a place to *install* binaries we made during the build. We
> > don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
> > /usr/sbin resp.
>
> And then we try and install the kernel using those utilties that are in
> directories that don't exist:
On Wed, Jul 26, 2000 at 08:56:03AM -0700, Marcel Moolenaar wrote:
> > Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
> > looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...
>
> WORLDTMP is a place to *install* binaries we made during the build. We
> don'
Bill Fumerola wrote:
> STRICTTMPPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
> INSTALLTMP= ${TMPDIR}/install.${TMPPID}
> IMAKEENV= ${CROSSENV} \
> PATH=${STRICTTMPPATH}:${INSTALLTMP}
>
> installkernel:
> cd ${KRNLOBJDIR}/${INSTALLKERNEL}
16 matches
Mail list logo
