<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FOG 1.6.0-RC-19 Available]]></title><description><![CDATA[<p dir="auto">The nineteenth release candidate for FOG 1.6.0 is available on the <code>rc-1.6.0</code> branch. It reports version <code>1.6.0-RC-19</code>.</p>
<p dir="auto">Test it on a lab or non-production server first. The upgrade from 1.5 to 1.6 is one-way: it changes the database schema, and there is no down-migration.</p>
<p dir="auto"><strong>Changed since RC-18</strong></p>
<ul>
<li><strong>Service restarts no longer flood <code>servicemaster.log</code> with PHP warnings (#1994, #1996).</strong> A service’s supervisor closes its database connection before it starts each worker. Its next log line could read a setting on that closed connection, which wrote “Trying to access array offset on false” at <code>FOGBase.php</code> lines 3747 and 3752. The supervisor now reopens the connection before it logs. A failed settings read no longer warns, and it no longer empties the settings cache.</li>
<li><strong>SSH: no more “Undefined array key “_link”” warning, and no fatal after a failed connect (#1997, #1999).</strong> <code>FOGSSH::disconnect()</code> unset its connection, so the next use of the shared SSH object warned. A disconnect with no live session also threw a <code>TypeError</code> on PHP 8.</li>
<li><strong>User export imports back (#1987, #1993).</strong> A user row with no password gets a random password and a warning to set one. A password hash is stored as-is, and a typed password is hashed. A new permission, <code>user.export</code>, adds “Include password hashes” to the user export page. It is denied by default, and each hash export writes an audit row.</li>
<li><strong>The installer warns about <code>no_root_squash</code> only on the <code>&lt;share&gt;/dev</code> export (#1988, #1990).</strong> An unrelated export, such as an ISO share, no longer raises the warning. Thanks to sgennadi, who reported it and proposed the fix.</li>
</ul>
<p dir="auto"><strong>FOS (kernel and init), from the Latest FOS release</strong></p>
<p dir="auto">An RC install or update downloads the Latest FOS release. Latest is still <code>EXP_20261027-181357</code>, unchanged since RC-18:</p>
<ul>
<li>Kernel 6.18.59, the current 6.18 LTS release.</li>
<li>FOS verifies TLS, which is the client half of #1978.</li>
<li>The Performance Test task.</li>
<li><strong>x64 and x86 boot an initramfs, not an ext2 initrd (FOGProject/fos#75).</strong> The file names stay <code>init.xz</code> and <code>init_32.xz</code>, and the boot menu does not change. <code>/tmp</code> is now a real RAM disk with a size limit: FOG_KERNEL_RAMDISK_SIZE sets the size, kept between 64 MB and half of the client’s memory.
<ul>
<li><strong>Warning: a customized init can no longer be loop-mounted.</strong> Add your files as an overlay cpio appended to <code>init.xz</code> instead: <a href="https://docs.fogproject.org/en/latest/kb/how-tos/customize-the-fos-init/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.fogproject.org/en/latest/kb/how-tos/customize-the-fos-init/</a> . A post-init script needs no rebuild at all: <a href="https://docs.fogproject.org/en/latest/kb/how-tos/post-init-scripts/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.fogproject.org/en/latest/kb/how-tos/post-init-scripts/</a></li>
<li>If a client fails to boot with this init, go to FOG Configuration &gt; Initrd Update and install the init from <code>EXP_20261027-155909</code>, the last ext2 init. Then report it on FOGProject/fos#75.</li>
</ul>
</li>
</ul>
<p dir="auto">API documentation: <a href="https://docs.fogproject.org/en/latest/1.6/kb/integrations/api" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.fogproject.org/en/latest/1.6/kb/integrations/api</a></p>
<p dir="auto"><strong>Before you upgrade</strong></p>
<ul>
<li>Back up your database and <code>/opt/fog/.fogsettings</code>.</li>
<li>Read the release notes: <a href="https://github.com/FOGProject/fogproject/blob/rc-1.6.0/docs/release/1.6.0-release-notes.md" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fogproject/blob/rc-1.6.0/docs/release/1.6.0-release-notes.md</a></li>
<li>1.6 removes Display Manager, Directory Cleaner, User Cleanup, Client Updater, Green FOG and the persistentgroups plugin. Their data is dropped. The site and accesscontrol plugins move into core.</li>
<li>PHP 7.4 or later is required. Plugins built for 1.5 do not load.</li>
</ul>
<p dir="auto"><strong>Install or update (as root)</strong></p>
<ul>
<li>A 1.6 beta or RC server: run <code>bin/updatefog.sh --channel rc</code> from your FOG checkout.</li>
<li>A 1.5 server installed from git: update to the current 1.5 stable, then run <code>bin/updatefog.sh --channel rc</code> from the checkout.</li>
<li>A new server, or a 1.5 server installed from a tarball:<br />
<code>curl -fsSL https://raw.githubusercontent.com/FOGProject/fogproject/working-1.6/bin/bootstrap.sh | bash -s -- --channel rc</code></li>
</ul>
<p dir="auto"><strong>Report problems</strong></p>
<p dir="auto">Open an issue at <a href="https://github.com/FOGProject/fogproject/issues" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fogproject/issues</a>. Include your FOG version, your OS, and the installer log from <code>bin/error_logs/</code>. Report a security problem through “Report a vulnerability” on the same repository, not in a public issue.</p>
]]></description><link>http://forums.fogproject.org/topic/18294/fog-1-6-0-rc-19-available</link><generator>RSS for Node</generator><lastBuildDate>Wed, 28 Oct 2026 17:01:05 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18294.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 Oct 2026 14:33:04 GMT</pubDate><ttl>60</ttl></channel></rss>