I guess it wouldn't be about testosterone then, but the study would hold more sway if there were any data going the other way. For that matter, what about gay geniuses - is it the same? Fact is, raw genius often makes for terribly imbalanced people - maybe marriage helps them. Either way, the study is flawed, whether it's true or not. Can the/. editors be modded as flamebait?
It is possible, and in my experience it can actually take more effort to make a web page that doesnt work on -most- architectures/browsers. What is it that really makes the page inaccessable for some browsers? It certainly isnt the real functionality of the page, the html. It's the pretty eyecandy stuff, mostly javascript, that doesnt really do anything for the page anyway.
When i write web pages, I pride myself that i can make a visually pleasing experience, but more importantly have it be viewable by the most people. -That- to me is skillfull web authoring.
What does compatable mean any more? The concept has been sufficiently blurred over the last few years that such a designation is dubious at best. Furthermore, why "Redhat" compatable? Can some explain which parts won't work with SUSE or Debian and why?
I suspect we are past the days of binary, black & white thinking about compatability. We need a more sophisticated "compatability designation" now, don't we? How about something like that geek code some of you sign with. A hardware version could contain all the info you need, and simply be run through a decoder to indicate all the details: a) Modem: Winmodem, only works when in another OS b) Sound Card: Specs, works with kernels 2.0.x c) NIC: Specs, blah blah blah
Perhaps it could even be expanded to give us a sense of the feel and mood of the hardware - techno-power machine with peripherals duct taped to the side and sitting inside a fridge, or pastel or neon iMac, etc.
Wow, after reading the article and many of the comments, im surprised at how restrictive dsl is elsewhere. Things appear to be much different here too, from installation through usage. There are only two parties involved here, the phone co provides the line, and then our choice of an isp. The only phone co is USWest, but there are several isps to choose from. I chose to also get my isp services from USWest to simplify things, and they seemed to have fewer restrictions as compared to the others. When it came time to order, that was very simple. One initial call proved that both of my analog lines at the time were capable of at least the lowest bandwidth rate, 256k/256k. I could have placed the order at that time, but i had to come up with some money to cover the $110 install fee first:) When I did get the money, I made the call to order, which was very simple. The line was tested once again, and then they told me to expect the equipment in the mail within the next couple weeks, and an install date set for about 3 weeks from that time. About a week later, equipment started arriving. First was an analog modem (apperently part of a promotion running at the time) then a box conataining the cisco 675 dls router and a 3com nic arrived several days before the instal date that i was given. I decided to hook it up and see if they were early on the installation at the co, and they were, it trained the line no prob! From there it was just a matter of installing the nic and hooking up the short ethernet cable between the two and configuring dhcp on the computer. One reboot later and i was on the net! I have since reconfigured everything, adding a hub and a few more computers (all of which is allowed in the agreement), one of which is the linux server from which this mail was sent:) In all, i am extremely happy with the quality of service, and the prices. My initial cost was $110 for the install (which included ALL the equipment above, plus a $100 speakerphone), and thereafter the monthly charges of $39 for the line fee and $19 for the 256k bandwidth (which actually trains at 640k/272k). The line fee was recently dropped to $29 though, so now i am even happier! So anyway, theres my story, since im probably out of space on this thing:P
Slashdot Mirror
old people are only for email.
17" monitors, with 15.7" viewable?
Ya, I have an 11 inch... but you can only see 6.
I guess it wouldn't be about testosterone then, but the study would hold more sway if there were any data going the other way. For that matter, what about gay geniuses - is it the same? Fact is, raw genius often makes for terribly imbalanced people - maybe marriage helps them. Either way, the study is flawed, whether it's true or not. Can the /. editors be modded as flamebait?
when you can't distinguish between editor incompetence and an April Fools joke. They look oddly the same!
And I guessed it three years ago. Shouldn't I be able to file that with the USPTO or something?
It is possible, and in my experience it can actually take more effort to make a web page that doesnt work on -most- architectures/browsers. What is it that really makes the page inaccessable for some browsers? It certainly isnt the real functionality of the page, the html. It's the pretty eyecandy stuff, mostly javascript, that doesnt really do anything for the page anyway.
When i write web pages, I pride myself that i can make a visually pleasing experience, but more importantly have it be viewable by the most people. -That- to me is skillfull web authoring.
What does compatable mean any more? The concept has been sufficiently blurred over the last few years that such a designation is dubious at best. Furthermore, why "Redhat" compatable? Can some explain which parts won't work with SUSE or Debian and why?
I suspect we are past the days of binary, black & white thinking about compatability. We need a more sophisticated "compatability designation" now, don't we? How about something like that geek code some of you sign with. A hardware version could contain all the info you need, and simply be run through a decoder to indicate all the details:
a) Modem: Winmodem, only works when in another OS
b) Sound Card: Specs, works with kernels 2.0.x
c) NIC: Specs, blah blah blah
Perhaps it could even be expanded to give us a sense of the feel and mood of the hardware - techno-power machine with peripherals duct taped to the side and sitting inside a fridge, or pastel or neon iMac, etc.
Hmmmm....
Wow, after reading the article and many of the comments, im surprised at how restrictive dsl is elsewhere. Things appear to be much different here too, from installation through usage. There are only two parties involved here, the phone co provides the line, and then our choice of an isp. The only phone co is USWest, but there are several isps to choose from. I chose to also get my isp services from USWest to simplify things, and they seemed to have fewer restrictions as compared to the others. :) :) :P
When it came time to order, that was very simple. One initial call proved that both of my analog lines at the time were capable of at least the lowest bandwidth rate, 256k/256k. I could have placed the order at that time, but i had to come up with some money to cover the $110 install fee first
When I did get the money, I made the call to order, which was very simple. The line was tested once again, and then they told me to expect the equipment in the mail within the next couple weeks, and an install date set for about 3 weeks from that time.
About a week later, equipment started arriving. First was an analog modem (apperently part of a promotion running at the time) then a box conataining the cisco 675 dls router and a 3com nic arrived several days before the instal date that i was given.
I decided to hook it up and see if they were early on the installation at the co, and they were, it trained the line no prob!
From there it was just a matter of installing the nic and hooking up the short ethernet cable between the two and configuring dhcp on the computer. One reboot later and i was on the net!
I have since reconfigured everything, adding a hub and a few more computers (all of which is allowed in the agreement), one of which is the linux server from which this mail was sent
In all, i am extremely happy with the quality of service, and the prices. My initial cost was $110 for the install (which included ALL the equipment above, plus a $100 speakerphone), and thereafter the monthly charges of $39 for the line fee and $19 for the 256k bandwidth (which actually trains at 640k/272k). The line fee was recently dropped to $29 though, so now i am even happier!
So anyway, theres my story, since im probably out of space on this thing
Okay, I realize this is more of a question than a comment, but I've hunted around the various *bsd sites and can't find the answer.
Can someone either give me the URL which describes the differences between netBSD, freeBSD and openBSD, or summarize the differences for me here?
How should I know which one to experiment with on my one non-linux box?
Many thanks,
looking for the cd image of the i386 arch. found it on mit, but its so slow as to be worthless
not sure if thats the correct syntax, but mounting an iso is completely possible