ru.linux

 
 - RU.LINUX ---------------------------------------------------------------------
 From : Sergey Lentsov                       2:4615/71.10   12 Jul 2001  16:16:00
 To : All
 Subject : URL: http://www.lwn.net/2001/0712/
 -------------------------------------------------------------------------------- 
 

    [1][LWN Logo] 
    
                                [2]Click Here 
    [LWN.net]
    
              Bringing you the latest news from the Linux World.
    Dedicated to keeping Linux users up-to-date, with concise news for all
                                  interests
    
    Sections:
     Main page
     [3]Security
     [4]Kernel
     [5]Distributions
     [6]On the Desktop
     [7]Development
     [8]Commerce
     [9]Linux in the news
     [10]Announcements
     [11]Linux History
     [12]Letters
    [13]All in one big page
    
    Other LWN stuff:
     [14]Daily Updates
     [15]Calendar
     [16]Linux Stocks Page
     [17]Book reviews
     [18]Penguin Gallery
    
     [19]Archives/search
     [20]Use LWN headlines
     [21]Contact us
    
    TUCOWS.com:
     [22]linux.tucows.com
     [23]Ext2
     [24]Themes
    
    Recent features:
    - [25]Gael Duval
    - [26]Kernel Summit
    - [27]Singapore Linux Conference
    - [28]djbdns
    - [29]LinuxWorld NY
    - [30]Jason Haas
    - [31]Larry Wall
    - [32]Bruce Momjian
    - [33]2000 Timeline
    - [34]Eric Raymond
    - [35]LWN coverage of Comdex 2000
    - [36]Ransom Love
    - [37]Guido van Rossum
    - [38]Paul Everitt
    - [39]Embedded Systems Conference
    - [40]Embedded Linux Consortium
    - [41]OLS Coverage
    
    Here is the [42]permanent site for this page.
    
    See also: [43]last week's LWN.
    
 Leading items and editorials
 
    A response to the challenge. [44]Last week LWN called for a free
    software response to Microsoft's .NET and HailStorm initiatives that
    went beyond mere copying of Microsoft's design. In response to our
    challenge, the community has rallied and announced two initiatives in
    this area. The Free Software Foundation has put out [45]a press
    release announcing its support for both projects. We are gratified
    that our challenge was received in this way.
    
    What...? You say all that was happening anyway? And, besides, nobody
    made it through our editorial? OK, maybe so...
    
    Anyway, as stated, there are two independent projects which have
    announced their existence over the last week, plus one other which has
    not put out any formal announcements so far. They differ significantly
    in their scope and goals; we'll have a look at all three.
    
    Ximian's Mono project came out with [46]an announcement of its
    existence on July 9. Of the two projects, Mono is less ambitious at
    the design level - it has set itself the task of reproducing a number
    of Microsoft-designed components that facilitate the development of
    .NET applications. In particular, Mono plans to produce:
      * A compiler for the C# language which produces "Common Language
        Runtime" (CLR) bytecodes. Interestingly, this compiler will not be
        based on the gcc backend.
      * A reimplementation of the Microsoft class libraries that work with
        the CLR.
      * A "Common Language Infrastructure" virtual machine which will make
        the whole thing work.
        
    All of the resulting code, of course, will be free software. Ximian
    hopes that, with enough outside participation, it can crank out most
    of the above software over the course of a year.
    
    This project probably needs to happen, but there are a couple of
    immediate concerns that come up. One is that Microsoft is being
    allowed to set the agenda; Mono is playing the "catch up" game
    creating free implementations of systems designed by others. It helps
    that Microsoft has submitted the relevant specifications for standards
    approval, but, in the end, it would not be surprising to see the
    company "embrace and extend" its own standards.
    
    The other concern is the "shared source" release of some of the .NET
    code. Those who hack on Mono are going to have to be tremendously
    careful to avoid any sort of exposure to the .NET code, or the whole
    project could find itself open to lawsuits. As [47]Eric Raymond put it
    a week ago, the shared source license is the truly viral one - a look
    at Microsoft's code can contaminate everything a programmer produces.
    
    Playing the game with Microsoft brings exposure to those sorts of
    hazards, but somebody probably has to do it. The .NET infrastructure
    is likely to prove hard to avoid. And, it is said, it even has some
    nice features. So we wish Ximian luck in its project. (See also:
    [48]the Mono Project home page).
    
    Then, there's DotGNU. At first, the DotGNU Project looks quite similar
    to Mono. There is a difference, though: while Mono is concentrating on
    the low-level plumbing for developers, DotGNU is looking hard at the
    services that will be implemented on top of that plumbing. Mono, for
    example, is not concerned with the HailStorm authentication services
    (other than providing a platform on which they can run); DotGNU,
    instead, describes HailStorm as "dangerous stuff" and has plans for
    the implementation of a freer alternative.
    
    DotGNU is not ignoring plumbing, though. Three of the project's
    highest priorities are:
      * The "DotGNU Core Platform," which is essentially a bytecode
        specification for a new virtual execution environment. Rather than
        go with the "Common Language" scheme, DotGNU wants to start over.
      * The "DotGNU Secure Execution Environment," a virtual machine which
        runs the core platform bytecodes.
      * The "DotGNU Distributed Execution Environment" takes the execution
        environment into a wide area clustered mode.
        
    This would all be cool stuff to have, but one must question the wisdom
    of creating yet another virtual machine definition. It seems like
    substantial amounts of effort could be saved by, for example, starting
    with the Java virtual machine - for which multiple free
    implementations already exist. The reason for this decision, according
    to DotGNU designer Norbert Bollow, is to support the needs of the
    distributed execution environment. The end result may look much like
    the Java platform, but some enhancements will be necessary.
    
    Also on DotGNU's list is:
      * "DotGNU Virtual Identities," the project's answer to HailStorm.
        The Virtual Identities scheme will not involve central servers or
        any single source of personal information;
        
    This is an area where DotGNU could, perhaps, make a real difference. A
    proper set of open, distributed personal information protocols could,
    simultaneously, make life easier for users of network services and
    address the concerns that surround HailStorm and its "Passport"
    system.
    
    DotGNU faces an uphill battle. The project is new, with no code to
    show. It's sponsoring organization, FreeDevelopers.net, is a
    distributed company with utopian ideals but little cash and no track
    record. And the project is ambitious, to say the least. DotGNU may
    well get to where it wants to be, but chances are that it will have to
    find some partners and/or backers first. It will also need to define a
    revenue model, since FreeDevelopers.net really is supposed to generate
    paychecks for its developers at some point.
    
    Finally, DotGNU and Mono would be well advised to find effective ways
    of working together. There is no room for misunderstandings and
    duplication of effort on a project of this scale. Given the different
    emphasis that each project has, it should be possible for the two to
    complement each other, with much better chances of success in the end.
    
    The Island of Project Nareau? A third contender for the next
    generation of Internet services exists, but, while its architecture
    and design process is well advanced, it has not yet started issuing
    press releases. The [49]Nareau Project has set out to develop "an
    open, user centric, cross platform, Internet3.0 platform," based on
    standard, existing components. If all goes well, the project will have
    code to show next month.
    
    Nareau developers do not see the need to create an entire new
    framework, as is being done by both Mono and DotGNU in their
    respective ways. Instead, Nareau plans to make use of the many tools
    and protocols that already exist. Thus, the project will be built on
    top of components like:
      * Server software: Apache, parts of Zope, Jabber, Jakarta
      * Client software: Mozilla, Komodo
      * Protocols: SOAP, Kerberos
        
    And so on.
    
    The Nareau vision sees a net with a great many "nodes," which can be
    anything from a cellular phone to a large server. These nodes
    communicate [50][Nareau architecture] directly with each other,
    generally without the need for central servers, using Jabber to send
    messages back and forth. These messages will be interpreted by objects
    living on the recipient systems, possibly intermediated by a set of
    rules implemented in a middle layer.
    
    A crucial component of Nareau will be the "CloudServer," which handles
    messaging and object publishing, but which does not concern itself
    with user interface issues. The Nareau rules system will be
    implemented in the CloudServer, as will authentication and access in
    general. It is thus the security gateway for a Nareau node; it is also
    hoped that it will make rule scripting easy to the point that most
    users will take advantage of the capability.
    
    The authentication aspect of Nareau is handled through a protocol
    called [51]Sunshine; it is Nareau's answer to HailStorm. It is, of
    course, a decentralized system, meaning that no single company can
    position itself as the sole arbiter of access to network services. Any
    reasonable system has to be that way, but that does leave each
    participant on the net with the problem of deciding which identity
    services it trusts. Finding a secure and simple solution to this
    problem will be a major and unavoidable challenge for any future
    identity service.
    
    Implementation of Sunshine is one of Nareau's first priorities.
    
    The interface to Nareau seen by most users will be a separate
    component called a "SpaceStation." The SpaceStation uses Mozilla to
    provide a user interface to the net. Since, like any proper, modern
    system, Nareau is designed around peer-to-peer principles, every
    SpaceStation will include a CloudServer as well. Thus, the
    SpaceStation will not only allow users to "browse" the net and control
    their experience there; it will also allow them to participate and
    publish their own objects.
    
    The Nareau developers hope to have a first release (implementing a
    calendaring system) available for release at [52]JabberCon in August,
    with a more complete release sometime around the end of the year.
    Until then, the project appears to be operating in a cathedral mode,
    with no downloads or public mailing lists available.
    
    The Nareau developers are hoping, eventually, to make money from the
    project, through the sales of consulting services, and, perhaps,
    proprietary components (though the base system will be released under
    the GPL). There may also be an "enterprise version" of the CloudServer
    subsystem. Even there, the project is talking about a "source
    available commercial license" - just don't call it "shared source."
    
    Inside this LWN.net weekly edition:
      * [53]Security: NAI gets DARPA funding, bugs in dip, OpenSSL,
        OpenSSH, lmail, tetex, tripwire, xdm, xloadimage, Oracle8i.
      * [54]Kernel: Piggyback tarballs; the challenge of 64-bit DMA.
      * [55]Distributions: Red Hat DMA issue, PowerPC options.
      * [56]On the Desktop: Windows on Linux, units clarification and KDE
        2.2Beta1
      * [57]Development: BlueBox distributed computing, BusyBox 0.52,
        Samba 2.2.1, TMDA anti-spam for qmail, GNU Medical Record Project
      * [58]Commerce: BRU and TOLIS group; Mitel Networks acquires
        e-smith; device driver book updated.
      * [59]History: KDE/GNOME flamewars, gaming platforms.
      * [60]Letters: LSB and Debian; .NET; IPFilter license.
        
    ...plus the usual array of reports, updates, and announcements.
    
    This Week's LWN was brought to you by:
      * [61]Jonathan Corbet, Executive Editor
      * [62]Elizabeth O. Coolbaugh, Managing Editor
      * [63]Michael J. Hammel, Senior Editor
        
    July 12, 2001
    
                               [64]Click Here 
    
                               [65]Click Here 
    
    
                                                        [66]Next: Security
    
    [67]Eklektix, Inc. Linux powered! Copyright Л 2001 [68]Eklektix, Inc.,
    all rights reserved
    Linux (R) is a registered trademark of Linus Torvalds
 
 References
 
    1. http://lwn.net/
    2. http://ads.tucows.com/click.ng/pageid=001-012-132-000-000-001-000-000-012
    3. http://lwn.net/2001/0712/security.php3
    4. http://lwn.net/2001/0712/kernel.php3
    5. http://lwn.net/2001/0712/dists.php3
    6. http://lwn.net/2001/0712/desktop.php3
    7. http://lwn.net/2001/0712/devel.php3
    8. http://lwn.net/2001/0712/commerce.php3
    9. http://lwn.net/2001/0712/press.php3
   10. http://lwn.net/2001/0712/announce.php3
   11. http://lwn.net/2001/0712/history.php3
   12. http://lwn.net/2001/0712/letters.php3
   13. http://lwn.net//2001/0712/bigpage.php3
   14. http://lwn.net/daily/
   15. http://linuxcalendar.com/
   16. http://lwn.net/stocks/
   17. http://lwn.net/Reviews/
   18. http://lwn.net/Gallery/
   19. http://lwn.net/archives/
   20. http://lwn.net/op/headlines.phtml
   21. http://lwn.net/op/Contact.html
   22. http://linux.tucows.com/
   23. http://news.tucows.com/ext2/
   24. http://unixthemes.tucows.com/
   25. http://lwn.net/2001/features/MandrakeSoft.php3
   26. http://lwn.net/2001/features/KernelSummit/
   27. http://lwn.net/2001/features/Singapore
   28. http://lwn.net/2001/features/djbdns.php3
   29. http://lwn.net/2001/features/linuxworldny/
   30. http://lwn.net/2001/features/JHaas/
   31. http://lwn.net/2001/features/LarryWall/
   32. http://lwn.net/2001/features/Momjian/
   33. http://lwn.net/2000/features/Timeline/
   34. http://lwn.net/2000/features/ESR/
   35. http://lwn.net/2000/features/Comdex/index.php3
   36. http://lwn.net/2000/features/Comdex/RansomLove.php3
   37. http://lwn.net/2000/features/Guido.php3
   38. http://lwn.net/2000/features/PaulEveritt.php3
   39. http://lwn.net/2000/features/ESC/
   40. http://lwn.net/2000/features/ESC/ELC.php3
   41. http://lwn.net/2000/features/OLS/
   42. http://lwn.net/2001/0712/
   43. http://lwn.net/2001/0704/
   44. http://lwn.net/2001/0704/
   45. http://www.businesswire.com/cgi-bin/f_headline.cgi?bw.070901/211902277
   46. http://www.businesswire.com/cgi-bin/f_headline.cgi?bw.070901/211902270
   47. http://lwn.net/2001/0712/a/esr-viral.php3
   48. http://www.ximian.com/tech/mono-index.php3
   49. http://nareau.weblogs.com/
   50. http://nareau.weblogs.com/
   51. http://nareau.weblogs.com/stories/storyReader$44
   52. http://www.jabbercon.com/
   53. http://lwn.net/2001/0712/security.php3
   54. http://lwn.net/2001/0712/kernel.php3
   55. http://lwn.net/2001/0712/dists.php3
   56. http://lwn.net/2001/0712/desktop.php3
   57. http://lwn.net/2001/0712/devel.php3
   58. http://lwn.net/2001/0712/commerce.php3
   59. http://lwn.net/2001/0712/history.php3
   60. http://lwn.net/2001/0712/letters.php3
   61. mailto:lwn@lwn.net
   62. mailto:lwn@lwn.net
   63. mailto:lwn@lwn.net
   64. http://ads.tucows.com/click.ng/buttonpos=lwnbutton125top
   65. http://ads.tucows.com/click.ng/buttonpos=125-001-016
   66. http://lwn.net/2001/0712/security.php3
   67. http://www.eklektix.com/
   68. http://www.eklektix.com/
 
 --- ifmail v.2.14.os7-aks1
  * Origin: Unknown (2:4615/71.10@fidonet)
 
 

Вернуться к списку тем, сортированных по: возрастание даты  уменьшение даты  тема  автор