
|
[openbeos]
||
[Date Prev]
[04-2004 Date Index]
[Date Next]
||
[Thread Prev]
[04-2004 Thread Index]
[Thread Next]
[openbeos] Re: x86 boot loader milestone
- From: Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 21 Apr 2004 14:32:25 -0400
On 2004-04-21 at 12:21:10 [-0400], Axel Dörfler wrote:
> > Would it be a long, hard process to get jam to make such a BFS image for
> > testing purposes? That would be great.
>
> Depends. Of course, we want to have an automated build, but it's probably not
> possible to build an image file containing an OpenBeOS installation that you
> could use right away with Bochs - the BeOS cache doesn't allow this to work
> reliably, unfortunately.
>
> However, it will be possible to install OpenBeOS on a mounted volume using
> Jam. That one you can use directly to boot from, but again, you won't be able
> to use it in Bochs until a reboot due to the BeOS cache. There is not much we
> can do about it.
So /bin/sync doesn't fully flush the cache?
> Basically, I understand "beta" to be feature complete, "alpha" to be a work
> in progress. Actually, I wanted to switch to "alpha" as soon as we have hard
> drive access. It's hard to estimate the status of the kernel given those
> levels. Some parts are 100% done, others are 100% missing, many are somewhere
> in between :)
> And testing is actually something that is a lot of effort as well.
I have to agree with you here. I wouldn't call a kernel that we can't boot from
BFS to be alpha yet.
Michael
|

|