| #
1d6b6ea2
|
| 11-Sep-2025 |
Mark Johnston <markj@FreeBSD.org> |
release: Create /firstboot in common VM image creation code
Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboo
release: Create /firstboot in common VM image creation code
Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboot, which is unlinked after boot.
Individual cloudware types shouldn't be responsible for creating it. Do so in a centralized place. Aside from simplifying things, this ensures that we create a metalog entry for the firstboot file.
Reviewed by: cperciva, emaste MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D52450
show more ...
|
| #
e7a766f9
|
| 15-Aug-2025 |
Gleb Popov <arrowd@FreeBSD.org> |
release: Enable nuageinit for BASIC-CI images
Approved by: manu Differential Revision: https://reviews.freebsd.org/D51917
|
| #
c41ba997
|
| 12-Mar-2025 |
Brooks Davis <brooks@FreeBSD.org> |
release/vm: partially support NO_ROOT
For images that don't require QEMU, support NO_ROOT. This entails: - Passing NO_ROOT down to mk-vmimage.sh (which sets it for installworld, etc) - Handlin
release/vm: partially support NO_ROOT
For images that don't require QEMU, support NO_ROOT. This entails: - Passing NO_ROOT down to mk-vmimage.sh (which sets it for installworld, etc) - Handling etcupdate bootstrapping - Adding assorted config file METALOG entries - Running makefs in the right directory and adding -D for dups
The main gap in basic NO_ROOT support is package installation. Each image type must also be updated to add METALOG entries for any files it adds.
Reviewed by: emaste Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D49320
show more ...
|
| #
d0b2dbfa
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
| #
fa04db47
|
| 04-Mar-2021 |
Glen Barber <gjb@FreeBSD.org> |
release: fix VMSIZE following 1ca8842f3ad9
truncate(1) is not case-sensitive with regard to setting the size of a file. makefs(8), however, does not honor upper-case values. Update release-specific
release: fix VMSIZE following 1ca8842f3ad9
truncate(1) is not case-sensitive with regard to setting the size of a file. makefs(8), however, does not honor upper-case values. Update release-specific files and the release(7) manual page to reflect this.
MFC with: 1ca8842f3ad9 Submitted by: ehem_freebsd_m5p.com (original) Differential Review: https://reviews.freebsd.org/D28979 Sponsored by: Rubicon Communications, LLC ("Netgate")
show more ...
|
| #
ea070051
|
| 02-Nov-2020 |
Emmanuel Vadot <manu@FreeBSD.org> |
release: Add an image for CI
A lot of projects CI can't do FreeBSD tests currently. The main reason is that the project CI infrastructure is runned on Linux and that our images aren't modifiable fro
release: Add an image for CI
A lot of projects CI can't do FreeBSD tests currently. The main reason is that the project CI infrastructure is runned on Linux and that our images aren't modifiable from a Linux hosts. Add a basic image specific for this case (called BASIC-CI for a lack of a better name). The image have no package pre-installed. It only have a few modification to have dhcp client runned on the default interface and sshd started with option to be able to log on without a password as root.
Sponsored by: The FreeBSD Foundation
Reviewed by: re (gjb@) Differential Revision: https://reviews.freebsd.org/D25598
show more ...
|
| #
1d6b6ea2
|
| 11-Sep-2025 |
Mark Johnston <markj@FreeBSD.org> |
release: Create /firstboot in common VM image creation code
Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboo
release: Create /firstboot in common VM image creation code
Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboot, which is unlinked after boot.
Individual cloudware types shouldn't be responsible for creating it. Do so in a centralized place. Aside from simplifying things, this ensures that we create a metalog entry for the firstboot file.
Reviewed by: cperciva, emaste MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D52450
show more ...
|
| #
e7a766f9
|
| 15-Aug-2025 |
Gleb Popov <arrowd@FreeBSD.org> |
release: Enable nuageinit for BASIC-CI images
Approved by: manu Differential Revision: https://reviews.freebsd.org/D51917
|
| #
c41ba997
|
| 12-Mar-2025 |
Brooks Davis <brooks@FreeBSD.org> |
release/vm: partially support NO_ROOT
For images that don't require QEMU, support NO_ROOT. This entails: - Passing NO_ROOT down to mk-vmimage.sh (which sets it for installworld, etc) - Handlin
release/vm: partially support NO_ROOT
For images that don't require QEMU, support NO_ROOT. This entails: - Passing NO_ROOT down to mk-vmimage.sh (which sets it for installworld, etc) - Handling etcupdate bootstrapping - Adding assorted config file METALOG entries - Running makefs in the right directory and adding -D for dups
The main gap in basic NO_ROOT support is package installation. Each image type must also be updated to add METALOG entries for any files it adds.
Reviewed by: emaste Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D49320
show more ...
|
| #
d0b2dbfa
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
| #
fa04db47
|
| 04-Mar-2021 |
Glen Barber <gjb@FreeBSD.org> |
release: fix VMSIZE following 1ca8842f3ad9
truncate(1) is not case-sensitive with regard to setting the size of a file. makefs(8), however, does not honor upper-case values. Update release-specific
release: fix VMSIZE following 1ca8842f3ad9
truncate(1) is not case-sensitive with regard to setting the size of a file. makefs(8), however, does not honor upper-case values. Update release-specific files and the release(7) manual page to reflect this.
MFC with: 1ca8842f3ad9 Submitted by: ehem_freebsd_m5p.com (original) Differential Review: https://reviews.freebsd.org/D28979 Sponsored by: Rubicon Communications, LLC ("Netgate")
show more ...
|
| #
ea070051
|
| 02-Nov-2020 |
Emmanuel Vadot <manu@FreeBSD.org> |
release: Add an image for CI
A lot of projects CI can't do FreeBSD tests currently. The main reason is that the project CI infrastructure is runned on Linux and that our images aren't modifiable fro
release: Add an image for CI
A lot of projects CI can't do FreeBSD tests currently. The main reason is that the project CI infrastructure is runned on Linux and that our images aren't modifiable from a Linux hosts. Add a basic image specific for this case (called BASIC-CI for a lack of a better name). The image have no package pre-installed. It only have a few modification to have dhcp client runned on the default interface and sshd started with option to be able to log on without a password as root.
Sponsored by: The FreeBSD Foundation
Reviewed by: re (gjb@) Differential Revision: https://reviews.freebsd.org/D25598
show more ...
|
| #
1d6b6ea2
|
| 11-Sep-2025 |
Mark Johnston <markj@FreeBSD.org> |
release: Create /firstboot in common VM image creation code
Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboo
release: Create /firstboot in common VM image creation code
Some services, such as growfs, only run upon the first boot of an image. The first boot is indicated by the presence of the file /firstboot, which is unlinked after boot.
Individual cloudware types shouldn't be responsible for creating it. Do so in a centralized place. Aside from simplifying things, this ensures that we create a metalog entry for the firstboot file.
Reviewed by: cperciva, emaste MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D52450
show more ...
|
| #
e7a766f9
|
| 15-Aug-2025 |
Gleb Popov <arrowd@FreeBSD.org> |
release: Enable nuageinit for BASIC-CI images
Approved by: manu Differential Revision: https://reviews.freebsd.org/D51917
|
| #
c41ba997
|
| 12-Mar-2025 |
Brooks Davis <brooks@FreeBSD.org> |
release/vm: partially support NO_ROOT
For images that don't require QEMU, support NO_ROOT. This entails: - Passing NO_ROOT down to mk-vmimage.sh (which sets it for installworld, etc) - Handlin
release/vm: partially support NO_ROOT
For images that don't require QEMU, support NO_ROOT. This entails: - Passing NO_ROOT down to mk-vmimage.sh (which sets it for installworld, etc) - Handling etcupdate bootstrapping - Adding assorted config file METALOG entries - Running makefs in the right directory and adding -D for dups
The main gap in basic NO_ROOT support is package installation. Each image type must also be updated to add METALOG entries for any files it adds.
Reviewed by: emaste Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D49320
show more ...
|
| #
d0b2dbfa
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
| #
fa04db47
|
| 04-Mar-2021 |
Glen Barber <gjb@FreeBSD.org> |
release: fix VMSIZE following 1ca8842f3ad9
truncate(1) is not case-sensitive with regard to setting the size of a file. makefs(8), however, does not honor upper-case values. Update release-specific
release: fix VMSIZE following 1ca8842f3ad9
truncate(1) is not case-sensitive with regard to setting the size of a file. makefs(8), however, does not honor upper-case values. Update release-specific files and the release(7) manual page to reflect this.
MFC with: 1ca8842f3ad9 Submitted by: ehem_freebsd_m5p.com (original) Differential Review: https://reviews.freebsd.org/D28979 Sponsored by: Rubicon Communications, LLC ("Netgate")
show more ...
|
| #
ea070051
|
| 02-Nov-2020 |
Emmanuel Vadot <manu@FreeBSD.org> |
release: Add an image for CI
A lot of projects CI can't do FreeBSD tests currently. The main reason is that the project CI infrastructure is runned on Linux and that our images aren't modifiable fro
release: Add an image for CI
A lot of projects CI can't do FreeBSD tests currently. The main reason is that the project CI infrastructure is runned on Linux and that our images aren't modifiable from a Linux hosts. Add a basic image specific for this case (called BASIC-CI for a lack of a better name). The image have no package pre-installed. It only have a few modification to have dhcp client runned on the default interface and sshd started with option to be able to log on without a password as root.
Sponsored by: The FreeBSD Foundation
Reviewed by: re (gjb@) Differential Revision: https://reviews.freebsd.org/D25598
show more ...
|