DragonFly boot2 - moved out of commits thread
wbh at conducive.org
Fri Mar 6 12:51:05 PST 2009
a0bdb4ab.squirrel at www.shiningsilence.com>
In-Reply-To: <c07dc815d7eeec7f50d216f5a0bdb4ab.squirrel at www.shiningsilence.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Message-ID: <49b18cb9$0$882$415eb37d at crater_reader.dragonflybsd.org>
X-Trace: 1236372667 crater_reader.dragonflybsd.org 882 188.8.131.52
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:13538
Justin C. Sherrill wrote:
> On Fri, March 6, 2009 1:42 pm, Oliver Fromme wrote:
>> In theory, the Forth code could leave the graphics screen
>> enabled. It's just a matter of removing one command from
>> beastie.4th. Then splash(4) should follow on seamlessly,
>> if it's configured to display the same image, which is
>> a decision to be made by the user, of course.
>> I haven't tried to do that myself, though.
> I read that and immediately thought "two-frame boot animation!". It could
> be very entertaining.
Given how little code is needed to X-Y 'drift' a small D.Mon around on a
black background, two panes should be enough to make a DragonFly appear
to move its wings..
. . or perhaps the creative could even 'cluster' a mating pair...
and if we ever import ZFS, watch the eggs hatch....
More information about the Kernel