Linked by Thom Holwerda on Sun 10th Sep 2006 20:38 UTC, submitted by fudel
Zeta Magnussoft, the company now responsible for development on Zeta, has announced it is accepting pre-orders for Zeta 1.21. This new release will include multi-user support, will be built with GCC4, among other improvements. Bernd Korz's weblog contains more information. Korz was (is?) the CEO of YellowTAB, the company that started Zeta. Read on for a short editorial on this announcement.
Thread beginning with comment 161311
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: multi user???
by memson on Mon 11th Sep 2006 14:31 UTC in reply to "RE[5]: multi user???"
memson
Member since:
2006-01-01

Vanders, BeOS doesn't use versioned Shared Objects for System libs. This then kills your entire point. BeOS != LINUX.

JT is right on this one. Listen to him.

To include the entire API again would needlessly expand the entire install base. If you are breaking binary compatibility, it should be all or nothing IMO. (Isn't that what Syllable dod to the original libAtheos.so?) You then have issues like linking drivers to the Kernel, input filters to the input server, various bits and pieces to the App server. That's just the tip of the iceberg.

I've looked at writing a thunking layer for BeOS to allow GCC 3.x to be used in plain R5.03. Way, way too much work.

Reply Parent Score: 1

RE[7]: multi user???
by fyysik on Mon 11th Sep 2006 15:02 in reply to "RE[6]: multi user???"
fyysik Member since:
2006-02-19

as far as i know from "first hands" for YT 1.2 were plans (and probably working version) to full support of Be API with GCC 4.*, while basically OS itself was built with 2.9*. So they planned to support both ABIs for transitional version but in "opposite" way.

Reply Parent Score: 1

RE[7]: multi user???
by Vanders on Mon 11th Sep 2006 15:24 in reply to "RE[6]: multi user???"
Vanders Member since:
2005-07-06

Fair enough. It was my understanding that BeOS/Zeta/Haiku used ELF and GCC as a system compiler. Following a symbolic link at compile time is a job for ld, and I'm going to ass-u-me that BeOS/Zeta/Haiku also use GNU binutils, yes?

Can the BeOS/Zeta/Haiku RTLD seriously not tell the difference between the filenames "libfoo.so.1" and "libfoo.so.2" in the DT_NEEDED section? Does it ignore the second part of the filename?

Even if it can't do that, it doesn't really change my point though, just the mechanism. Instead of libfoo.so.1 and libfoo.so.2 you could have libfoo.so and libfoo_2.so if you so wished; they are distinct libraries. Provided you do not try to mix GCC 2.95 and GCC 4 libraries together it should work.

This is exactly how we handle ABI changes in libsyllable. Whenever the ABI changes we increment the DSO version and ship the previous versions for compatability. So an installed system may have libsyllable.so.5, libsyllable.so.6 and libsyllable.so.7 installed. The only time this couldn't be done sensibly was when we upgraded to Glibc 2.3, which involved much deeper voodoo and it was easier to drop the old libraries.

Reply Parent Score: 1