Search results

When spammers "hijack" an open-relaying SMTP server, they don't "get into" it, they just bounce messages off of it. The way SMTP works is that it just takes RFC-compliant message and does something with it, where "something" is generally one of three things: 1. Accept it for delivery to...

I compiled this based on the FreeBSD source. It seems to work... http://www.freeke.org/files/unrar.sit.hqx

You handle that stuff from the Netinfo Manager application. Unfortunately, for now this stuff is poorly (non-existently?) documented.

As much as I respect lynx, there's a newer text-mode browser, called links, that wipes the floor with it. You should check it out here: http://links.browser.org It has dramatically better table handling, for example.

Here's a link to a page with a lot of info for installing OSX on older machines. It's a fair amount of work, but it seems a lot of people have had success using these instructions. http://homepage.mac.com/RyanRempel/OldWorld/Instructions.html

This isn't scientific by any means, (because of the difference between the PB and the final), but my subjective experience is that certain "pure" Unix apps are faster (or at least tremendously more convenient) from a UFS volume than from an HFS+ volume. My OSX PB system was set up as a...

Certain commands typically only invoked by root (like reboot and shutdown, for example) are probably not in your shell's default path. They are likely located in either /sbin or /usr/sbin. You'll need to explicitly path to them if you want to invoke them using sudo, like so: sudo...

blb & theed -- excellent: works great! Just what I was looking for.

I have entries for various hosts in my netinfo database. I'd like the OS to try resolving hostnames in netinfo first, rather than going to DNS. Right now, it seems like the OS is still going to DNS first for these hostnames. This would be handy when reading Slashdot, for example...

Okay, it looks like you've already successfully unarchived the source code, so you can proceed by going into the directory and starting the build process. Just cd into your irc2.10.3l/ directory and pick it up from the ./configure step.

Take advantage of tab completion in Terminal -- while sitting in the directory where you downloaded the package, type tar xvzf and just the first few letters of your package's filename, then press the TAB key. The shell will autocomplete the filename in your command. Very handy.

Ah, that sucks. :( Until Apple (hopefully) updates this via Software Update I guess it's time to block port 123 on my firewall. (I've been sync-ing my machines at work to my OSX box, which is rather a handy thing to be able to do...)

Generally speaking, if it's a reasonable modern piece of Unix software and it doesn't depend on things you don't have (i.e. X11) the general process is (from the Terminal, as an administrator): - gnutar xzvf {packagename}.tar.gz - cd {packagename} {before the next steps, peruse any...

BTW... whats with all these different commands? httpd? apachectl? apachectl is simply a script that starts and stops or restarts the Apache daemon, based on the parameters you run it with. It's just there because it's easier than messing around with PIDs and kill and HUPs and stuff...

They are making progress towards getting Mozilla to build with a native Mach-O back end. If they succeed in this, it should be, in theory, practical to build a nice, Cocoa-native/Aqua-goodness front-end and embed Mozilla's nicely standards-compliant (the most conformant CSS and all that...

You can set it to restrict javascript from opening new windows... which means death to popups -- yay!

You know what you doing! Move Zig! oops, erm... What I did was create a new group (bossgrp) using Netinfo, add myself (only) to it, and edit /etc/sudoers, replacing this line: %admin ALL=(ALL) ALL with %bossgrp ALL=(ALL) ALL

Hey, where didja get that desktop picture? I like stuff like that...

Oversimplifying things quite a bit, the BSD ports system provides a directory-tree of already-ported software. Once you've set up the ports system, you just cd to the named package in the ports tree , type bsdmake and (hopefully) your machine goes out, FTPs the source code for the package...

It gets launched by the inetd "super-daemon". inetd listens for incoming connections on the ports specified in /etc/inetd.conf. When it gets an incoming ftp connection, it launches (via tcpd, which can impose useful restrictions by ip range, etc.) the ftp daemon (if ftp is turned on). In...