I seriously doubt that hatred of MS is really
a motivating factor. A side benefit perhaps.
Mostly, I believe writing OSS is primarily
driven by the need for some specific code,
and the creative juices that most real hackers
have within them. Additionally, a desire not
to see their efforts die. Having personally
busted my butt for years to clean up a many million
lines of code proprietary app, and then to see it thrown away (because of marketing reasons,
not because the code did not work),
I really have little desire to code non-OSS software these days.
Sure, if you want to roll your clocks forward.
Do *you* want to test *ALL* of your software
with the date set forward say 1 month, 2 months,
3 months, etc? How *FAR* do you continue that
process?
Why should you have to go through that headache?
Then, what happens when you get the latest
weekly patch? Yep, you start all over!
At some point, you will always be testing,
never deploying.
A problem with Toms RootBoot is that since
it is not a standard 1.44MB floppy format,
it may not be readable in all drives.
Having encountered that problem, I no longer
use it, but have instead built my own linux
floppy on a standard 1.44MB format which has
what I need (basically ext2, uclibc, busybox, lilo, grub,
memtest, thin 2.4.18 kernel with some patches).
It's still a WIP, but I have some free space left
on the filesystem, and I'm building upon it
as I encounter scenarios.
[0] - Said scenarios[2] created by not doing safe
admin[1]
[1] - sometimes intentionally[2][7]
[2] - An example: Compiling new kernel, updating
lilo, rebooting on a headless box (with floppy drive) and discovering the kernel was no good.
[3] - was rebooted on prior kernel[4] in minutes using only my custom floppy and another computer[5][6] with floppy drive.
[4] - prior kernel only available on harddrive
on the dead machine[6].
[5] - must be same platform (x86) as dead machine, not headless.
[6] - Both machines must be bootable from floppy.
[7] - I learn more when I break[8] stuff.
[8] - You get to keep (and fix) the parts!
It's not that simple. Just treating them like
people is part of the problem. Most people
can deal with interruptions because they don't
stay on the same train of thought for very long.
Non-programmer types when they interrupt a
programmer *never* for a second believe they
are really causing a problem. But, IMNSHO,
those interruptions are real thought-killers.
I'd like to LART some managers who come by
every 10 or 15 minutes while I'm working on
a project with a very tight deadline, and ask
'Is it done yet?'
Not to mention that SBC *provides* routers
for home DSL users that have multiple computers.
I also NAT as do many others. The PTB still
don't have a fsck'n clue when it comes to home
networking. For some reason they believe that
home networks are costing Large Corps money,
when in fact, most people doing NAT at home
probably have a clue and actually reduce
problems (ex: CodeRed) due to firewalling.
While your link to longer battery life is quite important, many females prefer the thickness
of the battery when it comes to addressing the
tension in their pants.
Sorry, but this entire concept has
a strange smell to me. Technically it
seems cool, but I don't see the appeal of
Intel and Microsoft getting in bed together
one last time.
Slashdot Mirror
I seriously doubt that hatred of MS is really a motivating factor. A side benefit perhaps. Mostly, I believe writing OSS is primarily driven by the need for some specific code, and the creative juices that most real hackers have within them. Additionally, a desire not to see their efforts die. Having personally busted my butt for years to clean up a many million lines of code proprietary app, and then to see it thrown away (because of marketing reasons, not because the code did not work), I really have little desire to code non-OSS software these days.
Just to piss off Microsoft.
'nuff said.
Perhaps you haven't seen anything because Linux/GNU does not need it!
Or more likely, it's not visible to you.
Simple, stop subsidizing the junk mail.
Sending a letter should be 18 cents,
sending business spam via snail-mail should cost at least twice that.
I *knew* sex was cosmic!
Hmmm, did they arrive at this figure based upon the pr0n industry?
IIRC, all leap seconds when inserted or deleted, is well planned in advance. IIRC, GPS is prepared for these events also. Here's a link.
Why should you have to go through that headache?
Then, what happens when you get the latest weekly patch? Yep, you start all over! At some point, you will always be testing, never deploying.
Hell, you might as well have stuck with 98.
Do you forsee the death of POTS and modems in the future, or will they always be around?
True. However, for many oldtimers, they never fixed their bookmark for Dejanews which still functions.
They can only fill out the short form.
I don't know about you Earthlings,
but I plan to still be coding in C in 100 years.
So Bill *is* an alien then!
Having encountered that problem, I no longer use it, but have instead built my own linux floppy on a standard 1.44MB format which has what I need (basically ext2, uclibc, busybox, lilo, grub, memtest, thin 2.4.18 kernel with some patches).
It's still a WIP, but I have some free space left on the filesystem, and I'm building upon it as I encounter scenarios.
[0] - Said scenarios[2] created by not doing safe admin[1]
[1] - sometimes intentionally[2][7]
[2] - An example: Compiling new kernel, updating lilo, rebooting on a headless box (with floppy drive) and discovering the kernel was no good.
[3] - was rebooted on prior kernel[4] in minutes using only my custom floppy and another computer[5][6] with floppy drive.
[4] - prior kernel only available on harddrive on the dead machine[6].
[5] - must be same platform (x86) as dead machine, not headless.
[6] - Both machines must be bootable from floppy.
[7] - I learn more when I break[8] stuff.
[8] - You get to keep (and fix) the parts!
they'll know exactly where they are when the call for help.
Good FAQ. I would add points to it regarding the ideal hacker environment such as quiet, no interruptions, flexible hours, and working from home.
I'd like to LART some managers who come by every 10 or 15 minutes while I'm working on a project with a very tight deadline, and ask 'Is it done yet?'
The VW bugs are used as a comparison because they have been around as long as meteors and last nearly as long too.
I also NAT as do many others. The PTB still don't have a fsck'n clue when it comes to home networking. For some reason they believe that home networks are costing Large Corps money, when in fact, most people doing NAT at home probably have a clue and actually reduce problems (ex: CodeRed) due to firewalling.
A proud member of the NAT terrorist group!
Is this shorthand for Bad exploit?
While your link to longer battery life is quite important, many females prefer the thickness of the battery when it comes to addressing the tension in their pants.
Sorry, but this entire concept has a strange smell to me. Technically it seems cool, but I don't see the appeal of Intel and Microsoft getting in bed together one last time.
Speaking of /.-ing /.,
has anyone else else noticed performance problems since Slashdot moved to the left coast?
Mods, save your points for me since I'm going to be poking my GF later.