create new tag
, view all tags
As of autumn 2001 there has been a few different versions of BeOS:
  • last original release by Be inc. in form of BeOS 5 for x86 (Personal and Professional Edition, with no TWiki relevant differences) and BeOS 5 for PPC (available in Professional Edition); free download of BeOS PE x86
  • binary leak, unofficial release BeOS with code name Dano, which (?) was to be future BeOS 6, but is now updated by hacks as SUPERDano or PHOSPOROS. There is quite a bit of reworked/new code included into Dano so it is more POSIX compatible and can run MySQL and other databases previously problematic to port for BeOS 5.
  • OpenSource replacement of last official and well documented BeOS 5 release, is also progressing, but at the moment is not ready for anything but experimental use. Some companies (like German YellowTab) and non-profit organizations (like international association BeUnited) are supporting this development and will work on distributing, supporting, even representing OpenBeOS users/developers.

For these reasons it would be reasonable to concentrate on first two... BeOS 5 and BeOS Dano, resolving the Issues and using the Advantages of the platform.

Issues with TWiki on BeOS:

CustomPlatformDevlopment and ComparativePlatformAdvantages

  • DataBaseLikeFileSystem - as Irix's XFS is similar to the BFS and future versions of Windows and Linux will include data-base-like file systems it might be interesting to think of good use of it! Maybe TWiki or some future hybrid/successor of it will be equally important as client app and would benefit significantly from such SystemLevelIntegration? Ideas that come to my mind are useful fore:
    • help system and general system documentation (imagine upgrading your knowledgebase as easy as using apt-get ... or easier wink
    • transparent/mobile management/availability of personal information (imagine automaticly syncing your local and web versions of address-book, bookmarks, txt one wrote, websites you built...)

-- ZeljkoBlace - 18 Aug 2002

BeOS is quite interesting, I installed it once and found it very responsive. Any patches from people who are porting TWiki to BeOS are very welcome, of course. Anything platform-specific should be done in a plugin.

I've set the implementation date to N/A since this field is for when a feature has been actually done, rather than planned.

-- RichardDonkin - 18 Aug 2002

It works, but . . .

As BeOS is posixy, porting should be trivial; in theory. I got TWiki 200[01]1201 running; my environment:

  1. BeOS R5.0.3 Professional
  2. Perl 5.005 from tbd
  3. RobinHood 1.1 or 1.2 from http://www.bebits.com
  4. RCS should be there out of the box, as far as I can tell
  1. Like in TWikiDocumentation
  2. Perl's path is awful, better symlink it to /usr/bin
  3. BeOS' out of the box webserver 'PoorMan' does no CGI. 'RobinHood' seems the most widespread server. Its configuration: symlink twiki into webroot; edit virtual_hosts:
Server: port=80;
  Host: host="Default-Host" webroot="/boot/home/public_html/"
    VRes: pattern="twiki/bin/*" type="application/x-vnd.CGI" real=false;
    VRes: pattern="twiki/pub/*" type="application/x-vnd.RHV.File" real=true;
    VRes: pattern="cgi-bin/*" type="application/x-vnd.RHV.File" real=true;
    VRes: pattern="*.shtml" type="text/x-server-parsed-html" real=true;
    VRes: pattern="*.cgi" pattern="cgi-bin/*" type="application/x-vnd.CGI" real=true;
    VRes: pattern="*index.html" pattern="index" type="application/x-vnd.Be-directory" re
    VRes: pattern="VBeIcons/*" type="image/VBeIcon" real=false;
    VRes: pattern="*" type="application/x-vnd.RHV.404" real=false;


  1. one interim edit version of TWiki (200104 or so) failed for NetPositive
  2. edit and preview seem to wait for some ~30 second timeout to happen, before browser can render page. (NetPositive, Mozilla 0.9 and 1.0)
  3. After start up, RH shows erratic behaviour when you access twiki. The log says it ran, but the browser only shows the HTTP response header as plain text like ... Pragma: no-cache, then: Connection: close. After a few tries RH + the browser kind of "catch on", then it seems to work fine.
  4. attach/upload completes successfully, but the resulting file is "raw", w/o resource description. RH then tries to serve it as directory, which fails. If you touch the file from the local file system with the appropriate tool, the file information gets discovered and stored; after that, RH can serve it properly.

Most problems seem to relate to RobinHood rather than TWiki. -- anybody tried Apache for BeOS? It's supposed to be available. The last one is really BeOS specific; the upload code would have to know about BFS resource descriptions...

HTH -- PeterKlausner 30.Aug.2002

Re the last one - you might be able to just update the RCS commands in TWiki.cfg to do a 'touch' or whatever after the RCS command.

One other point - TWiki.cfg has OS detection code that should be used by anyone writing patches for the BeOS port. Have a look at the latest version as this has been enhanced a bit - see CVSget:lib/TWiki.cfg - and feel free to do a patch for that file which handles BeOS. Probably it could be handled with a $OS of 'UNIX' and $detailedOS of 'beos' - most UNIX code would just work, and any tweaks can look at $detailedOS.

-- RichardDonkin - 01 Sep 2002

Just realised that rcs for BeOS is available for both Pro version and Dano, and BeOS PE (free Personal Edition for download) gets it with installing of BeOS R5 Development Tools.

-- ZeljkoBlace - 03 Sep 2002

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng twiki.png r1 manage 73.9 K 2002-08-30 - 22:44 PeterKlausner Screenshot Robin Hood console w/ TWiki request
Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r7 - 2002-09-03 - ZeljkoBlace
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.