Re: [Trion-kernel-dev] Due to popular demand (?), Trion now has a wiki

[Jeff W. <jw...@ne...>]

> Before disk access really makes sense, the kernel must have reached a
> certain level of maturity. Once we've reached that point, I'll be totally
> unbiased which filesystem we're going to support first. The only thing
> that does matter, is that we start with a generic filesystem that is also
> supported by Linux/Windows (fat12 | ext2 | ISO). By implementing an
> incompatible standard as the very first filesystem in our kernel (Reiser |
> JeffFS | SFS), we would lose the possibility of data-exchange with other
> operating-systems. Something as simple as copying config files to our
> trion disk would be a mayor pain, as it'd require us to first write a
> Windows/Linux driver just to access the partition. Apart from that I also
> think that it will be much easier to debug/profile a custom file-system if
> we already have a "safe" ext12 partition that can be used to store
> debugging or performance data.

I agree completely.  I think it'll be much easier to develop a known, 
generally supported FS first.

> I386TaskManager.cpp is part of old source branch that probably hasn't been
> updated in years. All the recent work was moved to another module ("trion
> v0.2"). Also note that Sourceforge changed some details of its CVS system
> a couple of month ago. Logging-in using SSH now requires you to use
> ":ssh:[user-name]@trion.cvs.sourceforge.net:/cvsroot/trion" as your path.

Aye!  I totally forgot about the new module!  I've now synched it up.  And 
yes, I'd already updated to the new sourceforge settings.

> Unlike the old source branch the new release doesn't (yet?) use
> autconf/automake or even a handwritten config-file. There's thus also no
> need to configure anything, as the makefile will automatically use an
> appropriate toolchain. To check if the toolchain is installed properly,
> you may just type "i686-elf-gcc" - if the command isn't recognized, you'll
> have to download and install the toolchain package from the project site
> (sourceforge.net/project/showfiles.php?group_id=90198&package_id=109649).
> Note that there's no need to update the toolchain as the binaries are
> actually still the same as in the old release. As they still do their job,
> a new build just doesn't seem to be a top-priority for the moment.

It would be nice if we could use a localized toolchain... for example, if I 
have my sources in ~/osdev/trion v0.2/... I'd like to have my toolchain in 
~/osdev/trion v0.2/toolchain.

My reasoning being that this is a cross-compiler specifically for trion, and 
I'd therefore like to keep in contained within the trion tree.  I don't see a 
use for installing it overtop of my existing filesystem (aka /).

Stephen, does this sound doable?  Obviously I can add in the directories into 
the path, but does GCC make any assumptions about where to find files?

Cheers,
Jeff