DragonFlyBSD

By the way, what's the difference between machine and machine_arch?

Petr

:By the way, what's the difference between machine and machine_arch?
:
:Petr

When I first separated the nameing scheme out it seemed to work fine,
    but then we started to hit snags with third party applications getting
    confused.  MACHINE and MACHINE_ARCH (and uname) were very badly designed
    and the fact that both returned the same string 'i386' in many cases
    made it worse.  So many applications use the two interchangably now that
    we have no choice but to follow a scheme that returns the same results
    as other unixes.

Due to all of these problems I reverted the naming scheme before our
    most recent release.  Our build system still uses a 'platform'
    abstraction with its own naming scheme, but if you look at the files in
    /usr/src/sys/config/ you will notice that we have three naming directives
    now instead of two.  e.g.:

platform        vkernel         # platform architecture (i386, vkernel, etc)
    machine         i386
    machine_arch    i386            # cpu architecture (i386, etc)

If you were to ask me what the difference is between machine and
    machine_arch... oh wait, you DID ask what the difference was!  Well,
    I don't think any answer I give would make much sense.

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>

'Hysterical raisins' properly fits the bill imho :).

Cheers,
--
Thomas E. Spanjaard
tgen@netphreax.net

So we are keeping both machine and machine_arch due to compatibility
reasons so that 3rd party apps dont get confused by pc32, is that so?

Offtopic:
I didnt wanna start another thread, so i shall just ask now (i asked
this before but got no answer), how do i switch between 1:1 and M:1? Is
there an easy way to try the new beast without screwing up much with my
system?

Cheers,
Petr

:Matthew Dillon wrote:
:> If you were to ask me what the difference is between machine and
:> machine_arch... oh wait, you DID ask what the difference was! Well,
:> I don't think any answer I give would make much sense.
:>
:> -Matt
:> Matthew Dillon
:> <dillon@backplane.com>
:>
:>
:So we are keeping both machine and machine_arch due to compatibility
:reasons so that 3rd party apps dont get confused by pc32, is that so?
:
:Offtopic:
:I didnt wanna start another thread, so i shall just ask now (i asked
:this before but got no answer), how do i switch between 1:1 and M:1? Is
:there an easy way to try the new beast without screwing up much with my
:system?
:
:Cheers,
:Petr

libthread_xu is the basis for 1:1 threading.  libc_r will remain the
    basis for M:1 threading.

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>

:So we are keeping both machine and machine_arch due to compatibility
:reasons so that 3rd party apps dont get confused by pc32, is that so?

Right.

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>

Well, what I was wondering though is how do I switch app X to use
libthread_xu?

Thanks
Petr

nothing. libthread_xu still needs a little bit of work and switching the threading lib has to be implemented.

cheers
simon