It's both the Tru64 code and the "gen 2" HP-UX port. See SF download page.
And yes, I misread your original post as saying that AdvFS was originated in HP-UX. And yes, I'm well aware of how Compaq and HP screwed up DEC and pissed away some great technology. Of course, DEC did a pretty good job of screwing itself. Great engineers; incredibly piss-poor management.
Maybe you should have looked at the link first. The "MythTV devs are working on this" refers to them actually talking to Zap2It, not trying to screen scrape.
While I'm glad they did this, I'd guess it has very little to do with concern for constituents and mostly to do with the cost of implementing it. Can you say "unfunded mandate"? I knew you could.
While I think Nokia is making a mistake (I was about to order an N800, changed my mind when I heard they were dropping support for the 700), lack of support doesn't make a device a "paperweight". I've got an old Audrey that hasn't been updated in 5 years, and it still works fine for the purposes for which I bought it. Sure, it won't get support for the latest flashcrap version, but hell, we Linux people should be used to that by now...
Step 6. Post a hate-page on the web, but stick to the straight facts so they can't sue you for libel.
They can still sue for libel. If you did stick to provable facts, they probably won't win, but you'll spend a lot of time and money in the meantime. So, while it may feel good, decide ahead of time how much you're willing to pay for that good feeling.
...fails to see the difference. Well, not fails, really, but simply once again chooses to misrepresent the FSF and GPL in is long running anti-GPL campaign.
Brett, of course, knows this, but just in case anyone else is confused: Asking that people who take GPL software, modify it, and use it to externally to make money, to then also redsitribute those changes, is nothing at all like DRM. Nobody is asking ASPs to pay money for the software, or for using the software. Nobody is trying to restrict their use of the software. The ASPs are just being asked to follow the spirit of the GPL (sharing), rathing than using an unforseen loophole in the definition of "distribute".
Brett disagrees with the basic goal of the GPL, which is fine, but rather than just saying that, and getting on with his life, he somehow feels obliged to make it his life's work to rid the world of the scourge of the GPL, limiting other people's choices about how they choose to license and distribute code they wrote. Hey, that sounds kinda like DRM...
Ah, yes, the extremely bad idea of running updatedb at low priority surfaces again. Then, instead of finishing during the early morning hours, it lasts all day, interferring with real work. Yes, this is what really happens: we tried this quite a while ago in Debian, and it's a Bad Idea(tm). What happens, IIRC, is that updatedb gets CPU so rarely that other tasks end up flushing the file buffers, and updatedb has to re-read the disk, over and over.
If the problem is that your system isn't on all the time, and anacron is running updatedb when you log in, then just disable updatedb. You probably never use 'locate' anyway.
The Debian way will be to ignore that option, set a default for the option, and/or at best log a message that is easily missed (I don't know Debian so any inaccuracies are unintentional). Gentoo provides a complete default config that can be compared to the existing config.
Nope, that's not the "Debian way" (at least as I, long-time Debian user/developer, see it). Debian
provides a default config file (or files). When the package is upgraded, if the distributed config file is changed (new option, or new value for old option), then one of two things happens:
If the user has NOT changed their local version, just upgrade to the new distributed default. The assumption is if they were happy with the old default, they'll be happy with the new ones. This covers the vast majority of cases.
If the user has changed their local version, offer them the chance to look at the diff, and then either overwrite, don't overwrite, or shell it and deal with by hand. If they choose not to overwrite, then the distributed default is left alongside the real config file for later perusal/integration.
While there are a few obscure corners in the implementation, and individual developers can make mistakes, it mostly works pretty well. The net effect sounds pretty much like your description of the Gentoo way: don't overwrite local changes, and give them something to diff against.
I like RT, and we use it at work, but it's serious overkill for what the original poster wanted. If Trac is too heavyweight, it's unlikely that RT is going to be easier.
Comments won't protect you against bad programmers; they'll write bad/confusing code and comments no matter what.
However, I've found that writing semi-structured comments for each module and function (or object/method, if that's your poison) using something like doxygen is worthwhile for ongoing maintenance. It helps others see what the intent is, and provides a basis for writing unit tests. It even helps the original coder when they come back to the module 6 months later. It's not a matter of whether it's public code, just basic internal docs.
Sorry, no, We're talking about working professionals, who sell their prints for serious sums of money. These people can afford pretty much whatever they want, and a lot of them choose inkjets. You get more choices in materials and better color fidelity if you're willing to take the time and effort. Also, dyesub's make lousy B&W prints.
Or, one could assume that the people involved are interested in having and controlling a successfull small business. Sure, you may not get stupidly rich, but there can be a lot of satisfaction in simply controlling your own destiny and turning a profit every year.
And even if you *do* plan to grow the number of people in the company, the likelyhood is that you're not going to do it in the first six months, and that when you do, you're going to *move*. In the meantime, building up infrastructure is a waste of time. Building a small, reliable net that you don't have to dick around with on a daily basis should be your goal. When it's time to grow, buy new stuff. It will be cheaper and more capable then than it is now.
You keep saying you want his answer: I've told you where to look, and you're too lazy to spend the 60 seconds it would take to find it. Instead, you expect WW to spend the time re-entering the same answer here! And you're calling me arrogant? The mind boggles.
Already asked and answered. Now, you may not agree with him, but the reasoning is there. (Short version for the lazy: he doesn't think the actors pay should be coming out of the coders and designers pockets, and they need to get the collective act together and get their own deal.)
Because nobody has a clue what the colors mean. Because the default colors always include something dreadful like dark blue (unreadable on a black background) or yellow (unreadable on a light background.)
Instead, use
alias ls='ls -Fh'
so that it tacks on "/" on dirs, etc. Yeah, also
not necessarily the most obvious thing in the world, but at least you can read them.
No. And that's not what Tridge was doing either. Tridge didn't sign a license for anything. Tridge was looking at a BK on-disk repository. If you think that's unethical, then you better not be using anything that can read an MS Word file except MS Word.
If you read the thread here, Linus strongly implies that Tridge was not sniffing packets, but analyzing a BK repository on disk:
...I was hoping that that would convince Tridge that trying to
muck around with the internal BK file format was not worth it, and avert
the BK trainwreck.
Larry was ok with the idea to make my export format actually be natively
supported by BK (ie the same way you have "bk export -tpatch"), but Tridge
wanted to instead get at the native data and be difficult about it.
No need for anyone to use BK, and perfectly legitimate as far as I'm concerned.
Slashdot Mirror
It's both the Tru64 code and the "gen 2" HP-UX port. See SF download page.
And yes, I misread your original post as saying that AdvFS was originated in HP-UX. And yes, I'm well aware of how Compaq and HP screwed up DEC and pissed away some great technology. Of course, DEC did a pretty good job of screwing itself. Great engineers; incredibly piss-poor management.
Nitpick: it was never released with HP-UX. It was originally developed by DEC for their Unix product, originally OSF/1, currently called Tru64.
There's this little project of which you may have heard: http://www.kernel.org/
Does the phrase "reinvent the wheel" strike a chord with anyone?
They didn't learn that from TV, they learned it from Dick Cheney.
Maybe you should have looked at the link first. The "MythTV devs are working on this" refers to them actually talking to Zap2It, not trying to screen scrape.
While I'm glad they did this, I'd guess it has very little to do with concern for constituents and mostly to do with the cost of implementing it. Can you say "unfunded mandate"? I knew you could.
While I think Nokia is making a mistake (I was about to order an N800, changed my mind when I heard they were dropping support for the 700), lack of support doesn't make a device a "paperweight". I've got an old Audrey that hasn't been updated in 5 years, and it still works fine for the purposes for which I bought it. Sure, it won't get support for the latest flashcrap version, but hell, we Linux people should be used to that by now...
Step 6. Post a hate-page on the web, but stick to the straight facts so they can't sue you for libel.
They can still sue for libel. If you did stick to provable facts, they probably won't win, but you'll spend a lot of time and money in the meantime. So, while it may feel good, decide ahead of time how much you're willing to pay for that good feeling.
...fails to see the difference. Well, not fails, really, but simply once again chooses to misrepresent the FSF and GPL in is long running anti-GPL campaign.
Brett, of course, knows this, but just in case anyone else is confused: Asking that people who take GPL software, modify it, and use it to externally to make money, to then also redsitribute those changes, is nothing at all like DRM. Nobody is asking ASPs to pay money for the software, or for using the software. Nobody is trying to restrict their use of the software. The ASPs are just being asked to follow the spirit of the GPL (sharing), rathing than using an unforseen loophole in the definition of "distribute".
Brett disagrees with the basic goal of the GPL, which is fine, but rather than just saying that, and getting on with his life, he somehow feels obliged to make it his life's work to rid the world of the scourge of the GPL, limiting other people's choices about how they choose to license and distribute code they wrote. Hey, that sounds kinda like DRM...
Ah, yes, the extremely bad idea of running updatedb at low priority surfaces again. Then, instead of finishing during the early morning hours, it lasts all day, interferring with real work. Yes, this is what really happens: we tried this quite a while ago in Debian, and it's a Bad Idea(tm). What happens, IIRC, is that updatedb gets CPU so rarely that other tasks end up flushing the file buffers, and updatedb has to re-read the disk, over and over.
If the problem is that your system isn't on all the time, and anacron is running updatedb when you log in, then just disable updatedb. You probably never use 'locate' anyway.
The Debian way will be to ignore that option, set a default for the option, and/or at best log a message that is easily missed (I don't know Debian so any inaccuracies are unintentional). Gentoo provides a complete default config that can be compared to the existing config.
Nope, that's not the "Debian way" (at least as I, long-time Debian user/developer, see it). Debian provides a default config file (or files). When the package is upgraded, if the distributed config file is changed (new option, or new value for old option), then one of two things happens:
- If the user has NOT changed their local version, just upgrade to the new distributed default. The assumption is if they were happy with the old default, they'll be happy with the new ones. This covers the vast majority of cases.
- If the user has changed their local version, offer them the chance to look at the diff, and then either overwrite, don't overwrite, or shell it and deal with by hand. If they choose not to overwrite, then the distributed default is left alongside the real config file for later perusal/integration.
While there are a few obscure corners in the implementation, and individual developers can make mistakes, it mostly works pretty well. The net effect sounds pretty much like your description of the Gentoo way: don't overwrite local changes, and give them something to diff against.I like RT, and we use it at work, but it's serious overkill for what the original poster wanted. If Trac is too heavyweight, it's unlikely that RT is going to be easier.
Comments won't protect you against bad programmers; they'll write bad/confusing code and comments no matter what.
However, I've found that writing semi-structured comments for each module and function (or object/method, if that's your poison) using something like doxygen is worthwhile for ongoing maintenance. It helps others see what the intent is, and provides a basis for writing unit tests. It even helps the original coder when they come back to the module 6 months later. It's not a matter of whether it's public code, just basic internal docs.
Sorry, no, We're talking about working professionals, who sell their prints for serious sums of money. These people can afford pretty much whatever they want, and a lot of them choose inkjets. You get more choices in materials and better color fidelity if you're willing to take the time and effort. Also, dyesub's make lousy B&W prints.
Or, one could assume that the people involved are interested in having and controlling a successfull small business. Sure, you may not get stupidly rich, but there can be a lot of satisfaction in simply controlling your own destiny and turning a profit every year.
And even if you *do* plan to grow the number of people in the company, the likelyhood is that you're not going to do it in the first six months, and that when you do, you're going to *move*. In the meantime, building up infrastructure is a waste of time. Building a small, reliable net that you don't have to dick around with on a daily basis should be your goal. When it's time to grow, buy new stuff. It will be cheaper and more capable then than it is now.
You keep saying you want his answer: I've told you where to look, and you're too lazy to spend the 60 seconds it would take to find it. Instead, you expect WW to spend the time re-entering the same answer here! And you're calling me arrogant? The mind boggles.
Already asked and answered. Now, you may not agree with him, but the reasoning is there. (Short version for the lazy: he doesn't think the actors pay should be coming out of the coders and designers pockets, and they need to get the collective act together and get their own deal.)
Most of those .exe are just autoextracting zip files, which 'unzip' can extract just fine.
I'm stunned that there is not more of a response to this news here on Slashdot. OpenLaszlo is a great product.
OpenLaszlo may well be the killer product I'm looking for. I don't know. Why not?
BECAUSE THE ORIGINAL ARTICLE DOESN'T SAY WHAT THE FUCKING PROGRAM DOES!
There. Now I feel better.
I see it might having something to do with Flash, assuming that '.swf' isn't some project specific extension. I dunno.
Because nobody has a clue what the colors mean. Because the default colors always include something dreadful like dark blue (unreadable on a black background) or yellow (unreadable on a light background.)
Instead, use
so that it tacks on "/" on dirs, etc. Yeah, also not necessarily the most obvious thing in the world, but at least you can read them.A corrupt changeset could corrupt every repo it came in contact with: anybody who pulled it gets hit. Somebody smart has to figure out
$35K seems a little high (>300 hours, assuming $100K salary and 2.5x for benefits/overhead (pretty standard)), but not completely unreasonable.
No. And that's not what Tridge was doing either. Tridge didn't sign a license for anything. Tridge was looking at a BK on-disk repository. If you think that's unethical, then you better not be using anything that can read an MS Word file except MS Word.
If you read the thread here, Linus strongly implies that Tridge was not sniffing packets, but analyzing a BK repository on disk:
No need for anyone to use BK, and perfectly legitimate as far as I'm concerned.No, no, no. You welcome our new Overfiend