IABSD.fr/src/distrib

Branch :


Log

Author Commit Date CI Message
9067fdea 2025-06-06 22:47:27 chase growth forever
42bd01a5 2025-06-04 09:10:05 sync, libutil minor bump
c941e4bf 2025-05-31 18:26:18 sync
8bde094e 2025-05-30 12:03:57 sync
a295bea1 2025-05-24 15:37:11 add /usr/include/amd64/ghcb.h
bd0b34f7 2025-05-21 01:56:21 sync
dcae8de5 2025-05-20 02:00:14 do not offer http/nfs without network Offline installs/upgrades, e.g. when there are no interfaces, do default to fetching sets over HTTP, which cannot work ( # vmctl start -c -b /bsd.rd -d disk.img offline ... Let's install the sets! Location of sets? (disk http nfs or 'done') [http] Skip these two methods unless there is a physical interface around: Location of sets? (disk or 'done') [disk] Shorten and clarify the comments while here. Feedback OK afresh1
1eb5aefc 2025-05-18 09:54:48 unify random seeding The installer has feed_random() and store_random(), rc(8) has random_seed(). Call both store_random() and use the same wording to match, use variables for brevity and convey intended file usage. Replace the absoloute octal mode for chmod(8) with a symbolic (relative) one to explicitly show that this is where userland strips the sticky bit set by the bootloader: if set, seeds are skipped with NOTE: random seed is being reused. (Only with root outside of softraid, where bootloaders cannot write.) Always call the function on shutdown and silence just stderr (stdout already is quiet) instead of doing a preemptive append for brevity: see rc r1.437. Feedback OK deraadt
bb6aa9a9 2025-05-17 08:22:03 Now there must be a colon separator between the device and image. Found by Tetsuya Isaki at NetBSD and nono project.
8b901a85 2025-05-15 02:43:08 sync
45c18297 2025-05-07 04:38:23 sync
4ff0ea73 2025-05-04 12:32:41 Prefer disks bigger than 1G as default root disk on install -current picks the alphanumerically first disk as default, which isn't the beset choice if install media, softraid(4) key disks or small external media attaches before the disk one intends to use. Finding the "best" disk is hard, but reshuffling the list of disks such that tiny ones come last is easy and works well enough to cover those cases: Available disks are: sd0 sd1. -Which disk is the root disk? ('?' for details) [sd0] ? +Which disk is the root disk? ('?' for details) [sd1] ? sd0: VirtIO, Block Device (0.8G) sd1: VirtIO, Block Device (3.0G) While here, rename the variable to reflect how it is used as list of disks rather than a single one. OK afresh1
cc858a7a 2025-05-03 16:48:56 Sync the supported hardware list with arm64.html.
a186de17 2025-05-03 15:16:43 sync pkgconf switch
5403d912 2025-05-02 18:44:25 sync
0ab49d10 2025-05-02 18:44:03 sync
0e444de8 2025-05-02 15:57:54 sync
a0a0c593 2025-04-29 01:48:04 sync
9be89971 2025-04-28 16:07:24 sync
445fa840 2025-04-28 05:26:12 sync
19cb63d5 2025-04-25 20:01:11 sync
c9362caa 2025-04-25 05:19:28 sync
77bd11e7 2025-04-06 11:54:36 Make IPv6 link-local scope identifiers in "HTTP Server?" answers work It understands IPv6 addresses already, but chokes on the % character: HTTP Server? (hostname or 'done') [fe80::1%vio0] '[fe80::1%vio0]' is not a valid hostname. Accept it; ftp(1) understands them. The answer ends up in installurl(5) and syspatch(8) as well as sysupgrade(8) work just fine with it. OK florian
cbfbf6a8 2025-03-29 14:26:41 Reuse dmesg.boot file for amd64 MDEFI check, clarify this usage pattern install.md r1.63 assumed it to be present, r1.64 reverted to plain dmesg(8), now hoist creation of the current boot's dmesg in a new DMESGBOOT variable for reuse (again) and tweak comments around it. There are different reasons and ways the installer looks at dmesg: - Here it concerns feature detection of something that won't change across reboots or during install/upgrade time: whether we booted via EFI/GPT. - scan_dmesg() uses that file to lookup keyboards, displays, consoles, etc. - diskinfo() on the other hand needs to see all disks at runtime, so live 'dmesg | ...' is needed to find latest attach line for them. - start_dmesg_listener() is its own mechanism and keeps a file to watch for changes, i.e. nothing that should change whilst refining the above mentioned. deraadt agrees OK afresh1
d59cfb74 2025-03-26 15:17:04 sync
cb34f31a 2025-03-25 14:46:03 sync tzdata update, ok millert
6cd306d8 2025-03-25 08:17:46 Update sets sizes.
49eea2f0 2025-03-13 10:44:36 minor libssl bump (SSL_OP_NO_RENEGOTIATION/SSL_OP_ALLOW_CLIENT_RENEGOTIATION) code #ifdef'ing these and compiled with new headers won't work as expected on earlier libraries minor libtls bump to match libssl bump ok tb@
8082ed69 2025-03-09 15:56:22 sync libressl bump Bump is over. It's now safe to build the tree again.
73a4cbfd 2025-03-08 17:13:28 sync
7fb34247 2025-03-08 16:39:25 sync
10fc8ac3 2025-03-01 19:44:07 move to 7.7-beta
11d817a3 2025-02-22 16:18:27 sync
e6bf4359 2025-02-21 18:17:06 sync; curses pkg-config files
6d042f2b 2025-02-21 15:37:25 install.md runs too early for dmesg.boot to be available, use plain dmesg(1) Should have been in r1.63 "With ACPI >= 5, assume UEFI and default to GPT", otherwise an early grep ENOENT error shows and default detection fails. Reminded by kevlo, thanks.
46a4264a 2025-02-19 21:36:02 Use installboot -c in the installer such that a freshly installed or upgraded system will boot from the disk we installed on. ok deraadt@, kn@
c641a2ae 2025-02-18 21:03:41 media is still not big enough
af99e056 2025-02-16 11:27:23 sync
e245266b 2025-02-14 19:38:59 sync
e9994d6d 2025-02-14 08:08:05 With ACPI >= 5, assume UEFI and default to GPT Add another criteria besides efifb(4) attaching to determine whether the installer booted in UEFI mode and not stick with MBR in such cases. This at least avoids "An EFI/GPT disk may not boot. Proceed?" on some boxes. With deraadt kettenis beck
bd8a446d 2025-02-08 01:11:55 rework "Default IPv6 router?" to behave like the rest The only interactive question backed by ksh(1)'s select has a few drawbacks: no ! or ? support, no record in the response file and unexpected behaviour. Switch to ask_until() like 'Default IPv4 route?' and 'Access Point?' to fix all this; now one can drop into a shell without restarting an install to follow route(8)'s last EXAMPLE. florian likes it OK afresh1
c25c3844 2025-02-07 17:25:50 grow size of media
6b588656 2025-02-05 14:12:26 sort
f5b0dd38 2025-01-30 18:20:35 sync
a986de27 2025-01-28 01:17:03 Sync for perl 5.40.1
ce222dd0 2025-01-17 00:20:15 Finally include ARIN's RPKI Trust Anchor Locator Backstory: We strive to provide a source distribution that can be freely used, copied, modified, and redistributed by anyone and for any purpose. Unfortunately, up until now, several legal barriers stopped us from distributing the ARIN TAL. The main legal obstacles stemmed from the terms and conditions in the Relying Party Agreement (RPA) governing access to ARIN's RPKI repository and the way ARIN tried to ensure that agreement was binding. Originally, ARIN used a cumbersome email-based method of RPA acceptance. Then in 2016, ARIN moved to a browser user interface-based "clickwrap" method via their website, requiring affirmative assent via a mouse-click. In 2019, a new approach was offered where ARIN encouraged software distributors to pass through restrictive terms in irksome pop-ups during installation; this we also deemed unworkable. In 2022, this "Redistributor RPA" was subsumed in a single RPA, but without material change to the mechanics, and the terms remained a showstopper. Over the years various people suggested ARIN to adopt an "AS IS" disclaimer of warranties. In 2024, Job Snijders authored a modified version of the BSD license and proposed ARIN to include it in the optional comment section in the TAL file format. In 2025 ARIN updated its TAL to include this disclaimer. After more than a decade of iterations, this public key now is available to the public in an unencumbered fashion and can serve its main purpose, a purpose that can only occur through immensely widespread distribution. Some pointers for historic context: 2012 - https://web.archive.org/web/20130127143807/https://www.arin.net/resources/rpki/rpa.pdf 2015 - https://web.archive.org/web/20150203184532/https://www.arin.net/public/rpki/tal/index.xhtml 2017 - https://lists.arin.net/pipermail/arin-ppml/2017-January/031231.html 2017 - https://www.arin.net/vault/about/welcome/board/meetings/20170405/exhibit_d.pdf 2018 - https://mailman.nanog.org/pipermail/nanog/2018-September/097161.html 2019 - https://papers.ssrn.com/sol3/Papers.cfm?abstract_id=3308619 2019 - https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/yoo_rpki.pdf 2019 - https://www.arin.net/vault/announcements/20191021/ 2019 - https://www.theregister.com/2019/10/28/arin_rpki_open_source/ 2022 - https://www.arin.net/vault/announcements/20220926/ 2022 - https://www.arin.net/vault/announcements/20220929/ 2025 - https://www.arin.net/announcements/20250116-tal/ OK tb@ claudio@ deraadt@
01d58854 2024-12-30 23:13:16 sync
c75bffb0 2024-12-25 01:40:45 sync
cd549125 2024-12-23 11:10:28 sync
58f37af4 2024-12-19 23:57:27 sync
7502f200 2024-12-18 14:09:18 add libutil, missed with fsck_ext2fs commit (oops, I didn't realise it was used in ramdisks). reported/ok tb@
2d9a425e 2024-12-17 20:38:22 sync
395f60ac 2024-12-17 13:24:04 sync
18efafee 2024-12-16 23:27:58 sync
7777ed9e 2024-12-13 05:57:41 sync
b414cf9b 2024-12-10 08:41:46 sync
cead3da4 2024-12-09 12:49:15 sync
28676b80 2024-12-07 02:00:25 sync
484eec8f 2024-11-27 04:05:47 sync
5ad10c24 2024-11-26 14:01:03 sync, libutil major bump
b24f31a1 2024-11-23 15:42:58 sync
250b59b5 2024-11-21 13:47:22 sync libutil bump
2c998865 2024-11-20 06:54:17 sync
e202699e 2024-11-13 16:22:35 sync
81e7fdf6 2024-11-13 00:00:16 sync
db445f91 2024-11-11 03:58:26 sync with arm64.html
58b31cc3 2024-11-08 20:51:11 sync
255a35c3 2024-11-06 13:11:26 sync
8fcde362 2024-11-04 10:03:36 sync
ce166376 2024-10-16 18:47:47 a.out is no longer the commonly encountered binary file format, the world has moved to ELF. Move the a.out specific defines and macros, but the MID_xxx values, from <sys/exec.h> to <a.out.h>, and update the few userland binaries which really need these defines (i.e. boot-related tools for old architectures) to explicitly include <a.out.h> when needed. "Fine" deraadt@
a5ae96e3 2024-10-15 00:08:27 grow i386 media a bit
ece53d07 2024-10-14 02:45:44 sync
b3a69e4e 2024-09-28 17:09:52 catch up with the u-boot-aarch64 package split in install docs. changing the dtb isn't normally needed (and can cause problems) so don't suggest that. add some info for rk3588. partly from jsg.
32c9c526 2024-09-18 14:29:10 move common lines to mi
3715dbf7 2024-09-17 10:19:54 update install.md path
04695d73 2024-09-17 10:13:50 update list file paths
b2a5716b 2024-09-06 04:11:26 sync
a335b1f4 2024-09-03 15:28:58 sync
f4b86c04 2024-09-02 16:39:03 sync
84b38932 2024-09-02 08:05:18 sync
a4f38ae6 2024-09-02 07:58:05 sync
3b38da78 2024-08-31 10:55:42 sync libressl bump
987f106c 2024-08-31 10:45:37 sync
976eccd8 2024-08-31 09:29:32 sync
f0c9a4eb 2024-08-31 09:07:25 sync
ad08c004 2024-08-29 20:26:08 sync
f91d77c0 2024-08-24 09:16:12 sync
6b4f6e93 2024-08-24 09:08:38 sync
0ead25fe 2024-08-23 23:45:34 sync
e0187c52 2024-08-17 09:17:27 sync
96b324b9 2024-08-16 16:57:02 sync
e02236bf 2024-08-15 16:55:06 sync
3ee94cab 2024-08-15 14:43:28 sync
db6e2d4a 2024-08-14 15:34:39 mention apple machines needing activation after erase ok patrick@ kettenis@ krw@
91460ded 2024-08-14 10:50:20 miniroot now works with USB Type-A ports on Apple machines discussed with kettenis@ and confirmed on M1 Mac mini
302851d5 2024-08-12 21:04:46 sync libc, libssl and libtls bumps
83397631 2024-08-11 01:40:49 sync
d8baf6e2 2024-08-10 06:42:10 sync
d1e11f58 2024-08-09 04:40:09 Add OrangePi Zero2 (Allwinner H616). prompted by & ok jsg@
b6b65a68 2024-08-07 23:03:49 sync