[haiku-development] Re: Busted!
- From: "Michael Lotz" <mmlr@xxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 24 May 2009 15:18:58 +0200
On Sun, 24 May 2009 13:47:15 +0200, Stephan Assmus wrote
> On 2009-05-24 at 12:14:32 [+0200], Rob Judd <haiqu@xxxxxxxxxx> wrote:
> > I'd expect to need to develop on another platform via a network
> > connection if this were 2003, but the OS has been capable of
> > self-building for over a year. I think it's time some developers got OFF
> > Linux and actually used Haiku as a daily system. I'm fairly sure the bugs
> > would suddenly become apparent.
>
> I AM developing in Haiku, since months!
And Stephan's certainly not the only one. I'm developing on Haiku since almost
a year now. It's my main and indeed only platform. I very rarely revert to
BeOS for one thing or another (like once every few months) and I have one
Windows installation for a very specific task (I'm working on getting it done
on Haiku as well so I can remove that installation as well).
> > Besides, running on Linux isn't viable; I'm developing kernel drivers.
The way you could do this the easiest would be to embed your driver into your
local Haiku tree and add it to your image. Then you could just build the
network boot image and boot right off it. This provides a great turn around
time.
> > The crash I reported earlier isn't related to r30825 at all, I just went
> > right back to r30782 ans tried a clean build (totally deleting
> > generated/objects) and I'm still getting problems with `copyattr`
> > throwing an exception and shutting down the build. This raises two issues:
> >
> > 1. Why can no-one else verify this yet?
Most probably because you have something very specific in your setup that
noone else has. This might be a certain piece of hardware (with a faulty Haiku
driver) or a certain configuration of the system.
The most helpful would of course be if you could track down why this happens
in your case. It's very hard for someone else to debug the issues you mention
without being able to reproduce them.
Since you seem to run into BFS corruption so reliably, could you provide some
info on how you set it up? BFS block size and the partition size you are
using, how full your filesystem usually is. Maybe it is more likely to happen
with that specific combination you are using.
Regards
Michael
Other related posts:
