<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in startbsdinstall</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>66be6053 - bsdinstall: rename &quot;Live CD&quot; to &quot;Live System&quot;</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall#66be6053</link>
        <description>bsdinstall: rename &quot;Live CD&quot; to &quot;Live System&quot;This uses more generic wording in the FreeBSD installer, when offeringthe user to use the system booted without running the installer.The updated wording is also reflected in freebsd-version(1).Reviewed by:		emasteSponsored by:		The FreeBSD FoundationDifferential revision:	https://reviews.freebsd.org/D43233(cherry picked from commit 19bb1886be4f366e922f0be359874683a243624a)

            List of files:
            /freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall</description>
        <pubDate>Fri, 29 Dec 2023 18:23:48 +0000</pubDate>
        <dc:creator>Pierre Pronchery &lt;pierre@freebsdfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>a4504856 - bsdinstall: Fix race condition when shutting down after installation</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall#a4504856</link>
        <description>bsdinstall: Fix race condition when shutting down after installationWhilst reboot(8) will block whilst it runs, shutdown(8) does not,daemonizing instead. This means that we must wait after running it,otherwise we will exit and cause the system to attempt to go multi-userin parallel with the shutdown daemon killing init. With the newmulti-console support in the installer, runconsoles will immediatelykill this daemon, racing with the daemon being able to signal init asdesired, and I have seen this race be lost in QEMU with a single CPU. Inthe past this wasn&apos;t such an issue, since shutdown&apos;s daemon puts itselfin a new session group immediately after fork (and the parent doesn&apos;twait until that has happened, so whilst there&apos;s technically a racecondition in there where it could receive a SIGHUP from the death of theparent&apos;s session leader, in practice this is very unlikely to be hit.This means that the only consequence of this oversight before was thatyou might get the beginnings of more console output on the way tomulti-user and thus the console would look a little confusing.Reviewed by:	gjbFixes:		e4505364c087 (&quot;release/rc.local: Provide option to shutdown after installation complete&quot;)Fixes:		a09af1b7fd95 (&quot;bsdinstall release: Start installer on multiple consoles&quot;)Differential Revision:	https://reviews.freebsd.org/D36879

            List of files:
            /freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall</description>
        <pubDate>Thu, 06 Oct 2022 19:04:04 +0000</pubDate>
        <dc:creator>Jessica Clarke &lt;jrtc27@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>a09af1b7 - bsdinstall release: Start installer on multiple consoles</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall#a09af1b7</link>
        <description>bsdinstall release: Start installer on multiple consolesCurrently the installer is only started on the primary (&quot;high level&quot;)console. For systems where this is the video console and serial consolesaren&apos;t of interest, and headless systems with just a serial console,this works just fine, but for systems where both video and serialconsoles are present and meaningful this requires the user to select theright primary console in loader, with the poor user experience of thesystem appearing to hang if they leave the wrong one selected. Thisnotably differs from our multi-user behaviour of spawning getty on everyconsole, where the only issue with selecting the wrong primary consoleis a quieter boot process until the login prompt appears (or the systemcrashes).Instead, use the newly-added runconsoles helper to run the installer onevery console (except for ttyv*, where only ttyv0 will be used). Forinteractive installations, any of the consoles can be used, though onlyone should be used at a time as no effort is made to avoid multipleinstallations running at the same time clobbering each other. If theLive CD option is selected, the other installers (which should, if theuser is well-behaved, be sitting at the welcome screen) will be killed.If an automated install is in use, the primary console will be used todisplay its output, and the others will direct the user to the primaryconsole.Reviewed by:	brooks, gjbDifferential Revision:	https://reviews.freebsd.org/D36805

            List of files:
            /freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall</description>
        <pubDate>Mon, 03 Oct 2022 16:09:17 +0000</pubDate>
        <dc:creator>Jessica Clarke &lt;jrtc27@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d577d617 - bsdinstall release: Move code to a new startbsdinstall wrapper</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall#d577d617</link>
        <description>bsdinstall release: Move code to a new startbsdinstall wrapperThis separates out the install media-specific environment (creatingbsdinstall_etc) from actually running the installer on a given console.This will be used by a future change to start the installer on multipleconsoles.Reviewed by:	brooks, gjbDifferential Revision:	https://reviews.freebsd.org/D36803

            List of files:
            /freebsd-14.2/usr.sbin/bsdinstall/startbsdinstall</description>
        <pubDate>Mon, 03 Oct 2022 16:09:16 +0000</pubDate>
        <dc:creator>Jessica Clarke &lt;jrtc27@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
