Slashdot Mirror
Interview With Jordan Hubbard
Jeremy Andrews writes: "KernelTrap has interviewed kernel hacker and guru Jordan Hubbard, one of the creators of FreeBSD and currently a manager of Apple's Darwin project. With just a high school education, Jordan has offered some impressive contributions to the world of computing.
In this interview, Jordan talks about his current involvement with Darwin, as well as his past efforts with FreeBSD and 386BSD. He also reflects on his recent decision to step down from the core FreeBSD team."
Hewlett-Packard Install Network Printer Wizard
.INF file and the
.INF file and the "Have Disk..." option. These drivers and the behaviors that they exhibit are listed below, along with directions to install these drivers properly.
v 02.00
Table of Contents
1. Overview
2. DHCP
3. DNS
4. IP Address Support
5. Suggest IP Address (Autonet)
6. NetWare Support
a. Supported Versions
b. NDS Multiple Tree Support
c. NetWare 5 Support
d. No Novell Print Path
e. No NDS volumes
f. Support for NDS localities
7. Device Discovery
a. Gateway
b. Multi-homed Machines
c. 0.0.0.0 IP Addresses
d. Class A Subnet Masks
8. Driver Support
a. License Acceptance
b. Have Disk Support
c. HP Driver Updates
9. IPX Port Monitor and Data Corruption
10. Printer Names
11. Printer Share Name
12. Error Messages
13. Known Problems Installing HP Printer Drivers Under Windows 95/98
14. Known Problems Installing HP Printer Drivers Under Windows NT 4.0
1. Overview
This Read Me file contains last-minute product information for the Hewlett-Packard
Install Network Printer wizard for Windows 95/ 98 and Windows NT.
2. DHCP
If you try to change just the subnet mask on an HP JetDirect print server that has
been configured via DHCP, you will get an error message while using the Hewlett-Packard
Install Network Printer wizard. Once a JetDirect print server has been manually
configured, it will store the IP address, subnet mask and default gateway statically
instead of trying to obtain them dynamically. Allowing a static change only to the
subnet mask would cause DHCP-configured IP conflicts in the future. For more information
on this subject, see the HP JetDirect documentation.
3. DNS
In a DNS environment, the Hewlett-Packard Install Network Printer wizard will
automatically set up the port with the host name rather than the IP address. If you have
a DNS environment that allows Host lookup by IP, but not the reverse lookup, the printer
will never print a page. We consider this environment to be an invalid DNS environment.
To fix the port without changing the DNS environment, view Properties for the printer.
Select the ports tab. Select the port that is in use for that printer. Click Configure
Port. Change the host name to the correct IP address.
4. IP Address Support
Hewlett-Packard Install Network Printer Wizard do not support class D IP address. Class D IP
addresses are those addresses with the form of 224.xx.yy.zz
All addresses of the form 127.xx.yy.zz are reserved for loopback testing. They are not valid IP
to be used to configure device on the network.
5. Suggest IP Address (Autonet)
The algorithm for obtaining the IP address for the "Suggest Settings..." button is
derived from the Internet Draft DHC-IPV4-AUTOCONFIG by R. Troll entitled "Automatically
Choosing an IP Address in an Ad-Hoc IPv4 Network". The algorithm for generating the IP
address is to randomly generate an address in the 169.254.x.x reserved address range,
then determine if it is in use on the network. If it is in use, generate another address
in the range. Repeat until an address is generated that is not in use. The resulting
address is not intended for use on the Internet. Microsoft uses a similar scheme for
determining an IP address on Windows 98 and Windows 2000 when the system is in an environment
that doesn't have a DHCP or bootp server, and the system is configured to dynamically
determine and IP address.
6. NetWare Support
a. Supported Versions
The supported versions of NetWare are: 3.11, 3.12, 3.2, 4.11, 4.2. For Novell
queue creation, you must be logged into a Novell bindery or NDS server using a Novell
supplied client requester. See www.novell.com for client updates.
b. NDS Multiple Tree Support
The Hewlett-Packard Install Network Printer wizard only provides support for the NDS
tree the user is currently logged into. If a different tree is desired you must quit
the application, change your login to the desired tree and rerun the application.
c. NetWare 5.0 Support
If NetWare 5 is configured for IPX, and an IPX connection is being used on the client,
the Hewlett-Packard Install Network Printer Wizard can be used to create an NDS print
queue. If NetWare 5 is configured for TCP/IP and a TCP/IP connection is being used on
the client, the Hewlett-Packard Install Network Printer wizard can be used to create
an IP print path. If the client on which the application is being run has an IPX
connection to the NetWare 5 server, and the client is logged in, an NDS queue server
print path will be recommended. If IPX is not in use but TCP/IP is, a TCP/IP print
path will be recommended. In order to create NDS queues, an IPX connection with a
login must be present.
d. No Novell Print Path
The Hewlett-Packard Install Network Printer wizard relies upon several DLLs that ship
with the Novell Client for 95 and NT. The application will look for these DLLs and
the associated entry points within them. If any of the necessary DLLs are missing,
or if they do not have the needed entry points (perhaps an old version), a Novell
print path will not be available although other supported print paths will be. If a
Novell print path is not available when you think one should be, try upgrading your
Novell client software to a newer version.
e. No NDS volumes shown in NetWare 4.11
There is a known problem reading the list of available NDS volumes in NetWare 4.11 with
service pack prior to version 7. This problem has been seen in cases were the user
logs into an NDS context that is at a lower level than the available volumes. The solution
is to install the NetWare 4 Support Pack 7 or upgrade to NetWare 4.2.
f. Support for NDS localities
The Hewlett-Packard Install Network Printer Wizard cannot recognize localities in the
NDS context.
7. Device Discovery
a. Gateway
Discovery performance will be very slow if your client PC does not have a gateway
configured. To configure a gateway, choose "Network" in the Control Panel, and then
look at Properties for the TCP/IP protocol. An input should appear for entering a
gateway address. See the online help for a more information on TCP/IP and gateways.
b. Multi-homed Machines
Multi-homed machines are not supported. In a multi-homed machine, it is not possible
to distinguish between multiple devices with the same IP address. A multi-homed
machine is a computer with more than one network connection. It is possible for two
or more devices on different networks to have the same IP address. A multi-homed
machine would see both devices and there would be no guarantee that you are
configuring the correct device. In this case, either disable all but the correct
network card, or configure the HP JetDirect print server from another PC that is on
the correct network and has only one network card. This problem may also occur on
PCs that contains both a network card and a dial-up adapter.
c. 0.0.0.0 IP Addresses
Assuming that an IP address is not assigned, a JetDirect-connected printer will have
an IP address of "0.0.0.0" for approximately 2 minutes after a factory reset. After
2 minutes the IP address will automatically be assigned "192.0.0.192". Attempts to
configure a "0.0.0.0" device through an IP print path will fail. You must wait until
the HP JetDirect device has a non-zero IP address before attempting to configure it.
d. Class A Subnet Masks
If the machine running the Hewlett-Packard Install Network Printer wizard has an IP
subnet mask of "255.0.0.0" (which is known as a "Class A" subnet mask), device
discovery will suffer a significant performance degradation. To improve discovery
performance you must change your subnet mask to a non-Class A subnet mask.
8. Driver Support
a. License Support
Some drivers require the acceptance of a license. When installing a driver, if a
dialog appears that requests acceptance of a license, you must approve the license
before the application will continue. Failure to approve the license will result in
the application hanging.
b. Have Disk Support
To support new printers or drivers, the "Have Disk" button can be utilized during
driver installation. For the "Have Disk" functionality to work, the media must
contain an "inf" file (e.g. filename.inf). Some driver updates available on the
World Wide Web are in the form of self-extracting archives and are not in a format
that "Have Disk" can utilize. In this case, install the driver before running the
Hewlett-Packard Install Network Printer wizard.
c. HP Driver Updates
Hewlett-Packard driver updates can be found on the World Wide Web at:
www.hp.com/go/support
NOTE: This URL is subject to change.
9. IPX Port Monitor and Data Corruption
Some printers may experience data corruption when used with the Hewlett-Packard IPX
Port monitor under Windows NT. These errors may be corrected either by installing an
appropriate hot fix for NT or by installing Service Pack 4 from Microsoft.
10. Printer Names
When naming a printer within the Hewlett-Packard Install Network Printer wizard you
must enter a name in English that conforms to the Microsoft Printer Naming rules
(i.e. what would be accepted in the Microsoft Add Printer wizard). If a localized name
is required, assign the printer name in English and finish the install. Then open the
printer folder from the Control Panel and select the desired printer. Select "Rename"
from the File menu and rename the printer with a localized name.
11. Printer Share Name
Spaces are not allowed for naming printer shared name.
12. Error Messages
Error writing to for : The system cannot write to the specified file.
This error message may appear when attempting to print a test page or during regular
use. It usually means the printer is out of paper or unavailable. Check the printer
and make sure it is plugged in, has paper, etc. If you were running the Hewlett-Packard
Install Network Printer wizard when this occurred, there is no need to rerun the
application. Simply locate the printer in the printer folder and right mouse click on
it. Choose "Properties" and select to print a test page. If you have corrected the
error condition, a test page should now print.
Driver cannot install. Must run printer's setup program.
When installing certain HP printers (see tables below under #11 and #12), the Hewlett-Packard
Install Network Printer wizard may not be able to install the driver. You will receive an
error message stating that you need to run the printer's setup program. The Hewlett-Packard
Install Network Printer wizard may create the printer in the printer's folder despite this error.
The installed printer will not function properly. After the wizard exits, run the setup
program that comes with the printer. You may have to identify the printer as existing on a
local port such as LPT1. Install the printer using this setup program. Now delete both
printers from the printer folder (the printer created by the HP wizard and the printer created
by the printer's setup program). Run the HP wizard a second time. This time choose existing
drivers. You will see two similar printer strings. One will be from the first HP wizard
install and one from the printer's setup install. Choose one. If the wizard exists
successfully you chose the proper driver. If the installation fails, rerun the wizard and
this time choose the other driver. Finally, check to make sure the printer created is the
default printer. This can be accomplished by right mouse clicking on the printer in the
printer's folder and seeing if "Set As Default" is checked.
13. Known Problems Installing HP Printer Drivers Under Windows 95/98
Some HP printer drivers do not install correctly using the printer
"Have Disk..." option. These drivers and the behaviors that they exhibit are listed
below, along with directions to install these drivers properly.
Printer Model: HP LaserJet 8100
Behavior: PCL 6 driver will not install. The user will receive a "Spool 32" error.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the PCL 6 driver.
Printer Model: HP LaserJet 8000
Behavior: PCL 6 driver will not install. The user will receive a "Spool 32" error.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the PCL 6 driver.
Printer Model: HP Mopier 320
Behavior: PCL 6 driver will not install. The user will receive an error message telling them
to run the setup program that came with this printer, and then to run the printer
installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the PCL 6 driver.
Printer Model: HP LaserJet 4050
Behavior: PCL 5e driver will not install. The user will receive an error message telling them
to run the setup program that came with this printer, and then to run the printer
installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the PCL 5e driver.
Printer Model: HP Color LaserJet 4500
Behavior: Postscript driver will not install. The user will receive an error message telling
them to run the setup program that came with this printer, and then to run the
printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the Postscript
driver.
Printer Model: HP DeskJet 2500C
Behavior: The DeskJet 2500C driver will not install. The user will receive an error message
telling them to run the setup program that came with this printer, and then to run
the printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
Printer Model: HP LaserJet 5M
Behavior: The following drivers will not install properly: PCL Standard, PCL Enhanced,
Postscript. The user will receive an error message telling them to run the setup
program that came with this printer, and then to run the printer installer again.
Solution:
The drivers for the HP LaserJet 5M can not be installed with the "Install Network
Printer Wizard." Please use JetAdmin or Web JetAdmin to install this printer and drivers.
Printer Model: HP Color LaserJet
Behavior: The following drivers will not install properly: HP Color LaserJet, HP Color LaserJet
5/5M (CLJ5FR), HP Color LaserJet 5/5M (HP). The user will receive an error message
telling them to run the setup program that came with this printer, and then to run
the printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
Printer Model: HP Color LaserJet 5
Behavior: The following drivers will not install properly: HP Color LaserJet, HP Color LaserJet
5/5M (CLJ5FR), HP Color LaserJet 5/5M (HP), HP Color LaserJet 5/5M Postscript. The
user will receive an error message telling them to run the setup program that came
with this printer, and then to run the printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
Printer Model: HP LaserJet 6P
Behavior: The following drivers will not install properly: PCL Standard, PCL Enhanced,
Postscript. The user will receive an error message telling them to run the setup
program that came with this printer, and then to run the printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
Printer Model: HP LaserJet 6L
Behavior: The PCL Standard will not install properly. The user will receive an error message
telling them to run the setup program that came with this printer, and then to run
the printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
Printer Model: HP OfficeJet Pro 1170C
Behavior: The OfficeJet Pro 1170C driver will not install properly. The user will receive an
error message telling them to run the setup program that came with this printer, and
then to run the printer installer again.
Solution:
1. Run the file Setup.exe that came with the printer driver to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
Printer Model: HP DeskJet 1120
Behavior: There is a port monitor error right after installing the printer. The printer supplied
driver is not supported
Solution:
1. Run the Setup.exe that came with the printer to install the driver.
2. Run the "Install Network Printer Wizard" to install the printer with the driver.
14. Known Problems Installing HP Printer Drivers Under Windows NT 4.0
Some HP printer drivers do not install correctly using the printer
Printer Model: HP LaserJet 8100
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 PCL 6 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually.
Printer Model: HP LaserJet 5000
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 PCL 5 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP LaserJet 4050
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 PCL 5 and PCL 6
client drivers.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP LaserJet 2100
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 PCL and Poscript
client drivers.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP Laser Jet 6L
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 Postcript client
driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP Laser Jet 5P
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 Postcript client
driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP Laser Jet 5L
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 Postcript client
driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP Laser Jet 5
Behavior: Driver will not install. The user will receive an error message telling them to run
the setup program that came with this printer, and then to run the printer installer
again.
Solution:
1. Run the Setup.exe that came with the printer to install the driver.
Printer Model: HP LaserJet 5Si Mopier
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP DeskJet 895C
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP DeskJet 890
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP DeskJet 870
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP DeskJet 2000C
Behavior: Driver will not install. The user will receive an error message telling them
to run the setup program that came with this printer, and then to run the printer
installer again.
Solution:
1. Run the Setup.exe that came with the printer to install the driver.
Printer Model: HP DeskJet 2500C
Behavior: Windows NT 4.0 shared printers cannot install the Windows 95/98 client driver.
Solution:
1. Windows 95/98 client connecting to the Windows NT shared printer must install driver
manually
Printer Model: HP OfficeJet Pro 1170C
Behavior: No inf file that describe printer drivers.
Solution:
1. Run the Setup.exe that came with the printer to install the driver.
Printer Model: HP CopyJet
Behavior: No inf file that describe printer drivers.
Solution:
1. Run the Setup.exe that came with the printer to install the driver.
Copyright 1999 Hewlett-Packard Co. All Rights Reserved.
-- You are such a fucking fag
"With just a high school education..."
What a ridiculous thing to say. Did Jordan Hubbard's education stop after highschool? Was he locked down to whatever knowledge he had gleaned up until that point, never to accomplish any greater intellectual achievements? Did he just sit back and decide to learn nothing? When I was in college most CS programs were far behind industry practices. You might learn plenty of important things in college at that time, but nothing about software engineering that a determined enthusiast could not learn simply by reading Dr. Dobbs.
It's particularly disheartening to read this on a site like Slashdot, where people should know that technology moves so fast that they only way to succeed in the field is to have a large enough intellectual talent to teach oneself. The people that can do this should be respected for their objective accomplishments and not, as the poster implies, be patronized for overcoming a disability. There is more than one road to knowledge.
I'm not in any way diminishing the accomplishments of college graduates, but the way that sentence was written struck me as a bit off.
It is official. Netcraft now confirming: Dockers *Mobile Pants are dying.
One more crippling bombshell hit the already beleaguered Slashdot community when IDC confirmed that the mobile pants market share has declined yet again, now down to less than 1 percent of all pants. Coming on the heels of a recent Netcraft survey which plainly states that mobile pants have lost market share, this news serves to reinforce what we've known all along. Mobile pants are dying, as fittingly exemplified by an ariticle in the recent Pants Admin comprehensive pants poll.
You don't need to be a Kreskin to predict mobile pant's future. The hand writing is on the wall: Mobile pants faces a bleak future. In fact the future is so grim soon only Slashdot will be a mobile pants bastion. Things aren't looking very good for mobile pants. As many of us are already aware, mobile pants continues to lose market share. Extra pockets flow like a river of blood.
Let's keep to the facts and look at the numbers.
Mobile Pants wearer CmdrTaco states that he owns 5000 pairs of mobile pants. How many other people own them? Let's see. The number of non mobile pants wears versus CmdrTaco is roughly in ratio of 6 billion to 1. Therefore there are about 5 billion/1 = almost 0 wearer's of mobile pants. *Mobile Pants on PantNet are about 1/1000000 of the volume of other posts. Therefore there are about 1 regular mobile pants wearers. A recent article put non mobile pants wearin at about 99.999999% percent of the pants market. This is consistent with the number of pants posts.
All major surveys show that *Mobile Pants have steadily lost market share. Nothing short of a miracle could help it at this point in time. For all practical purposes, *Mobile Pants are dying.
Fact: *Mobile Pants are dead
I hope high gas prices are depriving your children, you fucking dumbass.
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
So why now? Why did *BSD fail? Once you get past the fact that *BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personalities?
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
Netcraft officially confirms: *BSD is dying
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and *BSD's long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
I am a *BSD user
and I try hard to be brave
That is a tall order
*BSD's foot is in the grave.
I tap at my toy keyboard
and whistle a cheerful tune
but keeping happy is so hard,
*BSD will be dead soon.
Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dbblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
By Chinese Karma Whore, Version 1.0
Everyone knows bout BSD's failure and imminent demise. As we pore over the history of BS, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
I sometimes think that a lot of the best examples of how to solve these problems are in our own past, the 60's and 70's being something of a golden age for OS research, and we just need to go back and study some of those examples and figure out how to bring them up to date and complete that "last 10%" they never managed (because it would have taken 90% of the time, as the adage goes).
I'm glad he stuck it out and pushed through on that last 10% for us to enjoy. You don't see as much of that going on but it is nice to see that some people still push through the glamour to finish a project. He could have just said forget it and quit when things went bad with 386BSD.
Just look at Freshmeat/Sourceforge/parts unknown for all the projects that start but lose steam and stop. My hats off to all of you code monkeys out there keeping on and producing. I'll see if I can do anything to help because I know I couldn't complete my own project.
One mo'e cripplin' bombshell hit th' already beleaguered *BSD community when IDC cornfirmed thet *BSD market share has dropped yet agin, now down t'less than a frackshun of 1 percent of all sarvers. Comin' on th' heels of a recent Netcraf' survey which plainly states thet *BSD has lost mo'e market share, this hyar noos sarves t'reinfo'ce whut we've known all along, acco'din' t' th' code o' th' heells! *BSD is collapsin' in complete disarray, as fittin'ly exemplified by failin' daid last [samag, acco'din' t' th' code o' th' heells!com] in th' recent Sys Admin comprehensive netwawkin' test.
Yo' doesn't need to be a Krehide [amdest.com] t'predick *BSD's future. Th' han' writin' is on th' wall: *BSD faces a bleak future. In fack thar won't be enny future at all fo' *BSD on account o' *BSD is dyin'. Thin's is lookin' mighty bad fo' *BSD. As menny of us is already aware, *BSD corntinues t'lose market share. Red ink flows like a rivah of blood, cuss it all t' tarnation.
FreeBSD is the dawgoned-est indangered of them all, havin' lost 93% of its co'e developers. Th' sudden an' unpleasant departures of long time FreeBSD developers Jo'dan Hubbard an' Ichabod Smif only sarve t'unnersco'e th' point mo'e clearly. Thar kin no longer be enny doubt: FreeBSD is dyin'.
Less keep t'th' facks an' look at th' numbers.
OpenBSD leader Theo states thet thar are 7000 users of OpenBSD. How menny users of NetBSD is thar? Less see. Th' number of OpenBSD vahsus NetBSD posts on Usenet is roughly in ratio of 5 t'1. Tharfo'e thar are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet is about ha'f of th' voloom of NetBSD posts. Tharfo'e thar is about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of th' *BSD market. Tharfo'e thar is (7000+1400+700)*4 = 36400 FreeBSD users. This hyar is cornsissent wif th' number of FreeBSD Usenet posts.
Due t'th' troubles of Walnut Creek, abysmal sales an' so on, FreeBSD went out of business an' was taken on over by BSDah who sell t'other troubled OS. Now BSDI is also daid, its co'pse turned on over t'yet t'other charnel house.
All majo' surveys show thet *BSD has steadily declined in market share. *BSD is mighty sick an' its long term survival prospecks is mighty dim, dawgone it. Eff'n *BSD is t'survive at all it will be among OS dilettante dbblers. *BSD corntinues t'decay. Nothin' sho't of a miracle c'd save it at this hyar point in time. Fo' all prackical purposes, *BSD is daid.
Fack: *BSD is dyin'
I hope high gas prices are depriving your children, you fucking dumbass.
Noch schlägt EIN lähmend bombshell den schon beleaguered *BSD Gemeinschaft, als IDC hat bestätigt das *BSD Markt Anteil noch wieder fallenlassen hat, jetzt hinunter zu weniger als einem Bruch von 1 Prozent allen Dienern. Kommen auf den Absätzen einer neuen Netcraft Vermessung, die klar das erklärt *Hat BSD mehr Märkte Anteil verlorenDiese Nachrichten dient, was wir haben gewußt alle entlang zu verstärken. *Bricht BSD in vollständiger Unordnung zusammen, als durch passen veranschaulicht hat Versagende Verstorbene dauern [Samag.Com] im neuen Sys Admin Umfassende networking Prüfung.
Sie müssen kein sein Kreskin [Amdest.Com], *Zukunft BSD vorauszusagen. Die schreibende Hand ist auf der Wand: *steht BSD eine kahle Zukunft gegenüber. Eigentlich dort nicht wird irgendeine Zukunft überhaupt für *BSD weil sein *Stirbt BSD. Dinge schauen sehr schlecht für *BSD an. Während viele von uns sind schon bewußt, *BSD zu verlieren weiter Markt Anteil fortsetzen. Rote Tinte fließt wie ein Fluß des Bluts.
FreeBSD ist das gefährdetste von ihnen alle, verloren 93% von seinem Kern Entwicklern. Die plötzlichen und unangenehmen Abfahrten FreeBSD Entwickler Jordanien Hubbard langer Zeit und Mikrophon Smith dient nur, den Punkt deutlicher zu unterstreichen. Können Sie dort nicht mehr ist irgendein Zweifel: FreeBSD stirbt.
Lassen Sie, daß uns zu den Tatsachen behalten, und schauen Sie die Zahlen an.
OpenBSD erklärt Leiter Theo, daß es 7000 Verbraucher von OpenBSD gibt. Wie viele Verbraucher von NetBSD gibt es? Lassen Sie, daß uns sehen. Die Anzahl OpenBSD gegen NetBSD Posten auf Usenet ist ungefähr in Verhältnis der 5 bis 1. Handeln Sie daher dort von 7000/5 = 1400 NetBSD Benutzern. BSD/OS Posten auf Usenet handeln von Hälfte des Bands von NetBSD Posten. Daher gibt es ungefähr 700 Verbraucher des BSD/OS. Ein neuer Artikel stellt FreeBSD an um 80 Prozent vom *BSD Markt. Daher gibt es (7000+1400+700)*4 = 36400 FreeBSD Benutzer. Dies ist verträglich mit dem Anzahl FreeBSD Usenet Posten.
Aufgrund der Schwierigkeiten von Walnuß Flüßchen, abgrundtiefer Umsatz und so weiter, FreeBSD ist aus Geschäft gegangen Und von BSDI wurde übernommen, der ein ander gestört OS verkauft. Jetzt ist BSDI auch totSeine Leiche hat zu noch einem anderen charnel Haus umgedreht.
Alle größeren Vermessungen zeigen das *BSD ständig Abnahme Marktes Anteil. *Ist BSD sehr krank und sein langfristiger Überleben Aussichten sind sehr dunkel. Wenn *BSD soll überleben überhaupt es unter OS dilettante dabblers sein wird. *Setzen BSD fort, weiter zu verfallen. Nichts könnte kurz von einem Wunder es zu diesem Zeitpunkt sparen. Für alle praktischen Zwecke, ist *BSD tot.
Tatsache: stirbt *BSD
I hope high gas prices are depriving your children, you fucking dumbass.
Are you a Scientologist?
BTW, Trolls we are now scientologists.
It is official; Netcraft confirms: * BSD dies still strikes laehmend bombshell a that already beleaguered * BSD community, when IDC has confirms * the BSD market portion still again drops, now down to less than a break of 1 per cent all servants. Come on the paragraphs of a new Netcraft measurement, which clearly avowedly * has BSD more markets portion this message serves, which we have known all along to strengthen. * BSD in complete disorder breaks down, when through illustrated the malfunctioning deceased fit to last [ samag.com ] [ Samag.Com ] in the new Sys Admin comprehensive one networking examination. They do not have its Kreskin [ amdest.com ] [ Amdest.Com ] to forecast * future BSD. The writing hand is on the wall: * faces BSD a bald future. Actually there any future at all for * BSD because will be * dies BSD. of things to look very badly for * BSD on. During many of us are already conscious to lose * BSD far market portion continue. Red ink flows like a river of the blood. FreeBSD is most endangered of them all this, lost 93% of his core developers. The sudden and unpleasant departures FreeBSD developer Jordan Hubbard of long time and microphone Smith serves only to underline the point more clearly. Cannot do you no more are any doubt there: FreeBSD dies. Leave that to the facts keep us, and look at you the numbers. OpenBSD explains leader Theo that there are 7000 consumers of OpenBSD. How are there many consumers of NetBSD? Leave that see us. The number of OpenBSD against NetBSD post on Usenet is approximate in relationship of the 5 to 1. Act therefore of 7000/5 = 1400 NetBSD users there. BSD/OS posts on Usenet act of half of the volume of NetBSD post. Therefore there are approximately 700 consumers of the BSD/OS. A new article places FreeBSD on by 80 per cent of * the BSD market. Therefore it gives (7000+1400+700)*4 = 36400 FreeBSD users. This is compatible with number of the FreeBSD Usenet post. Due to the difficulties of walnuss to rivers, abyss-deep conversion and so on, FreeBSD out of business went and of BSDI was taken over, some other disturbed OS sold. Now BSDI is also its corpse to still another another charnel house turned. All larger measurements constantly show * the BSD acceptance of market portion. * BSD is very ill and its long-term surviving prospects is very dark. If * BSD is to survive at all it under OS dilettante dabblers will be. * Continues BSD to purge further. Nothing could briefly save from a miracle it at this time. For all practical purposes, * BSD is dead. Fact: dies * BSD
Not sure why they make a reference to his education - as if the vocational type of schooling you get as an undergraduate in this country has any merit whatsoever. The only type of school worth pursuing in the good ol' US of A is graduate school. It is an entirely different ball game, and you best know what you are doing or else...
...
I've known people with Masters degrees in computer science who still weren't sure of the differences between a char* and a char[] in C... if that is of any consolation to those who think they've missed out a lot by not going to school. School has its purpose - however, it is entirely 100% up to the individual whether he comes out of it with more or less knowledge and aptitude to do what he's supposed to
'A lie if repeated often enough, becomes the truth.' - Goebbels
Good thing security is in quotes. Not a small mountain, nor has it been scaled. See the Saving the UNIX API thread from a few months ago on the cap-talk mailing list.
begin 644 bsd-is-dying.txtJ oMr7VNbEUO43n64BjP aNdQapZN1cUm 64BmOL-kP4ZiN m-WPqpWQqVZ2 64BjPKppPaZoS G-rO4Ji657Ze EZB2643XMqxpP bFn64NjQW-gZ QaBZPbEUPqMUM Klg65BZQbNZU R4VZ64lVR4JnR 0-CNLFXQa3ao NLAUR4VVR0+eE ZB264VVQm-gn 64tZRrAUQqJmR aJn65Fj657Zg P0-VP4xiNmsU8 Y7HF0-dQm-Xm Qa3t90-VQm-aO LFoOKtbP5YUY 64lVQrEUKrBVP K3b9aBjPJoUh Q57ZO4JiQqZqN G-iNLFrPr7fY 65Fj647Z642UG r7ZQqhdPW-P2 7rAUNbJoRL7Z9 W-IO4IUO43ie EZB264NVMqJn6 42UMalZMKgUo 647Z643iSG-aR LFpQaIUMLEUd Qm-YSKZiNmsUJ 4VdPaRn643m2 9W--Qm-hMKtt6 4xa65Jn643md PbJZQm-oPm-gP rBZ64pVQahZZ 642UQaZqNL6UP qMUMaljPqEib NL7ZN0-jNW-oO 4Jh643gP0kUZ 64FZRaJgPr-ZQ bAi1EcB0YlZg Pqxf643o65FcN G-iRKpWNL7nn R43oNLAUR4VVR 0-oO4JmNG-V6 PrQUPK3iSG-pQ qJmQm-jNW-Ci 63FcNG-iRKpWN L6UPqMUHr-Zi 63JnNKtZR0-dQ m-mPrJbO4lta Pr7Z65FcNL7Z6 43mNG-VMaxpm QmsUEZB29oxH6 5-jQrFn64xio O4IURaxgRKpZ6 4xa62tZR27Hm NG-VMaxpR0+rA 1+URLBZQbAUZ 65-pR0-4QaJZE ZB2643o643WU PK3mOqJo9W-IO 4JmNKNjQaIUo 61oUAnMoA1+UF b7ZNI7HF0-pd R4UUR4VZ64tpP K7ZQW-jNW-4p NG-oPm-oO4IUR 57jRK7gNLAUV P4Jn643iN0-nP m-jPWkUFb7ZV PaEURq3n65FVO qJi64xqNL6Um PrJWP4JY62xH9 W-CPrQUEZB2U R5JmPaJY64xqN L6UR4wUSKJoB 0Y3gP0-hMKdjQ W-nRL7qNLZng SG-YNKBgOKtZN 0-dPW-hML7ff 643iN0-dR5AUP 4xiNm-oNL7hm SG-YOKoi62Za6 0d0IoEUOLAUW NG-VPKxiNm-DI m-cPq7WSKZnU R4wUN4JXMLYi6 2tjR4VdPaQUV RaIUOLEUMLEUR 4VdQm-kPqZiV P0-kRL7kPrBZQ mkU8Y7HF0-dY SKZiNm+B0W+B
hGLEUOLAUPaxr64xaNaZXOK3g60oUHa
h8Y7HF0-dQm-YSKZiNm+B0ZZZR0-VPaxoO4J
hP4kUO4Zo65FcNG-WNKlZMKRpNL7ZN0+eEZB
hMqJiR4lt62Z2Em-XPqtaOL7hNKEUR4VVR0+
hNLBn65FcMKsUMG-aQa3XR4ZjPW-jNW+l65-
hQbAi62BjPKZiNm-jPW-oO4IUO4JZP5AUPqM
hR0-nRL7qNLYURqVdMqUUQ4lVOKtgSG-nR43
hPrBo64pjQaIUPK3mOqJo65BcML7Z90-oO4Z
hOKtaPr7XNG-rO43o65RZ7rNZ64hiPrRi643
hPqlgML-nOKtb64Zi64BjPL-gNLFZ64FdQq3
hNLVZPL-gOKNdNKEUMbYUNa3dP4ZiNm-YNK3
hOKsUR4VZ657ZMqJiR0-HSLAUEKFhOKsUMqx
hOKtb65FZQrEi1EcB0ZZjRG-YPqsbR0-iNKJ
hMKpYNLBo9aBjPJoUR4wUQ57ZN4ZXR0+eEZB
hN0-rQaZoOKtb64Zn64xi65FcNG-rMKlgCW+
hNbJoRL7Z9W-7PW-aMKBo65FcNL7Z65RjPWR
hMKlg64NjQW+eEZB2647ZMq3pQqIU8Y7HF0-
hNG-gPqxfOKtb65NZQbYUMa3Y64NjQW+eEZB
hNG-VP57ZMKFt643rML7Z90+eEZB264BjPbF
hR0-nO43mNGsUIaJY64ZiOm-aP4xrQm-gOKh
h62NmNKJ0IoEUOLAUR4VZ64pjQrEUNKtYMKt
hO43qOKtb64ljQrEUCHAZ64xa64ZoQm-XPr7
hR0Rn64hZNL+UR4wUR4VZ64NVMrFn643iN0-
h9W+B0Uo8Hr-ZPY7HF0-gNK3YNL6UJ4VZPm-
hQaIUBn+kA0-pQqJmQm-jNW-DQ4JiEZB29W-
hNLF0IoEUML7Z65FcNL7ZDm-ANLEbQm-nNKI
hPY7HF0-qNL7nRLAUHaJoEZB265-jQrFn64x
h64Zi657VR4Zj64xa61IUR4wUAGsUJ4VZQaJ
hR0+rA1+k9nIUDG+lB1+k62tZR27HF0-pQqJ
h63JnNKtZR0-VQaIUMK7jRLEUO43gNW-jNW-
hF0-kPrBoQmsUJ4VZQaJaPr7Z65FcNL7Z643
hPqMUEZB29oxH9W--657ZMqJiR0-VQbFdMql
hPrJo61Uk65-ZQaBZPbEUPqMUR4VZ60d0IoE
hR4VZQaIUML7Z60UrA1+k8n2oA1+fBn+k8Gc
hQqJmQmsUJ4VdQm-dQm-XPqtnOLBoNKto65R
hQaJZEZB263JnNKtZR0-kPrBoQmsU1EcB0YF
hPqMUJq3gPbJo62BmNKJf90-VMbZnPK3g65B
hNI7HF0-rNKto64xpR0-jNW-WRLBdPaJnQm-
hMbYUEZB2GG-rO4wUQqJgP0-VPaxoO4Jm65F
hGG-dQm-VP5Bj64FZMKEg64ZoQm-XPr7kQqI
h643iPrFcNL6UMqVVQatZP0-cPrJnNGsU1Ec
h65BcPrQUR4VVR0+eEZB264VVQm-nR4JVN4Z
hNLEUQqVVQaIi60d0IoEUOLAURaJmSG-nOKB
h65BpQbNdRa3g65-mPrBkNKBoQm-VQaIURaJ
hR4wUQrJmRaZqNG-VR0-VP4kUOLEURqZgP0-
hR0-YMK7WP4JmQmsU8Y7HF0-XPqtoOKtpNLA
hQqVjQbEUPqMUMG-hOL7VMqlZ64BjRKlY65B
hR0-dPW-oOKpZ9W-4Pr6UMKlg65-mMKBoOKB
WQm-YNK3Y9W+B0Uo8Fa3XR1cU8Y7HF0-dQm-
+
end
What's up with you just recyling the same old material over and over again when there is plenty of new material you could troll with?
I mean - not a single mention of the OpenBSD remote root exploit (via Apache) that was posted to Bugtraq last night. Come on - put forth a little effort and come up with something new from time to time rather than just rehashing the same message we've seen so many times, we don't even notice it anymore.
At this point, your trolling is so poor, I'm considering wiping my last Linux box and switching it to FreeBSD as well.
I think this has to be taken somewhat out of context to be offended by it at all. I by no means intended to imply that it was exceptional for a high school graduate without the benefit of a college education to excell at something like software engineering, and some of the best software people I know never went beyond a high school "education" in the formal sense of the word. I also would never say or even imply that a university education was unnecessary or a waste of time. In fact, I can think of few things more fun than being able to spend 4-6 years in the pursuit of academic research or learning the kinds of esoteric things that one's career would never expose one to, like oceanography or astronomy in my particular case. I just never had the luxury of being able to do that, and a luxury it is when you have to take care of yourself from an early age (I left home at 15) so I hope those folks who are in college, especially those who's parents are footing the bill, fully appreciate the blessings they have! Now that I can afford it, it's a bit late...
- Jordan Hubbard co-founder, the FreeBSD Project. Director, UNIX Technology. Apple Computer
I had to look at C Class - Arrays, String Constants and Pointers to learn all the differences (I only got 1 out of the 4).
Comment removed based on user account deletion