On Wed, 11 Jun 2003, Axel Dörfler wrote:
> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
[...]
> > > > For file systems, I want to enforce the driver_settings format. I
> > > > don't
> > > > know if it makes sense to loosen that limit for the partition
> > > > modules,
> > > > but if you could come up with a good reason :-)
> > > > And that information would only be of interest for file systems,
> > > > so we
> > > > could just add it there. But we'll see - I still have to extend
> > > > the
> > > > current driver_settings implementation for this usage.
> > Since I will need it rather soon -- basically only the disk system
> > management in KDiskDeviceManager and the basic C functions exported
> > by the
> > disk manager are to be done, before I will start to port the intel
> > module
> > to the new interface -- I can do that, if you don't object.
>
> Hm... I could try to do that tomorrow, but if I don't find the time,
> feel free to do it.
I guess, I'll reach the point, where I need it (well, `need' is not
exactly correct, since it would be possible to leave the parameter stuff
out for scanning, but it would be nice to have it, for that part could be
completed then) Friday or on the weekend at the latest. So, if you haven't
done it till then, I'll just go ahead and implement it.
> But it should probably be moved from kernel/core to kernel/libroot/os/
> right?
It will be needed in both kernel- and userland, and unless I'm mistaken,
the kernel is not supposed to access libroot, is it? So, it has to be
compiled and linked into both, and, I think, it doesn't make much
difference where the sources are located, then.
> Maybe we want to wait with that move until we have our own repository,
> though, to not lose any changes information.
Have I missed something? Have the plans to move to an own server become
more concrete? I thought, it was agreed on leaving the repository at SF
for the time being, perhaps do mirror it at our site, and decide later on
whether or not to move it.
However, as SF provides a CVS tarball, we wouldn't lose any version info,
if we would move, anyway.
> OTOH there haven't been a lot. Also keep in mind that this file has to
> be used in the boot loader, too - though it would be okay to cut some
> of its functionality out.
> I also need to clean it up a bit, since the boot loader now has a Posix
> -like environment, the special open/read/write ops don't have to be
> used anymore.
Oh, nice.
[...]
CU, Ingo
