Slashdot Mirror

I think I remember seeing somewhere that there's a hotkey to switch between apps, but I haven't used that in over a decade in any serious fashion on any OS, so I never took note.

Never design a UI for me then. I use [Alt]-[Tab] to switch between windows, [Alt]-[F1] through [Alt]-[F6] to switch between virtual desktops (or [Alt]-1 through [Alt]-4 when using MSVDM on my WinXP laptop), and [Ctrl]-A-<number> to switch between panes in my screen session. About the only thing I don't multiples are my vim sessions -- I no long split things vertically. (Although I used to, with splitvt .)

I live on hot keys to hop around my highly multiplexed desktop!

And this, perhaps, is why I'll never design a UI for others.... :-)

Yes, I point out that distinction here. And, I commend the correction of a flawed license. It leaves a more palatable choice for those who are adverse to the GPL, yet the work can now be considered compatible with the FSF's licenses. This doesn't negate the fact it leaves the work without protection from abuse, but some people aren't inclined towards the community in that manner.

Software should be free because it is ideas and ideas are non-rivalous resources.

Ah, I think I see where our differences are a little more clearly. I don't consider software ideas. I believe it is commonly held that software is the implementation of ideas. In addition, there is nothing that keeps ideas from being at odds or at rivalry with another except for the integral meaning of those ideas. Case in point would be our disagreement with this issue. But, I believe you meant that "software" (being ideas in your terms) are non-rivalous resources. That's not true.

But at the same time, software should be protected from "theft"

If that is a concern, BSD will not get you there. Use the GPL or LGPL.

and "splintering", something that just can't happen with a non-rivalous resource.

Splintering in itself isn't something to be avoided. Software, to maintain usefulness and creativity in the long run, may require forking. However, without a mechanism to ensure that growth and change be reincorporated back into the original community would bring about another round of the Unix Wars. Rivalry, breathes vitality into variety. Currently, the GPL is a popular mechanism to ensure that forking doesn't become true splintering that can be brought about by unchecked greed and selfishness. Forking is healthy, and allows exploration into newer ideas when older ideas become stale. It is derivation, and that's progress. Using a GPL'd product as the base of your derivation simply means that you acknowledge that your derivations aren't built on air, but on the collective back of the community. Your simply adding your brick to the house built by others. Future brick layers will in turn give back to you as well. No GPL'd product can remain permanently forked as long there is a single person willing to maintain unity. BSD invites permanent forks by rivalrous private corporations seeking vendor lock-in and other expensive surprises for consumers.

Perhaps I don't see the problems produced by Unix that you do, being an old unix hand myself.

That explains the difference of opinion. People have forgotten how Linux was ridiculed by Unix-purists. No self-respecting Unix guru would believe that this little GPL'd missing link (the rest of the GPL'd OS was already made, just missing the kernel) would amount to anything more than a toy. Perhaps with another license, that would have been true. The toy turned out to be a juggernaught under the protection of the GPL.

The common set of tools with a predictable interface meant that I could do work on any system, no matter if it was Linux, Sun, NeXT, IRIX or AIX.

Yes, you can thank GNU and GPL for that: "and thus quite often any machine running a commercial Unix variant would stock GNU versions of utilities to take advantage of these features and to have a standardized version of them."

But I think that you don't really know your history here. The Free BSDs developed about the same time as GNU/Linux in response to a primarily proprietary Unix market. If anyone is responsible for the rise of proprietary Unix, it was Bell Labs and AT&T during the 1970s! (See this history for more details.) Since the Open Source BSDs were stalled due to a lawsuit from 1992-1994 (the same period when

An important distinction. BSD as a license in its original form is incompatible with the GPL and is recommended against usage. However, seeing the error in their ways, the BSD license has been modified and is now compatible with the GPL. Unfortunately, it is still weak and flacid, and I couldn't personally recommend using it in good conscience.

