That depends on your priorities. "Real" RAID cards lock the raid meta-data to a specific vendor (sometimes to a specific line). So if your card dies, you're forced to buy another one. If you want to upgrade (more ports, better RAID processor), same story - you're vendor locked.
Software RAID is slower (though a reasonable system doing just software RAID has no trouble outperforming a cheap "real" RAID card) but you can move the drives into another system running the same software and have access to the data.
I had data across a couple of software-raided drives under linux and a couple non-raided external USB drives, and I knew that eventually I was going to either run out of space, or a drive would fail and I'd lose data.
I started looking, and talking to friends, and decided that what I really wanted was a ReadyNas NV (http://www.infrant.com/products/products_details.php?name=ReadyNAS%20NVPlus) from Infrant (now Netgear) - I knew four satisfied customers. Trouble was cost - about $1100.
So I decided to try it on the cheap, and picked up an NSLU2 (http://en.wikipedia.org/wiki/NSLU2) which can run a customized linux distro (http://www.nslu2-linux.org/) and do software raid across attached drives.
I experimented with some drives I had on hand and discovered that while it would technically work, it was really only going to be useful for network backups (and fairly slow ones at that). It wouldn't replace the direct attached storage for doing photo storage (and editing) as it's only 100Mb Ethernet attached, and a fairly underpowered processor that mostly keeps up doing raid, as long as it's just mirroring. It is, however, functional, and more reliable in theory than non-RAIDED drives.
The total cost is in line with your budget - NSLU2s can be had on ebay, and then it's just drives (500GB drives are just over $100), drive enclosures, and some time.
For me, however, the experiment cost me under $100, and made it clear to me that if I wanted good performance, there was a price tag attached - either in dollars or in dollars and space (i.e. build a bigger dedicated raid server). So I resold the NSLU2 and started watching for a good deal on the ReadyNAS.
I found it a month or so ago - at the moment (Q3 of 07), if you spend the $1100 on a ReadyNAS with 2x500GB drives, they'll throw in a 3rd 500GB drive as a purchase incentive. That made it 1TB usable storage for about $1/GB. Still more than raw disk, certainly, but enough to convince me to give it a go.
I've had the ReadyNAS for a month, my home directory's living on it, as are all our digital photos, and media - it "just works." I started with 2x500GB drives, added the third and it grew the volume. I can add one more 500GB drive, which lowers the effective $/GB before the chassis is full. If 4x500GB isn't big enough one day, I can replace each drive, one at a time, with larger drives and the volume will expand to fit once all drives match.
And think about those managers over the course of your career whom you've enjoyed working for, and felt most productive under. If you can - ask them for advice. If any of them were, or are, in the same company - that's even better.
Finally, many companies have "intro to management" courses offered by HR - sometimes they're mandatory when you're promoted into a role with direct reports, sometimes they're not. Take one, either way. You may not learn much, but at least it should give you a sense of the "management process" in your company from a perspective you may not have glimpsed before.
Although you didn't ask for them, since I was in a similar position a few years ago, I'll offer a few specific suggestions and observations.
First of all, your management responsibilities won't just do themselves - they'll take time. Seems obvious - but I've seen (and worked for) first time managers who figured they could just go on writing code, and the rest would "sort it self out."
Second - you have two bosses - the people you work for and the people who work for you. You're accountable to each of them for different things.
One major job is to facilitate communication in both directions. Make sure the folks working for you know what's expected of them, and how that contributes to the company goals/direction. Similarly, you need to make sure the people you work for understand what your team is doing - what it's challenges are, what it's successes have been. And don't neglect communication within the team. You'll likely eventually be called on to smooth ruffled feathers, or sort out conflicts among your direct reports. It's not fun, but it's part of the job.
Another key role is facilitator. Get obstacles - technical, organizational and otherwise - out of your team's way *before they're stymied by them* so they can execute.
One way to do this is to make sure you talk to everyone working for you regularly - at least once a week, more often if the environment is "highly dynamic" (i.e. sh*t changes quickly). Find out how they're doing - and, most importantly, what they need from you so they can get it done.
If your management role includes "pay and review" responsibilities (as opposed to "just" technical leadership) - get to know the appropriate folks in HR. Most companies have a pay grade system that basically defines compensation latitude - learn it, and learn where your reports are on the scale.
Depending on the make up of the team, and the "formality" of the environment, this can either be grabbing coffee together, or having a more formal scheduled one-on-one.
Keep notes on these meetings - and encourage your reports to do the same. Note commitments made, those that are made good on, those that aren't. When folks volunteer to take on additional responsibility, and when they shirk the responsibility they have. When you end up writing reviews, these notes are useful to justify pay rises or lack thereof.
Finally, one of the hardest things for first time managers is the transition from "one of the team" to "running the team." It's especially tricky if you manage anyone with whom you have a personal relationship (friendship, dating, etc.) The generally safe thing is "don't." But my experience is that overlapping relationships are maintainable, but only with early explicit agreement on both sides.
I've worked for, and managed, friends a number of times over the years - and the very first conversation, either way, has been something like:
That's what I had to do. No amount of distribution switching is going to help. It's all the same stuff underneath.
I'd had nothing but trouble with the Nvidia card (and drivers) in my wifes machine, so when it was time to upgrade my graphics card, I went ATI...
I bought a Radeon 9600XT - performed great under windows, oops'ed the kernel reliably under Linux. Took me a month of occasional debugging to figure out it was related to my running an SMP machine (dual PIIIs, not a dual-core). I submitted the bug to ATI, along with the kernel oops, and waited...
About 3 months later they released a new driver build - the release notes didn't mention anything about an SMP crash, but I tried them all the same. When the kernel oops'ed, I made the decision to ditch the ATI card.
Sold it to a colleague who was windows only and replaced it with a GeForce FX 5700U (the card that seemed to have the closest performance in the price range). The drivers have been solid and perform well. I've seen none of the crashes that anti-Nvidia folks claim occur so often, not even under heavy load on a dual proc machine.
So as much as I hate to say it - in my experience the best solution is to get rid of the ATI card and buy something from NVidia. The hardware is brutish and inelegant, but the drivers work.
I got a powerbook three weeks ago - and have been using linux since.99p11 or so.
Let me start by saying that the powerbook hardware is sweet. The driving factor behind the purchase was that I wanted a good screen (I have the 15"), large disk, lots of RAM, and for the package to weigh less than 6 lbs. I looked for a long time and failed to find a good solution in the intel space. (HP makes a machine that's really close - but has crappy intel shared memory graphics.)
My biggest gripes with OSX are around customizability (i.e., it aint).
Focus-follows-mouse? Sorry, no can do (yea, I know there's a virtual desktop program that, for $40, will do a hacked up focus-follows-mouse, that breaks apps like Firefox and Thunderbird - no thank you).
Multi-screen support? Sucks - someone please explain why it makes sense to have the menu bar on screen A while the application window is on screen B? Shouldn't the menu bar at least move to the screen with the active window? Similarly, certain dialogs insist on opening on the primary screen - even if the active app window is on a different one. Talk about annoying. It's seems fairly obvious that no one @ Apple actually did usability testing on their multi-monitor support.
While I appreciate the design goal of sheets (modal dialogs that are tied to the parent window border) the inability to get a modal dialog out of the way so you can intelligently answer the question it's posing can be terribly frustrating (particularly bad in Thunderbird's spellcheck).
Oh, and why the hell is the setting for default browser/mailer hidden in Safari/Mail? Seems like a fairly obvious system-level property to me.
Turning on Full Keyboard Navigation really doesn't mean full keyboard navigation. Non text-entry widgets never get keyboard focus - so selecting items from drop-down lists, or toggling checkboxes/radio buttons requires reaching for the mouse. Irksome.
Package management is hideous and hacky. The.app structure they adopted from NeXT Step is fairly cool, and uninstalling an app that you've dragged and dropped into Applications is easy - not so with packages (.pkg) that are installed with apples installer. They potentially sprinkle stuff in many places (Applications, Library, etc.) and there's no provided means to un-install them. Fortunately there's an opensource tool (OSXPM) that mostly bridges that gap.
I have a friend at Apple, and when I asked him these (and other) questions his basic answer was: "just use it - you'll adapt."
There are parts of OS X that are really good - and that Linux would do well to adopt. Wireless networking just works - and configuration is painless. Dynamic reconfiguration when screens are added/removed - gads I wish X could do that (I've gotten close using some the MergedFB support in the ATI driver, custom shell scripts and the xrandr extension - but it requires manual intervention). Oh, and it's certainly full of eye candy.
Essentially, OS X is fine as long as "think different" means "think like Apple" - but if you want your machine to adapt to *you* rather than the other way around, it falls short.
So I'll probably download the live CD and give it a whirl. I'm watching the evolving Fedora PPC support with great interest.
I had bought a 9600XT after reading several reviews that gave it outstanding marks for "fps/$." Some OpenGL apps were fine (and plenty fast), but others (notably Wine) crashed my box. Turns out the drivers were oopsing when running an SMP kernel on SMP hardware.
After reporting the (reproducable) kernel oops, I waited 7 months for the next driver release in the hopes it would be fixed. No such luck. I ditched my 9600XT and bought a GeForce 5700U - it just works.
What's sorta ironic is that the 5700U (a massive card, with a huge fan, several passive heatsyncs that requires it's own power input) is in the same "performance ballpark" on most tests (and significantly underperforms on some, like pixel shading, IIRC) as the 9600XT (a small card, with a small fan, and no passive heatsyncs).
It's a great contrast between design elegance and brute force. If ATI could write working drivers...
It appears that at least some of the Diebold machines DO have internal printers, but Diebold has been notably coy about mentioning that, and indeed has been strangely resistant to the whole idea of verifiability.
True, in fact Cringly wrote about this in his March 11 column
The temp. range in which it occurs (and is sustainable) is specific to each liquid. Also, AFAIK, it also doesn't occur if you heat the body while in constant contact with the liquid.
"It has everything to do with it," said Gandalf. "You do not know the real peril yet; but you shall. I was not sure of it myself when I was last here; but the time has come to speak. Give me the ring for a moment"
Frodo took it from his breeches-pocket, where it was clasped to a chain that hung from his belt. He unfastened it and handed it slowly to the wizard. It felt suddenly very heavy, as if either it or Frodo himself was in some way reluctant for Gandalf to touch it.
Gandalf held it up. It looked to be made of pure and solid gold. "Can you see any markings on it?" he asked.
... For a moment the wizard stood looking at the fire; then he stooped and removed the ring to the hearth with the tongs, and at once picked it up. Frodo gasped.
Check out Subclipse. I haven't tried it myself (since I don't use subversion yet). It looks fairly feature complete though.
It may be feature complete, but it's Windows only (a linux version has been planned for some time, but there's been no visible progress). I've been using eclipse for both Java and C/C++ under linux for some time - and the lack of subversion support is one of the key reasons I'm still using CVS.
The Neuros HD was reviewed a few days ago in the Mercury News - and the author had some less than stellar things to say about it. The software issues he mentioned will, I'm sure, be eventually worked out - but apparently the unit uses USB 1 (gack!) rather than Firewire or USB2.
Anyone care to compute out how long it would take to actually fill that 20GB hard drive that USB 1 speed?
I agree he is playing fair. He made it known well ahead of time that there would be two versions, when they would be released, and what was to be included on them.
Agree completely. I would have liked (in a perfect world) for them to mention that upcoming release in the promotions for this release - i.e. at the end of the radio ad, in typical "car-ad" small print "and look for the special 4 disc extended release in november," or something similar.
As for myself - we had a number of friends who (for whatever reason - typically kids) missed it in the theatre, we bought it and have had folks over to watch it - we've definitely gotten our $20 out of it.
When the the 4 disc version is released in November, I intend on donating the two disc version to my local public library.
If a company is going to dump a product, they should open source it.
Great theory - it'll never work in the large. Large projects are often encumbered with 3rd party licenses (like for crypto libs, or O-R mapping tools, or the ever despised^?popular RogueWave components) which can't be extracted to produce a usable body of code and clearly can't be opensourced...
Our God's the FUN God! Our God's the SUN God! RA! RA! RA!
Ok, that was damn funny... If only I had mod points.
Re:I don't even know the situ. and I see the bias!
on
Two Helpings of WINE
·
· Score: 1
However, changing the license in this way was at least impolite. Possibly there were discussions that I didn't notice, but if so, then nobody's brought them up since. I think it likely that any discussions were basically "private". So neither side had justified their position to the public, except via PR releases.
There certainly was discussion on changing the Wine license - and lots of it - on the wine development lists - and the topic appeared in KC Wine as far back as December of 1999.
That's not to say the change was right or wrong, just that it was discussed and held for open vote among the Wine developers.
It's also interesting to note that in his initial (lengthy) message on the subject, Gavriel from Transgaming had this to say on the LGPL:
Using the LGPL may limit the abilities of those who need to work on code that cannot legally have source revealed.
One of the other non-DirectX things that we have spent significant amount of effort on is copy protection. We have extended Wine to support both SafeDisc and SecuRom protected programs. For the moment, our work on this code is not even in our AFPLed tree. Until we have a chance to make a legal determination on whether or not releasing the source code would violate the US DCMA, we have little choice but to keep it secret.
If Wine was LGPLed, we might not have the option to distribute this code at all, which would thus severly limit the utility of our entire endeavour. It's not hard to imagine other commercial efforts where similar issues might occur.
And Jeremy (of Codeweavers - the folks being villified in this article) went on record with this statement:
With all that, speaking on behalf of CodeWeavers, I would neither call for nor oppose a switch to the LGPL. Since that change would impact me and my customers somewhat slowly, I think I could make the necessary adjustments in time. The most important thing is for us to continue to have a vital and thriving Wine community.
Finally, speaking strictly on a personal basis, and with no corporate considerations whatsoever, I would welcome a change to the LGPL; I have always preferred it to BSD style licenses (and to the GPL, for that matter); with LGPL projects, I feel more certain that I know exactly where I stand and how my code will be used.
Not that facts have ever changed the course of a/. debate, but I figured I'd throw some onto the table...
In the interest of full disclosure, I've got licences for both Codeweavers Crossover products (plugin and office) and am a Transgaming subscriber - I'm supporting both companies - but, more importantly, I'm hoping eventually to replace the three (!) different wine installations on my machine with a single install - something that won't be possible 'till all the children in this particular playground start to get along.
As for original ideas... um...Han shooting first was pretty cool. But then he changed that in the SE release and claimed it was an editing mistake.
Though I wouldn't argue it was a terribly original idea - I would argue that it was a fairly central demonstration of Han's character - of who he was, at heart; a scoundrel who had no moral problem using pre-emptive violence to save his own skin.
I liked much of the stuff added to the SE - but that change felt like blatant revisionist history in the interest of political correctness.
FWIW: I've done this sort of thing several times (each time I do a major upgrade on a machine) - and in almost every case, I hit the local parts swap, pick up the missing parts (in this case probably to the tune of $50 or so - small IDE drive, basic CDROM, and floppy) and donate a working machine rather than a collection of parts. The tax writeoff is nice, of course, but the knowledge that I've given someone a working machine is better.
As for destinations - I give local schools and libraries first shot at them.
Slashdot Mirror
That depends on your priorities. "Real" RAID cards lock the raid meta-data to a specific vendor (sometimes to a specific line). So if your card dies, you're forced to buy another one. If you want to upgrade (more ports, better RAID processor), same story - you're vendor locked.
Software RAID is slower (though a reasonable system doing just software RAID has no trouble outperforming a cheap "real" RAID card) but you can move the drives into another system running the same software and have access to the data.
I had data across a couple of software-raided drives under linux and a couple non-raided external USB drives, and I knew that eventually I was going to either run out of space, or a drive would fail and I'd lose data.
I started looking, and talking to friends, and decided that what I really wanted was a ReadyNas NV (http://www.infrant.com/products/products_details.php?name=ReadyNAS%20NVPlus) from Infrant (now Netgear) - I knew four satisfied customers. Trouble was cost - about $1100.
So I decided to try it on the cheap, and picked up an NSLU2 (http://en.wikipedia.org/wiki/NSLU2) which can run a customized linux distro (http://www.nslu2-linux.org/) and do software raid across attached drives.
I experimented with some drives I had on hand and discovered that while it would technically work, it was really only going to be useful for network backups (and fairly slow ones at that). It wouldn't replace the direct attached storage for doing photo storage (and editing) as it's only 100Mb Ethernet attached, and a fairly underpowered processor that mostly keeps up doing raid, as long as it's just mirroring. It is, however, functional, and more reliable in theory than non-RAIDED drives.
The total cost is in line with your budget - NSLU2s can be had on ebay, and then it's just drives (500GB drives are just over $100), drive enclosures, and some time.
For me, however, the experiment cost me under $100, and made it clear to me that if I wanted good performance, there was a price tag attached - either in dollars or in dollars and space (i.e. build a bigger dedicated raid server). So I resold the NSLU2 and started watching for a good deal on the ReadyNAS.
I found it a month or so ago - at the moment (Q3 of 07), if you spend the $1100 on a ReadyNAS with 2x500GB drives, they'll throw in a 3rd 500GB drive as a purchase incentive. That made it 1TB usable storage for about $1/GB. Still more than raw disk, certainly, but enough to convince me to give it a go.
I've had the ReadyNAS for a month, my home directory's living on it, as are all our digital photos, and media - it "just works." I started with 2x500GB drives, added the third and it grew the volume. I can add one more 500GB drive, which lowers the effective $/GB before the chassis is full. If 4x500GB isn't big enough one day, I can replace each drive, one at a time, with larger drives and the volume will expand to fit once all drives match.
Debugging the Development Process: http://www.amazon.com/Debugging-Development-Proces s-Practical-Strategies/dp/1556156502
Peopleware:
http://www.amazon.com/Peopleware-Productive-Projec ts-Tom-DeMarco/dp/0932633439
And think about those managers over the course of your career whom you've enjoyed working for, and felt most productive under. If you can - ask them for advice. If any of them were, or are, in the same company - that's even better.
Finally, many companies have "intro to management" courses offered by HR - sometimes they're mandatory when you're promoted into a role with direct reports, sometimes they're not. Take one, either way. You may not learn much, but at least it should give you a sense of the "management process" in your company from a perspective you may not have glimpsed before.
Although you didn't ask for them, since I was in a similar position a few years ago, I'll offer a few specific suggestions and observations.
First of all, your management responsibilities won't just do themselves - they'll take time. Seems obvious - but I've seen (and worked for) first time managers who figured they could just go on writing code, and the rest would "sort it self out."
Second - you have two bosses - the people you work for and the people who work for you. You're accountable to each of them for different things.
One major job is to facilitate communication in both directions. Make sure the folks working for you know what's expected of them, and how that contributes to the company goals/direction. Similarly, you need to make sure the people you work for understand what your team is doing - what it's challenges are, what it's successes have been. And don't neglect communication within the team. You'll likely eventually be called on to smooth ruffled feathers, or sort out conflicts among your direct reports. It's not fun, but it's part of the job.
Another key role is facilitator. Get obstacles - technical, organizational and otherwise - out of your team's way *before they're stymied by them* so they can execute.
One way to do this is to make sure you talk to everyone working for you regularly - at least once a week, more often if the environment is "highly dynamic" (i.e. sh*t changes quickly). Find out how they're doing - and, most importantly, what they need from you so they can get it done.
If your management role includes "pay and review" responsibilities (as opposed to "just" technical leadership) - get to know the appropriate folks in HR. Most companies have a pay grade system that basically defines compensation latitude - learn it, and learn where your reports are on the scale.
Depending on the make up of the team, and the "formality" of the environment, this can either be grabbing coffee together, or having a more formal scheduled one-on-one.
Keep notes on these meetings - and encourage your reports to do the same. Note commitments made, those that are made good on, those that aren't. When folks volunteer to take on additional responsibility, and when they shirk the responsibility they have. When you end up writing reviews, these notes are useful to justify pay rises or lack thereof.
Finally, one of the hardest things for first time managers is the transition from "one of the team" to "running the team." It's especially tricky if you manage anyone with whom you have a personal relationship (friendship, dating, etc.) The generally safe thing is "don't." But my experience is that overlapping relationships are maintainable, but only with early explicit agreement on both sides.
I've worked for, and managed, friends a number of times over the years - and the very first conversation, either way, has been something like:
"we're friends, and I'd like to stay friends, b
I'd had nothing but trouble with the Nvidia card (and drivers) in my wifes machine, so when it was time to upgrade my graphics card, I went ATI...
I bought a Radeon 9600XT - performed great under windows, oops'ed the kernel reliably under Linux. Took me a month of occasional debugging to figure out it was related to my running an SMP machine (dual PIIIs, not a dual-core). I submitted the bug to ATI, along with the kernel oops, and waited...
About 3 months later they released a new driver build - the release notes didn't mention anything about an SMP crash, but I tried them all the same. When the kernel oops'ed, I made the decision to ditch the ATI card.
Sold it to a colleague who was windows only and replaced it with a GeForce FX 5700U (the card that seemed to have the closest performance in the price range). The drivers have been solid and perform well. I've seen none of the crashes that anti-Nvidia folks claim occur so often, not even under heavy load on a dual proc machine.
So as much as I hate to say it - in my experience the best solution is to get rid of the ATI card and buy something from NVidia. The hardware is brutish and inelegant, but the drivers work.
I got a powerbook three weeks ago - and have been using linux since .99p11 or so.
.app structure they adopted from NeXT Step is fairly cool, and uninstalling an app that you've dragged and dropped into Applications is easy - not so with packages (.pkg) that are installed with apples installer. They potentially sprinkle stuff in many places (Applications, Library, etc.) and there's no provided means to un-install them. Fortunately there's an opensource tool (OSXPM) that mostly bridges that gap.
Let me start by saying that the powerbook hardware is sweet. The driving factor behind the purchase was that I wanted a good screen (I have the 15"), large disk, lots of RAM, and for the package to weigh less than 6 lbs. I looked for a long time and failed to find a good solution in the intel space. (HP makes a machine that's really close - but has crappy intel shared memory graphics.)
My biggest gripes with OSX are around customizability (i.e., it aint).
Focus-follows-mouse? Sorry, no can do (yea, I know there's a virtual desktop program that, for $40, will do a hacked up focus-follows-mouse, that breaks apps like Firefox and Thunderbird - no thank you).
Multi-screen support? Sucks - someone please explain why it makes sense to have the menu bar on screen A while the application window is on screen B? Shouldn't the menu bar at least move to the screen with the active window? Similarly, certain dialogs insist on opening on the primary screen - even if the active app window is on a different one. Talk about annoying. It's seems fairly obvious that no one @ Apple actually did usability testing on their multi-monitor support.
While I appreciate the design goal of sheets (modal dialogs that are tied to the parent window border) the inability to get a modal dialog out of the way so you can intelligently answer the question it's posing can be terribly frustrating (particularly bad in Thunderbird's spellcheck).
Oh, and why the hell is the setting for default browser/mailer hidden in Safari/Mail? Seems like a fairly obvious system-level property to me.
Turning on Full Keyboard Navigation really doesn't mean full keyboard navigation. Non text-entry widgets never get keyboard focus - so selecting items from drop-down lists, or toggling checkboxes/radio buttons requires reaching for the mouse. Irksome.
Package management is hideous and hacky. The
I have a friend at Apple, and when I asked him these (and other) questions his basic answer was: "just use it - you'll adapt."
There are parts of OS X that are really good - and that Linux would do well to adopt. Wireless networking just works - and configuration is painless. Dynamic reconfiguration when screens are added/removed - gads I wish X could do that (I've gotten close using some the MergedFB support in the ATI driver, custom shell scripts and the xrandr extension - but it requires manual intervention). Oh, and it's certainly full of eye candy.
Essentially, OS X is fine as long as "think different" means "think like Apple" - but if you want your machine to adapt to *you* rather than the other way around, it falls short.
So I'll probably download the live CD and give it a whirl. I'm watching the evolving Fedora PPC support with great interest.
I had bought a 9600XT after reading several reviews that gave it outstanding marks for "fps/$." Some OpenGL apps were fine (and plenty fast), but others (notably Wine) crashed my box. Turns out the drivers were oopsing when running an SMP kernel on SMP hardware.
After reporting the (reproducable) kernel oops, I waited 7 months for the next driver release in the hopes it would be fixed. No such luck. I ditched my 9600XT and bought a GeForce 5700U - it just works.
What's sorta ironic is that the 5700U (a massive card, with a huge fan, several passive heatsyncs that requires it's own power input) is in the same "performance ballpark" on most tests (and significantly underperforms on some, like pixel shading, IIRC) as the 9600XT (a small card, with a small fan, and no passive heatsyncs).
It's a great contrast between design elegance and brute force. If ATI could write working drivers...
True, in fact Cringly wrote about this in his March 11 column
The temp. range in which it occurs (and is sustainable) is specific to each liquid. Also, AFAIK, it also doesn't occur if you heat the body while in constant contact with the liquid.
Frodo took it from his breeches-pocket, where it was clasped to a chain that hung from his belt. He unfastened it and handed it slowly to the wizard. It felt suddenly very heavy, as if either it or Frodo himself was in some way reluctant for Gandalf to touch it.
Gandalf held it up. It looked to be made of pure and solid gold. "Can you see any markings on it?" he asked.
It may be feature complete, but it's Windows only (a linux version has been planned for some time, but there's been no visible progress). I've been using eclipse for both Java and C/C++ under linux for some time - and the lack of subversion support is one of the key reasons I'm still using CVS.
Blipverts - here we come!
Anyone remember CHiRP? It seemed like such a good idea at the time...
just curious if anyone out there has gotten it to run with an "older" Radeon card using the XFree radeon drivers?
glxgears (and Neverwinter Nights) run just fine - but et just presents a black screen and goes nowhere.
Anyone?
Seems that while SCO has stopped serving the bits, planetmirror still has this stuff laying about:
The click-through license:
and the files that live behind it (accessible without accepting the license, no less)
5th Edition UNIX
6th Edition UNIX
7th Edition UNIX
Mini UNIX
UNIX System III
UNIX 32V
I haven't laughed out loud at a /. post in ages - the people I work with are looking at me like I'm a mad man...
That's awesome...
Thanks.
Anyone care to compute out how long it would take to actually fill that 20GB hard drive that USB 1 speed?
And here I thought I was the only one who had the urge to be violently ill at that suggestion...
:)
Mulled Wine - absolutely, made with Mead - even better
Agree completely. I would have liked (in a perfect world) for them to mention that upcoming release in the promotions for this release - i.e. at the end of the radio ad, in typical "car-ad" small print "and look for the special 4 disc extended release in november," or something similar.
As for myself - we had a number of friends who (for whatever reason - typically kids) missed it in the theatre, we bought it and have had folks over to watch it - we've definitely gotten our $20 out of it.
When the the 4 disc version is released in November, I intend on donating the two disc version to my local public library.
Ok, that was damn funny... If only I had mod points.
There certainly was discussion on changing the Wine license - and lots of it - on the wine development lists - and the topic appeared in KC Wine as far back as December of 1999.
That's not to say the change was right or wrong, just that it was discussed and held for open vote among the Wine developers.
It's also interesting to note that in his initial (lengthy) message on the subject, Gavriel from Transgaming had this to say on the LGPL:
And Jeremy (of Codeweavers - the folks being villified in this article) went on record with this statement:Not that facts have ever changed the course of a /. debate, but I figured I'd throw some onto the table...
In the interest of full disclosure, I've got licences for both Codeweavers Crossover products (plugin and office) and am a Transgaming subscriber - I'm supporting both companies - but, more importantly, I'm hoping eventually to replace the three (!) different wine installations on my machine with a single install - something that won't be possible 'till all the children in this particular playground start to get along.
But at only 40Meg per hip zip, that's barely an album per disk at "normal" (VBR) encode rates. Seems hardly worth it.
Though I wouldn't argue it was a terribly original idea - I would argue that it was a fairly central demonstration of Han's character - of who he was, at heart; a scoundrel who had no moral problem using pre-emptive violence to save his own skin.
I liked much of the stuff added to the SE - but that change felt like blatant revisionist history in the interest of political correctness.
As for destinations - I give local schools and libraries first shot at them.
Just my .02