[openbeos] Issues
- From: "Daniel Reinhold" <danielr@xxxxxxxxxxxxx>
- To: "OpenBeOS mailing list" <openbeos@xxxxxxxxxxxxx>
- Date: Sun, 14 Oct 2001 18:37:55 CDT
Hey all...
John Gabriele has been working on an updated FAQ for the website. He
came up with a few "issues" that I don't have a definitive answer for.
So I'm going to post them here and see is anyone else has some good
answers.
* What is the "sockets-as-files" issue?
I think this is another way of saying will OpenBeOS support true
Berkeley sockets? Ok, net guys, are we? Can we support this and still
retain source compatibillity for R5 net programs?
* What is the "memcpy" issue?
Dunno, you got me! I've never even heard of this one. What's up with
memcpy?
* What is the issue with BONE and the Printing Kit?
Well, I know that the BONE beta that's been floating around screws up
printing somewhat (well, I've read as much on BeGroovy threads). But
probably a better way to ask this is "Will OpenBeOS support BONE?" Now
BONE itself is an upgrade to the R5 kernel. AFAIK, our net guys intend
to keep networking in userland. This is correct, no? However, they
could design it so that it provides BONE-like services. Are there any
plans for this? (this relates to the sockets question above)
* What happens when www.be.com is no longer available?
Actually, I don't think this will happen for awhile -- a year or more,
to take a wild guess. Still, something to think about. I know that all
of the old Be Newsletters are available as one big zip (which I've been
meaning to grab). Stephen van Egmond has the annotated BeBook online
(and available as a download), so that's taken care of. Beforever (and
several other sites) have mirrored some of Be ftp stuff including the
Personal Edition download. Ryan Christiansen just recently zipped up
the entire Be Bug Database (up to Oct 9 2001) and made it available on
BeBits (baby, it's big!). There are probably still some bits and pieces
that may need to find a new, safe home.
* Can you recommend any books to help me get started with OS
development?
Uh...uh...
* What happens if Palm agrees to license the code to BeUnited?
Oh boy, the big one! Well, for my part, I plan to continue working on
OpenBeOS for as long as it takes until it's finished, regardless of
what happens with any other initiatives. Hope I'm not the only one!
Other related posts:
