it may be worth noting that DSL (most DSLs, but i'm not sure about all) are, by definition, half-duplex. that's why, for example, a 1Mbit sDSL line can afford to be ~1/4 the cost of a T1, can be sold by the same people, and isn't direct competition. also, if you're total rate is less than 1/4 when going bi-directional, you've got some network hardware or line quality issues. there should be some slow-down (context switches of any form are not free), but that's ridiculous. complain to Verizon.
giving back to the world is not free. charity costs you something. do it anyway.
and spread that burden out tremendously, often to the point where the individual chunks are well within what people are already paying for. the bandwidth to run a tracker feeding (say) 10,000 people is dramatically lower than the bandwidth needed to feed the content to 10,000 people. that's the whole point.
if your point here is something along the lines of "/. isn't likely to bring down apple, they can handle it.", fine, i agree. but i'd still really like to see a torrent for this. torrents distribute the load of the download better. i, as an end user, would likely get better performance that way. as it is, the download's taking forever, but my bandwidth's fine. responding to the parent, i don't think it's/.'s job to post the torrent, though. i like torrents, find them generally quite useful, and wish more places would start using them. but it should be the content provider - Apple, in this case - putting the torrent and seed up.
// This not the first nor the last time something like this has shown up.
what? doesn't that mean that the next root vulnerability would have had to already have shown up? or is the author precognitive? the link given as "last" certainly isn't... can we please think about these little jabs before tossing them around?
for the record, i wasn't suggesting getting anyone drunk; rather, give it as a gift. given we're talking about techies, maybe a large DIMM or ThinkGeek gift certificate would've been better, but alcohol's always worked well when we needed to grease the wheels with the landlord, or utility guy, or trash collectors, and so on.
The IPSec facilities in Panther should be more than sufficient for what you need. In my experience (in very nearly the exact same situation, as well as similar ones at corporation), the hardest part is wrangling the proper information out of your support staff. First you have to find someone who know WTF you're talking about. then they have to find the information. then they (may) have to get approval to give it to you. that generally involves convincing some clueless administrative type that you're not an 3vi1 h4xx0r. and then they have to actually give it to you. and the odds of getting the info right on the first try is not so good. my biggest bit of advice is find some friendly, knowledgeable admin, find out what she likes to drink, and buy her lots of it.
also interesting is the fact that running the same experiment on my Panther PowerBook yields almost exactly the numbers you saw (my NetBSD count is 145; other two are spot on). i've got no idea what this says, but i found it pretty interesting. note also that apple's own claim is that the system is mostly FreeBSD-based, with bits pulled in from [Open,Net]BSD, as well. they're not hiding anything.
Kodak's film cameras suck, and always (more or less) have. they make very good film, paper, and associated supplies, but their actual cameras are plain awful. this is pretty commonly accepted by professionals in most areas (i can't say all; i hear they have some film-based forensic cameras that are good if you need that sort of thing). their digital cameras, while not the best available, are pretty good. this is just kodak realizing that they can make more money by selling something they do well than something they do poorly.
what would be real news is if Kodak were to stop producing film.
...Win95, which Microsoft wisely abandoned in the late 90's.
well, yeah... when the released Win98. but there's no substantial difference at the core. and despite Microsoft's claims that Win98 would be the last OS they produced based on the old DOS core, the subsequently released Win98 SE (which was at least as different from Win98 as Win98 was from Win95) and the infamous Windows ME.
if you've never experienced a virus or worm on 2000, you're extraordinarily lucky, regardless of your patching policy. the fact of the mater is that Microsoft - like most vendors - reply to incidents after they are reported in the wild (and with worse lag time than most). i manage a network with a few dozen Win2k boxes on it; we patch regularly, and we're constantly hit by viruses. and, for the record, the macs on the same net have never been hit by a single worm, virus, trojan, or what have you.
...it grew up together with the Internet as a networked OS. This was not an afterthought.
well, that's not quite true... or rather, it relies on a particular read of history. networking (like graphics) in unix was not part of the initial system. it was largely bolted on after the fact. X11 is particularly un-unix-like, but sockets violate the "everything is a file" model (or at least take substantial liberties with it), as well. however, far from detracting from the initial point about the elegance of the unix model, the fact that these "extras" have been integrated so well is a further testament to the quality, survivability, and extensibility of the model. we've seen what happens to other systems when networking or graphics are bolted on the side (um, DOS? WfW 3.11?).
for a look at what unix would have looked like had it really grown up with networking (and graphics), and what security would look like in that world, take a look at Plan 9 from Bell Labs.
and, incidentally, this H-O-H alignment is also what makes water the only thing that expands when it freezes. the crystallization process forces the molecules to lock into a shape that prevents them from flowing around each other.
I worked at Bell Labs in Murray Hill when the building was gradually being converted, one hallway at a time, from old-style offices to cubicles. It was a huge project. And almost nobody who had to work in the results was happy with it. Specifics varied from hallway to hallway, but generally you had a bunch of 3/4 height walls for most people, two to a cubicle, and the management types got "offices", or cubicles with full-height walls.
when it came time for my group (6-8 people) to move in, we cut a deal with our business unit's leader: expand our lab space, give us two pseudo-real offices, and you don't have to give us any cubes. the result was wonderful: we got a largish lab, where we all set up our workstations (with convention essentially resulting in each person having "their" workstation), we had a place to go for one-on-one meetings, personal phone calls, or naps (we brought a couch into one of the offices), we had great information exchange, and it was just plain fun. we took all our technical books and put them in one of our new shared offices, essentially creating a library, again increasing the benefits of pooled knowledge. it was the best work environment i've ever been in.
the model we were going on was actually found in-house, existing for years: 1127. this is the Bell Labs Research group that made C, Unix, and most else that's still good about computing. everyone had an office they were hardly ever in. mostly, that core group hung out in the Unix Room (so called because, well, it's where Unix (and later Plan 9) was created).
today, i work in two different locations for my employer. in one, everyone's got their own office (real offices, even!). in the other, it's open plan, with three offices and a conference room. i much prefer the later. i find myself more productive, more aware of what's going on in the rest of the company, and (being in IT) more able to respond to issues other people are talking about. in the former office, i'm routinely blind-sided by issues people have been complaining about - to themselves or their office mate - for weeks. the open environment hugely helps exchange of ideas and improves productivity, even after factoring in the seemingly "lost" time people spend just chatting - which, of course, makes the place a lot more fun to work, and improves morale.
good ideas require interaction. nobody - and i mean nobody - is smart enough to see all possible ends on their own. ask ken and dennis if they could've done what they did without easy collaboration from their peers.
Well, Bill, you may be right, but just keep in mind that re-implementing what ken and dennis designed before you probably didn't impress them so much, either. seriously, he's spot on here. there's lots of good things about linux, but few of them are technical. OS X is doing real new stuff.
no, my encryption device rotates the magnet for me. the magnet's composed of super-cooled bits i salvaged when my overclocked Athlon exploded. the magnet rotation's controlled by a Z80 i programmed with an electron microscope and magnetized dental pick. and yes, i still do the math myself. in my head.
as much as i'd love to see AT&T or Lucent buy back the UNIX IP rights Novell retains ("Look, we gave you the UNIX thing, but you blew it. Sorry."), wouldn't they need, um, money to buy out another company? Lucent in particular seems laughable. i love the company, but they've got a ways to go before they're out of their existing hole enough to look at buying companies with quite substantial assets.
i really like FreeBSD. it was my first Unix. i switched to linux for a while, and came running back. on 386 architecture boxes, it remains my unix of choice. that being said, however, FreeBSD hardly addresses the concerns about Linux's suitability for the desktop. if you buy the original claims, OS X deals with them while FreeBSD does not. mind you, i don't really buy the original claims, at least not for the reasons given. i don't think it's suitable for the desktop, but for other reasons. and how messed up are the slashdot moderators? i'm glad to be modded up and all, but i was going for "Funny", not "Insightful". Insightful? yeah, to the seven slashdot readers who've never heard of OS X.
where did i say i'd like to be the one making that choice? clearly Mr. Gaiman has concerns over the potential uses of such a story. i'm saying given the inability for him to do any reasonable controlled distribution, it's a reasonable decision to hold it back.
this practice of throwing "politically correct!" around like some sort of slur to anyone who does things the accuser doesn't like it just stupid. it's an attempt to avoid talking about the real issues and instead hiding behind a blanket statement of "don't tell me what to do" or the like. it very much reminds me of a song:
and you'll go "wah wah wah, you're so P.C." and i will say "hey, wait... my my my how have the tables turned that being a f***1ng prick is a desireable trait. "If you own the Washington Readskins you're a cock" - Atom and his Package
Thinking the way you're talking is why AltaVista is no longer the dominant search engine and Google is. Plenty of organizations have the horsepower to do a more than adequate job of the spidering half of the project. heck, plenty of people actively do the spidering half (other search engines & network mappers, to name two). the hard part is indeed the algorithms. What the Google folks (Page and... what's the other guy's name again? he needs an algorithm named after him) understood early on, and what AltaVista failed to learn (at least until it was too late) is that returning as many relevant pages as possible is not the answer. Having less results is acceptable (and can even be good), but what's crucial is having the most relevant sites up front.
and, of course, there's other things which help Google as an entity survive, but that's aside from their search results.
You've managed to completely replace what Mr. Gaiman actually said with a behavior you'd like to demonize and set him up as a straw man. The issue was never that he was afraid to write about "something as important as the very nature of life itself." He's done that several times - and often in ways that do tick off your "PC establishment". The point here is that the story he considered writing could well have hurt someone. A story about a serial killer's convention isn't likely too. The hypothetical girl you described is every bit as important as the girl Mr. Gaiman describes. The point here isn't that he's interested in not giving tools to one side or the other, but rather that it's already a very difficult decision, and there's already loads of pressure put on by lots of people on both sides, and he'd rather not add to that for anyone. While I'd personally be very interested in seeing the story, given the inability to do any reasonable controlled distribution, I think this was a wonderful show of compassion on Mr. Gaiman's part.
Slashdot Mirror
it may be worth noting that DSL (most DSLs, but i'm not sure about all) are, by definition, half-duplex. that's why, for example, a 1Mbit sDSL line can afford to be ~1/4 the cost of a T1, can be sold by the same people, and isn't direct competition.
also, if you're total rate is less than 1/4 when going bi-directional, you've got some network hardware or line quality issues. there should be some slow-down (context switches of any form are not free), but that's ridiculous. complain to Verizon.
giving back to the world is not free. charity costs you something. do it anyway.
and spread that burden out tremendously, often to the point where the individual chunks are well within what people are already paying for. the bandwidth to run a tracker feeding (say) 10,000 people is dramatically lower than the bandwidth needed to feed the content to 10,000 people. that's the whole point.
if your point here is something along the lines of "/. isn't likely to bring down apple, they can handle it.", fine, i agree. but i'd still really like to see a torrent for this. torrents distribute the load of the download better. i, as an end user, would likely get better performance that way. as it is, the download's taking forever, but my bandwidth's fine. /.'s job to post the torrent, though. i like torrents, find them generally quite useful, and wish more places would start using them. but it should be the content provider - Apple, in this case - putting the torrent and seed up.
responding to the parent, i don't think it's
// This not the first nor the last time something like this has shown up.
what? doesn't that mean that the next root vulnerability would have had to already have shown up? or is the author precognitive? the link given as "last" certainly isn't...
can we please think about these little jabs before tossing them around?
wow. where are my mod points when i need them.
for the record, i wasn't suggesting getting anyone drunk; rather, give it as a gift. given we're talking about techies, maybe a large DIMM or ThinkGeek gift certificate would've been better, but alcohol's always worked well when we needed to grease the wheels with the landlord, or utility guy, or trash collectors, and so on.
The IPSec facilities in Panther should be more than sufficient for what you need. In my experience (in very nearly the exact same situation, as well as similar ones at corporation), the hardest part is wrangling the proper information out of your support staff. First you have to find someone who know WTF you're talking about. then they have to find the information. then they (may) have to get approval to give it to you. that generally involves convincing some clueless administrative type that you're not an 3vi1 h4xx0r. and then they have to actually give it to you. and the odds of getting the info right on the first try is not so good.
my biggest bit of advice is find some friendly, knowledgeable admin, find out what she likes to drink, and buy her lots of it.
i was curious, so i ran the experiment. my numbers, at least on OS X Server, are quite different. like, a ton different. it's quite curious. observe:
/usr/bin/* /bin/* /usr/sbin/* /sbin/* 2>/dev/null | fgrep OpenBSD | wc -l
16
: cider;ident /usr/bin/* /bin/* /usr/sbin/* /sbin/* 2>/dev/null | fgrep FreeBSD | wc -l
65
: cider;ident /usr/bin/* /bin/* /usr/sbin/* /sbin/* 2>/dev/null | fgrep NetBSD | wc -l
20
: cider;ident
also interesting is the fact that running the same experiment on my Panther PowerBook yields almost exactly the numbers you saw (my NetBSD count is 145; other two are spot on). i've got no idea what this says, but i found it pretty interesting.
note also that apple's own claim is that the system is mostly FreeBSD-based, with bits pulled in from [Open,Net]BSD, as well. they're not hiding anything.
Kodak's film cameras suck, and always (more or less) have. they make very good film, paper, and associated supplies, but their actual cameras are plain awful. this is pretty commonly accepted by professionals in most areas (i can't say all; i hear they have some film-based forensic cameras that are good if you need that sort of thing). their digital cameras, while not the best available, are pretty good. this is just kodak realizing that they can make more money by selling something they do well than something they do poorly.
what would be real news is if Kodak were to stop producing film.
// Microsoft's iPod-Killer... ?
Nope. Sorry.
Let's see... game for linux... 4-7 people... moderate systems... easy!
:-)
CVS and make world
very exciting!
...when can i expect it for my TI 99/4A?
if you've never experienced a virus or worm on 2000, you're extraordinarily lucky, regardless of your patching policy. the fact of the mater is that Microsoft - like most vendors - reply to incidents after they are reported in the wild (and with worse lag time than most). i manage a network with a few dozen Win2k boxes on it; we patch regularly, and we're constantly hit by viruses.
and, for the record, the macs on the same net have never been hit by a single worm, virus, trojan, or what have you.
however, far from detracting from the initial point about the elegance of the unix model, the fact that these "extras" have been integrated so well is a further testament to the quality, survivability, and extensibility of the model. we've seen what happens to other systems when networking or graphics are bolted on the side (um, DOS? WfW 3.11?).
for a look at what unix would have looked like had it really grown up with networking (and graphics), and what security would look like in that world, take a look at Plan 9 from Bell Labs.
there is, of course, another cure for having to watch Jake 2.0...
and, incidentally, this H-O-H alignment is also what makes water the only thing that expands when it freezes. the crystallization process forces the molecules to lock into a shape that prevents them from flowing around each other.
I worked at Bell Labs in Murray Hill when the building was gradually being converted, one hallway at a time, from old-style offices to cubicles. It was a huge project. And almost nobody who had to work in the results was happy with it. Specifics varied from hallway to hallway, but generally you had a bunch of 3/4 height walls for most people, two to a cubicle, and the management types got "offices", or cubicles with full-height walls.
when it came time for my group (6-8 people) to move in, we cut a deal with our business unit's leader: expand our lab space, give us two pseudo-real offices, and you don't have to give us any cubes. the result was wonderful: we got a largish lab, where we all set up our workstations (with convention essentially resulting in each person having "their" workstation), we had a place to go for one-on-one meetings, personal phone calls, or naps (we brought a couch into one of the offices), we had great information exchange, and it was just plain fun. we took all our technical books and put them in one of our new shared offices, essentially creating a library, again increasing the benefits of pooled knowledge. it was the best work environment i've ever been in.
the model we were going on was actually found in-house, existing for years: 1127. this is the Bell Labs Research group that made C, Unix, and most else that's still good about computing. everyone had an office they were hardly ever in. mostly, that core group hung out in the Unix Room (so called because, well, it's where Unix (and later Plan 9) was created). today, i work in two different locations for my employer. in one, everyone's got their own office (real offices, even!). in the other, it's open plan, with three offices and a conference room. i much prefer the later. i find myself more productive, more aware of what's going on in the rest of the company, and (being in IT) more able to respond to issues other people are talking about. in the former office, i'm routinely blind-sided by issues people have been complaining about - to themselves or their office mate - for weeks. the open environment hugely helps exchange of ideas and improves productivity, even after factoring in the seemingly "lost" time people spend just chatting - which, of course, makes the place a lot more fun to work, and improves morale.
good ideas require interaction. nobody - and i mean nobody - is smart enough to see all possible ends on their own. ask ken and dennis if they could've done what they did without easy collaboration from their peers.
Well, Bill, you may be right, but just keep in mind that re-implementing what ken and dennis designed before you probably didn't impress them so much, either.
seriously, he's spot on here. there's lots of good things about linux, but few of them are technical. OS X is doing real new stuff.
no, my encryption device rotates the magnet for me. the magnet's composed of super-cooled bits i salvaged when my overclocked Athlon exploded. the magnet rotation's controlled by a Z80 i programmed with an electron microscope and magnetized dental pick. and yes, i still do the math myself.
in my head.
now that is l33t.
as much as i'd love to see AT&T or Lucent buy back the UNIX IP rights Novell retains ("Look, we gave you the UNIX thing, but you blew it. Sorry."), wouldn't they need, um, money to buy out another company? Lucent in particular seems laughable. i love the company, but they've got a ways to go before they're out of their existing hole enough to look at buying companies with quite substantial assets.
still, the irony would be rich...
i really like FreeBSD. it was my first Unix. i switched to linux for a while, and came running back. on 386 architecture boxes, it remains my unix of choice. that being said, however, FreeBSD hardly addresses the concerns about Linux's suitability for the desktop. if you buy the original claims, OS X deals with them while FreeBSD does not.
mind you, i don't really buy the original claims, at least not for the reasons given. i don't think it's suitable for the desktop, but for other reasons.
and how messed up are the slashdot moderators? i'm glad to be modded up and all, but i was going for "Funny", not "Insightful". Insightful? yeah, to the seven slashdot readers who've never heard of OS X.
where did i say i'd like to be the one making that choice? clearly Mr. Gaiman has concerns over the potential uses of such a story. i'm saying given the inability for him to do any reasonable controlled distribution, it's a reasonable decision to hold it back.
this practice of throwing "politically correct!" around like some sort of slur to anyone who does things the accuser doesn't like it just stupid. it's an attempt to avoid talking about the real issues and instead hiding behind a blanket statement of "don't tell me what to do" or the like. it very much reminds me of a song:
and you'll go "wah wah wah, you're so P.C."
and i will say "hey, wait...
my my my how have the tables turned
that being a f***1ng prick is a desireable trait.
"If you own the Washington Readskins you're a cock" - Atom and his Package
Dern. Now where am i supposed to get a good Unix OS suitable for both desktop and server use?
Thinking the way you're talking is why AltaVista is no longer the dominant search engine and Google is. Plenty of organizations have the horsepower to do a more than adequate job of the spidering half of the project. heck, plenty of people actively do the spidering half (other search engines & network mappers, to name two). the hard part is indeed the algorithms. What the Google folks (Page and... what's the other guy's name again? he needs an algorithm named after him) understood early on, and what AltaVista failed to learn (at least until it was too late) is that returning as many relevant pages as possible is not the answer. Having less results is acceptable (and can even be good), but what's crucial is having the most relevant sites up front.
and, of course, there's other things which help Google as an entity survive, but that's aside from their search results.
You've managed to completely replace what Mr. Gaiman actually said with a behavior you'd like to demonize and set him up as a straw man. The issue was never that he was afraid to write about "something as important as the very nature of life itself." He's done that several times - and often in ways that do tick off your "PC establishment". The point here is that the story he considered writing could well have hurt someone. A story about a serial killer's convention isn't likely too.
The hypothetical girl you described is every bit as important as the girl Mr. Gaiman describes. The point here isn't that he's interested in not giving tools to one side or the other, but rather that it's already a very difficult decision, and there's already loads of pressure put on by lots of people on both sides, and he'd rather not add to that for anyone.
While I'd personally be very interested in seeing the story, given the inability to do any reasonable controlled distribution, I think this was a wonderful show of compassion on Mr. Gaiman's part.
Where are my mod points when i need 'em?
// as long as the developers agree with a 3:1 majority.
well, if they have to have three times as many developers as they have, we're not likely to see very many changes made, are we?
unless some people are more equal than others...
(yes, i'm kidding)