I agree with you that an original name does not hurt. See gnucash, for example. It is not called GQuiken or GMoney, and it still does a good description of its use (and is an excellent product:).
But I disagree regarding GAIM. It's a clone product whose operations depends exclusively on the AIM protocol, so the name makes sense. It's the same with licq and other icq clones. Better yet, we have jabber, that has its own name (as it doesn't depend on the icq or aim protocol) and implementations (like gabber, kabber or whatever).
That is a good initiative, but they are certainly not the first one to have it.
Doesn't 2600 use donations to pay their lawyers and legal fees?
What about FSF?
I also agree that Konqueror is faster and lighter (I use it the most I can, even though I don't use kde), but if we want to fight the IE dominance, we need a standards compliant browser that runs in Winblows/Mac, as these are the platform most web designers use. You can't force a designer to make code Konqueror compatible (the main problem resides in the javascript realm, where "We estimate that 90% of the web's script work with Konqueror"); it's already hard to convince them to be Mozilla-compatible (as they are spoiled with the 'easier way you can do stuff with IE').
Ideally, we should be able to use konqueror as primary browser (due to its performance), and have Mozilla as a backup, for the pages that doesn't work with konqueror (yet). Unfortunately, this scenario is not possible yet, as not all pages work with Mozilla neither, so we still need that crappy Navigator 4.7 as the last resort:(
Is this a ready-to-use, more stable version or just a time-to-market urging version, to help Eazel problems?
KDE 2.1 took a while to be ready, but they did a good job (mainly at the konqueror front).
Hmm, I thought watch was a standard tool, but it belongs to procps:
#rpm -qf/usr/bin/watch
procps-2.0.7-8
It is a very useful tool, that "executes a program periodically, showing output fullscreen"".
Anyway, if you don't have it, just the date +%s should work...
Thanks for the suggestion, but that is not the point.
The point is, it should be easier to update packages, once they are available.
In your case, you had to remove the older version and add the new one. In my case, I tried many options and sticked to a 8.0 beta upgrade (which I must say, worked really fine).
Maybe the worst problem with the rpm package is that it doesn't have a recursively upgrade of dependencies. I tried to upgrade the kde packages (from the cooker), but they required glibc 2.2. Then I tried to upgrade glibc 2.2 too, but about a hundred of packages depended on it, and so on... If apt-get solves this problem, that's a good reason to migrate to a debian-like installation...
If you find that the instructions are unclear, the choices ambiguous, the order illogical, or something like that, I could see the problem. But, the only "problem" you describe is that it's text based.
I'm sorry, I wasn't clear. The problem is not really being text-based, but the overall organization of packages is a total mess. Slackware was text-based (maybe it's still is, but I don't know as I don't use it), but it's installation was not a nightmare at all.
I agree when people say that once you get used to the Debian installation, it becomes easy (in fact, that interactive configuration of packages is really cool). I just don't have the patience to learn it (I give it a try once in a while, but I always give up at the end:). And I might be wrong, but the installation procedure of the last version I tried (2.2) looked the same as the first one I tried many years ago (0.9 or so, I think).
I've been using Mandrake for years now and, although it's a good distribution, it's hard to upgrade the big guys (like X 4.0.3 or kde 2.1.1).
I recently tried debian 2.2 to try out the famous apt-get, but I think it's text based installation is a pain in the ass (and I'm not even a newbie - I started with slackware many years ago).
In my opinion, a distro with an easy installation system and a smooth way to upgrade is the way to go. Will Progeny do it? I hope so...
Interoperability is a key competitive strength..... Providing ways to plug into those other operating systems - both at a system level (e.g. files, user directories etc.) and at an application level (e.g. data formats) is essential.
Slashdot Mirror
I agree with you that an original name does not hurt. See gnucash, for example. It is not called GQuiken or GMoney, and it still does a good description of its use (and is an excellent product :).
But I disagree regarding GAIM. It's a clone product whose operations depends exclusively on the AIM protocol, so the name makes sense. It's the same with licq and other icq clones. Better yet, we have jabber, that has its own name (as it doesn't depend on the icq or aim protocol) and implementations (like gabber, kabber or whatever).
That is a good initiative, but they are certainly not the first one to have it.
Doesn't 2600 use donations to pay their lawyers and legal fees?
What about FSF?
>IT'S A FILE MANAGER. see? see how stupid that sounds?
If that was so simple, Micro$#&t would not being sued for integrating its "file manager" with its "OS"!
...until next week. :)
This kind of news doesn't makes sense in a Friday night (especillay not it being April 1st
I also agree that Konqueror is faster and lighter (I use it the most I can, even though I don't use kde), but if we want to fight the IE dominance, we need a standards compliant browser that runs in Winblows/Mac, as these are the platform most web designers use. You can't force a designer to make code Konqueror compatible (the main problem resides in the javascript realm, where "We estimate that 90% of the web's script work with Konqueror"); it's already hard to convince them to be Mozilla-compatible (as they are spoiled with the 'easier way you can do stuff with IE').
:(
Ideally, we should be able to use konqueror as primary browser (due to its performance), and have Mozilla as a backup, for the pages that doesn't work with konqueror (yet). Unfortunately, this scenario is not possible yet, as not all pages work with Mozilla neither, so we still need that crappy Navigator 4.7 as the last resort
Is this a ready-to-use, more stable version or just a time-to-market urging version, to help Eazel problems? KDE 2.1 took a while to be ready, but they did a good job (mainly at the konqueror front).
Hmm, I thought watch was a standard tool, but it belongs to procps:
/usr/bin/watch
#rpm -qf
procps-2.0.7-8
It is a very useful tool, that "executes a program periodically, showing output fullscreen"".
Anyway, if you don't have it, just the date +%s should work...
Someone once mentioned that on the SVLUG list, as it is also close to the Linux 10th birthday, in August.
... with the command:
watch -n 1 date +%s
or better yet:
watch -n 1 'echo "The time is near: `date +%s`"'
If you haven't mentioned, we would not even remember such a thing still exists! Here we go again...
Thanks for the suggestion, but that is not the point.
The point is, it should be easier to update packages, once they are available.
In your case, you had to remove the older version and add the new one. In my case, I tried many options and sticked to a 8.0 beta upgrade (which I must say, worked really fine).
Maybe the worst problem with the rpm package is that it doesn't have a recursively upgrade of dependencies. I tried to upgrade the kde packages (from the cooker), but they required glibc 2.2. Then I tried to upgrade glibc 2.2 too, but about a hundred of packages depended on it, and so on... If apt-get solves this problem, that's a good reason to migrate to a debian-like installation...
If you find that the instructions are unclear, the choices ambiguous, the order illogical, or something like that, I could see the problem. But, the only "problem" you describe is that it's text based.
:). And I might be wrong, but the installation procedure of the last version I tried (2.2) looked the same as the first one I tried many years ago (0.9 or so, I think).
I'm sorry, I wasn't clear. The problem is not really being text-based, but the overall organization of packages is a total mess. Slackware was text-based (maybe it's still is, but I don't know as I don't use it), but it's installation was not a nightmare at all.
I agree when people say that once you get used to the Debian installation, it becomes easy (in fact, that interactive configuration of packages is really cool). I just don't have the patience to learn it (I give it a try once in a while, but I always give up at the end
I've been using Mandrake for years now and, although it's a good distribution, it's hard to upgrade the big guys (like X 4.0.3 or kde 2.1.1). I recently tried debian 2.2 to try out the famous apt-get, but I think it's text based installation is a pain in the ass (and I'm not even a newbie - I started with slackware many years ago). In my opinion, a distro with an easy installation system and a smooth way to upgrade is the way to go. Will Progeny do it? I hope so...
Interoperability is a key competitive strength. .... Providing ways to plug into those other operating systems - both at a system level (e.g. files, user directories etc.) and at an application level (e.g. data formats) is essential.
Did somebody say M$ Word?
It was already proved on that Homer 3D Simpsons Halloween episode :)
Not really an easter egg neither, but funny (especially at the first time you realize it :)