Crap. Looks like the Johnny Cash lyric filter is broken again. Although I think Shel Silverstien wrote that song. Whatever. Time to get back to hackin' the slashcode.
Dylan used to be a lot closer to scheme, using prefix notation complete with large numbers of paren's. Descriptive variable and function names are important in both Scheme and Dylan, things like 'full?' and 'set!.' A lot of early Dylan compiler work was done in Scheme & Lisp. Thomas, the Dylan-like compiler was written in Scheme, Apple's Dylan was written in MacLisp. The biggest difference is that everything in Dylan is an object, including functions, classes. Also, Dylan has a much stronger module system, some really interesting stuff in terms of sealing, and a flexible type system.
Not the IRC admins - they've got to put up with more shit than anyone. The lame admins that let script kiddiez root their boxes. Telnetd shouldn't exist - all traces of it's existance should be eliminated from the civilized world. Come on, OpenSSH is free and allows for unrestricted use.
All of the recent DDoS attacks have been from captured boxen. Eliminate capturable boxen and you eliminate the DDoS attacks.
Perhaps we should band together, set up every machine we know of to drop packets headed for port 23. Some slashdotters must have access to big ole backbone routers. We don't let people send flammable material through the mail, why should we allow root passwords to travel as clear text?
Something just doesn't sit right with me when you have to have a small MAC partition to install Linux.
This just isn't true. Don't use BootX, use Quik. BootX is easier to use, but requires MacOS. Quik is more like lilo (although it's based on the Solaris boot loader (silo?)). The RedHat based PPC Linux distros are "optimized" for installing/booting from MacOS.
Debian is the best PPC Linux distro I've used.
If you want to execute 68k code fast, the most sensible option is to make a dynamically recompiling emulator running on Alpha (or x86)
I'm not sure how true that is. I'm pretty sure PPC chips have some special instructions and such that make it possible to emulate 68k code fairly fast. It's not full hardware emulation or anything, but even old, old powermacs run 68k code at fairly suprising speeds.
OpenFirmware isn't the closest thing to a CLI on a mac. There are several CLI shells available for MacOS. One's called MacShell, there's another called nshell.
OpenFirmware, which was developed mostly by Sun, isn't a shell. It's just Forth with a bunch of stuff stuck on it. It's more like a really nice x86 BIOS than anything else. Then idea with OpenFirmware is that all devices have some Forth that acts as a driver that can be used to operate the device until an OS loads a real driver. It's on all PCI Macs (There are only 3 non-PCI macs, the x100s). It's on most Suns. It used to be called "OpenBoot."
The really slick thing about OpenFirmware is that it builds a device tree, which is what makes "hardware...a non-issue."
1.Is OpenBSD more secure in some fundamental way that a well maintained Linux distribution? One of the OpenBSD project's principals is proactive security. They go through all the code for core part of the OS, including the kernel, and look for things that might cause problems. 2.Is OpenBSD more stable than a well maintained Linux distribution? Probably not. The BSD model of releases is most like Debians, where everything's frozen and all bugs are chased out and then there's a release. BSD installs (at least Net and Open) tend to be fairly minimal, but additonal software is easy to add. 3.Will the OpenSource software we normally need (firewall, Apache, PHP4, Perl, Python) and so on probably compile on OpenBSD? Yes. The ports tree is a wonderful thing. Firewalls are done a little differently then under linux, but it's mostly just subtle things. 5.Is the performance of a well maintained OpenBSD system better than a well maintained Linux distribution? Probably not. BSD uses a different scheduling model than Linux, so there's bound to be some difference, but it's not much. 6.Does Linux have anything like the one time use password system? Yes. There's something called OPIE telnet. 7.Does OpenBSD support multiple CPU's better then Linux? OpenBSD doesn't support SMP. FreeBSD does, but it's not as "secure"
Apple is ordering a couple million PowerPCs every year. I honestly don't see why IBM isn't taking that account more seriously. I'm sure there are good reasons for it. But they must be pretty serious for IBM to turn away all that business. I might be wrong about this, but I believe that IBM supplied most of G3s Apple uses. In fact, I'm 99% sure the copper G3s used in PowerBooks and other boxen are IBM. And since Apple is still makeing iMacs with G3s in them, IBM is still getting money.
A K7 would make a great streaming server, plus it would have plenty of power left over to run other stuff. A G4 isn't such a great idea, as the ideal solution would probably involve MacOSX and Quicktime streaming server, which isn't cheap. K7s are cheap and fast; the perfect budget server.
If Apple shipped a complete development environment with their OS and stopped sueing people I might consider it. Why ship a development environment with a consumer OS? When you buy a play station, to they send you everything you need to write games? Anyway, Macintosh Programming Workshop (MPW) is Apple's FREE Programming environment. You can download it from their website, along with hundreds of other useful tools, code snippets, SDKs, and useful stuff. Plus you get MrC, one of the best PPC compilers for PowerPCs.
Anyway, i have a random question for anyone who may be listening: _is_ internal firewire a good idea, or even possible? i'd imagine there's some reason apple isn't doing it already. What is it?
internal fireware is a good idea.
macs in the future will have internal firewire drives.
apple hasn't done it yet because: a) firewire hasn't caught on totally, yet b) ide is cheap
Or has someone come up with a solution to this snafu of which I'm unaware?
It's the same solution you use if you want to run X apps on a NeXt. It's a little library that translates from X to DisplayPostscript. Apparently, it was a pretty easy port. You can find it, if you loook
Slashdot Mirror
Camino doesn't use Cocoa text field widgets. Otherwise, it would have spellchecking built-in, wouldn't it?
That ain't pseudocode, sonny; that's Pascal!
Crap. Looks like the Johnny Cash lyric filter is broken again. Although I think Shel Silverstien wrote that song. Whatever. Time to get back to hackin' the slashcode.
I take offense at your request to abuse my taco. Sick bastard.
Dylan used to be a lot closer to scheme, using prefix notation complete with large numbers of paren's. Descriptive variable and function names are important in both Scheme and Dylan, things like 'full?' and 'set!.' A lot of early Dylan compiler work was done in Scheme & Lisp. Thomas, the Dylan-like compiler was written in Scheme, Apple's Dylan was written in MacLisp. The biggest difference is that everything in Dylan is an object, including functions, classes. Also, Dylan has a much stronger module system, some really interesting stuff in terms of sealing, and a flexible type system.
Hasn't John Bonham been dead for, like, 20 years now?
Script Kiddies aren't the problem.
Poor admins are.
Not the IRC admins - they've got to put up with more shit than anyone. The lame admins that let script kiddiez root their boxes. Telnetd shouldn't exist - all traces of it's existance should be eliminated from the civilized world. Come on, OpenSSH is free and allows for unrestricted use.
All of the recent DDoS attacks have been from captured boxen. Eliminate capturable boxen and you eliminate the DDoS attacks.
Perhaps we should band together, set up every machine we know of to drop packets headed for port 23. Some slashdotters must have access to big ole backbone routers. We don't let people send flammable material through the mail, why should we allow root passwords to travel as clear text?
Something just doesn't sit right with me when you have to have a small MAC partition to install Linux. This just isn't true. Don't use BootX, use Quik. BootX is easier to use, but requires MacOS. Quik is more like lilo (although it's based on the Solaris boot loader (silo?)). The RedHat based PPC Linux distros are "optimized" for installing/booting from MacOS. Debian is the best PPC Linux distro I've used.
If you want to execute 68k code fast, the most sensible option is to make a dynamically recompiling emulator running on Alpha (or x86)
I'm not sure how true that is. I'm pretty sure PPC chips have some special instructions and such that make it possible to emulate 68k code fairly fast. It's not full hardware emulation or anything, but even old, old powermacs run 68k code at fairly suprising speeds.
OpenFirmware isn't the closest thing to a CLI on a mac. There are several CLI shells available for MacOS. One's called MacShell, there's another called nshell.
OpenFirmware, which was developed mostly by Sun, isn't a shell. It's just Forth with a bunch of stuff stuck on it. It's more like a really nice x86 BIOS than anything else. Then idea with OpenFirmware is that all devices have some Forth that acts as a driver that can be used to operate the device until an OS loads a real driver. It's on all PCI Macs (There are only 3 non-PCI macs, the x100s). It's on most Suns. It used to be called "OpenBoot."
The really slick thing about OpenFirmware is that it builds a device tree, which is what makes "hardware...a non-issue."
In closing, I would like to add that Forth rocks.
I bought the cheapest Athlon mobo I could buy, a FIC SD-11. It's got a crap powersupply. It doesn't crash. It hasn't crashed.
The problem isn't with the mobo, it's with FUD, which could probably be traced to intel or intelosers.
1.Is OpenBSD more secure in some fundamental way that a well maintained Linux distribution?
One of the OpenBSD project's principals is proactive security. They go through all the code for core part of the OS, including the kernel, and look for things that might cause problems.
2.Is OpenBSD more stable than a well maintained Linux distribution?
Probably not. The BSD model of releases is most like Debians, where everything's frozen and all bugs are chased out and then there's a release. BSD installs (at least Net and Open) tend to be fairly minimal, but additonal software is easy to add.
3.Will the OpenSource software we normally need (firewall, Apache, PHP4, Perl, Python) and so on probably compile on OpenBSD?
Yes. The ports tree is a wonderful thing. Firewalls are done a little differently then under linux, but it's mostly just subtle things.
5.Is the performance of a well maintained OpenBSD system better than a well maintained Linux distribution?
Probably not. BSD uses a different scheduling model than Linux, so there's bound to be some difference, but it's not much.
6.Does Linux have anything like the one time use password system?
Yes. There's something called OPIE telnet.
7.Does OpenBSD support multiple CPU's better then Linux?
OpenBSD doesn't support SMP. FreeBSD does, but it's not as "secure"
There are still plenty of G3s available. And they go up to 500mhz too.
Apple is ordering a couple million PowerPCs every year. I honestly don't see why IBM isn't taking that account more seriously. I'm sure there are good reasons for it. But they must be pretty serious for IBM to turn away all that business.
I might be wrong about this, but I believe that IBM supplied most of G3s Apple uses. In fact, I'm 99% sure the copper G3s used in PowerBooks and other boxen are IBM. And since Apple is still makeing iMacs with G3s in them, IBM is still getting money.
A K7 would make a great streaming server, plus it would have plenty of power left over to run other stuff. A G4 isn't such a great idea, as the ideal solution would probably involve MacOSX and Quicktime streaming server, which isn't cheap. K7s are cheap and fast; the perfect budget server.
If Apple shipped a complete development environment with their OS and stopped sueing people I might consider it.
Why ship a development environment with a consumer OS? When you buy a play station, to they send you everything you need to write games?
Anyway, Macintosh Programming Workshop (MPW) is Apple's FREE Programming environment. You can download it from their website, along with hundreds of other useful tools, code snippets, SDKs, and useful stuff. Plus you get MrC, one of the best PPC compilers for PowerPCs.
A while ago, apple produced a powerbook with swapable inserts to change the look of the book. It was kinda neat.
estate taxes only apply for inheritances over $600,000
You mean federal estate taxes, a lot of states have estate taxes too, and can they start lower.
Anyway, i have a random question for anyone who may be listening: _is_ internal firewire a good idea, or even possible? i'd imagine there's some reason apple isn't doing it already. What is it?
internal fireware is a good idea.
macs in the future will have internal firewire drives.
apple hasn't done it yet because:
a) firewire hasn't caught on totally, yet
b) ide is cheap
There ain't no reason why you can't use firware inside a box, silly. Just put a jack on the mobo.
Or has someone come up with a solution to this snafu of which I'm unaware?
It's the same solution you use if you want to run X apps on a NeXt. It's a little library that translates from X to DisplayPostscript. Apparently, it was a pretty easy port. You can find it, if you loook
This is the same reason why my coffeemaker doesn't have a pIII-500 in it.
My coffemaker has a PIII-500 in it - for a heating element!
You mean to tell me that if you see a drop of water, you can't imagine an ocean.
If all I've ever seen are drops of water, there is no way I could imagine an ocean, let alone understand an ocean.
Look on the prefs page. It says the Local Time thing is funky.
probably, seeing as how only ftp.ru.freebsd.org is reporting a full 3.3 mirror.