Slashdot Mirror

Debian/kFreeBSD has its web site's pages copyrighted by SPI, web pages which mention that "Debian" is a registered trademark without mentioning the status of "FreeBSD".

But the people I blame are the directors of the FreeBSD Foundation which now owns the FreeBSD trademark at least as far as it applies to "CD ROMs featuring an archive of computer programs which may be accessed for use archived on a CDROM." (And it appears the FreeBSD Foundation is working to expand the applicability of the FreeBSD trademark.) But there is already a Debian/kFreeBSD iso.

Considering that a simple cease and desist was sufficient to force CentOS to scrub references on its web site to the phrase "Red Hat" and other such trademarks (other than apparently a link to someone else's article), I am baffled what either Debian/kFreeBSD or the FreeBSD Foundation is waiting for.

Like most of the rest of the comments in this vein, you really obviously have no clue about the discussions that have preceded this.

Do a Google. Read previous /. discussions and the discussion on Groklaw.

Get a clue.

Start with this:

The FreeBSD Foundation acquires the FreeBSD Trademark

    The FreeBSD Foundation is pleased to announce the acquisition of
    the FreeBSD trademark.

    In October of last year, Wind River Inc. agreed to assign the
    FreeBSD trademark to the FreeBSD Foundation. As with most things
    involving paperwork and government entities, progress has been
    slow, but transfer is now complete in both the U.S. and Germany.
    Transfer requests for the United Kingdom and Japan are expected
    to complete shortly.

    The Foundation would like to thank Wind River for their assistance
    with the Trademark transfer, and Murray Stokely for his diligence
    and hard work in shepherding the process.

    As originally registered by Walnut Creek CDROM, the FreeBSD
    trademark applies to "CD ROMs featuring an archive of computer
    programs which may be accessed for use archived on a CDROM." With
    the trademark transfer complete in two jurisdictions, the Foundation
    is now turning its attention to updating the trademark to reflect
    its current usage by the FreeBSD project. The new trademark
    filing should be submitted to all four jurisdictions in January.

The official statement is here: http://www.freebsdfoundation.org/

Helevius

I usually don't reply to trolls, but this one is soo funny, I can't resist. I just want to say that I noticed that your list of assholes is expanding: now you added Scott Long as well (and the doc people for God's sake!!!). As ulib noted, you'll have almost all FreeBSD developers leave FreeBSD development for your 'enhachments.

To add more fun to what ulib noted: did you spell-check the announcments on your site? I mean, how should anyone take you and your 'enhachments' seriously if you can't check your own site for errors. Not being English is not an excuse in this case (what, you don't have the resource to get one man proof read it for you?). You are way out of touch with reality my friend. And to think that you probably made your threats with a straight face, and to think that you are trolling on slashdot... what would your customers say?

Haha, maybe there is a connection between your "Nigerian royal family member" style and the fact that you are selling FreeBSD renamed to HawkinsOS for 138$! Oh, it is only 1000$ if you buy 8 packages! YESSS, that's really the best deal if I ever heard one. You are one little entertaining troll. And this, in your about HawkinsOS box on your website:

About

HawkinsOS is being developed by T.J.HAWKINS. It relies heavily on the FreeBSD Foundation. More information will become available soon.

Consulting

Documentation of HawkinsOS

Community (!)

Well, you get the picture. Everything will be availabe if you deposit some money there after june 15 2004. :))))))

Official, Sun-approved BSD Java is available right now.

Lawyers file lawsuit. Lawyers settle lawsuit, with defendant agreeing to donate money to lawyers. How is this constructive?

Rather than giving money to the FSF, why not give money to groups which write free software?

This is not their first brush with open source. After acquiring BSDi, they encouraged BSD/OS users to move to FreeBSD, than dropped support entirely (or rather. they transferred FreeBSD sponsorship to FreeBSD MALL). Anyway, the point is, that back then, when this announcement [slashdot.org] was made, I saw the usual argument of BSD licence being more "liberal" than GPL. It seems that this might not be the case after all.

for sure
and the shame atitude they have not releasing and passing the FREEBSD trademark to freebsdfoundation hands

for freebsd folks its like talking to a wall, no answers, no dont cares, no nothing. Windriver doesnt pass the brand because of their wAllnut Creek/BSDi buy, and that puts a treat and fear like the recent SCO SCANDAL

FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to change soon.

that soon is there for more than 2 years!

BTW windRIVER works for DEfense and Military many of their RTOS are used on teleguided missels and on weapons of mass "distraction"
no one with bloody hands can join the penguin wagon since this is a free OS for free minds. Like FREEBSD is either.

If they join so, they should show how they changed their policy and thinking about OSS comunity! not by words or press releases but by actions!

So anyone know what will happen to the source?

Would donating BSD/OS source code to the FreeBSD Foundation let Wind River write it off as a tax deduction?

I donate regularly to the FreeBSD foundation (not much, $100/yr, I also give the same to EFF and the FSF).

If your business relies on FreeBSD as ours does, I suggest you do the same.. it's not really a donation, it's an investment in your business' future technology needs!!

Go ahead, take a look at that rack/shelf/desk filled with FreeBSD machines. Think about how great it is that you've got a simple, secure, stable platform and you didn't pay anything but a few hours of your time.

Now head over to the page and give 'em a few bucks.

