d68ee484 | 21-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Clean up a bit the 'clean' target
The '.didbootstrap' mark file was a legacy of the removed pkgsrc bootstrap procedure. |
ab75f1d9 | 21-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Let vnconfig(8) auto determine/create the vn device |
ccc073f1 | 21-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Unconfigure vn(4) and clean up after creating efiboot.img |
aab461e0 | 20-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Simplify the adjustments to loader.conf for IMG boot
Use 'sed' similar to fstab adjustments instead of grep+echo to adjust 'boot/loader.conf' to the IMG boot. |
a7b36ea4 | 20-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Adjust fstab to remove '-C' option for /tmp tmpfs mount
For the /tmp mount, no need to copy the origin contents; also, there shouldn't be any contents at this early boot stage. |
66d900e9 | 20-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Adjust fstab and reuse it for IMG boot
The root '/' filesystem is mounted by the kernel, so it can be omitted from 'etc/fstab'. This also makes the 'fstab' file be used by the IMG boot, s
nrelease: Adjust fstab and reuse it for IMG boot
The root '/' filesystem is mounted by the kernel, so it can be omitted from 'etc/fstab'. This also makes the 'fstab' file be used by the IMG boot, so just reuse it.
show more ...
|
e11cbfed | 20-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Fix up rc.conf to mount root readwrite for IMG boot
While there, remove the obsolete comments in 'etc/rc.conf'. |
935aaf82 | 09-Jan-2025 |
Aaron LI <aly@aaronly.me> |
nrelease: Add root_rw_mount="NO" to rc.conf to fix ISO boot
The ISO root filesystem is obviously readonly and cannot be remounted to 'rw'. Without setting 'root_rw_mount=NO', the ISO boot would abo
nrelease: Add root_rw_mount="NO" to rc.conf to fix ISO boot
The ISO root filesystem is obviously readonly and cannot be remounted to 'rw'. Without setting 'root_rw_mount=NO', the ISO boot would abort after failing to remount the root filesystem.
This is a follow-up fix to my previous commit 31b00396377857ebb62259aa944f9351fa62ea44.
Reported-by: Sergey Zigachev (servik)
show more ...
|
44d26fef | 08-Jan-2025 |
Matthew Dillon <dillon@apollo.backplane.com> |
cd9660 - Fix unexpected file/dir mode mask in 7764eb663ae501
* 7764eb663ae501 used the modes of the underlying mount point as the default fmask and dmask for cd9660 mounts when no masking options
cd9660 - Fix unexpected file/dir mode mask in 7764eb663ae501
* 7764eb663ae501 used the modes of the underlying mount point as the default fmask and dmask for cd9660 mounts when no masking options are specified. This is unexpected. Prior to that commit, the modes from ISO were used verbatim.
* This commit returns to the old (more expected) operation when -m/-M is not specified.
* Also make some adjustments to ensure that new kernels work with old worlds and vise-versa. Make use of the fields require the related mount flag and also default the fields to all modes when -m/-M is not specified. Any mismatch will have the prior (expected) operation.
Reported-by: Sergey Zigachev (servik)
show more ...
|
8958ea92 | 21-Dec-2024 |
Aaron LI <aly@aaronly.me> |
initrd: Add diff/sdiff back to rescue and fix build
Update the rescue/Makefile to include the updated diff/sdiff utilities; however, diff3 is excluded because it's a shell script and relies on libex
initrd: Add diff/sdiff back to rescue and fix build
Update the rescue/Makefile to include the updated diff/sdiff utilities; however, diff3 is excluded because it's a shell script and relies on libexec/diff3prog. As a result, we must remove /rescue/diff3 via "make upgrade"; otherwise, /rescue/diff3 would become a separate binary (because of hardlinks) and break initrd build because of exceeded size.
Bug: https://bugs.dragonflybsd.org/issues/3376
show more ...
|
48363b68 | 21-Dec-2024 |
Aaron LI <aly@aaronly.me> |
diff3(1): Rewrite Makefile by using SCRIPTS
Meanwhile, rename the script "diff3" to "diff3" to work with SCRIPTS. |
7876b5d2 | 21-Dec-2024 |
Aaron LI <aly@aaronly.me> |
libexec/diff3prog: Don't duplicate the installation of diff3.1
The diff3.1 man page is already being installed by usr.bin/diff3. |
a95b5cf7 | 21-Dec-2024 |
Aaron LI <aly@aaronly.me> |
diff(1): Remove unnecessary "-Wall" COPTS
The "-Wall" option is already set by default. |
d775d69b | 21-Dec-2024 |
Aaron LI <aly@aaronly.me> |
sdiff(1): Remove unused stuff from Makefile |
f7ba04f4 | 21-Dec-2024 |
Aaron LI <aly@aaronly.me> |
sdiff(1): Remove Makefile.depend
That was auto-generated in FreeBSD's code base; we don't need it.
|
9b7e606c | 02-Dec-2023 |
Martin Neitzel <neitzel@marshlabs.gaertner.de> |
mail(1): Catch SIGWINCH to adapt to terminal size changes
Turn setscreensize() into a signal handler for SIGWINCH. This allows users to resize their terminal and have long subject lines become visi
mail(1): Catch SIGWINCH to adapt to terminal size changes
Turn setscreensize() into a signal handler for SIGWINCH. This allows users to resize their terminal and have long subject lines become visible in "h(eader)" listings without the need to restart mail(1).
Submit: https://bugs.dragonflybsd.org/issues/3375
show more ...
|
d5ba4fae | 20-Dec-2024 |
Aaron LI <aly@aaronly.me> |
rc.d: Fix a typo in the comment of dhclient script |
ab4c55c7 | 18-Dec-2024 |
Matthew Dillon <dillon@apollo.backplane.com> |
dsynth - Include "add" in "help" output.
* Include a blurb on the "add" directive in the dsynth help output.
Submitted-by: Pierre-Alain TORET <daftaupe@dragonflybsd.org> |
1a7f0986 | 03-Dec-2024 |
Aaron LI <aly@aaronly.me> |
rc.d: Improve dhclient script
* Make use of the pid file to check the current status * Improve the handling of arguments * Improve error reporting
Obtained-from: FreeBSD |
5eebb8b7 | 03-Dec-2024 |
Aaron LI <aly@aaronly.me> |
rc.conf.5: Document the missing dhclient_flags_<interface>
This interface-specific dhclient(8) flags variable is supported by the rc script, but was missing in the man page.
Obtained-from: FreeBSD |
c726e452 | 03-Dec-2024 |
Aaron LI <aly@aaronly.me> |
rc.d: Fix nfsd/yp* scripts to set ${command_args}
These scripts were failing to set ${command_args} because they set "command_args=${<name>_flags}" before performing "load_rc_config". As a result, t
rc.d: Fix nfsd/yp* scripts to set ${command_args}
These scripts were failing to set ${command_args} because they set "command_args=${<name>_flags}" before performing "load_rc_config". As a result, the "command_args" variable was empty and the "<name>_flags" settings in rc.conf were effectively ignored.
Fix this issue by moving the "command_args" assignment after calling "load_rc_config".
Reported-by: kentish (on IRC) Referred-to: FreeBSD
show more ...
|
bd23261b | 30-Nov-2024 |
John Marino <dragonflybsd@marino.st> |
libstdc++: Fix unsigned wraparound in codecvt::do_length [PR105857]
When the max argument to std::codecvt<wchar_t, char, mbstate_t>::length is SIZE_MAX/4+1 or greater the multiplication with sizeof(
libstdc++: Fix unsigned wraparound in codecvt::do_length [PR105857]
When the max argument to std::codecvt<wchar_t, char, mbstate_t>::length is SIZE_MAX/4+1 or greater the multiplication with sizeof(wchar_t) will wrap to a small value, and the alloca call will have a buffer that's smaller than requested. The call to mbsnrtowcs then has a buffer that is smaller than the value passed as the buffer length. When libstdc++.so is built with -D_FORTIFY_SOURCE=3 the mismatched buffer and length will get detected and will abort inside Glibc.
When it doesn't abort, there's no buffer overflow because Glibc's mbsnrtowcs has the same len * sizeof(wchar_t) calculation to determine the size of the buffer in bytes, and that will wrap to the same small number as the alloca argument. So luckily Glibc agrees with the caller about the real size of the buffer, and won't overflow it.
Even when the max argument isn't large enough to wrap, it can still be much too large to safely pass to alloca, so we should limit that. We already have a loop that processes chunks so that we can handle null characters in the middle of the input. If we limit the alloca buffer to 4kB then we'll just loop each time that buffer is filled.
Reported-by: Jonathan Wakely (GNU GCC)
show more ...
|
bbd7e133 | 29-Nov-2024 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Fix signal / signal-mask-change race
* Fix race between incoming signals and sigsuspend(), ppoll(), or pselect() when used to change the signal mask. A signal can be received and queue
kernel - Fix signal / signal-mask-change race
* Fix race between incoming signals and sigsuspend(), ppoll(), or pselect() when used to change the signal mask. A signal can be received and queued to a process that is in the middle of unmasking said signal without triggering signal processing.
* Our kernel *sleep*() and wakeup functions avoid whole-process locks to ensure high thread performance, but this can result in a race when a signal cannot be delivered to a thread and gets queued to the process instead.
In order to keep the high-performance sleep, we instead use atomic ops and a ref-counter only in code paths related to general signal delivery to the process. Code which changes the signal mask then waits for the ref-counter to become zero as needed to ensure proper interlocked tests across signal mask changes to close the race.
show more ...
|
a6741f0b | 20-Nov-2024 |
Tomohiro Kusumi <tkusumi@netbsd.org> |
sbin/hammer2/cmd_snapshot.c: Fix error handling
pfs.name is not valid when ioctl(HAMMER2IOC_PFS_GET) failed. |
6cd7b653 | 17-Nov-2024 |
Tomohiro Kusumi <tkusumi@netbsd.org> |
sbin/hammer2: Fix usage() |