However, the problem is that GPL software is not truly "free." The GPL says, "I own this, and you can't use this except on MY terms."

Nonsense. What you have described is the purpose of any license, including the BSD.

By placing all of the reference works for HTML, and HTTP into the public domain (rather than under a GPL copyright) the web exploded and we have forums like Slashdot.

Please keep in mind that due to the wisdom of Slashdot's developers, you are enjoying the use of a product under the protection of the GPL.

Had Mr. Berners-Lee used the GPL, I have doubts as to whether we would have widespread adoption of the web.

There's no reason to assume that. Your doubts are unfounded.

= 9J =

this.

The next person to write an app with a gratuitous G, K, or X at the beginning (gPornViewer, kFlamewriter, XBitTwiddler) wins scorn, derision, and a swift kick in the ass, absolutely free of charge. Moreso if you use a name that's already taken.

Not sure what you mean by "media library", a Jukebox?

It looks like a media player to me:

Freshmeat project page

Even if that's the old version.

You are new around here, aren't you? You see, open source is all about choice. If I don't like the last digits of pi, I can simply fork the project and make it end the way I want!

Was this Mars clock for the PalmOS anywhere in that explosion of links called a story?

I hope that Apache gets some viable competition.

It's not like there isn't options.

There's several other capable open source (Free Software) http servers available.

I would list a few of the better ones but I can't be bothered sifting through Freshmeat's unmoderated topic entries for http servers. But, by all means, have a look - there are some good ones there.

One that I've seen quite a few updates for on Freshmeat is Thy.

Although the way you relate Apache's monopoly to that of Windows is unfair. Apache is forcing a monoculture because it is that much better than the best of the rest, although the lesser known projects are fighting to be heard because everybody just looks to Apache or IIS for their http server needs.

First of all; he already has logs. He asked about log analysis, not log creation. If you mean to insert a custom php function into every file dologline() or something, that would be a) slow, b) hard-to-impossible to implement on potentially thousands of files c) incompatable if he is using any other server generated pages. And it would miss static objects, images for example.
If you mean, write your own log parser in PHP, again that would be both slow and painfull. PHP isnt paticularly good at text manipulation (which is ironic, seeing as how thats what html generation basicly is). And even if it was as good (or better then), say Perl, Perl has massive amounts of free modules avialable desigined for log analysis, statistics, report generation. PHP is lacking in the third party lib field.

I dont know the state of Activestate (*cough*) so I dont know how well existing, built for Unix, Perl log analysis packages would work. I suspect that many just would. To which, I point out a freshmeat link.

Besides that, there were severe graphics issues, you had to have them in the arcane .wpg format.

Actually .wpg is a well-documented format.

About 14 years ago I remember writing a library for outputting charts in .wpg format. It wasn't too difficult because the docs were quite good. This was for vector graphics, though, which probably isn't what you want. There are free (as in beer) Windows programs which convert other formats to wpg; a quick Google turned up Paint Shop Pro, there must be others. On Linux there is ImageMagick which is also downloadable at no charge.

I use gimp often when I don't want to wait/reboot for photoshop but every single time I do I find myself swearing and cursing at that clueless UI.

Check out the development versions of the GIMP, they've been doing lots of work overhauling the UI. Lots of rearranging of information and functionality, improved ability to customize things, and the dockable windows/tabs similar to Photoshop. They just released a 2.0rc1, so it's nearly stable. It's a little more cutting edge than I'm willing to deal with right now, but if it's driving you up a wall it might be worth checking out.

the one thing on my list of needed software is a SIMPLE photo editor

