Changes between Version 18 and Version 19 of R1/Alpha1/ReleaseNotes
- Timestamp:
- Sep 13, 2009, 12:26:26 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
R1/Alpha1/ReleaseNotes
v18 v19 7 7 = Haiku R1 Alpha 1 Release Notes = 8 8 9 The goal for Haiku R1 is essentially, a fully working and stable operating system. A viable replacement for BeOS R5 (and later). 10 For Haiku R1 Alpha 1 the goal was to be a usable version of Haiku that is self-hosting, that is, that can check out the sources from SVN, and compile them, and to enable current and future Haiku developers a (mostly) stable operating system to work on their software projects. Therefore we have included the basic build tools, along with clients for cvs, svn, git and hg. This release of Haiku is capable of running binaries built with either GCC 2 or GCC 4. Use of GCC 4 is discouraged, as no compatibility is guaranteed with future versions of Haiku (eg, post-R1). 9 These are the release notes for Haiku R1 Alpha 1, our first official release. For this first alpha release, we strived to provide a usable version of Haiku that is self-hosting, that is, that can check out the sources from SVN, and compile them. We have tried hard to make this release as good as possible. Still there are a few known issues and missing features, some of them collected below. Please keep in mind that this is alpha software, which means it is not yet feature complete and still contains known and unknown bugs. 10 11 Another goal that has driven the release of the Alpha 1 was to provide current and future Haiku developers a (mostly) stable operating system to work on their software projects. Therefore we have included the basic build tools, along with clients for cvs, svn, git and hg. This release of Haiku is capable of building and running binaries using either GCC 2 or GCC 4. The use of GCC 4 is discouraged however if not absolutely necessary, as no API compatibility is guaranteed with future versions of Haiku. 11 12 12 13 … … 24 25 LiveCD and first boot performance: After an initial installation or a boot into LiveCD mode, some background tasks are executed to finish the installation setup. This is known to degrade performance. On harddisk installs this usually is not a problem as the tasks are done quickly. In LiveCD mode and also when booting from USB the performance hit is more prominently visible due to the usually bad seek performance on CDs and the slow write back of small files on USB devices. Since the CD is read-only, this setup takes place on every start of the LiveCD. On writable media it will only be done once, so further boots shouldn't experience the same delays. 25 26 26 Font rendering in this release is not optimal. Due to the uncertain situation about patents, the official release has known to be patented code disabled. This sadly includes hinting code used by FreeType that would provide better looking font rendering if enabled. Once the situation is better understood and a decision has been made these technologies might get re-enabled for official releases.27 Font rendering in this release is not optimal. Due to the uncertain situation about patents, the official release has disabled code, which is known to be patented. This sadly includes hinting code used by FreeType that would provide better looking font rendering if enabled. Once the situation is better understood and a decision has been made these technologies might get re-enabled for official releases. 27 28 28 29 The hda driver for HD Audio devices is known to fail with at least some VIA and nVidia devices. Some newer codecs are also not yet supported. … … 33 34 Haiku does not yet have support for wireless networking. 34 35 36 There's no package management yet. 37 38 The Haiku boot manager (bootman) supports a single hard disk drive only. 39 35 40 DriveSetup does not install a basic bootloader when partitioning a disk. This requires bootman or another MBR bootloader to be manually installed on hard drives that were previously blank. 36 41 … … 40 45 41 46 USB keyboards attached to OHCI or to USB 2.0 hubs do not work in Kernel Debugging Land (KDL). They need to be connected to UHCI root ports to work in KDL. Also note that when entering the kernel debugger by means of a panic it is possible that the keyboard does not work. To work around this issue you can manually enter the kernel debugger once and leave it again to enable the USB keyboard. 42 43 There's no package management yet.44 45 The Haiku boot manager (bootman) supports a single hard disk drive only.46 47 47 48 Printing to printers connected via USB port or parallel port wont work, because device drivers are missing.
