<?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[Annoying boot message on boot]]></title><description><![CDATA[<p dir="auto">Hello all!</p>
<p dir="auto">I got a really small yet annoying problem with my (embedded nanobsd) pfSense install,<br />
upon boot it asks for what image to boot:<br />
[1] FreeBSD<br />
[2] FreeBSD</p>
<p dir="auto">Thus pressing 'enter' and the box boots up just fine; however, as this is an embedded<br />
device, this requires me to serial up to the device on every single boot, just to do this<br />
one keypress.. as this message never times out, and thus just sits there until I do.</p>
<p dir="auto">If anyone could please point me in the right direction for where or what file this config option is located in,<br />
and this way I can give it a timeout, or just get it to boot option [1] by default, without requiring user interaction.</p>
<p dir="auto">Any help would be greatly appreciated!<br />
MeatPuppet</p>
]]></description><link>https://forum.netgate.com/topic/37897/annoying-boot-message-on-boot</link><generator>RSS for Node</generator><lastBuildDate>Sat, 10 Oct 2026 05:20:26 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/37897.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 02 Oct 2011 14:38:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Annoying boot message on boot on Mon, 03 Oct 2011 23:25:53 GMT]]></title><description><![CDATA[<p dir="auto">The settings under diag&gt;nanobsd all seem right, the correct partition is selected.. it all appears fine.</p>
<p dir="auto">It should noted this is an ancient CF install on a watchguard x700, being upgraded, modified, hacked,<br />
countless times over the years, there is no question about it, <em>this is no doubt my own fuckup somewhere.</em><br />
You know the drill, its buried in the rack, and its always just 'easier' to hack than fix. If it works (TM), and all that.</p>
<p dir="auto">The only reason the problem has come to my mind recently is an (<em>non IT gear related</em>, all RCCB) RCD issue that<br />
has caused some semi-infrequent, yet very annoying power drops (ups can only last that long, and cant<br />
afford diesel or independent power.. electrician has been called, its the 3rd time trying to find this @*!# fault).<br />
Thus I'm giving up; and making the network fully autonomous, so it can pull itself from cold-&gt;operational by itself.</p>
<p dir="auto">Nevermind, the <em>only</em> sensible approach to all this is to use this brilliant excuse to do what I've should have done<br />
some time ago; <em>do a clean install</em>, and perhaps use this opportunity to move my ass to pfSense 2.0..</p>
<p dir="auto">Thanks, your reply finally put some sense in me :)<br />
MeatPuppet</p>
]]></description><link>https://forum.netgate.com/post/298861</link><guid isPermaLink="true">https://forum.netgate.com/post/298861</guid><dc:creator><![CDATA[MeatPuppet]]></dc:creator><pubDate>Mon, 03 Oct 2011 23:25:53 GMT</pubDate></item><item><title><![CDATA[Reply to Annoying boot message on boot on Mon, 03 Oct 2011 05:05:46 GMT]]></title><description><![CDATA[<p dir="auto">It always boots the selected active partition (from Diag&gt;nanobsd if you want to see which that is or change it) by default, never heard of anyone having to touch anything there.</p>
]]></description><link>https://forum.netgate.com/post/298750</link><guid isPermaLink="true">https://forum.netgate.com/post/298750</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Mon, 03 Oct 2011 05:05:46 GMT</pubDate></item></channel></rss>