7485684f | 03-Mar-2024 |
Aaron LI <aly@aaronly.me> |
Whitespace cleanups |
7364150d | 12-Mar-2024 |
Aaron LI <aly@aaronly.me> |
less(1): Fix the installation name of 'lesspipe.sh'
Don't change the installation name, as the exact name of 'lesspipe.sh' is used in 'zless.sh'. |
798ad93f | 11-Mar-2024 |
Aaron LI <aly@aaronly.me> |
less(1): Regenerate defines.h and update Makefiles
- Regenerate 'defines.h' as described in 'README.DRAGONFLY'. - Update the Makefiles for less(1), lessecho(1) and lesskey(1). - Install the lessecho
less(1): Regenerate defines.h and update Makefiles
- Regenerate 'defines.h' as described in 'README.DRAGONFLY'. - Update the Makefiles for less(1), lessecho(1) and lesskey(1). - Install the lessecho.1 man page.
show more ...
|
70bb9b56 | 06-Mar-2024 |
Aaron LI <aly@aaronly.me> |
sockstat(1): Fix and improve output formatting
The main issue with the old formatting was that the FD column was limited to 2 characters, so there would be no space between FD and PROTO columns.
In
sockstat(1): Fix and improve output formatting
The main issue with the old formatting was that the FD column was limited to 2 characters, so there would be no space between FD and PROTO columns.
Increase the FD column to 5 characters, and increase the PID column to 6 characters. In addition, refactor the output formatting code to clean up the mess.
While there, clean up the code a bit to save some type castings.
show more ...
|
9f7ef25b | 04-Mar-2024 |
Ricardo Branco <rbranco@suse.de> |
gzip(1): Set file flags after setting file times
Only set the source file flags on the target file after the timestamp has been set; otherwise setting the timestamp will fail if the flags don't perm
gzip(1): Set file flags after setting file times
Only set the source file flags on the target file after the timestamp has been set; otherwise setting the timestamp will fail if the flags don't permit it (i.e., uchg).
To reproduce the issue: $ /usr/bin/touch /tmp/foo $ /bin/chflags uchg /tmp/foo $ /usr/bin/gzip -v /tmp/foo gzip: couldn't utimes: /tmp/foo.gz: Operation not permitted
GitHub PR: https://github.com/DragonFlyBSD/DragonFlyBSD/pull/21 See also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=120208
show more ...
|
a4775f72 | 03-Mar-2024 |
Ricardo Branco <rbranco@suse.de> |
hexdump(1): Ignore zero st_size to work on pseudo-filesystems
hexdump(1) was not able to skip on files residing on pseudo-filesystems, for example: hexdump -s1 /proc/$$/status
GitHub PR: https://gi
hexdump(1): Ignore zero st_size to work on pseudo-filesystems
hexdump(1) was not able to skip on files residing on pseudo-filesystems, for example: hexdump -s1 /proc/$$/status
GitHub PR: https://github.com/DragonFlyBSD/DragonFlyBSD/pull/20
show more ...
|
5f8e6ce5 | 03-Mar-2024 |
Ricardo Branco <rbranco@suse.de> |
wc(1): Ignore zero st_size to work on pseudo-filesystems
Without this fix, 'wc -c' was failing on pseudo-filesystems, for example: wc -c /proc/$$/status
GitHub PR: https://github.com/DragonFlyBSD/D
wc(1): Ignore zero st_size to work on pseudo-filesystems
Without this fix, 'wc -c' was failing on pseudo-filesystems, for example: wc -c /proc/$$/status
GitHub PR: https://github.com/DragonFlyBSD/DragonFlyBSD/pull/19
show more ...
|
ad668869 | 02-Mar-2024 |
Aaron LI <aly@aaronly.me> |
netstat(1): Increase column width of interface name
Given that the interface can be renamed, the interface name may be generally longer, so increase the column width of interface name by 2 character
netstat(1): Increase column width of interface name
Given that the interface can be renamed, the interface name may be generally longer, so increase the column width of interface name by 2 characters (from 6 to 8).
Referred to FreeBSD.
show more ...
|
3da8e663 | 28-Feb-2024 |
Aaron LI <aly@aaronly.me> |
awk(1): Raise WARNS to 5 for internal 'maketab' tool |
edd1b3cf | 23-Jan-2024 |
Aaron LI <aly@aaronly.me> |
netstat(1): Fix alignment of 'Drop' and 'Time' columns |
49d2b1cb | 16-Jan-2024 |
Matthew Dillon <dillon@apollo.backplane.com> |
dsynth - Adjust /boot mounts for chroot
* Fix issue where Intel microcode couldn't be installed within the chroot due to trying to write into /boot.
* Replace /boot null-mount with a /boot tmpfs
dsynth - Adjust /boot mounts for chroot
* Fix issue where Intel microcode couldn't be installed within the chroot due to trying to write into /boot.
* Replace /boot null-mount with a /boot tmpfs and mkdir /boot/modules.local. Leave other /boot directories unpopulated for now (we'll fix that if we hit problems). i.e. no /boot/kernel or anything else is in the chroot any more.
* This also allows us to remove the /boot/modules.local tmpfs mount we had before, improving performance slightly.
Reported-by: tuxillo
show more ...
|
a361ab31 | 02-Jan-2024 |
Matthew Dillon <dillon@apollo.backplane.com> |
Add integrated dports build feature to build-all and install-all targets
When WITH_DPORTS=YES is used build-all and install-all, these targets will also build the base set of ports and all of their
Add integrated dports build feature to build-all and install-all targets
When WITH_DPORTS=YES is used build-all and install-all, these targets will also build the base set of ports and all of their dependencies using configuration data and the "dragonfly/base" dport found in "/usr/src/dports.base".
This feature is intended to be used by the nrelease build in an upcoming commit, and may also be used manually.
The /usr/dports tree must exist and contains the dports repo to use as the basis of the dports build. It will be null-mounted in the chroot and the "/usr/src/dports.base/dragonfly" directory will be null-mounted under it to provide the "dragonfly/base" meta-port. The DPORTSBASE make variable may be used to override the location of the main dports repo.
The build-all and install-all targets use a sophisticated chrooted environment to do a completely clean dports build with dsynth. It It will actually "make installworld" plus a clean "make distribution" inside the chroot environment to create the environment, and the host system's /etc/resolv.conf will be copied in.
build-all - Augmented when used WITH_DPORTS=YES install-all - Augmented when used WITH_DPORTS=YES buildportschroot - Build a fresh chroot environment for dsynth mountports - Do all null mounts and cp's needed for the env buildports - Run dsynth build dragonfly/base in the env installports - Install the built ports on the host system (see note) umountports - Remove the null mounts
WITH_DPORTS=YES - executes buildportschroot, mountports, buildports, and umountports when run from build-all.
executes mountports, installports, umountports when run from install-all.
DPORTSBASE=path - Defaults to /usr/dports, may be used to override the location where the main dports tree can be found.
NOTE: Installports may require interactivity as the base system might already have installed ports. Generally speaking it is best to not revert any ports you might already have installed, so feel free to tell it not to install anything.
* Added various make targets and augmented build-all and install-all
* /usr/local/sbin added and the stale /usr/pkg/bin removed from _HOSTPATH.
* Add /usr/src/dports.base infrastructure.
It contains the dsynth.ini and pkg.conf files that will be used for the local dsynth operations. Some paths are replaced with SED when copied to the chroot. The dsynth.ini is relative to the chroot.
It also contains the dragonfly/base dport which is the meta-port that dsynth will be told to build.
All other dports related files and directories are null-mounted from /usr/dports.
* Add /usr/distfiles.base to mtree/BSD.usr.dist. This directory is also created by the build if it does not exist since the host system might not have run a new installworld recently.
This directory will be used during build-all (buildports) to store the distfiles required to build dragonfly/base, so they only need to be fetched once.
* Add the "-C ConfigBase" option to dsynth to make running it from the chrooted environment easier. This overrides the /etc/dsynth directory and removes /etc/dsynth as a fallback.
* dsynth conditionalizes calling syscap_set() for backwards compatibility with older host systems that might not have been upgraded to include the feature yet.
show more ...
|
e43c2985 | 11-Dec-2023 |
Aaron LI <aly@aaronly.me> |
netstat(1): Update route.c to get rid of some file-global variables
No functional changes. |
04a3b05a | 11-Dec-2023 |
Aaron LI <aly@aaronly.me> |
netstat(1): Whitespace cleanups |
7d605468 | 10-Nov-2023 |
Aaron LI <aly@aaronly.me> |
netstat(1): Fix build against with <net/radix.h> gaining 'const' |
3525c8d7 | 20-Oct-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
systat - Change -pv, add -w option
* Add -w (wide mode) option, currently only affects -pv
* Change -pv to use a wider contention label and to include the contending lock's address when in wide m
systat - Change -pv, add -w option
* Add -w (wide mode) option, currently only affects -pv
* Change -pv to use a wider contention label and to include the contending lock's address when in wide mode.
* Move the sample_pc (root only) display over to wide-mode.
show more ...
|
2b3f93ea | 13-Oct-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Add per-process capability-based restrictions
* This new system allows userland to set capability restrictions which turns off numerous kernel features and root accesses. These restricti
kernel - Add per-process capability-based restrictions
* This new system allows userland to set capability restrictions which turns off numerous kernel features and root accesses. These restrictions are inherited by sub-processes recursively. Once set, restrictions cannot be removed.
Basic restrictions that mimic an unadorned jail can be enabled without creating a jail, but generally speaking real security also requires creating a chrooted filesystem topology, and a jail is still needed to really segregate processes from each other. If you do so, however, you can (for example) disable mount/umount and most global root-only features.
* Add new system calls and a manual page for syscap_get(2) and syscap_set(2)
* Add sys/caps.h
* Add the "setcaps" userland utility and manual page.
* Remove priv.9 and the priv_check infrastructure, replacing it with a newly designed caps infrastructure.
* The intention is to add path restriction lists and similar features to improve jailess security in the near future, and to optimize the priv_check code.
show more ...
|
2c5f241e | 30-Aug-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
dsynth - Add -f option for purge-distfiles
* purge-distfiles normally refuses to run if the dports tree has Makefile or dependency errors, because that may cause it to remove distfiles that are
dsynth - Add -f option for purge-distfiles
* purge-distfiles normally refuses to run if the dports tree has Makefile or dependency errors, because that may cause it to remove distfiles that are actually needed.
* Add the -f option to force it to run anyway.
show more ...
|
b81e76a3 | 29-May-2023 |
Pierre-Alain TORET <pierre-alain.toret@protonmail.com> |
dsynth - Replace portsmon link by FreshPorts |
55f88487 | 04-Apr-2023 |
Sascha Wildner <saw@online.de> |
ktrace/kdump: Implement sysctl tracing.
Useful to know which sysctls exactly are being accessed.
Adapted-from: FreeBSD |
943ee1f8 | 19-Mar-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
dsynth - Fix bug, but actually keep the behavior
* Fix a bug where dexec was not copying the entry environment. But actually, that is the behavior we want (a clean environment prior to adding ou
dsynth - Fix bug, but actually keep the behavior
* Fix a bug where dexec was not copying the entry environment. But actually, that is the behavior we want (a clean environment prior to adding our own dsynth-managed environment) so then comment out the code.
Reported-by: mjg
show more ...
|
0085a56d | 11-Mar-2023 |
Antonio Huete Jimenez <tuxillo@quantumachine.net> |
backlight(9): Initial port.
- backlight(9) is a generic panel backlight driver. - backlight(8) is the userland program to control backlight devices' properties. - Required by linuxkpi
Taken f
backlight(9): Initial port.
- backlight(9) is a generic panel backlight driver. - backlight(8) is the userland program to control backlight devices' properties. - Required by linuxkpi
Taken from: FreeBSD
show more ...
|
6b8aa754 | 03-Mar-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
dsynth - Add Numa_setsize option (defaults to disabled) (2)
* Add missing numa.c file |
3bd7e0a7 | 27-Feb-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
dsynth - Add Numa_setsize option (defaults to disabled)
* Currently only for testing purposes and not recommended for general use. Default is 0 (disabled).
* If enabled, a value of 2 or 4 are th
dsynth - Add Numa_setsize option (defaults to disabled)
* Currently only for testing purposes and not recommended for general use. Default is 0 (disabled).
* If enabled, a value of 2 or 4 are the only really viable choices, otherwise the cpu mask will be so fragmented that even highly parallel bulks are going to wind up with cpu threads left idle.
The NUMA partitioning is hacked at the moment but will generally work with both AMD and Intel.
This works by round-robining N cpumask domains across available builder slots. Insofar as DragonFlyBSD goes, this will localize per-process / per-thread anonymous page allocations and kernel memory resources.
* However, DragonFlyBSD still spreads buffer cache pages (the file cache) across all domains, including for tmpfs, The reason is that such pages tend to be very long-lived and fully localizing them can exhaust the VM page queues for related cpus and domains, forcing contention inside vm_page_alloc() as multiple cpu threads contend for fewer VM page queue slots.
show more ...
|
46c51ac5 | 22-Feb-2023 |
Matthew Dillon <dillon@apollo.backplane.com> |
buildworld - Fix bootstrapping from DFly 4.10
* xinstall has to manually include pwcache.c from libc when creating the bootstrap version from an old world. The Makefile was a bit messed up and
buildworld - Fix bootstrapping from DFly 4.10
* xinstall has to manually include pwcache.c from libc when creating the bootstrap version from an old world. The Makefile was a bit messed up and included pwcache.c twice, as well as included it outside of the bootstrap portion of the build, resulting in a link failure.
* Fix the Makefile so this works. Tested on an old solidrun micro-pc.
show more ...
|