Linux Today: Linux News On Internet Time.

More on LinuxToday

Developer Linux News for Feb 15, 2002

  • ZaurusZone.com: Setting Up Your Qtopia Developer Workstation (2002-02-15 17:48:46)
    "As the Zaurus platforrm is Open Source and requires components from multiple sources to create a working developer environment, we've created this "cheat sheet" to help you get going quickly."

  • Linux Documentation Project Weekly News: 2002-02-12 (2002-02-15 16:01:15)
    This week: numerous updated documents from the LDP.

  • O'Reilly Network: Advanced makefiles (2002-02-15 12:49:49)
    "In this article, we analyze a fairly complicated makefile. This makefile was captured from actual use in the wild, and sections specific to that project have been removed for this article. ... Sysadmins, make can be useful to you, too! As we step through the makefile, think about how the techniques here can be applied to rebuilding a configuration script, or an installation script, or as an auto-updating tool."

  • Dr. Dobb's: Embedded Development with Qt/Embedded (2002-02-15 11:20:21)
    "What sets Qt/Embedded apart from other embedded toolkits is that it was not specifically developed for embedded devices. Instead, Qt/Embedded is a port of the Qt toolkit for UNIX/X11, Windows, and MacOS X. Consequently, you can leverage your experience in developing desktop applications when approaching embedded application development. You don't have to learn a new API, nor do you have to pick up new programming techniques."

  • Minutes of the GNOME Board meeting February, 12 2002 (2002-02-15 06:05:20)
    Noteworthy: pending draft statement on the project's relationship with the Free Software Foundation and license policy; ssh tunneling for GNOME CVS access?; backwards compatibility discussed; more.

  • ITWales.com: The ITW Interview: Alan Cox, Kernel Hacker, Linux (2002-02-15 00:52:15)
    "The fact that there are multiple suppliers of the operating system gives a great deal of comfort to companies using it. In addition the license ensures that they can always get a custom change made for their own use, even if the main distributors are not interested. In the open source world one example of this was Y2K. When packages had Y2K problems and were no longer maintained by their authors, anyone or any group of users could fix or pay for fixing work. There was no 'enforced upgrade' risk."