[openbeos] Re: binary middle ground
- From: Zenja Solaja <solaja@xxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Thu, 13 Sep 2001 12:31:07 +1000
Isn't that tying one FS implementation into the kernel? What happens if down
the road you decide to primarily support XFS, or a 128bit filesystem. For
this specific reason the FS is an addon (with its accompanying module), not
embedded into the kernel. Remember, BeOS isn't as monolithic as
Linux/Windows. Fixing/changing an addon is much easier when it isn't tied
to the kernel. Again, all of this is in the BeBook.
> -----Original Message-----
> From: Michael Phipps [SMTP:mphipps1@xxxxxxxxxxxxxxxx]
> Sent: Thursday, September 13, 2001 1:33 AM
> To: openbeos@xxxxxxxxxxxxx
> Subject: [openbeos] Re: binary middle ground
>
>
> OH - I had a thought.
> (and maybe Manuel can confirm if this is true or not)
> What if the boot loader was statically linked with BeFS?
> It could load the kernel, et all into memory, then turn control over.
>
>
> >> It's true that the kernel needs enough knowledge of the layout to load
> the
> >bfs
> >
> >That's incorrect. The kernel knows *nothing* about the BFS layout.
> >
> >> driver. Btw we don't have many choices here. Either we use static
> drivers,
> >then
> >> we don't have problems, but we have to rebuild the kernel, either we
> use
> >> dynamicaly loaded drivers (which is more in use these days, just look
> at
> >> Linux), but we need a minimal static bfs driver anyway. Linux's
> approach
> >is a
> >> bit different, since it uses modules (= dynamicaly loaded drivers), but
> >also
> >> static drivers, for ones that are needed at boot-time (like ext2fs).
> This
> >is
> >
> >The only statically linked "drivers" in BeOS kernel are: rootfs, pipefs,
> >devfs,
> >/dev/zero/, /dev/null, /dev/dprintf and a couple of modules. All other
> stuff
> >including BFS & IDE are dinamically linked at boot time.
> >
> >
> >manuel.,
>
>
>
>
----------------------
CONFIDENTIALITY NOTICE
----------------------
This email is intended only to be read or used by the addressee.
The information contained in this e-mail message may be confidential
information. If you are not the intended recipient, any use, interference
with, distribution, disclosure or copying of this material is unauthorised
and prohibited. Confidentiality attached to this communication is not waived
or lost by reason of the mistaken delivery to you.
If you have received this message in error, please delete it and notify us
by return e-mail or telephone Aristocrat Technologies Australia Pty Limited
on +61 2 9413 6300.
Other related posts:
