of pkg base materials.
Question: Are any of the changes to be MFC'd at some point?
If I do I will merge a large batch at once, and probably adjust
the order. For example, I'll merge the pci_host_generic changes
before pci_pci changes so that stable branches will be bisectable.
--
John Baldwin
y be 64-bit.
BAR == a range of memory or I/O port addresses decoded by a device,
usually mapped to a register bank, but sometimes mapped to internal
memory (e.g. a framebuffer)
Window == a range of memory or I/O port addresses decoded by a bridge
for which transactions are passed across the bridge to be handled by
a child device.
--
John Baldwin
On 2/14/24 9:57 AM, Mark Millard wrote:
On Feb 14, 2024, at 08:08, John Baldwin wrote:
On 2/12/24 5:57 PM, Mark Millard wrote:
On Feb 12, 2024, at 16:36, Mark Millard wrote:
On Feb 12, 2024, at 16:10, Mark Millard wrote:
On Feb 12, 2024, at 12:00, Mark Millard wrote:
[Gack: I
On 2/14/24 8:42 AM, Warner Losh wrote:
On Wed, Feb 14, 2024 at 9:08 AM John Baldwin wrote:
On 2/12/24 5:57 PM, Mark Millard wrote:
On Feb 12, 2024, at 16:36, Mark Millard wrote:
On Feb 12, 2024, at 16:10, Mark Millard wrote:
On Feb 12, 2024, at 12:00, Mark Millard wrote:
[Gack: I
.]
On Feb 12, 2024, at 10:41, Mark Millard wrote:
On Feb 12, 2024, at 09:32, John Baldwin wrote:
On 2/9/24 8:13 PM, Mark Millard wrote:
Summary:
pcib0: mem 0x7d50-0x7d50930f
irq 80,81 on simplebus2
pcib0: parsing FDT for ECAM0:
pcib0: PCI addr: 0xc000, CPU addr: 0x6, Size
with the faulting instruction pointer (as long as it isn't in
a kernel module), e.g. for gdb you would use 'gdb /boot/kernel/kernel' and then
'l *', e.g. from above: 'l *0x80acb962'
--
John Baldwin
, but I wouldn't expect
rman_manage_region to fail.
Logging the return value from rman_manage_region would be the first step I think
to see which error value it is returning.
Probably I should fix pci_host_generic.c to handle translation properly however.
I can work on a patch for that.
--
John Baldwin
ran delete-old after your last
upgrading that used LLVM 15. We might need something to cope with this
during the install target for libc++ in particular where this has occurred
multiple times historically.
--
John Baldwin
On 11/15/23 3:06 PM, Bakul Shah wrote:
On Nov 15, 2023, at 7:57 AM, John Baldwin wrote:
On 10/9/23 5:21 PM, Bakul Shah wrote:
Any hints on how to use bhyve's -G option to debug a VM
kernel? I can connect to it from gdb with "target remote :"
& bhyve stops the VM initia
the CI
is green as that would give us greater confidence of "we believe these
are good" before they are uploaded for publishing.
--
John Baldwin
run at
terminal.
My guess is something to do with commit
23099099196548550461ba427dcf09dcfb01878d,
though I don't see how it could work any differently in this case as the only
change to part_config there was to return if if geom_gettree fails, and if it
fails, provider_for_name would presumably have failed anyway.
--
John Baldwin
y stepping via
temporary breakpoints) when debugging the kernel this way.
--
John Baldwin
);
```
Seems 14.0 only create one KTLS thread.
IIRC 13.2 create one thread per core.
That part should not be different. There should always be one thread per core.
--
John Baldwin
we would want to do it for 14.0 as 13.x -> 14 upgrades
are affected in the same way.
--
John Baldwin
cpdate
does refuse to do a "new" upgrade until you resolve all the conflicts from your
previous upgrade to ensure that conflicted upgrades aren't missed.
--
John Baldwin
in userspace to always use a dynamically sized mask.
This could perhaps be done in an API-preserving manner by making cpuset_t
an opaque wrapper type in userland and requiring CPU_* to indirect to
functions in libc, etc. That's a fair bit more work however.
--
John Baldwin
enc_xform_des
for example.
--
John Baldwin
-U also reports 1400063.
FWIW, this was a cross-build, maybe that played a role too.
If you do a NO_CLEAN=yes build, we don't relink binaries just because
crt*.o changed (where the note is stored).
--
John Baldwin
saved FPU contexts and reuses a context? If so, I would just suggest
that ZFS switch to using FPU_KERN_NOCTX instead which runs all SSE
type code in a critical section to disable preemption but avoids
having to allocate and manage FPU contexts.
--
John Baldwin
On 5/4/22 1:38 PM, Steve Kargl wrote:
On Wed, May 04, 2022 at 01:22:57PM -0700, John Baldwin wrote:
On 5/4/22 12:53 PM, Steve Kargl wrote:
On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote:
I don't know the entire FreeBSD ecosystem. Do people
use FreeBSD on embedded systems (e.g
On 5/4/22 12:53 PM, Steve Kargl wrote:
On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote:
On 5/2/22 10:37 AM, Steve Kargl wrote:
On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote:
On Sun, 1 May 2022 at 11:54, Steve Kargl
wrote:
diff --git a/gcc/config/freebsd-spec.h b/gcc
le threads, and I think GCC can safely do the
same.
--
John Baldwin
in 13.0 so I couldn't
apply those in every branch.
I build this directly on -current. I'm guessing that these are what
triggered this behaviour:
commit 8b83d7e0ee54416b0ee58bd85f9c0ae7fb3357a1
Author: John Baldwin
Date: Mon Apr 18 16:06:27 2022 -0700
Make -Wunused-but-set-variable a fatal
foo.core instead of a valid core dump.
--
John Baldwin
/D34147.
It is work to keep it working though and I hadn't worked on it again
until recently.
--
John Baldwin
mail accounts to forward cron
periodic e-mails just fine. It even supports STARTTLS and SMTP AUTH.
I haven't tried using it for simple local delivery to /var/mail/root.
--
John Baldwin
On 1/1/22 9:00 AM, Ed Maste wrote:
On Fri, 31 Dec 2021 at 18:04, John Baldwin wrote:
However, your point about libcxxrt.so.1 is valid. It needs to also be moved
to /lib if libc++.so.1 is moved to /lib.
libcxxrt.so.1 has always been in /lib.
Oh, I was thrown off by the .so indirection
On 12/31/21 2:59 PM, Mark Millard wrote:
On 2021-Dec-31, at 14:28, Mark Millard wrote:
On 2021-Dec-30, at 14:04, John Baldwin wrote:
On 12/30/21 1:09 PM, Mark Millard wrote:
On 2021-Dec-30, at 13:05, Mark Millard wrote:
This asks a question in a different direction that my prior
reports
inst
both of those libraries when -lc++ is encountered.
I have finally reproduced Cy's build error locally and am testing my fix. If it
works I'll commit it.
--
John Baldwin
On 12/14/21 9:40 AM, Gleb Smirnoff wrote:
On Tue, Dec 14, 2021 at 09:28:07AM -0800, John Baldwin wrote:
J> > AFAIK, today it will always panic only with WITNESS. Without WITNESS it
would
J> > pass through mtx_lock as long as the mutex is not locked.
J>
J> Yes, but the defa
On 12/13/21 12:25 PM, Gleb Smirnoff wrote:
On Mon, Dec 13, 2021 at 11:56:35AM -0800, John Baldwin wrote:
J> > J> So there are two things here. The root issue is that the devel/apr1
port
J> > J> runs a configure test for TCP_NDELAY being inherited by accepted
sockets.
J>
a rather annoying beep whose volume
I couldn't control that I actually prefer to have off normally. On further
reflection, the beep I was looking for for bad input may actually be an
xscreensaver thing for an invalid character to unlock the screen vs a sysbeep
anyway.
--
John Baldwin
the
VOP/VFS are not MFC'd. However, in this case, it might be
ok to do so, since it is unlikely there is an out of source tree
file system with a custom VOP_ALLOCATE() method?
I do not see much wrong with #2, this is what I would do myself.
I also think this is fine.
--
John Baldwin
On 12/13/21 9:35 AM, Gleb Smirnoff wrote:
Hi John,
On Mon, Dec 13, 2021 at 07:45:07AM -0800, John Baldwin wrote:
J> So there are two things here. The root issue is that the devel/apr1 port
J> runs a configure test for TCP_NDELAY being inherited by accepted sockets.
J> This te
d the machine looked hung. (The
fact that that sysbeep is off so I couldn't tell if typing in commands was
doing anything vs emitting errors probably didn't improve trying to diagnose
the hang as "sitting in ddb" initially, though I don't know if DDB itself
emits a beep for invalid commands, etc.)
--
John Baldwin
ked into the code. Just a thought.)
So the new changes always build a temporary tree (vs trying to build
/var/db/etupdate/current in place). For -n it should be that it just
doesn't change /var/db/etcupdate/current at the end, but if it did the
move anyway that would explain the bug you are seeing. That does indeed
look broken. Please file a PR as a reminder for me to fix it.
--
John Baldwin
t; with "File still has conflicts, are you sure?",
so it will only install a file to /etc with those changes if you have
explicitly confirmed you want it.
--
John Baldwin
:
v2-sparc64-sav.in
Only in /usr/obj/DESTDIRs/main-amd64-poud/usr/tests/usr.sbin/sa:
v2-sparc64-u.out
Only in /usr/obj/DESTDIRs/main-amd64-poud/usr/tests/usr.sbin/sa:
v2-sparc64-usr.in
I'll commit fixes for some of these.
--
John Baldwin
re/i18n/esdb/ISO-8859 (cleandir)
678 ===> tests/sys/cddl/zfs/tests/cli_root/zfs_clone (cleandir)
I think Jess has a possible fix. This is some regression added in the
build system several months ago.
--
John Baldwin
as already there in February, this is not the case. Will try to
reproduce this, but wasn't able up to now.
The congestion control changes just probably exacerbated the bug by
adding a new reference on this module, just as they exposed the bug
with khelp using the wrong SYSINIT subsystem.
--
John Baldwin
ped in /usr/src/cddl/lib/libavl
My guess is that this was fixed by
git: 9e9c651caceb - main - cddl: fix missing ZFS library dependencies
--
John Baldwin
No, these lines are for removing the current versions of the
libraries if you do 'make delete-old WITHOUT_DIALOG=yes'.
They weren't bumped previously when I bumped them for ncurses
(probably my fault).
--
John Baldwin
/include/dialog.h:extern DIALOG_VARS dialog_vars;
/usr/include/dialog.h:extern DIALOG_COLORS dlg_color_table[];
Then we need to bump libdialog's so version to 10? (I don't
think libdialog has symbol versioning)
--
John Baldwin
7io 0pf+0w
I'm curious if this is a know issue either in Qemu or in FreeBSD for
risc-v or if I'm doing anything wrong here?
It is a known issue with how we brand FreeBSD/riscv binaries. Jess
(cc'd) has a WIP review with a possible fix IIRC.
--
John Baldwin
this
proposal happen.
Again just in case: THIS IS NOT A PROPOSAL TO REMOVE CSH FROM BASE!
I think this is fine. I would also be fine with either removing 'toor' from the
default password file or just leaving it as-is for POLA. (I would probably
prefer removing it outright.)
--
John Baldwin
s if you had run 'make cleanworld' up above where you list
'make clean')
--
John Baldwin
t; /tmp/etc.diff
(etcupdate diff doesn't show any diffs.)
Today I've just updated current and etcupdate -p gives:
"Failed to build new tree"
What might be wrong?
You can look in /var/db/etcupdate/log to check for errors.
--
John Baldwin
R=yes' to force your builds
to use the
clang 11 included in stable/13 instead of the host clang 12. You could also
MFC the fixes
from head to use -Wno-error= instead of -Wno-error-.
--
John Baldwin
ou can use 'etcupdate revert /path/to/file'. Otherwise, you can
use the patch generated by 'etcupdate diff' either as a guide to manually
update files to remove unwanted differences, or as input to patch -R.
--
John Baldwin
On 6/15/21 11:22 AM, Bakul Shah wrote:
On Jun 15, 2021, at 9:03 AM, John Baldwin wrote:
On 6/10/21 8:13 AM, Bakul Shah wrote:
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod
-kmod /usr/local/sys/modules
Now it gets compiled every time you do make buildkernel.
If things break you can do a git pull in the drm-kmod dir
and rebuild.
This is what I do now as well. I think this is probably the
sanest approach to use on HEAD at least.
--
John Baldwin
On 6/7/21 12:58 PM, Ian Lepore wrote:
On Mon, 2021-06-07 at 13:53 -0600, Warner Losh wrote:
On Mon, Jun 7, 2021 at 12:26 PM John Baldwin wrote:
On 5/20/21 9:37 AM, Michael Gmelin wrote:
Hi,
After a binary update using freebsd-update, all files in /etc
contain
"empty" VCS Id he
e we might eventually remove them in the future, but doing so
right now would introduce a lot of churn and the conversion to git
had enough other churn going on.
--
John Baldwin
On 4/24/21 4:42 AM, Graham Perrin wrote:
On 21/04/2021 18:19, John Baldwin wrote:
On 4/17/21 12:52 PM, Graham Perrin wrote:
2)
<https://reviews.freebsd.org/D28062#change-5KzY5tEtVUor> line 2274
etcupdate -p
I get:
> No previous tree to compare against, a sane comparison is not
e.g. I use it frequently
to update rootfs images I use with qemu for RISC-V or MIPS that I run under
qemu, or when updating the SD-card for my RPI that I cross-build on an x86
host).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.f
turn $?
}
update_etcupdate() {
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
work fine on the next upgrade.
However, I'm curious how you didn't get the etcupdate bootstrap when
you initially installed.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
normally. The actual tree comparison isn't affected.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
'ktls_enable_tx' and 'ktls_enable_rx'
are failing, or barring that printf. For example, does ktls_create_session()
fail, or does ktls_try_sw() fail? It is probably easiest to debug this using
a userland application using openssl than trying NFS over TLS.
--
John Baldwin
, the 12.x dialog4ports was still going to fail
as the 12.x version of those libraries were already broken. I haven't checked
to see if the affected libraries have been added to misc/compat12x.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
ht
in both directions (or if you use TLS 1.1 with
TOE offload on a Chelsio T6).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 2/11/21 9:59 AM, Hartmann, O. wrote:
On Wed, 10 Feb 2021 07:21:20 +0100
"Hartmann, O." wrote:
On Tue, 9 Feb 2021 15:15:38 -0800
John Baldwin wrote:
On 2/9/21 2:16 PM, Hartmann, O. wrote:
On Wed, 3 Feb 2021 17:34:24 +0100
Guido Falsi via freebsd-current wrote:
On 03/0
On 2/9/21 2:16 PM, Hartmann, O. wrote:
On Wed, 3 Feb 2021 17:34:24 +0100
Guido Falsi via freebsd-current wrote:
On 03/02/21 17:02, John Baldwin wrote:
On 2/2/21 10:16 PM, Hartmann, O. wrote:
On Mon, 1 Feb 2021 03:24:45 +
Rick Macklem wrote:
Rick Macklem wrote:
Guido Falsi wrote
in serf (an Apache library used by
subversion). It would also affect any other software using serf. The serf in
ports will also have to be patched.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
t;knew" it was using
KTLS and would use direct read/write after letting OpenSSL (or a similar
library) handle the handshake.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
issing detail, maybe:
If you want to get a list of all services started when FreeBSD boots
in the order they are started, enter "service-e".
?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
in periodically, though
that opens the question of how to deal with cherry-picks to stable (for
which asking developers to do a rebase --ignore-date prior to pushing is
probably the simpler approach).
If we did want monotonically increasing dates without having a staging
branch, we could perhaps
8crypto(4)) at that point, but aesni in GENERIC makes sense
right now (and I'd say to MFC it to 12). armv8crypto in arm64
GENERIC will make sense once AES-XTS support (currently in a review)
lands.
--
John Baldwin
___
freebsd-current@freebsd.org mailing
ess region for config register read/write
as this code does:
https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L339
Also, that means the vm_bus.c can't hardcode reading from bus 0. Instead,
vmd(4) might need to export an IVAR to vmd_bus(4) that is the starting
tting a bug in a NIC driver for example.
I think netstat -s would be a better place to start to try to debug this.
> https://github.com/opnsense/core/issues/4415
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/ma
config() is
correct.
--
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
each time you update. Then you can
easily go back to that tag by name instead of having to look up the
hash.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
On 12/28/20 12:24 PM, John Baldwin wrote:
> I got this panic again today in a VM when quitting a gdb
> session after killing a child process via 'kill'.
>
> panic: Assertion pgrp->pg_jobc > 0 failed at
> /git/bhyve/sys/kern/kern_proc.c:816
> cpuid = 1
> time = 160918
094001a00,
frame=0xfe0094671b00) at /git/bhyve/sys/kern/kern_fork.c:1069
#6
#7 0x0008007b71aa in ?? ()
kgdb can't find the panicking process due to the zombproc removal, so I will
have to go work on kgdb to recover from that change. :(
--
Joh
e any output, I'm not
>> likely to use it too often ...
>
> Update: I have created a fork of zfs-stats to work on:
>
> https://github.com/stesser/zfs-stats
>
> Initial change is to work around the long delay mentioned above and to
> use the correct name for the vd
personally, e.g., while running commands like dd[0], cp, mv,
> poudriere etc.), not for getting debug output.
I agree with this.
> Question: Speaking of discovering the feature, wouldn't it make sense
> to document this tunable on the stack(9) and/or tty(4) man page(s)?
This sounds l
On 5/27/20 2:05 PM, Hans Petter Selasky wrote:
> On 2020-05-27 15:41, Justin Hibbits wrote:
>> On Wed, 27 May 2020 06:27:16 -0700
>> John Baldwin wrote:
>>
>>> On 5/27/20 2:39 AM, Andriy Gapon wrote:
>>>> On 27/05/2020 11:13, Andriy Gapon wrote:
&
multi-pass and to resume all the
bridges
first before trying to resume leaf devices (including timers), but that's a
fair bit
of work. It might be that we just need to resume timer interrupts later after
the
new-bus resume (I think we currently do it before?), though the reason for that
fffe00a7a19ad0
>> amd64_syscall() at amd64_syscall+0x140/frame 0xfe00a7a19bf0
>> fast_syscall_common() at fast_syscall_common+0x101/frame 0xfe00a7a19bf0
>>
>> I am not sure if this is just a coincidence but it appears as if a write to
>> some
>> PCI configuratio
let me know if you see problems with me doing this?
I don't see any problems, per se, but I still need to do some changes on my
end for software KTLS RX before it's ready to merge (I'm hoping to kill
the iovecs in the kthreads entirely).
--
John Baldwin
__
e first step towards
any of that is probably to remove some of the cruft from cdefs.h and
possibly some other places.
(BTW, it would be good to know if it's at all useful to keep any of the
icc bits around.)
--
John Baldwin
___
freebsd-current@free
ernal toolchain
for 13)
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
d to have ctfconvert installed. This
does mean you need to use a custom kernel instead of GENERIC.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
.x host)
Have you been able to bisect it at all? I think libedit is probably a
good candidate as well.
What I see is that tramp-mode just hangs until I kill the ssh session it
is using, and then I see the same output you had below in the debug
window showing the extraneous newlines.
On 1/26/20 8:08 PM, Rick Macklem wrote:
John Baldwin wrote:
[stuff snipped]
Hmmm, this might be a fair bit of work indeed.
Right now KTLS only works for transmit (though I have some WIP for receive).
KTLS does assumes that the initial handshake and key negotiation is handled by
OpenSSL
On 1/12/20 8:23 PM, Benjamin Kaduk wrote:
> On Thu, Jan 09, 2020 at 10:53:38PM +, Rick Macklem wrote:
>> John Baldwin wrote:
>>> On 1/7/20 3:02 PM, Rick Macklem wrote:
>>>> Hi,
>>>>
>>>> Now that I've completed NFSv4.2 I'm on to the next
s = SSL_new(...);
/* fd is the existing TCP socket */
SSL_set_fd(s, fd);
OpenSSL_connect(s);
if (BIO_get_ktls_send(SSL_get_wbio(s)) {
/* Can use KTLS for transmit. */
}
if (BIO_get_ktls_recv(SSL_get_rbio(s)) {
/* Can use KTLS for receive. */
}
--
John Baldwin
___
On 12/19/19 12:06 PM, Ryan Libby wrote:
> On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
>>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as fla
On 12/18/19 4:16 PM, Mark Millard wrote:
>
>
> On 2019-Dec-18, at 13:48, John Baldwin wrote:
>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as
on
newer FreeBSD releases (e.g gcc9 for 13.0 and gcc6 for 12.x).
I do plan to switch the default toolchains for make universe/tinderbox
for targets using -xtoolchain-gcc based on GCC 6 over to the
freebsd-gcc6 variants in the next week or so.
--
John Baldwin
On 10/22/19 8:42 PM, Alexey Dokuchaev wrote:
> On Tue, Oct 22, 2019 at 04:34:53PM -0700, John Baldwin wrote:
>> On 10/18/19 10:05 AM, Alexey Dokuchaev wrote:
>>> hi there,
>>>
>>> i've made my -CURRENT world and installed, but "make delete-old"
hing, or ObsoleteFiles.inc lacks a few entries?
These are from the OpenSSL 1.1.1 commit. However, they are tagged as
OLD_LIBS and check-old-libs and delete-old-libs should be automatically
deleting these? Does 'make check-old' report these files as
old libraries?
--
John Baldwin
On 9/25/19 10:33 AM, Sergey Kandaurov wrote:
> On Sat, Sep 21, 2019 at 08:43:58PM -0400, Ryan Stone wrote:
>> I have written a short test program that runs unlinkat(2) in
>> capability mode and fails due to not having the write capabilities:
>>
>> https://people.freebsd.org/~rstone/src/unlink.c
>>
On 8/30/19 10:42 AM, Kyle Evans wrote:
> On Fri, Aug 16, 2019 at 7:38 PM John Baldwin wrote:
>>
>> On 8/16/19 3:05 AM, Gary Jennejohn wrote:
>>> I tried to build a kernel today and it failed in modules-all even
>>> though I had LOCAL_MODULES=""
On 8/16/19 5:33 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 17:23:08 -0700
> John Baldwin wrote:
>
>>> I use better way:
>>> /etc/make.conf:
>>> # Modules to build with kernel.
>>> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod
>>> graphics/gpu
ule}
(${target:S/^reinstall$/install/:S/^clobber$/cleandir/})"
@cd ${LOCAL_MODULES_DIR}/${module}; ${MKMODULESENV} ${MAKE} \
@@ -83,6 +84,7 @@ modules-${target}:
${target:S/^reinstall$/install/:S/^clobber$/cleandir/}
.endfor
.endif
+.endif
.endfor
# Handle ports (as def
ing (you have to just use
LOCAL_MODULES=) this already exists. You can set it in
/etc/src.conf, in a kernel config, or on the command line.
> Rather than a default to on with an opt out mechanism perhaps
> while we gain experience change this to a default to off with
> an opt in mechanism?
It'
On 8/16/19 3:52 PM, Rozhuk Ivan wrote:
> On Fri, 16 Aug 2019 15:40:24 -0700
> I use better way:
> /etc/make.conf:
> # Modules to build with kernel.
> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod graphics/gpu-firmware-kmod
This doesn't work for folks who use pre-built packages.
-
On 8/14/19 1:19 PM, Ian Lepore wrote:
> On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote:
>> On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
>>
>>> On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
>>>> On 8/14/19 11:06 AM, Kyle Evans wrote:
&
only one /usr/local/sys/modules? Do I need multiple port trees
> just to pull in out of tree module sources?
In some ways, installing sources for DRM is a compromise for the fact that we
can't have DRM in the base source anymore (for various reasons). However,
virtualbox is also probably in t
1 - 100 of 2772 matches
Mail list logo
