Hmm, odd. I seem to remember that the Xfree86 port had an WITH_MATROX_GXX_DRIVER (or somesuch) knob you could twiddle, but looking at the port Makefile, it seems to be gone.
Basically, what it did was download the Matrox Gxx source drivers and build them with X11. It's how I got my dual-head Matrox G400 working under FreeBSD on my other workstation.
Oh well... Guess I'd have to wait with updating X on that box.
Heck, I did a portupgrade after cvsupping my ports and hey presto, new X. Woohoo! What a nice present.
Oh, I have to remark that the nvidia drivers for FreeBSD work surprisingly well under Xfree 4.3. So far no problems. My Geforce 4 is happily screaming away at 1600x1200. Life is good:)
That's because the whole CSS2 spec in impossible to implement fully. It's ambiguous in lots of places. Heck, it's released, but it's not even done yet.
Be glad most modern browsers implement at least a substantial subset of it. It's hard enough as it is.
Kdevelop is an IDE (Integrated Development Environment). I agree 'Meccano' isn't fitting for a compiler (and gcc is a crappy name too, but at least we can call it 'cc' and it will still listen:), but it _is_ fitting for an environment in which you can write code and do GUI design in.
Having a threshold in place (su/sudo-ing to root, run package management program, seeing what cruft it all depends on, and then choose if you want to continue or abort) really takes down the incentive to just haphazardly install software of which you are not really sure you need.
My windows using neighbours call me about twice a month to reformat/reinstall their boxes because they installed so much shareware crap they downloaded from the web on their boxes, it's no longer workable. I once pondered disabling the Adminsitrator user from them, but they aren't my boxes, so I couldn't really do that.
And I'm not focussing on Linux, I mean any UNIX is qualitatively better because you have to do a little more effort to get your machine _just right_, and then stop touching it unless for upgrades/security fixes et al.
I did. He thought it was stupid too. He thought using only _one_ letter to brand was silly. He said if he had his way, he'd prefix everything with 'kde' to make it extra clear it's a KDE app.
But that's just him. It's the tie he wears I guess.
I like app names that actually have to do something with their function, i.e. Rosetta instead of KBabel, or Meccano (you know, the construction kits made from metal strips, screws, gears and bolts you could construct stuff like cranes with etc) instead of boring Kdevelop. You catch my drift.
Simply a sed -e s/c/k/ on a name does not a good appname make. *sigh*
9. Despite the advancements of RPM handling, apt-get from Debian and Gentoo's Portage, users are still not comfortable downloading applications and easily installing them. Either dependancy hell (RPM) when downloading apps from the web, bad interfaces for apt-get (Synaptic is not what I would call "niiice") while Gentoo itself is a nightmare to install for new users, makes the installation of... random Linux applications pretty impossible for new users.
And how is that a bad thing? No more shareware syndrome. Panic installing of random software is a sure fire way to hose your system. Experts know this, lusers don't.
Joe-sixpack windows (and mac) users are very prone to the shareware syndrome, _because_ it's do frigging easy to install random software. Although the uninstallation step on the newest Mac OS is a breeze (drag app into the garbage), under windows, the uninstallation can leave a lot of cruft behind.
Oh well, I'm just ranting. It's just something that caught my eye and couldn't help noticing.
I disagree. The app name shouldn't have _anything_ to do with KDE. It should be enough of a clue if a KDE app sticks to the KDE design guidelines. That way everything has a consistent look and feel, no matter what the name is.
Marketing shmarketing. Yes, you have a point that KDE "friendly names" are probably the only thing a user sees, but THEY follow that silly K-naming abhorration too! Aargh!
In short, the K naming scheme must die. Maybe the KDE project needs something like RFC 2100 but then regarding application names.
I hope KDE drops that whole K-naming gimmick. Although I love KDE, and I use it every day, it's the one thing that I find downright irritating.
So, I plea to everyone that develops new KDE apps, _DON'T_ use that silly K-ism shtick. It was fun the first two versions. It's getting old. Be original for a change, okay? Thanks.
Where was this stuff 10 years ago? I wouldn't have dumped my c64 for that stupid x86 hardware. *sigh*
Seriously, this is very cool stuff. I might dig up my old CBM from the attic to play with this. Now only to be able to hook my oceanic 1541 drive to my PC or my Mac somehow. Or are there ways to simulate a c64 disk drive from a PC with a resoldered C64 disk cable?
How _does_ one transfer software from PC to a real hardware C64 nowadays? Can some people in the know drop some pointers to FAQ's and links?
I thought FreeBSD already had a native java in ports. It used the Sun Linux java vm to compile the classes on FreeBSD. See/usr/ports/java/jdk13
And I installed it over 6 months ago. Am I missing something here? Or was that stuff alpha to begin with (although I never experienced problems with it, it didn't _feel_ beta anyway)
Did you compile KDE with gcc3? Did you enable --enable-final with your build? Did you optimize your CFLAGS? Did you prelink your binaries? More importantly: did your distribution ship KDE with these performance enhancements?
I have to say that KDE 3.1 is pretty snappy on my measly PII 400 with 320 MB of RAM under Gentoo Linux.
My bet is that it will probably be filed in the Total Rubbish And Stupid Headcases cabinet;)
Re:Roots on Windows aren't as l337
on
Windows Rootkits
·
· Score: 1
And what about being able to execute windows scripting host scripts? If you _really_ want to, you can do almost anything from the console prompt in NT, but you'd have to work for it.
Of course, if the admin as so kind to put a c or bourne shell + cygwin on the NT box, heck, you can do whatever you want.
Well, some paranoid person I know once sent me a strace dump of 'ls' and claimed that his system was 'trojaned' because it was reading his password file for 'no apparent reason'. I explained that ls needs to look up the users and groups from the password file/NIS/whatever and uses the getpwent family of calls for it, which can result in/etc/passwd being read.
Of couse that didn't satisfy him. I told him to look in the source of ls(1) and read the getpwent manpage.
It's misconceptions like these that make good stories:)
Slashdot Mirror
Basically, what it did was download the Matrox Gxx source drivers and build them with X11. It's how I got my dual-head Matrox G400 working under FreeBSD on my other workstation.
Oh well... Guess I'd have to wait with updating X on that box.
Oh, I have to remark that the nvidia drivers for FreeBSD work surprisingly well under Xfree 4.3. So far no problems. My Geforce 4 is happily screaming away at 1600x1200. Life is good :)
Bravo, and true too. :)
Whoops SCO. Heh. :)
So you're saying that you agree with SCO and their silly suit?
Yah I know, that was a brainfarted typo you made. Couldn't help reacting :) We all know you ment "original UNIX" instead of "original Linux".
(right, I'll stop...)
Other languages have subroutines too, you know, like BASIC? LCARS in Visual Basic, now _THAT_ is a scary thought. I'd rather debug it in C or in perl.
Be glad most modern browsers implement at least a substantial subset of it. It's hard enough as it is.
Mod this comment up. It hits the nail right on the head.
Thanks for the tip! And yes, that thing _is_ kinda leet, in an oldschool sorta way :)
Kdevelop is an IDE (Integrated Development Environment). I agree 'Meccano' isn't fitting for a compiler (and gcc is a crappy name too, but at least we can call it 'cc' and it will still listen :), but it _is_ fitting for an environment in which you can write code and do GUI design in.
Having a threshold in place (su/sudo-ing to root, run package management program, seeing what cruft it all depends on, and then choose if you want to continue or abort) really takes down the incentive to just haphazardly install software of which you are not really sure you need.
My windows using neighbours call me about twice a month to reformat/reinstall their boxes because they installed so much shareware crap they downloaded from the web on their boxes, it's no longer workable. I once pondered disabling the Adminsitrator user from them, but they aren't my boxes, so I couldn't really do that.
And I'm not focussing on Linux, I mean any UNIX is qualitatively better because you have to do a little more effort to get your machine _just right_, and then stop touching it unless for upgrades/security fixes et al.
It depends how you polarize your view of course :)
Rosetta has no K in there, so I prefer it over KBabel anytime :) Heck, I'd settle for just Babel.
But that's just him. It's the tie he wears I guess.
I like app names that actually have to do something with their function, i.e. Rosetta instead of KBabel, or Meccano (you know, the construction kits made from metal strips, screws, gears and bolts you could construct stuff like cranes with etc) instead of boring Kdevelop. You catch my drift.
Simply a sed -e s/c/k/ on a name does not a good appname make. *sigh*
9. Despite the advancements of RPM handling, apt-get from Debian and Gentoo's Portage, users are still not comfortable downloading applications and easily installing them. Either dependancy hell (RPM) when downloading apps from the web, bad interfaces for apt-get (Synaptic is not what I would call "niiice") while Gentoo itself is a nightmare to install for new users, makes the installation of... random Linux applications pretty impossible for new users.
And how is that a bad thing? No more shareware syndrome. Panic installing of random software is a sure fire way to hose your system. Experts know this, lusers don't.
Joe-sixpack windows (and mac) users are very prone to the shareware syndrome, _because_ it's do frigging easy to install random software. Although the uninstallation step on the newest Mac OS is a breeze (drag app into the garbage), under windows, the uninstallation can leave a lot of cruft behind.
Oh well, I'm just ranting. It's just something that caught my eye and couldn't help noticing.
Marketing shmarketing. Yes, you have a point that KDE "friendly names" are probably the only thing a user sees, but THEY follow that silly K-naming abhorration too! Aargh!
In short, the K naming scheme must die. Maybe the KDE project needs something like RFC 2100 but then regarding application names.
So, I plea to everyone that develops new KDE apps, _DON'T_ use that silly K-ism shtick. It was fun the first two versions. It's getting old. Be original for a change, okay? Thanks.
Seriously, this is very cool stuff. I might dig up my old CBM from the attic to play with this. Now only to be able to hook my oceanic 1541 drive to my PC or my Mac somehow. Or are there ways to simulate a c64 disk drive from a PC with a resoldered C64 disk cable?
How _does_ one transfer software from PC to a real hardware C64 nowadays? Can some people in the know drop some pointers to FAQ's and links?
Guess us slashdot folk threw a wrench in the gears. Hmmm...
And I installed it over 6 months ago. Am I missing something here? Or was that stuff alpha to begin with (although I never experienced problems with it, it didn't _feel_ beta anyway)
I have to say that KDE 3.1 is pretty snappy on my measly PII 400 with 320 MB of RAM under Gentoo Linux.
Saying KDE is slow is fudding.
And where, pray tell can I find the algo's? Right. Never mind.
My bet is that it will probably be filed in the Total Rubbish And Stupid Headcases cabinet ;)
Of course, if the admin as so kind to put a c or bourne shell + cygwin on the NT box, heck, you can do whatever you want.
Of couse that didn't satisfy him. I told him to look in the source of ls(1) and read the getpwent manpage.
It's misconceptions like these that make good stories :)