[This email contains coarse language due to the absurdity of the thread
level we're in. My apologies to those offended. Also, my apologies to
the author of the original mail. You have triggered very sensitive areas
of my mind. :)]
[This probably belongs to -chat, -flame (we should create that one) or
On Sun, 12 Aug 2001, Jim Bryant wrote:
> Also, dinosaurs or not, DOD is now an INVESTOR in the FreeBSD system. Name
> any other group besides maybe BSDI that has provided $1.4 million [USD] to
> the project.
> We should look towards making FreeBSD the open-source OS of choice in the
> DOD environment, in which Linux has already made major inroads where FreeBSD
> isn't even allowed to tread yet.
I do not agree with that statement. We should not distort FreeBSD's
vision to fit what a few people believe to be DOD wishes. Even if it
would be the DODs wishes, I say: fuck the DOD. Fuck the army. FreeBSD is
a Free project. We don't have to comply to some freakin military.
> Actually, it is up to us to resolve this. I don't think you understand how
> DOD operates. The vendor makes the changes, not DOD. Not the admin.
And FreeBSD is the *vendor*? I don't think so. At least I don't hope so.
If I'm mistaken, slap me, but the project should not bend over for any
big guy who pulls out enough money.
I know this will sound ridiculous, but what if Mucrosoft put 1M$ in
FBSD? Would we fucking bend over? I hope not.
> Moving the non-GPL shells to /bin is a trivial request that can solve
> problems that you obviously don't understand.
Then we could also answer a trivial request such as making apache part
of the base system! If the DOD need a webserver, they're screwed? They
panic? What the heck is that? And why should we care about such
> DOD will is a vast new market for FreeBSD, and if we don't think ahead now
> and consider what will make admins recommend FreeBSD over Linux, Solaris, or
> HP-UX, then we'll never reach the kind of market penetration that Linux,
> Solaris, and HP-UX have in the DOD market.
Saying: "the military uses our sw, you should use it too" should make
admins use the sw? What a sick world we're in.
Wasn't the DOD using NT?
> Key to this is an admin-friendly
> environment designed to get around the pre-cambrian attitudes that prevent
> DOD admins from using standard tools just because it's in the wrong place on
> the disk array or because it's considered a third-party option, or even
> worse: freeware [ooooh! step away from the keyboard, son. you going to
> prison, boy!].
Bash standard? Funny.
I had very good comments on the easiness (sp?) ppl have installing
third party apps in the install process. And the ports collection, and
the packages, etc... FreeBSD is very admin friendly, IMHO.
> DOD is only an example of an organization that can benefit from such a
> trivial change. They can already get this with Sun, and probably HP as well
> [I haven't seen the latest minor release to 11.x, but I bet they are
> following Sun's lead].
I don't give a flying fluck about the DOD, they can go blow themselves
up on freakin Mars. Seriously.
> Try thinking outside the box sometime. If you want a "traditional" unix, I
> think there is still a PDP-11 emulator and DL01 image of V7 at
Yeah. Let's go with the New Technology: NT. All these buzzwords and
semantics are messing things up here. It's not a matter of tradition,
it's a matter of license (bash is GPL, FBSD is BSD-licensed), and
functionality (bash != sh). See also the comment about resistance to
have perl in the base system.
Linux have bash in the base system simply because there's no other free close
relative to sh around.
> I'm more for an evolutionary unix where the idea of what's standard changes
> to reflect the needs of it's admins and users in diverse environments.
As much as I appreciate "evolution", I think this mentality is exactly
the thing that makes us pull away from support from old hardware. That's
> going nowhere due to outdated beliefs "oh, but that belongs in
Again, it's not a belief. It's a philosophy that is behind FreeBSD.
I would actually like to get *more* stuff out of the base system. Small
is beautiful. We could probably include about 10 other shells in /bin
just on the grounds that it's "standard" or "useful".
> If something after years of use becomes a standard tool,
> it needs to be moved into the base distribution. I give perl as a prime
> example of one time that this actually happened, despite the arguments for
> or against perl, it *IS* a standard tool, and it *IS* expected to be
Perl might be a standard tool (again, a funny thought) but being
"available" does not necessarly mean to have it in the base system.
Anyways, this has probably been burnt to death long time ago, I should
not get into this.
> My argument for the trivial move of the non-GPL shells to /bin, so long as
> they are statically linked, is based on experience in a market in which
> FreeBSD just got it's foot inside of the door. We have already done this
> with tcsh. I don't see what the problem is getting the rest of the non-GPL
> shells into /bin is.
I missed something here. Is tcsh GPLed? I don't think so... A quick look
at /usr/src/contrib/tcsh gives me 2 matches for "GNU", config.guess and
config.sub. The rest looks like standard BSD license. Am I wrong?
> Of course, if my argument is somehow bad, then we do have a real dilemma
> here. Better remove tcsh from /bin at once to clear up this dilemma!
Er... Why not? Screw csh/tcsh.
I never minded installing tcsh using ports/packages when I used it.
> How about an instant poll:
> 1). Since tcsh was included as a "standard" tool in /bin, do you use it in a
> standalone scenario?
> b). No
Actually, a standalone scenario for me resloves to single-user mode. And
in that case, /bin/sh is ran. And it's what I use. For everything else I
can just exec bash or zsh. :)
> 2). Since tcsh was included as a "standard" tool in /bin, is it root's
> default shell?
> a). Yes
This is hardly arguable. Just check /usr/src/etc/master.passwd :)
Please, jim, do not take my comments too harsh. I have a very strong...
opinion of the military, and of "progress", "evolution" or whatever you
want to call that mad "fuite en avant" (I don't know the proper idiom in
english (this was french)).
Have a nice day.