There's a built-in Eudora HTML renderer. It's just not as 'nice' as using the Microsoft renderer. But to be honest, I prefer the HTML mail I receive to 'have it's back broken' to a degree. Not that I use eudora anymore, as I switched to Sylpheed awhile back, which is much better (it automatically threads mailing-list subscribed messages, for one thing).
They probably test the memory modules in some sort of a burn-in fixture. I'd hate to think they'd just clean and resticker them.
I have a whole pile of memory modules for some-odd Sun hardware that I wouldn't mind 'trading in' for something. I bought a pile of them that were supposed to work in my SS5's from somebody on eBay and he shipped me totally different modules. Then sent the right ones and said 'keep the other's.' I think they're StarFire Server memory or something.
And I, conversely, am a little worried about this.
Part of how I make my living is buying and selling used computer hardware. If there comes to be an easy and tax-advantageous way for instututions to donate their computers to a formal organization, the supply to people like me will dry up. Similarly, the suppy of surplus computers for people to experiment with software like Linux and the BSD Unixes will dry up. Many people have gotten their start experimenting with OSS on spare machines they got for almost nothing.
If the market tightens up, because Microsoft makes it easier to relicense and use 'legitimate' Windows on said machines, the current 'secondary market' which I am a part of, will wither and die.
I'm not interested in joining the Peace Corps and donating my time.
Microsoft can be real pricks about what is required to transfer their software.
I wanted to sell my copy of Office 2000 on eBay recently. It's the early edition of O2K from before there was even an 'activation' requirement. I have the CD, the jewel case, and the jewel case has the original CD key on it.
I got an email from one of Microsoft's eBay spies warning me that since I wasn't including the manual, the box, etc. that I couldn't resell the CD on eBay.
Now, I've seen countless instances where people have gotten away with such sales, usually of older versions. In fact, I bought Microsoft Office 4 for Macintosh that way on eBay. But Microsoft knows that O2K is still a 'cash cow' for them and they go to considerable effort to make sure (even to the point of employing people to crack down on individual sales of single copies) that nobody is reselling their software.
Sun also gives far more then the street value on used gear for trade in.
I'd like to know more about that deal with Sun. It wouldn't be a bad deal for me to trade in five SS5's and four SS10's, plus five or six IPXs and five or so IPCs if I could get a Blade 100 for a hundred bucks or so.
I'd want to keep a representative example of each old Sun box for the collection, of course, but I'm up to my ears in Sun hardware at the moment.
Yes, but the computers in Africa and Asia had to be shipped there somehow, by somebody.
I buy used computers at auction and resell them on eBay. I find deals like 80 Pentium II machines that I get by the skid for $40. If I, as an American, tried to refurbish those machines and donate them to an overseas charity, I would find myself in lots of trouble if I didn't ship them as bare machines. And shipping them as bare machines raises the likelihood that they'll end up as nothing, since I'm handing off systems that aren't going to do a single thing out-of-the-box, which makes it less likely anybody at the other end will have the know-how and resources to bring up an OS on them. So if there's a clear 'legitimate' path for the machines to get Windows installed on them for use overseas, and I can see to it that they're installed properly and ready-to-go, I am more likely to find it worthwhile to participate in such a program.
Back in the day I ran Linux and X on my 486DX-33 with 16 megs of RAM. It ran pretty nicely. Probably better, since it had a lot more apps, than your Mac 512K did.
At the time, a 486 with 16 megs of RAM was the NORM, and many, many people ran Linux, with X, on such machines.
Pointing back to your Mac with 512K is a little ridiculous and irrelevant, to be honest.
I've been 'spoiled' by the clean well-focused tightness of NetBSD going way back to 1.3.2, when I first installed it, over NFS, on my Toshiba 486 laptop. The laptop has only a floppy drive and PCMCIA slots, so an ethernet install was the only reasonable way I could see. At that time, in the Linux 1.2 kernel era, PCMCIA support in Linux was a 'hang a bag on the side' set of kernel extensions that one had to fool with to get working. With NetBSD, PCMCIA ethernet support was integrated into the kernel core and 'just worked' in the single boot floppy needed for the install.
The 'minimal, clean' philosophy extends all the way through NetBSD. A basic install for most architectures is an 80-100 MB set of gzipped tarballs you can easily download. This gets you a working system, with all the basic functionality, a C compiler, X11 with the basic Tab Window Manager (TWM), networking, etc. The installer lets you 'pare' this down even further if, say, you don't need X11 or dev tools. When you want to extend your system beyond this base, you turn to the packages collection, which is really a massive build script, with 'configuration-wrapper' scripts and patches that are applied over the standard source tarballs from whomever the package actually comes from. You can also applie the packages as binaries using the pkg_add command and a large repository of prebuilt packages available from the NetBSD ftp sites.
Because the base system is small and fully integrated, you can also compile the whole base userland from a set of integrated gzipped tarballs (*.tgz files). It's as simple as unpacking the source tarballs and issuing a top-level make command. The whole kernel and base userland can also be upgraded with CVS live over the network and rebuilt.
Once you learn how to admin and run with NetBSD on one architecture, you know most of what you'll need to for running it on different architectures. All the ports of NetBSD, for Mac68k, MacPPC, i386, Sparc, Sparc64, VAX, MIPs, etc. built from the same core source files. The structure of the/etc/ directory is common to all architectures.
And NetBSD has adopted a philosophy of doing things right, one time, and keeping things that way. Most of the info you need to set up and admin a NetBSD system you can learn from the classic UNIX books and documentation. The O'Reilly X Window System documentation (the big 8 book set) tells you almost anything you need to know, for instance.
There isn't a cadre of people out there trying to make NetBSD 'easy to use.' Thus, there aren't a bunch of people muddying things up and producing all kinds of croft and layers of GUI stuff to do basic tasks. There isn't a perceived goal of 'win over OS foo' which eggs the developers on to misdirected goals of competitiveness. The excellence of NetBSD stands on it's own and is based in what it is, not how it 'compares' to other OS projects and products.
Anyway, I think NetBSD is cool, it gives the users who are interested in 'getting under the hood' the opportunity to explore along well-followed paths of classic UNIX, and also lets the computer enthusiast run a Common OS on his whole collection of machines. I've run NetBSD on a Macintosh SE/30, a Quadra 650, on various PC compatibles going from a 386sx laptop to a Quad PentiumPro server, on all the classic Sun Sparc machines (IPC, IPX, LX, Classic, SS2, SS5, SS10, Ultra1), and on an RS/6000 box with the PowerPC chip.
Eudora can work for this, too, but one danger Eudora users should be aware of is that Eudora uses the Microsoft HTML viewer for viewing HTML mail unless you specifically go into the config and tell it not to use the MS HTML viewer. This is a really important part of configuring Eudora.
Sylpheed is the best...email program... evah of course.
To extend your analogy to fit better, consider a world in which many doors, windows, cabinets, etc. are designed in such a way that it's impossible to install a key lock. Others are designed so that a keylock can be installed, but there's only one supply anywhere in the world for key blanks for that particular lock. So you can't lock certain places at all, because you only have one key, and there are five of you who need access to that cabinet or room.
I used to try running Windows 2000 as a non-privledged user.
The problem is, not every Windows program out there is written to be aware of the fine-grained security model of Windows NT. In a 'perfect world' every Windows developer would code properly, with security in mind. As it stands, the complex NT security model is just ignored by a lot of people. It might work great in a locked-down corporate environment with a limited-set of software, i.e. where the user isn't allowed to install anything, and the software installed is a narrow well-tested set. It won't ever work in looser environments. Given the lax 'security culture' of Microsoft and it's user base, it's unworkable.
It seems sort of schizophrenic that they make nice finished wooden cases, but then put one of those big dorky windows in the side, so you can see a bunch of grey ribbon cables and the assorted mess.
I guess it's for the people who buy those round cables with neon strips on them, or something.
A wooden case to me means 'traditional' looking, to blend in with the decor. I don't see that when I visit the page you linked.
Wood veneer is also laminated onto expensive but not-as-attractive hardwood to make very expensive high quality furniture.
For which, mind you, rich people spend more money than it's worth.
Wooden cabinet floorstanding Television Sets have always looked nicer than their 'portable' counterparts. There's nothing wrong with having a little more style and housing electronic equipment in a nice enclosure.
I, for one, am looking forward to the upcoming NetBSD 2.0 release. Just installed NetBSD-current on a new four-way server and it's running great with SMP. Looks like the 2.0 release is scheduled in the next several months.
Slashdot Mirror
There's a built-in Eudora HTML renderer. It's just not as 'nice' as using the Microsoft renderer. But to be honest, I prefer the HTML mail I receive to 'have it's back broken' to a degree. Not that I use eudora anymore, as I switched to Sylpheed awhile back, which is much better (it automatically threads mailing-list subscribed messages, for one thing).
They probably test the memory modules in some sort of a burn-in fixture. I'd hate to think they'd just clean and resticker them.
I have a whole pile of memory modules for some-odd Sun hardware that I wouldn't mind 'trading in' for something. I bought a pile of them that were supposed to work in my SS5's from somebody on eBay and he shipped me totally different modules. Then sent the right ones and said 'keep the other's.' I think they're StarFire Server memory or something.
And I, conversely, am a little worried about this.
Part of how I make my living is buying and selling used computer hardware. If there comes to be an easy and tax-advantageous way for instututions to donate their computers to a formal organization, the supply to people like me will dry up. Similarly, the suppy of surplus computers for people to experiment with software like Linux and the BSD Unixes will dry up. Many people have gotten their start experimenting with OSS on spare machines they got for almost nothing.
If the market tightens up, because Microsoft makes it easier to relicense and use 'legitimate' Windows on said machines, the current 'secondary market' which I am a part of, will wither and die.
I'm not interested in joining the Peace Corps and donating my time.
The greatest equalizer mankind has ever seen is probably a volcano or a forest fire.
I wouldn't classify Open source as a similar phenomenon, and I hope you wouldn't either.
Microsoft can be real pricks about what is required to transfer their software.
I wanted to sell my copy of Office 2000 on eBay recently. It's the early edition of O2K from before there was even an 'activation' requirement. I have the CD, the jewel case, and the jewel case has the original CD key on it.
I got an email from one of Microsoft's eBay spies warning me that since I wasn't including the manual, the box, etc. that I couldn't resell the CD on eBay.
Now, I've seen countless instances where people have gotten away with such sales, usually of older versions. In fact, I bought Microsoft Office 4 for Macintosh that way on eBay. But Microsoft knows that O2K is still a 'cash cow' for them and they go to considerable effort to make sure (even to the point of employing people to crack down on individual sales of single copies) that nobody is reselling their software.
Sun also gives far more then the street value on used gear for trade in.
I'd like to know more about that deal with Sun. It wouldn't be a bad deal for me to trade in five SS5's and four SS10's, plus five or six IPXs and five or so IPCs if I could get a Blade 100 for a hundred bucks or so.
I'd want to keep a representative example of each old Sun box for the collection, of course, but I'm up to my ears in Sun hardware at the moment.
Yes, but the computers in Africa and Asia had to be shipped there somehow, by somebody.
I buy used computers at auction and resell them on eBay. I find deals like 80 Pentium II machines that I get by the skid for $40. If I, as an American, tried to refurbish those machines and donate them to an overseas charity, I would find myself in lots of trouble if I didn't ship them as bare machines. And shipping them as bare machines raises the likelihood that they'll end up as nothing, since I'm handing off systems that aren't going to do a single thing out-of-the-box, which makes it less likely anybody at the other end will have the know-how and resources to bring up an OS on them. So if there's a clear 'legitimate' path for the machines to get Windows installed on them for use overseas, and I can see to it that they're installed properly and ready-to-go, I am more likely to find it worthwhile to participate in such a program.
Back in the day I ran Linux and X on my 486DX-33 with 16 megs of RAM. It ran pretty nicely. Probably better, since it had a lot more apps, than your Mac 512K did.
At the time, a 486 with 16 megs of RAM was the NORM, and many, many people ran Linux, with X, on such machines.
Pointing back to your Mac with 512K is a little ridiculous and irrelevant, to be honest.
There's nothing wrong about loving Euros.
Even if you're a parochial American bound to your ways who will never visit Europe, they are convertable to dollars.
I've been 'spoiled' by the clean well-focused tightness of NetBSD going way back to 1.3.2, when I first installed it, over NFS, on my Toshiba 486 laptop. The laptop has only a floppy drive and PCMCIA slots, so an ethernet install was the only reasonable way I could see. At that time, in the Linux 1.2 kernel era, PCMCIA support in Linux was a 'hang a bag on the side' set of kernel extensions that one had to fool with to get working. With NetBSD, PCMCIA ethernet support was integrated into the kernel core and 'just worked' in the single boot floppy needed for the install.
/etc/ directory is common to all architectures.
The 'minimal, clean' philosophy extends all the way through NetBSD. A basic install for most architectures is an 80-100 MB set of gzipped tarballs you can easily download. This gets you a working system, with all the basic functionality, a C compiler, X11 with the basic Tab Window Manager (TWM), networking, etc. The installer lets you 'pare' this down even further if, say, you don't need X11 or dev tools. When you want to extend your system beyond this base, you turn to the packages collection, which is really a massive build script, with 'configuration-wrapper' scripts and patches that are applied over the standard source tarballs from whomever the package actually comes from. You can also applie the packages as binaries using the pkg_add command and a large repository of prebuilt packages available from the NetBSD ftp sites.
Because the base system is small and fully integrated, you can also compile the whole base userland from a set of integrated gzipped tarballs (*.tgz files). It's as simple as unpacking the source tarballs and issuing a top-level make command. The whole kernel and base userland can also be upgraded with CVS live over the network and rebuilt.
Once you learn how to admin and run with NetBSD on one architecture, you know most of what you'll need to for running it on different architectures. All the ports of NetBSD, for Mac68k, MacPPC, i386, Sparc, Sparc64, VAX, MIPs, etc. built from the same core source files. The structure of the
And NetBSD has adopted a philosophy of doing things right, one time, and keeping things that way. Most of the info you need to set up and admin a NetBSD system you can learn from the classic UNIX books and documentation. The O'Reilly X Window System documentation (the big 8 book set) tells you almost anything you need to know, for instance.
There isn't a cadre of people out there trying to make NetBSD 'easy to use.' Thus, there aren't a bunch of people muddying things up and producing all kinds of croft and layers of GUI stuff to do basic tasks. There isn't a perceived goal of 'win over OS foo' which eggs the developers on to misdirected goals of competitiveness. The excellence of NetBSD stands on it's own and is based in what it is, not how it 'compares' to other OS projects and products.
Anyway, I think NetBSD is cool, it gives the users who are interested in 'getting under the hood' the opportunity to explore along well-followed paths of classic UNIX, and also lets the computer enthusiast run a Common OS on his whole collection of machines. I've run NetBSD on a Macintosh SE/30, a Quadra 650, on various PC compatibles going from a 386sx laptop to a Quad PentiumPro server, on all the classic Sun Sparc machines (IPC, IPX, LX, Classic, SS2, SS5, SS10, Ultra1), and on an RS/6000 box with the PowerPC chip.
Eudora can work for this, too, but one danger Eudora users should be aware of is that Eudora uses the Microsoft HTML viewer for viewing HTML mail unless you specifically go into the config and tell it not to use the MS HTML viewer. This is a really important part of configuring Eudora.
...email program... evah of course.
Sylpheed is the best
To extend your analogy to fit better, consider a world in which many doors, windows, cabinets, etc. are designed in such a way that it's impossible to install a key lock. Others are designed so that a keylock can be installed, but there's only one supply anywhere in the world for key blanks for that particular lock. So you can't lock certain places at all, because you only have one key, and there are five of you who need access to that cabinet or room.
There are tons of good .chm files in the ebooks binary newsgroups. Hmm, I bet some of them are buggy now...
I used to try running Windows 2000 as a non-privledged user.
The problem is, not every Windows program out there is written to be aware of the fine-grained security model of Windows NT. In a 'perfect world' every Windows developer would code properly, with security in mind. As it stands, the complex NT security model is just ignored by a lot of people. It might work great in a locked-down corporate environment with a limited-set of software, i.e. where the user isn't allowed to install anything, and the software installed is a narrow well-tested set. It won't ever work in looser environments. Given the lax 'security culture' of Microsoft and it's user base, it's unworkable.
It seems sort of schizophrenic that they make nice finished wooden cases, but then put one of those big dorky windows in the side, so you can see a bunch of grey ribbon cables and the assorted mess.
I guess it's for the people who buy those round cables with neon strips on them, or something.
A wooden case to me means 'traditional' looking, to blend in with the decor. I don't see that when I visit the page you linked.
Wood veneer is also laminated onto expensive but not-as-attractive hardwood to make very expensive high quality furniture.
For which, mind you, rich people spend more money than it's worth.
Wooden cabinet floorstanding Television Sets have always looked nicer than their 'portable' counterparts. There's nothing wrong with having a little more style and housing electronic equipment in a nice enclosure.
I, for one, am looking forward to the upcoming NetBSD 2.0 release. Just installed NetBSD-current on a new four-way server and it's running great with SMP. Looks like the 2.0 release is scheduled in the next several months.