Bose may sound good to the average listener (they tend to bump up the treble and bass which sounds good at initial impression, but tires later) but especially their lower end systems (especially the small cubes) are lacking in the mid-bass/mid region.
Do your research! Here's a couple links to some good Home Theater boards which should get you going:
The single best advise I can give when looking for speakers is to go and listen to a bunch of them, and bring your own listening material! It's hard enough trying to judge speakers when they're playing off different equipment and in different rooms, so stick with one CD/DVD that you're familiar with.
Don't you realize? EVERYONE has skeletons in their closet. Some people just have more/or less of them. I don't know anyone who hasn't done at least one thing which would be embarassing on a national level.
The system DOES WORK. The problem is that the majority of people are "happy enough" with the way things are that they don't get involved. When things get bad, the people will speak up (unless they've all been brainwashed by then!;-)
I've got two K6-2 systems myself, have built half a dozen for friends and family, and know a bunch more who've built themselves K6-2 systems.
All of them are rock solid and perform great for the money that was put into them.
Of course, I didn't go out and but the cheapest motherboard available when for a $10 more a stable, good performing was available.
You may think that the K6-2 is "cheap" and "bad", but informed people know better.
The Duron is the same way. I've got a Duron 700 sitting here on my desk. I didn't chimp on the motherboard. It runs great (fast and stable) the the speed is indiscernable from an Athlon 700 and saved me $80 in the process. When I need a speed boost in a year or so, I'll drop in a 1.2GHz Athlon (which should run about $100 by then) and run for another year with no other changes.
Your "numbers" on the mysql site don't even include the latest release of Postgres (7.0.2) which contains many significant speed improvements. Meanwhile, and alpha version of mysql is being used. Your "numbers" as such are rather useless at this point in time.
I really wish moderators would look at the information in posts first before modding them up.
Here's what Linus has to say about the whole issue himself as posted to linux-kernel. Makes sense really, and he'd doing it for the good of *everyone* using Linux, not just him.
--- begin quote --
Date: Tue, 18 Jan 2000 20:28:45 -0800 (PST) From: Linus Torvalds cc: Kernel Mailing List Subject: Re: Using "linux" in a domain name
[ sorry for the off-topic thing to "linux-kernel", it's just the best medium I can think off off-hand ]
Ok, I've been getting tons of email about the trademark thing due to the action of stopping the auctioning off of linux-related names, so instead of just answering individually (which was how I started out), I'll just send out a more generic email. And hope that slashdot etc pick it up so that enough people will be reassured or at least understand the issues.
And hey, you may not end up agreeing with me, but with the transmeta announcement tomorrow I won't have much time to argue about it until next week;)
Basically, the rules are fairly simple, and there really are just a few simple basic issues involved:
- I (and obviously a lot of other people) do not want to have "Linux" as a name associated with unacceptable (or borderline) behaviour, and it's important that "Linux" doesn't get a name of being associated with scams, cybersquatting, etc etc. I'd personally hate that, for rather obvious reasons. I _like_ being proud of Linux, and what has been achieved. I'd rather not have to apologize for it..
- Trademark law requires that the trademark owner police the use of the trademark (unlike, for example, copyright law, where the copyright owner is the copyright owner, always is, and always will be unless he willingly relinquishes ownership, and even THEN he ends up having rights).
This is nasty, because it means, for example, that a trademark owner has to be shown as caring about even small infringements, because otherwise the really bad guys can use as their defense that "hey, we may have misused it, but look at those other cases that they didn't go after, they obviously don't care.."
- Even with things that aren't scams or something like that, VALID uses of "Linux" may be bad if they mean that other valid uses of "Linux" are blocked.
Those are the kind of ground rules, I think everybody can pretty much agree with them..
What the above leads to is
- I'm required to ask people to acknowledge the trademark. When you use the term "Linux" in official marketing literature etc, you should acknowledge it as a trademark owned by me. Not because I love seeing my name in print, but simply because of the "policing" issue (#2) above.
(And no, that does NOT mean that you have to add that to normal, everyday use of the term. Common sense rules the day, think of the situations where you see the silly "xxxx is a trademark of yyyy", and realize that yyyy may not really care except the legal issues force them to;)
- _Intent_ matters. It matters a lot.
If your intent is to use the word "linux" as part of a real Linux project, that doesn't mean that you automatically absolutely have to get permission from me. That's the LAST thing I want. I want "Linux" to be as free as possible as a term, and the real reason for having a trademark in the first place was to _protect_ it rather than use it as some kind of legalistic enforcement thing.
But, for example, if your intent is to register "mylinux.com" (made up example, I don't know if it is registered or not) only in the hopes of selling the domain name for mucho dinero later, then that kind of intent is not something I (or anybody else, I think) would find really acceptable, because now the use of "linux" in this case has really been a question of blocking somebody ELSE from using the term and using it to get money.
This is where the cybersquatting laws come in, for example, allowing the use of a trademark as a way to make sure that such squatting activity does NOT happen.
- Being "specific" is _good_. Being specific largely avoids the problem of many people/organizations wanting the same name. We had an example long ago of somebody who would have wanted to register "Linux Expert" as a servicemark, yet obviously that is a pretty generic term. Not good, if it means that there will be confusion about who owns the term.
In contrast (to give some tangible examples), something like "VA Linux" or "Red Hat Linux" oviously isn't a generic term: it's a very _targeted_ term for something very specific. Those kinds of names do not detract from other peoples ability to call _their_ Linux company something else.
- Finally, you have to judge the "officialdom" and the importance of the business side of your usage. Not because I or anybody else really cares all that much, but more because of the "pain factor" if the name is asked for by somebody else.
Basically, ask yourself the question: "What if somebody else had a project, and happened to chose the same name for his project as I have for mine, how strong a protection do I want for MY version of the project?"
Also, ask yourself: "Would anybody ever have reason to question the name, and do I need to make provisions for protecting this particular instance of it" (and note that "anybody" may not be me as the trademark owner myself, but it may be a competitor who wants to make life uncomfortable for you)
If you decide that you want some official protection from the mark, that probably means that you want to own your own version of the trademark, ie a "service mark" or a "combination mark". There are obvious cases where such a thing is wanted - you should not be surprised to hear that various Linux companies own their own combination marks, or have at the very least gotten that ownership verbally approved by me pending getting the paperwork done.
So basically, in case the trademark issue comes up, you should make your own judgement. If you read and understood the above, you know pretty much what my motivation is - I hate the paperwork, and I think all of this is frankly a waste of my time, but I need to do it so that in the future I don't end up being in a position I like even less.
And I'm _not_ out to screw anybody. In order to cover the costs of paperwork and the costs of just _tracking_ the trademark issues (and to really make it a legally binding contract in the first place), if you end up going the whole nine yards and think you need your own trademark protection, there is a rather nominal fee(*) associated with combination mark paperwork etc. That money actually goes to the Linux International trademark fund, so it's not me scalping people if anybody really thought that that might be the case;)
I hope people understand what happened, and why it happened, and why it really hasn't changed anything that we had to assert the trademark issue publically for the first time this week. And I hope people feel more comfortable about it.
And finally - I hope that people who decide due to this that what they really want is trademark protection for their own Linux trademark, that they could just wait a week or two, or contact maddog at Linux International rather than me. We're finally getting the shroud of secrecy lifted from transmeta (hey, we'll have a real web-site and zdtv is supposed to webcast the announcement tomorrow), and I'd rather worry about trademarks _next_ week.
Ok?
Linus
(*) "Nominal fee". What an ugly sentence. It's one of those things that implies that if you have to ask, you can't afford it. In reality, it's more a thing where both intent and the size of the project will make a difference - and quite frankly it's also a way to slightly discourage people who aren't really serious about it in the first place.
It is much better to start with a slower chip, say a Athlon 500, and then clock it up as necessary while lower the cache divider.
I bet a fair number of 500Mhz Athlon cores can do 750Mhz but are held back by the cheaper L2 cache they run. Getting a 750Mhz chip at the cost of a 500 aint too bad, even if it isn't as fast as the "real" Athlon 750s.
FWIW, egcs-1.1.2 is generally considered to be the most recent compiler available which should work safely for just about everything, including the kernel. Heck, if RedHat uses it as their default compiler, the advantages must outweigh the disadvantages of gcc-2.7.3.2. My own personal experiences reflect this.
I've tried a couple of kernels with gcc-2.95, but every time I do, weird things start happenning after a day or so, so I revert back to the same kernel compiled with egcs-1.1.2.
I wouldn't trust pgcc to compile my kernel unless it was a test machine where I didn't care how stable it was. It's good for squeezing the last ounce of performance out of a program, but make sure you benchmark!
I used to keep gcc-2.7.3.2 around for testing certain things, but deleted it after it wasn't getting any use.
My current setup now includes gcc-2.95.2 as the default compiler, and I installed egcs-1.1.2 into/usr/local/egcs-1.1.2/ for those kernel recompiles. Works great!
The company I work for uses NES on IRIX, and we've got constant problems with the webserver spontaneously rebooting itself, and taking out all current connections with it. It's a well known problem with NES, and it doesn't happen only on IRIX, but I've seen reports of it happening on Solaris as well, with no explanation or fixes.
We've also had problems with NES locking up completely under only moderate load, and no clue as to why it happenned... I've also seen reports of this from other users, so I know I'm not the only one. Very frustrating!
There's a lot of good information over at the UCSD Shiley Eye Center. One of my good friend's wife is going to get Intacs next Wednesday at Shiley, we'll see how it goes. And if it works well, I may be next in line!
well, the compilation died on me too but if you keep re-executing the commandline (make bzImage, or whatever) it'll eventually finish building.
If you have to reissue 'make bzImage' commands to finish building the kernel, you most definately have some faulty hardware, most likely bad memory. I bet that you're seeing signal 11's when compiling.
I've had plenty of the same problems as you, while using the glibc versions of Netscape. They got worse after I upgraded XFree86 to 3.3.5, with hangs all the time. I've switched to the libc5 build of Netscape 4.61 (I'm running glibc-2.1.2), and it hasn't crashed in a whole week which is amazing! Give it a shot, anyway...
From the limited experience that I have in the workplace, it seems that most of these "old-farts" (who I envision as ~45+) are just as enthusiastic about Linux as us young folks. In some cases, even more so!
The problem is that in many cases, these people are middle-management. They make decisions that will affect your life.
You have a decent point here. One of the reason's we didn't end up deploying Linux more often, was because it was different, and perceived as a "toy" OS, lacking features/stability that other well established (eg. Solaris) Unices offered. This was a headache for me for quite a while.
The managers wanted a "Real Unix Sysadmin" for our desktop Linux boxes. I countered "Well, then why don't I have a 'Real NT Sysadmin' for my NT machine? I have more problems with that than my Linux box!"
All he could say was that upper management demanded it. Luckily the Unix sysadmin is a great guy, and only logged in once or twice. But giving him root made management happy, so go figure.
The solution to making management happy? We used Linux under the table where managers didn't notice, because it always worked, just like countless other people out there.
It's pretty good. I've been playing the beta whenever I have a chance. There's a few seg-faults left to sort out, and getting the last ounces of performace out of it. (still a bit sluggish on my K6-2 300) The developers at Loki Entertainment Software have been real helpful throughout the process.
Actually, the exploit went way farther back than 2.2.1, back to the middle 2.1.X days (around 2.1.80 or so). Unlike Microsoft, the exploit was patched in a timely manner. -Dave
The AC Patches are a collection of patches that Alan throws together for testing purposes. I consider them to be "almost production" quality. He often fixes important bugs in the release kernel, so they're usually not a bad idea. There's always a ton of new features in them. Right now, it's the closest thing to a development branch of the kernel. You can get them ftp.kernel.org (or any of the mirrors).
There was one little bug that kept it from compiling if you had enables BSD process accounting. Affected quite a lot of people, but a patch was out within minutes of the 2.2.4 release. Other than that, I assume that Linus released this to get a bunch of little things fixed before he left town for a couple weeks.
Try this to get your Tulip working.
on
Linux 2.2.4
·
· Score: 1
There's two things you can try. First of all, try using the DEC driver, (leave both the DEC and Tulip drivers enabled). It's the CONFIG_DE4X5 option in your.config, also right above the Tulip driver in the menuconfig. If that doesn't detect your card either, grab the latest driver from Donald Beckers site and replace tulip.c with it. Someone else posted the URL to Donald's site.
-Dave
Here's how to get knfsd to work
on
Linux 2.2.4
·
· Score: 1
I just posted this under the "Technical Question?" thread. Here's the recipe: 1. Get HJL's knfsd-1.2 package from ftp://ftp.varesearch.com/pub/support/hjl/knfsd/ 1a. Untar it. 2. Compile it with `make` 3. Install it with `make install` 4. Replace/etc/init.d/nfs and/etc/init.d/nfs with the etc/rc.nfsd and etc/rc.nfsfs in the knfsd package. 5. Make sure portmap is setup to start BEFORE nfs starts. 6. Start nfs `/etc/init.d/nfs start` 7. Check to make sure it all worked `/etc/init.d/nfs status`
spoke:~>/etc/rc.d/init.d/nfs status rpc.kmountd (pid 125) is running... nfsd (pid 135 134) is running... lockd (pid 106) is running...
No problems here. Grab HJLs latest knfsd package (currently 1.2), compile it and install it, and replace your current/etc/init.d/nfs and/etc/init.d/nfsfs with the rc.nfsd and rc.nfsfs in the knfsd-1.2 package.
Grab the latest knfsd package at: ftp://ftp.varesearch.com/pub/support/hjl/knfsd/
Slashdot Mirror
Bose may sound good to the average listener (they tend to bump up the treble and bass which sounds good at initial impression, but tires later) but especially their lower end systems (especially the small cubes) are lacking in the mid-bass/mid region.
Do your research! Here's a couple links to some good Home Theater boards which should get you going:
www.hometheatertalk.com
www.hometheaterforum.com
The single best advise I can give when looking for speakers is to go and listen to a bunch of them, and bring your own listening material! It's hard enough trying to judge speakers when they're playing off different equipment and in different rooms, so stick with one CD/DVD that you're familiar with.
Don't you realize? EVERYONE has skeletons in their closet. Some people just have more/or less of them. I don't know anyone who hasn't done at least one thing which would be embarassing on a national level.
;-)
The system DOES WORK. The problem is that the majority of people are "happy enough" with the way things are that they don't get involved. When things get bad, the people will speak up (unless they've all been brainwashed by then!
Crap, stupid type-o. Should be don't, not dodn't!
I've got two K6-2 systems myself, have built half a dozen for friends and family, and know a bunch more who've built themselves K6-2 systems.
All of them are rock solid and perform great for the money that was put into them.
Of course, I didn't go out and but the cheapest motherboard available when for a $10 more a stable, good performing was available.
You may think that the K6-2 is "cheap" and "bad", but informed people know better.
The Duron is the same way. I've got a Duron 700 sitting here on my desk. I didn't chimp on the motherboard. It runs great (fast and stable) the the speed is indiscernable from an Athlon 700 and saved me $80 in the process. When I need a speed boost in a year or so, I'll drop in a 1.2GHz Athlon (which should run about $100 by then) and run for another year with no other changes.
Well, you know how the saying goes:
There's lies, damned lies, and statistics.
:-)
At UCSD before ethernet/cable modem was available to everyone, we did string up our own network.
You should have seen it, coax running through windows, along the roof, under ground, across paths, it was great.
Well, it was great until the RA went around cutting the cable at 10ft intervals.
Your "numbers" on the mysql site don't even include the latest release of Postgres (7.0.2) which contains many significant speed improvements. Meanwhile, and alpha version of mysql is being used. Your "numbers" as such are rather useless at this point in time. I really wish moderators would look at the information in posts first before modding them up.
But, according to this Anandtech article yhey will hopefully be available by the end of 2000.
On my buddies Rev 7 Creative 128 board, installing ALSA seemed to get sound working great.
--- begin quote --
-- end quote --I bet a fair number of 500Mhz Athlon cores can do 750Mhz but are held back by the cheaper L2 cache they run. Getting a 750Mhz chip at the cost of a 500 aint too bad, even if it isn't as fast as the "real" Athlon 750s.
I've tried a couple of kernels with gcc-2.95, but every time I do, weird things start happenning after a day or so, so I revert back to the same kernel compiled with egcs-1.1.2.
I wouldn't trust pgcc to compile my kernel unless it was a test machine where I didn't care how stable it was. It's good for squeezing the last ounce of performance out of a program, but make sure you benchmark!
I used to keep gcc-2.7.3.2 around for testing certain things, but deleted it after it wasn't getting any use.
My current setup now includes gcc-2.95.2 as the default compiler, and I installed egcs-1.1.2 into /usr/local/egcs-1.1.2/ for those kernel recompiles. Works great!
I can't get NT Option Pack to install without .dll errors on any machines with SP6, so Lotus Notes isn't the only one with problems!
We've also had problems with NES locking up completely under only moderate load, and no clue as to why it happenned... I've also seen reports of this from other users, so I know I'm not the only one. Very frustrating!
There's a lot of good information over at the UCSD Shiley Eye Center. One of my good friend's wife is going to get Intacs next Wednesday at Shiley, we'll see how it goes. And if it works well, I may be next in line!
well, the compilation died on me too but if you keep re-executing the commandline (make bzImage, or whatever) it'll eventually finish building.
If you have to reissue 'make bzImage' commands to finish building the kernel, you most definately have some faulty hardware, most likely bad memory. I bet that you're seeing signal 11's when compiling.
Check the The Signal 11 FAQ for clues on how to debug your problem.
First hint, if you're overclocking, don't!
I've had plenty of the same problems as you, while using the glibc versions of Netscape. They got worse after I upgraded XFree86 to 3.3.5, with hangs all the time. I've switched to the libc5 build of Netscape 4.61 (I'm running glibc-2.1.2), and it hasn't crashed in a whole week which is amazing! Give it a shot, anyway...
The problem is that in many cases, these people are middle-management. They make decisions that will affect your life.
You have a decent point here. One of the reason's we didn't end up deploying Linux more often, was because it was different, and perceived as a "toy" OS, lacking features/stability that other well established (eg. Solaris) Unices offered. This was a headache for me for quite a while.
The managers wanted a "Real Unix Sysadmin" for our desktop Linux boxes. I countered "Well, then why don't I have a 'Real NT Sysadmin' for my NT machine? I have more problems with that than my Linux box!"
All he could say was that upper management demanded it. Luckily the Unix sysadmin is a great guy, and only logged in once or twice. But giving him root made management happy, so go figure.
The solution to making management happy?
We used Linux under the table where managers didn't notice, because it always worked, just like countless other people out there.
It's pretty good. I've been playing the beta whenever I have a chance. There's a few seg-faults left to sort out, and getting the last ounces of performace out of it. (still a bit sluggish on my K6-2 300) The developers at Loki Entertainment Software have been real helpful throughout the process.
Actually, the exploit went way farther back than 2.2.1, back to the middle 2.1.X days (around 2.1.80 or so). Unlike Microsoft, the exploit was patched in a timely manner. -Dave
The AC Patches are a collection of patches that Alan throws together for testing purposes. I consider them to be "almost production" quality. He often fixes important bugs in the release kernel, so they're usually not a bad idea. There's always a ton of new features in them. Right now, it's the closest thing to a development branch of the kernel. You can get them ftp.kernel.org (or any of the mirrors).
There was one little bug that kept it from compiling if you had enables BSD process accounting. Affected quite a lot of people, but a patch was out within minutes of the 2.2.4 release. Other than that, I assume that Linus released this to get a bunch of little things fixed before he left town for a couple weeks.
There's two things you can try. First of all, try using the DEC driver, (leave both the DEC and Tulip drivers enabled). It's the CONFIG_DE4X5 option in your .config, also right above the Tulip driver in the menuconfig. If that doesn't detect your card either, grab the latest driver from Donald Beckers site and replace tulip.c with it. Someone else posted the URL to Donald's site.
-Dave
I just posted this under the "Technical Question?" thread. Here's the recipe: /etc/init.d/nfs and /etc/init.d/nfs with the etc/rc.nfsd and etc/rc.nfsfs in the knfsd package.
1. Get HJL's knfsd-1.2 package from ftp://ftp.varesearch.com/pub/support/hjl/knfsd/
1a. Untar it.
2. Compile it with `make`
3. Install it with `make install`
4. Replace
5. Make sure portmap is setup to start BEFORE nfs starts.
6. Start nfs `/etc/init.d/nfs start`
7. Check to make sure it all worked `/etc/init.d/nfs status`
Nope, lockd does the locking.
/etc/rc.d/init.d/nfs status
/etc/init.d/nfs and /etc/init.d/nfsfs with the rc.nfsd and rc.nfsfs in the knfsd-1.2 package.
spoke:~>
rpc.kmountd (pid 125) is running...
nfsd (pid 135 134) is running...
lockd (pid 106) is running...
No problems here.
Grab HJLs latest knfsd package (currently 1.2), compile it and install it, and replace your current
Grab the latest knfsd package at:
ftp://ftp.varesearch.com/pub/support/hjl/knfsd/
-Dave