Linked by Thom Holwerda on Tue 8th Jan 2008 08:18 UTC, submitted by Kaj de Vos
Syllable, AtheOS After an extensive development period, the Syllable project has released Syllable Desktop 0.6.5 with improvements all over. As always there are bug fixes, most notably in USB and the network stack, leading to large reliability and performance improvements. LibUSB and SANE were ported, so there is now USB access from user space and support for scanners. There are new network and video drivers, including a unique S3 DeltaChrome driver that Arno Klenke wrote from scratch. Two new window decorators debut from John Aspras. CD burning ability is now integrated in the form of SimpleBurn and CDRTools. A new network preferences applet from Andrew Kennan was integrated, and also Arno Klenke's port of OpenBeFS. Many ports were upgraded and the system layout has been heavily reorganised. Files needed for compiling software have been split off in a separate package. This is also the release that harmonises a number of things between Syllable Desktop and Syllable Server. The full change log is here. Installation CDs, the upgrade, and images for emulators are here. Additional software can be found here.
Permalink for comment 294975
To read all comments associated with this story, please click here.
RE[4]: OpenBFS
by jonas.kirilla on Tue 8th Jan 2008 22:16 UTC in reply to "RE[3]: OpenBFS"
Member since:

Vanders, I'm sure you know this, so just so no one gets the wrong idea here: GRUB doesn't have to understand B(e)FS to boot BeOS or Haiku. You simply use GRUB's chainload feature, as described in

This way GRUB loads and hands off to BeOS/Haiku's loader which is embedded in the partition's own boot record. You can use the command 'makebootable', but the BeOS (and future Haiku) installer should already have done that for you. (This is not BeOS's MBR menu known as 'bootman' - two separate things. Bootman, if you choose to install it, loads the partition boot record code put there by 'makebootable'.)

The only reason for GRUB to have intrinsic knowledge of a certain filesystem is to host GRUBs menu settings and additional components -within- the filesystem of a specific partition, like the one you've got Linux or Syllable on. Without this intrinsic knowledge of a certain filesystem, a boot menu can't fit much more than chainloading in the tiny space of a disk's Master Boot Record. In my opinion chainloading is cleaner than sort of spilling over into a partition, but people seem to enjoy bloat. ;P The only good reason I can see for doing it might be being able to load different operating systems with multiple presets of boot parameter for each.

Reply Parent Score: 3