Yeah, but there's a problem. The receiving system can't reject the message until after it accepts it since the Subject is part of the DATA portion of the SMTP message. Therefore, I am still paying for the unwanted bandwidth (and I pay $2/gig from my colo provider for my server). Now if they could mandate an ADV string in the HELO or MAIL part of the conversation, the SMTP server could reject and close the connection immediately.
A decent SMTP server can send a 5xx error message at any time. We use Postfix, which can reject mail based on regexes anywhere in the headers or body. And that is reject, as opposed to bounce, so if anyone gets stuck with a double-bounce, it's the open relay they used.
One of my favourites was Foxfire or Firefox or something like that. Ace flight sim for that old 8 bit machine.
Are you thinking of Skyfox? That was a cool game. In some fancy airplane, shooting up aliens tanks and motherships near ground, and up into the sky to shoot up alien planes.
And then Skyfox II just rocked. They stuck you out in space. I've got that game on my C64 emulator (and an actual physical copy of the game, so I have the blue-on-blue copy-protection map).
The biggest problem is that they have a central repository, where all packages are held. This is great for all important packages, but there's a lot of stuff that could be split off into auxillary repositories and maintained separately. Things like bash, ssh, and apache should be in the central repository. Games, IM clients, and media players are examples of extra stuff that can be updated at any time. A good division is whether or not you might use it on a server. I don't think this would overly complicate things; this kind of division would only be needed for Stable.
If I'm understanding correctly, the microwave beam has a very limited range. This would make it much harder to accidentally hurt someone with it. You can hurt someone on the other side of a large room, or possibly in the next room over, with an industrial laser.
It's actually a thought I had earlier today. Imagine you're a small place with a few servers (but they're rackmount with hot-swap drives). All of a sudden, the motherboard on one bites the dust. No worries, slap the drives in another server, and...well, some creative planning would be required to get the working server hosting the stuff on the dead server. UML would certainly make this process much easier and doubtless quicker. You'd have two servers running a bit slower, but that sure beats one server not running at all.
As for bash on OS X, personally, I really like the way Apple put together the aliasing and tab expansion intellegence into tcsh. Although it does make things annoying once in a while, it's really nice for it to know that I only want directories to be expanded when I have typed cd as the command, and lots more stuff like that.
Someone here recently made a similar comment about tab completion in Suse 7.3. Looking through the bash man page, I found that adding 'complete -d cd' to your.bashrc will do this.
One day I really should read up on what bash can do, and how to do it.
One step better: Tie this to your reality-enhancing goggles so you can actually see the transparent virtual keyboard.
This was my thought too, tie it in with transparent VR goggles, with images of Johnny Mnemnonic in my head.
For that matter, why stick with a conventional flat keyboard? Rotate your hands 90 degrees, duplicate some of the middle keys on both sides for ease of use. And definately allow custom movements. finger_snap=keyboard_on, hand_clap=keyboard_off. (smart-ass comments to follow)
Funny, I've never been paranoid about installing/patching anything, regardless of the operating system. It seems to me that a GOOD ADMIN would have any important data backed up prior to installing/upgrading any mission critical servers. Just because you're a negligent moron doesn't mean that Windows sucks.
No, Windows sucks entirely on its own merits, and in this case, I am not a negligent moron. This was a fresh install of a public access machine. We have *no* Windows servers. If you like using something that requires backups mid-install, that's up to you.
But you're right about backups. I've learned that I should make an emergency rescue disk with registry backup, followed by a reboot, after every single app I install, so I can catch whichever app it is that corrupts the registry (automatically backed up by Windows after being corrupted?). A minor glitch which will completely destroy the operating system.
Let's see. I install Win2K Pro. I start setting it up with some degree of security, install a few apps. It occurs to me to check for updates (it had to do with getting strong encryption in Win2K), so I download SP2. I install it, or try to. Partway through, it decides it can't find its files, no matter how many times I point to it. So I cancel, and then it can't find the files it needs to undo what it did. Again, telling it where the files are does no good.
Start over with installing Win2K Pro, but the SP is either the very next step or will not happen.
In retrospect, it could have been that I removed permissions from Outlook Express (obviously an essential part of the operating system).
I can certainly understand how anyone would be paranoid about installing something in Windows.
Slashdot Mirror
gentoo gentoo gentoo gentoo gentoo gentoo gentoo gentoo gentoo mandrake MANDRAKE aah hat ooh red hat
with many apologies to everyone.
Howard Stern?
They removed the need for make clean, and added make help. And maybe some other stuff too, you can see with make help. :)
Isn't that called listening to the radio?
Q: How many phones do Nokia sell each year?
A: Millions
Q: How many of their phones explode each year?
A: 1 or 2
Conclusion: the cost of settling is less than the cost of a recall. Therefore, no recall.
A decent SMTP server can send a 5xx error message at any time. We use Postfix, which can reject mail based on regexes anywhere in the headers or body. And that is reject, as opposed to bounce, so if anyone gets stuck with a double-bounce, it's the open relay they used.
Are you thinking of Skyfox? That was a cool game. In some fancy airplane, shooting up aliens tanks and motherships near ground, and up into the sky to shoot up alien planes.
And then Skyfox II just rocked. They stuck you out in space. I've got that game on my C64 emulator (and an actual physical copy of the game, so I have the blue-on-blue copy-protection map).
The biggest problem is that they have a central repository, where all packages are held. This is great for all important packages, but there's a lot of stuff that could be split off into auxillary repositories and maintained separately. Things like bash, ssh, and apache should be in the central repository. Games, IM clients, and media players are examples of extra stuff that can be updated at any time. A good division is whether or not you might use it on a server. I don't think this would overly complicate things; this kind of division would only be needed for Stable.
If I'm understanding correctly, the microwave beam has a very limited range. This would make it much harder to accidentally hurt someone with it. You can hurt someone on the other side of a large room, or possibly in the next room over, with an industrial laser.
You scared me...I read that as Min-Mei
It's actually a thought I had earlier today. Imagine you're a small place with a few servers (but they're rackmount with hot-swap drives). All of a sudden, the motherboard on one bites the dust. No worries, slap the drives in another server, and...well, some creative planning would be required to get the working server hosting the stuff on the dead server. UML would certainly make this process much easier and doubtless quicker. You'd have two servers running a bit slower, but that sure beats one server not running at all.
but will it only cost $5?
And Noah said, "God...what's a qubit?"
I still say that Emacs should be adapted to be a palmtop OS.
Someone here recently made a similar comment about tab completion in Suse 7.3. Looking through the bash man page, I found that adding 'complete -d cd' to your
One day I really should read up on what bash can do, and how to do it.
This was my thought too, tie it in with transparent VR goggles, with images of Johnny Mnemnonic in my head.
For that matter, why stick with a conventional flat keyboard? Rotate your hands 90 degrees, duplicate some of the middle keys on both sides for ease of use. And definately allow custom movements. finger_snap=keyboard_on, hand_clap=keyboard_off. (smart-ass comments to follow)
No, Windows sucks entirely on its own merits, and in this case, I am not a negligent moron. This was a fresh install of a public access machine. We have *no* Windows servers. If you like using something that requires backups mid-install, that's up to you.
But you're right about backups. I've learned that I should make an emergency rescue disk with registry backup, followed by a reboot, after every single app I install, so I can catch whichever app it is that corrupts the registry (automatically backed up by Windows after being corrupted?). A minor glitch which will completely destroy the operating system.
Let's see. I install Win2K Pro. I start setting it up with some degree of security, install a few apps. It occurs to me to check for updates (it had to do with getting strong encryption in Win2K), so I download SP2. I install it, or try to. Partway through, it decides it can't find its files, no matter how many times I point to it. So I cancel, and then it can't find the files it needs to undo what it did. Again, telling it where the files are does no good.
Start over with installing Win2K Pro, but the SP is either the very next step or will not happen.
In retrospect, it could have been that I removed permissions from Outlook Express (obviously an essential part of the operating system).
I can certainly understand how anyone would be paranoid about installing something in Windows.