Well, a quick search on Freshmeat (bookmark it, you'll find it very useful) suggests the following:
If you're not after actual re-touching capability, VIPS might be what you want. (Oh, you are. Oops.)
Well, for the princely sum of US$25, JPhotoBrush Pro looks good (there's a trial version available for download).
For very basic manipulation, IV might do. And if you want something really basic...
If you're willing to play with something considerably less mainstream, PyWiew caught my interest for being pure Python. Does sound a bit esoteric, though.

Finally, you could see for yourself what else is out there. There's more than freshmeat, of course. Like the Linux section of Tucows.

Incidentally, if you have the time to learn it, Gimp can be very useful. Best way (like all *NIX at home learning) is to find someone who knows what they're doing and get them to teach you.

P.S. - If you like Linux, try FreeBSD sometime. Not as popular or well covered, but has advantages too.

HTH, etc.

the one thing on my list of needed software is a SIMPLE photo editor

Well, a quick search on Freshmeat (bookmark it, you'll find it very useful) suggests the following:
If you're not after actual re-touching capability, VIPS might be what you want. (Oh, you are. Oops.)
Well, for the princely sum of US$25, JPhotoBrush Pro looks good (there's a trial version available for download).
For very basic manipulation, IV might do. And if you want something really basic...
If you're willing to play with something considerably less mainstream, PyWiew caught my interest for being pure Python. Does sound a bit esoteric, though.

Finally, you could see for yourself what else is out there. There's more than freshmeat, of course. Like the Linux section of Tucows.

Incidentally, if you have the time to learn it, Gimp can be very useful. Best way (like all *NIX at home learning) is to find someone who knows what they're doing and get them to teach you.

P.S. - If you like Linux, try FreeBSD sometime. Not as popular or well covered, but has advantages too.

HTH, etc.

> But a buddy was showing me some of his favorite GTK themes on his Gnome desktop, and I have to admit that I was impressed. Unfortunately, when I checked to see how many packages I'd have to install for Gnome, there were over 30 -- Mozilla was one of the dependencies!

> So, can any /.ers recommend a... svelt window manager that supports some of this wonderful eye candy?

The eyecandy comes from different places. Applications that use the GTK+ widgets will render with your choice of GTK+ theme, regardles of what window manager you use. The window manager eyecandy will only effect the "decorations" around the windows, though some of them will allow nice customizations for that. The panel and panel applets are provided by GNOME itself.

I use GNOME, but mostly for the panel these days; most of my favorite applications have been cast aside by current GNOME management. However, by using GARNOME I can comment out the builds for crap that I don't want, and almost trivially add back in a cast-aside GTK+ application that I do want.

I use the Sawfish window manager (another cast-aside), customized to look like the old ShinyFusion theme I used to use under Enlightenment, with many virtual desktops to organize my work (I typically stay logged in for six months at a time), and with lots of nifty buttons in the "decorations" to allow things like maximize-vertically, maximize-horizontally, maximize-both, etc.

BTW, you can window shop for eyecandy at themes.org. It is organized according to what component supports a theme (window manager, toolkit, etc.).

I've been doing a lot of thinking lately about better ways to interface with data, generally with searches but it applies to most anything. Naturally this was inspired by reading some Sci-Fi (Saturn's Race by Niven and someone...the book is in the other room.) I got to thinking, the perfect interface I can imagine is much like an actual room, things laid out visually where you would expect them. The normal 2D GUI has always seemed a bit unnatural to me.

When this is applied to searches, I'd like to see information grouping, liek was mentioned in circles, although I want it more organic. tree structures, book shelves, whatever is most appropriate to the current search, and I want them interchangable so I can format my view however I think works best. In a web search, I like the idea of a street. The major sites, amazon,com, ibm.com, etc are all represented by nice looking storefronts, but there are also dark alleys I can do down, to find less reputable places. So in this case, information is arranged by reputation of the source.

I've been doing a lot of thinking lately about better ways to interface with data, generally with searches but it applies to most anything. Naturally this was inspired by reading some Sci-Fi (Saturn's Race by Niven and someone...the book is in the other room.) I got to thinking, the perfect interface I can imagine is much like an actual room, things laid out visually where you would expect them. The normal 2D GUI has always seemed a bit unnatural to me.

When this is applied to searches, I'd like to see information grouping, liek was mentioned in circles, although I want it more organic. tree structures, book shelves, whatever is most appropriate to the current search, and I want them interchangable so I can format my view however I think works best. In a web search, I like the idea of a street. The major sites, amazon,com, ibm.com, etc are all represented by nice looking storefronts, but there are also dark alleys I can do down, to find less reputable places. So in this case, information is arranged by reputation of the source.

You are right, I was wrong. It is not the CoolClean theme but the CleanBig theme As shown here.

I saw it on CNN and it was infact the clean big theme.

How about putting MAME and a few arcade games? ;) KnoppiXMAME.

They are using the Cool Clean window manager theme which was default under redhat 7.x. Compare with this screenshot

Since TCSH is truely free, it is more desirerable on a philisophical basis.

I didn't realize that because I don't use tcsh at all but thanks for pointing out the licensing thing here. And agreed - the GPL is less desirable - really the BSD license is the way to go and I'll continue using it in the future (tropism)

Does tcsh/csh have more "interactive" features than bourne? On the command line? I've never gotten this... what, for example? Thanks

a radio tuner -- I've got one driven by your serial port if you want

"radio VCR" software. There's some free stuff out there.

There's even Linux Options.

Hell block everything except http,https,ftp and DNS.

Great, so you can browse the web and transfer files to insecure sites. But then you can't send or receive mail, make secure file transfer (scp) or shell (ssh) connections, or use any kind of instant messaging client. In other words, if your idea of internet access is limited to passively absorbing web pages, you're covered, but if you were thinking of actually doing anything, it's useless.

If you want to avoid abuse of a tiny wireless network, what you're mostly going to be concerned about is bandwidth consumption. There are quite a few tools for controlling bandwidth consumption under Linux; check them out. If you aren't providing all available bandwidth to the first user who tries to hog it, neither Kazaa abusers or coffee-swilling part-time spammers are going to cause you much grief.

If you want to get a bit more fine-grained than that, there are a buttload of tools to help you monitor what your users are doing, and many of them are scriptable and can set off some kind of alarm if someone is behaving badly.

In any event, you'll offer a much better service if you block only those things which you want to always avoid from the outset, and install tools to help you detect and interrupt the occasional abuse of otherwise innocuous services.

Hell block everything except http,https,ftp and DNS.

Great, so you can browse the web and transfer files to insecure sites. But then you can't send or receive mail, make secure file transfer (scp) or shell (ssh) connections, or use any kind of instant messaging client. In other words, if your idea of internet access is limited to passively absorbing web pages, you're covered, but if you were thinking of actually doing anything, it's useless.

If you want to avoid abuse of a tiny wireless network, what you're mostly going to be concerned about is bandwidth consumption. There are quite a few tools for controlling bandwidth consumption under Linux; check them out. If you aren't providing all available bandwidth to the first user who tries to hog it, neither Kazaa abusers or coffee-swilling part-time spammers are going to cause you much grief.

If you want to get a bit more fine-grained than that, there are a buttload of tools to help you monitor what your users are doing, and many of them are scriptable and can set off some kind of alarm if someone is behaving badly.

In any event, you'll offer a much better service if you block only those things which you want to always avoid from the outset, and install tools to help you detect and interrupt the occasional abuse of otherwise innocuous services.

Modern P2P apps can utilize any port you specify. In fact, they can hunt for an open port and use that. You need a packet shaping application on the router that can throttle bandwidth used by Kazaa and the like so your www users maintain acceptable connectivity.

There are several open source packet shaping solutions available that would work for a coffee shop. Monowall is just one.

You're trolling, right?

Changes:
This release adds support for the latest GeForce FX and Quadro FX GPUs, UBB
and FSAA Stereo, Red Hat Enterprise Linux 3.0, and GLX_SGI_swap_control,
improves XPixamp support, and reduces CPU usage when OpenGL applications
are syncing to vblank.

Complete Changelog/Readme

On my SE P900 (and before that P800, and before that on my Osaris [PSION clone]) I read eBooks on the toilet.

I use gutenmark to convert guten-texts to half-decent html from which I build eBooks using mobi-pocket publisher.

MobiPocket-Reader is the BEST ebook reader in the world (with a free version) supporting more platforms than you can imagine (TRY!)

Mobi have an extensive online library, but also supply a personal publisher tool that can work text, html, and open-ebook format sources (not too strict) to produce ebooks.

I've produced my own ebook of up to 30MB with this tool although it took a long while to build.

Sam

Actually an entirely separate front page section with recent software releases would be a pretty cool thing.

Tried these?

cpufreqd
autospeedstep
cpudyn

Tried these?

cpufreqd
autospeedstep
cpudyn

Tried these?

cpufreqd
autospeedstep
cpudyn

Why is an insignificant little dot-release suddenly front page "news" around here? C'mon, guys, this isn't Freshmeat.

Cheers,
IT

This looks very similar to a little Perl program I recently wrote, although mine doesn't use a CDDB-type system.

Anyway, it's called 'Audiotag,' and is designed to be a decent mass tagger with sane options and supports MP3, OGG, and FLAC.

If you're interested... Audiotag

Anyway, it's called 'Audiotag,' and is designed to be a decent mass tagger with sane options and supports MP3, OGG, and FLAC.

If you're interested... Audiotag

Personally, I use Aerial Chat(configured on my site: http://www.cataromance.com/chat/xindex.php -- the project: http://freshmeat.net/projects/aerialchat/). It's the one I settled on after trying out at least a dozen others. The problem that I've found is either they're difficult to set up or they don't work on everyone's computer. This one has a safe mode for older browsers. What I'd really like to see in a chat is the ability to moderate the chat when we have a guest speaker. Still waiting for that option. If anyone knows of a good one, let me know! :)

There are "commercial-with-source" licenses out there. In fact, there's quite a lot of software so licensed.

Myth: Stopping new development for weeks or months to fix bugs is the best way to produce stable, polished software.

Reality: Stopping new development for awhile to find and fix unknown bugs is fine. That's only a part of writing good software.

I don't see too much disparity here between the "myth" and "reality".

The author was emphasizing the fact that feature freezes *alone* are not enough to ensure the quality of your software. They have their time and they have their place, but they *must* be used in concert with other good development practices in order to be effective.

BTW, the metaphor or whatever "osmosis" is trying to make a point is pretty silly. Osmosis is the transfer of water through a semipermeable membrane.

Err, I've been hearing this metaphor for as long as I can remember. "Learning by osmosis" is a figure of speech used to imply a method of learning whereby the knowledge comes more or less automatically as a side-effect of simply being submerged in the material. The best example I can think of is living in a foreign country to learn their language. The author was trying to illustrate the general futility of trying to understand a program's structure just by skimming its hundreds or thousands of lines of code.

Myth: Bad or unappealing code or projects should be thrown away completely.

Reality: Solving the same simple problems again and again wastes time that could be applied to solving new, larger problems.

This is again true for open and closed source projects. Go look at one of the windows (closed source) freeware/shareware depositories and you will find at least 5-10 programs that all do the same thing more or less. If these were open source projects, I would imagine that there would be a good amount of code reuse going on here.


You imagine incorrectly.

I will say however, that UNIX (I'm generalizing that opensource is more of a UNIX like thing here) in general is a framework and our stuff plays well with one another. We have programs have STDOUT, and STDERR messages that are formatted for external processing and parsing, we have exit statuses in our programs so they can be &&ed and ||ed or test for their success or failure. We have signals, pipes, and sockets for IPC. Look at the number of opensource installs and the wide variety of things that they do and tell me that we are not solving a number of real problems well.

You both miss and prove the author's point at the same time. Unix is a framework, true enough. But the original intent of Unix (and I do mean original, as in "well before it was even called Unix") was as a development environment. Overtime it gradually became more flexible, hackers locked onto it and extended it in ways never dreamed and now, decades later we have an operating system whose design allows it to be used for almost anything from PDAs and embedded systems to the largest mainframes and clusters.

Open source software solves lots of real problems. That's the single reason that it's gaining so much ground these days. But there are a heck of a lot of projects out there that are essentially dead in the water because the developers are concentrating so much on the Next Big Thing rather than actually attempting to solve a problem. See the multitude of web content management projects as an example.

Myth: Stopping new development for weeks or months to fix bugs is the best way to produce stable, polished software.

Reality: Stopping new development for awhile to find and fix unknown bugs is fine. That's only a part of writing good software.

I don't see too much disparity here between the "myth" and "reality".

The author was emphasizing the fact that feature freezes *alone* are not enough to ensure the quality of your software. They have their time and they have their place, but they *must* be used in concert with other good development practices in order to be effective.

BTW, the metaphor or whatever "osmosis" is trying to make a point is pretty silly. Osmosis is the transfer of water through a semipermeable membrane.

Err, I've been hearing this metaphor for as long as I can remember. "Learning by osmosis" is a figure of speech used to imply a method of learning whereby the knowledge comes more or less automatically as a side-effect of simply being submerged in the material. The best example I can think of is living in a foreign country to learn their language. The author was trying to illustrate the general futility of trying to understand a program's structure just by skimming its hundreds or thousands of lines of code.

Myth: Bad or unappealing code or projects should be thrown away completely.

Reality: Solving the same simple problems again and again wastes time that could be applied to solving new, larger problems.

This is again true for open and closed source projects. Go look at one of the windows (closed source) freeware/shareware depositories and you will find at least 5-10 programs that all do the same thing more or less. If these were open source projects, I would imagine that there would be a good amount of code reuse going on here.


You imagine incorrectly.

I will say however, that UNIX (I'm generalizing that opensource is more of a UNIX like thing here) in general is a framework and our stuff plays well with one another. We have programs have STDOUT, and STDERR messages that are formatted for external processing and parsing, we have exit statuses in our programs so they can be &&ed and ||ed or test for their success or failure. We have signals, pipes, and sockets for IPC. Look at the number of opensource installs and the wide variety of things that they do and tell me that we are not solving a number of real problems well.

You both miss and prove the author's point at the same time. Unix is a framework, true enough. But the original intent of Unix (and I do mean original, as in "well before it was even called Unix") was as a development environment. Overtime it gradually became more flexible, hackers locked onto it and extended it in ways never dreamed and now, decades later we have an operating system whose design allows it to be used for almost anything from PDAs and embedded systems to the largest mainframes and clusters.

Open source software solves lots of real problems. That's the single reason that it's gaining so much ground these days. But there are a heck of a lot of projects out there that are essentially dead in the water because the developers are concentrating so much on the Next Big Thing rather than actually attempting to solve a problem. See the multitude of web content management projects as an example.

Myth: Stopping new development for weeks or months to fix bugs is the best way to produce stable, polished software.

Reality: Stopping new development for awhile to find and fix unknown bugs is fine. That's only a part of writing good software.

I don't see too much disparity here between the "myth" and "reality".

The author was emphasizing the fact that feature freezes *alone* are not enough to ensure the quality of your software. They have their time and they have their place, but they *must* be used in concert with other good development practices in order to be effective.

BTW, the metaphor or whatever "osmosis" is trying to make a point is pretty silly. Osmosis is the transfer of water through a semipermeable membrane.

Err, I've been hearing this metaphor for as long as I can remember. "Learning by osmosis" is a figure of speech used to imply a method of learning whereby the knowledge comes more or less automatically as a side-effect of simply being submerged in the material. The best example I can think of is living in a foreign country to learn their language. The author was trying to illustrate the general futility of trying to understand a program's structure just by skimming its hundreds or thousands of lines of code.

Myth: Bad or unappealing code or projects should be thrown away completely.

Reality: Solving the same simple problems again and again wastes time that could be applied to solving new, larger problems.

This is again true for open and closed source projects. Go look at one of the windows (closed source) freeware/shareware depositories and you will find at least 5-10 programs that all do the same thing more or less. If these were open source projects, I would imagine that there would be a good amount of code reuse going on here.


You imagine incorrectly.

I will say however, that UNIX (I'm generalizing that opensource is more of a UNIX like thing here) in general is a framework and our stuff plays well with one another. We have programs have STDOUT, and STDERR messages that are formatted for external processing and parsing, we have exit statuses in our programs so they can be &&ed and ||ed or test for their success or failure. We have signals, pipes, and sockets for IPC. Look at the number of opensource installs and the wide variety of things that they do and tell me that we are not solving a number of real problems well.

You both miss and prove the author's point at the same time. Unix is a framework, true enough. But the original intent of Unix (and I do mean original, as in "well before it was even called Unix") was as a development environment. Overtime it gradually became more flexible, hackers locked onto it and extended it in ways never dreamed and now, decades later we have an operating system whose design allows it to be used for almost anything from PDAs and embedded systems to the largest mainframes and clusters.

Open source software solves lots of real problems. That's the single reason that it's gaining so much ground these days. But there are a heck of a lot of projects out there that are essentially dead in the water because the developers are concentrating so much on the Next Big Thing rather than actually attempting to solve a problem. See the multitude of web content management projects as an example.

Just a quick comment for those stuck with NTLM at work. I run a local NTLM proxy server so I can run whatever browser or HTTP tool I like on whatever OS I need. I just point my browser at the proxy and it just works.

The proxy I use is written in Python, is small, and is really easy to install. NTLM Authorization Proxy Server.

Since you are authenticating with your user name and password, from your machine, and you are still actually going through the company web proxy just like IE would, there's absolutely no logical reason for the local "preventers of information services" to complain. At least, in my case, they haven't been able come up with an actual reason yet that hasn't been easy to dismiss. Not for want of trying, though ...

Now that it's a federal offense to harvest addresses from the web, I've just updated Seed Spambots to embed more IP/epoch in the email addresses.

Freshmeat Page

Freshmeat hasn't yet updated to 1.02, so the links are out-of-date.

The 1.02 version: demo download

I check all these daily:

MacInTouch
MacNN
MacMinute
MacFixIt
Mac OS X Hints
MacSurfer

Great software update resources:

VersionTracker
MacUpdate
OS X freshmeat

Other great sites:

O'Reilly Mac DevCenter
O'Reilly Mac OS X Page
Apple Mac OS X downloads
Apple Third Party Products Guide

Developer sites:

Mac OS X Developer Home Page
Mac OS X Developer Documentation
Darwin
OpenDarwin
fink

abc123abc123abc123abc123abc123abc123abc123abc123ab c123abc123abc123abc123abc123abc123abc123abc123abc1 23abc123abc123abc123abc123abc123abc123abc123abc123 abc123abc123abc123abc123abc123abc123abc123abc123ab c123abc123abc123abc123abc123abc123abc123abc123abc1

Try snowdrop

Here's an article on Freshmeat expressing similar sentiments.

XPDF

Star Control 2 (now GPL) (I always win)
xpuyopuyo (she always wins)
Chu Chu Rocket for dreamcast (anybody's guess)

If anyone's still reading this, try Ansel + patches I've made to it. Email me or leave a comment to get the patches...keep meaning to put 'em up somewhere.

Here are two useful utilities to flush out the SucKIT rootkit:


Kernel Security Therapy Anti-Trolls

and

Kernel Security Checker

Have a nice day !

Here are two useful utilities to flush out the SucKIT rootkit:


Kernel Security Therapy Anti-Trolls

and

Kernel Security Checker

Have a nice day !