There are 9000 ports in the FreeBSD ports system. Why post an article on gettext? Why not post articles on p5-X11-IdleTime 0.01 (8/25/2003 10:49)? At least it's a NEW port, not not just a minor release of something that's been in the ports tree for years.

It isn't just because it's a slow news day. There was an announcement this morning that Sun FINALLY approved the distribution of Java binaries for FreeBSD.

Should work for other major open source projects.

• SCO is suing IBM, allegedly because big blue stole some sort of "secret recipe" from SCO to integrate it into Linux.
• IBM -- again, AFAIK -- never collaborated with the BSDs, and the BSDs are therfore immune to the law suit

Want certified Java in FreeBSD?

Here's where to donate money:

http://www.freebsdfoundation.org/

How about this statement instead?

The other one is boring. 404 blah blah blah.

I know I'm going to get modded down for this but the link in the article is wrong.

http://freebsdfoundation.org/

The TrustedBSD project provides a set of trusted operating system
extensions to the FreeBSD operating system, targeting the Common
Criteria for Information Technology Security Evaluation (CC). This
project is still under development, and much of the code is destined
to make its way back into the base FreeBSD operating system.
This Web site will provide access to documentation,
code relating to features that are still under development, and
code that has its fingers in too many places to justify integrating
into the base operating system. Targeted features include:

• Extensible and audited authorization framework to support
  access control modules. This framework provides
  general-purpose labeling of kernel subjects/objects, centralized
  policy management, and access to a variety of run-time security
  events. This will allow the compile-time, boot-time, and
  run-time extension of the operating system security model
  based in both TrustedBSD access control modules, and
  third-party modules that employ the extension framework.
• Mandatory access control modules based on the framework
  supporting a variety of access control models, including fixed
  and floating label Biba integrity policies, the MLS
  confidentiality policy, Type Enforcement, and other customized
  policies designed for common FreeBSD deployment scenarios.
  In addition, the SELinux FLASK and Type Enforcement
  implementations will be provided via an SEBSD module, providing
  access to the higher level FLASK service abstraction, and
  mature TE implementation.
• Improvements in system privilege to reduce the level of
  risk associated with common system management functions.
• Access control lists for the file system and other kernel
  resources allowing fine-grained and manageable discretionary
  access control.
• Event auditing support, and single-host modular IDS system
  to monitor security events and notify administrators in the event
  of irregularities.

The TrustedBSD Project is made possible through the generous
sponsorship and donations of a variety of organizations, including
DARPA, NAI Labs, Safeport Network Services, the University of
Pennsylvania, Yahoo!, and others. Contributions to support the
TrustedBSD Project are welcome; please consider making donations
through the FreeBSD
Foundation.

Let's see, in the past while "FreeBSD" has been moved from Walnut Creek CDROM, to BSDi and then to Wind River, and now back to Walnut Creek CDROM (aka FreeBSD Mall). This has had one big influence on the design of FreeBSD, and that was the fine grained SMP locking for 5.0-CURRENT. BSDi released the source code of BSD/OS to FreeBSD developers, so that the kernel hackers could get into the niggly details of how they implemented their locking, which was known to work well on SMP systems.

Wind River had little influence, although they did a lot of work on getting the FreeBSD handbook into a state where it could be published.

The main design influences come from personal coders. The biggest recent influence on the design (remember the OS is not new) has probably been Whistle Communications, who have a number of people working on FreeBSD and have contributed a number of interesting subsystems, like NetGraph, and the kernel threading code going into 5.0-CURRENT. Yahoo! have a big influence on bug fixing, because they tend to work their boxes hard.

But on the whole, most of the code comes from individuals, although the most productive coders are those being paid to work full time. There were a number of such people at WC/BSDi/Wind River. Discussions occur on the mailing lists (mostly freebsd-arch).

Bandwidth has been a problem with the moves, because the main FreeBSD servers were on Walnut Creek CDROM servers. When Wind River bought BSDi, they didn't buy the CDROM bussiness, which lead to the downfall of ftp.freesoftware.com (aka ftp.freebsd.org), which used to be ftp.cdrom.com. Hopefully this change will lead to that coming back... ftp.freebsd.org is currently hosted in the Netherlands.

The problem now is that because of the 'official sponsor' vacumn created by Wind River when they announced that they were dropping FreeBSD, two other groups stepped forward. The first was the FreeBSD Foundation, which is a non profit established to fund FreeBSD (see recent announcements concerning Java for FreeBSD), and the second is Daemon News, who recently announced their own FreeBSD CD distribution, via "BSD Mall". Confused yet? How big a problem this is is yet to be seen, but anyway, the only real reason for CD's is to give them to Linux users... ;-)

FreeBSD has always been a one stop OS, and this is going to confuse things. If you're a Linux geek, try FreeBSD. You'll find that a one stop OS is nice; you don't have to hunt for patches, or wait till your distribution gets the latest kernel, or worry about matching glibc with your kernel... With FreeBSD you decide if you want to run -STABLE or -CURRENT, and you just track it. The only time you have to worry about versions is with external packages.

Regards,
-Jeremy

You are correct, Java support has been incorporated into the FreeBSD-STABLE source tree since briefly before the 4.5-PRERELEASE code freeze, and has been in testing since then. As far as I know it's working fine, and should be in 4.5-RELEASE without any worries. The FreeBSD Foundation worked with Sun to get this licensing taken care of.