At the very least, it's horrible publicity for Microsoft to look as though the only way they can get users to use their operating systems is by stuffing said operating systems down people's throats, especially while trying to prove that they're not a monopoly.
Who the heck buys CDs just for the lyrics, anyways? If I was a musician, I would _want_ my lyrics posted all over everywhere; it's free advertising. Musicians are trying to sell CDs and concert tickets, not the little book with the lyrics on it in the cover. How many bands these days have even halfway intelligent lyrics? Stupid music industry types... Some people need to learn to choose their battles, and stop fighting the consumers...
I don't understand why RedHat insists on defaulting to the Win95 wanna-be desktop. You're right; the AfterStep that ships with it is _much_ better looking than the default. Although we should give them credit for making it easy enough to switch...
I am running a legacy EtherExpress Pro 10+ card on a PCI machine, and for some reason the IRQ and I/O port settings I choose using the DOS utilities don't carry over when I boot into Linux. I can set the IRQ to, say, 10 using the DOS utility, but if I try to tell eepro.o to use those settings it won't work. However, when I just let eepro.o probe for the card, it sets it up on IRQ 7 for some reason and works fine. Have you tried that yet? Taking all the hard-coded irq and i/o port stuff out? Other than that, I would take all the advice listed above (ping the loopback, ping its own address, etc.) And one other thing -- did you check the cabling? In my experience a surprising number of network problems end up being that.
On a side note, why is the EtherExpress Pro driver disabled in the kernel 2.2.0pre4 make xconfig? The code's all there, but for whatever reason I had to go in and edit the.config file by hand to make it compile in eepro.c. Or am I missing something here?
Slashdot Mirror
At the very least, it's horrible publicity for Microsoft to look as though the only way they can get users to use their operating systems is by stuffing said operating systems down people's throats, especially while trying to prove that they're not a monopoly.
Who the heck buys CDs just for the lyrics, anyways? If I was a musician, I would _want_ my lyrics posted all over everywhere; it's free advertising. Musicians are trying to sell CDs and concert tickets, not the little book with the lyrics on it in the cover. How many bands these days have even halfway intelligent lyrics? Stupid music industry types... Some people need to learn to choose their battles, and stop fighting the consumers...
I guess I should bathe less regularly, then.
I don't understand why RedHat insists on defaulting to the Win95 wanna-be desktop. You're right; the AfterStep that ships with it is _much_ better looking than the default. Although we should give them credit for making it easy enough to switch...
I am running a legacy EtherExpress Pro 10+ card on a PCI machine, and for some reason the IRQ and I/O port settings I choose using the DOS utilities don't carry over when I boot into Linux. I can set the IRQ to, say, 10 using the DOS utility, but if I try to tell eepro.o to use those settings it won't work. However, when I just let eepro.o probe for the card, it sets it up on IRQ 7 for some reason and works fine. Have you tried that yet? Taking all the hard-coded irq and i/o port stuff out? Other than that, I would take all the advice listed above (ping the loopback, ping its own address, etc.) And one other thing -- did you check the cabling? In my experience a surprising number of network problems end up being that.
.config file by hand to make it compile in eepro.c. Or am I missing something here?
On a side note, why is the EtherExpress Pro driver disabled in the kernel 2.2.0pre4 make xconfig? The code's all there, but for whatever reason I had to go in and edit the