I have a Fujitsu P-series, and it is a d*amn sweet machine. Just installed RH9 on it, and it blows major chunks (sound broken, XFree86 broken, i8253 timer problems up the wazoo...). I'd love to see these two play better together...
Given that the base HW req's for DV/X are so low (by today's standards), this might let us nip two persistent problems:
1. How do we make old computer hardware useful?
2. How do we get low-cost computers to lots of people?
Set up a bunch of 486s, or P-Is running DV/X, give them each a Gnome or KDE desktop running on some other server, and let people surf, or whatever. One high power machine, lots of terminals.
ObPine:
I remember drooling over DV/X back in the day... I ran DV on my 386DX-25 for two reasons: I had 8MB of RAM and DV let me use ALL of it, and it let me do modem-intensive apps in the background. I never "up" graded to DV/X, though - hadn't the $$, and I fell into Linux in the 0.99 days.
I've always thought the best (=fastest) way to get an ugly law repealed is to make it inconvenient for those it's supposed to benefit.
Case in point: where would Microsoft be w.r.t./. posting the contents of Win2K Kerberos if they had to click-through a license to absolve/. of all responsibility for the content of the site?
/. is software, too - let's use the laws (even the bad ones) to our best advantage.
First, I'll flash my tailfeathers a bit: I started with Slackware back when kernel 1.0 FINALLY came out. Now, I've strayed and come back, in part because I noticed that RedHat & Debian are about twice the size with the same functionality, and in part because I can fit all of the a, n and d series on a Zip disk to install on my Libretto.
One of your stated goals is to keep packages as pristine as possible. I find this to be one of the greatest features of Slackware: I don't need to wait for a package update; I can download the latest source, and pretty much *know* that configure --prefix=/usr && make && make install will do The Right Thing. You also state that you send any changes you need to make back to the developers.
What I wanted to know is, how responsive are developers to this kind of feedback? I recently built & installed something from source (Enlightenment, maybe?) that had a --fsstnd config option, and I thought that just screamed Patrick.
Slashdot Mirror
Is it just me, or does this look almost identical to the (circa 1996) Descent II trailer (Can't seem to get this to work under WinXP)?
The Citroen DS can drive on three wheels. It has many other superb qualities as well.
Since it's a Citroen, I believe that this reinforces the point...
I have a Fujitsu P-series, and it is a d*amn sweet machine. Just installed RH9 on it, and it blows major chunks (sound broken, XFree86 broken, i8253 timer problems up the wazoo...). I'd love to see these two play better together...
-nik
Somebody should point these two at each other.
Given that the base HW req's for DV/X are so low (by today's standards), this might let us nip two persistent problems:
... I ran DV on my 386DX-25 for two reasons: I had 8MB of RAM and DV let me use ALL of it, and it let me do modem-intensive apps in the background. I never "up" graded to DV/X, though - hadn't the $$, and I fell into Linux in the 0.99 days.
1. How do we make old computer hardware useful?
2. How do we get low-cost computers to lots of people?
Set up a bunch of 486s, or P-Is running DV/X, give them each a Gnome or KDE desktop running on some other server, and let people surf, or whatever. One high power machine, lots of terminals.
ObPine:
I remember drooling over DV/X back in the day
THAT'S IT!!!
/. posting the contents of Win2K Kerberos if they had to click-through a license to absolve /. of all responsibility for the content of the site?
I've always thought the best (=fastest) way to get an ugly law repealed is to make it inconvenient for those it's supposed to benefit.
Case in point: where would Microsoft be w.r.t.
/. is software, too - let's use the laws (even the bad ones) to our best advantage.
One of your stated goals is to keep packages as pristine as possible. I find this to be one of the greatest features of Slackware: I don't need to wait for a package update; I can download the latest source, and pretty much *know* that configure --prefix=/usr && make && make install will do The Right Thing. You also state that you send any changes you need to make back to the developers.
What I wanted to know is, how responsive are developers to this kind of feedback? I recently built & installed something from source (Enlightenment, maybe?) that had a --fsstnd config option, and I thought that just screamed Patrick.