> Red Hat & Xfree86 usually entirely lock up on me
> and require a reboot at least once a week, and
> xfree86 needs killing at least daily.
Erm... The ONLY time I've had Linux crash is when I compiled the kernel for the wrong processor architecture by accident (duh) and got a Kernel Panic. (told it it was going to be on an Athlon and it was a dual Pentium III system.;P My only plea for mercy is that I use the same monitor/keyboard/mouse for both computers and a switchbox to go back and forth:P)
(this is about the kernel, not an app, though I've not had many abends in Linux.... of any kind...)
As far as xfree86, I've never had it crash after getting it PROPERLY CONFIGURED, though it sometimes takes four or five hours to do that, and there was an "issue" with a Matrox card once that took me a few days to solve (option HWCursor = "0" is a Good Thing).
The moral of the story is - if it's crashing on you repeatedly, and the only reason I and most people I know have to shut down/reboot Linux boxen is power failure, evacuation of the building, or a lightning strike somehow scrambles the bios chip (I can't afford a UPS at home and power strips apparently aren't worth a damn - Note to anyone building their own systems - Tyan not only makes awesome motherboards, they have a help-desk for end users and will send you a replacement BIOS chip at no cost to you whatsoever, and their tech staff won't treat you like an idiot, either:D) then I'd be inclined say your problem is a configuration issue. If it's more than one machine, I'd say there is something you're overlooking or some erroneous assumption in your procedure (written or not) for installing Linux.
The verb is "to be," which is one of the few verbs that can be implied in English. The subject would properly be rendered as "This," an indefinite pronoun which, when the subject of an implied "to be," can also be implied.
If you couldn't follow that, then you're not enough of a grammar cop to be criticizing anyone.
Just have the range of IPs that the DHCP server has available to it for use excluded from LaBrea's scanning and you'll be fine. He explains in detail how to do set up ranges of IPs that will be ignored.
(I know I'm not putting this well, I'm tired:P) is if there were some way to combine this set of redirect conditions (which is what I'm currently using on my server - I know the worm doesn't follow them but it keeps the size of my error log down:P):
within Labrea in such a way that any GET to/scrips/,/_vti_bin/, etc. would trigger the "tar baby" effect, but other HTTP requests would go through. That way we could have our Apache web servers and our Tar Pits too. I would LOVE to have one of those.
--
Searching for Truth, Justice, and the Guy Who Boosted My Wallet a Few Weeks Back....
Quite simply, you'll destroy your eyes reading on-line documentation for long periods of time, the letters are *much* harder to see compared with the stark difference between the white of a paper page and the black of printed text.
A few other points:
A paper manual is customizeable; you can scribble in the margines, highlight important mentions, add to it, photocopy chunks of it and tack them on your wall, or just color the diagrams if you're bored. You can even dog-ear the pages if you are so inclined, leaving a permanent mark. PDF files are set in stone unless you fork over the money for Acrobat or have Illustrator.
A paper manual is a rugged stand-alone piece of equipment; it requires no power, is immune to EMP and can survive most operator errors, functions independently of any OS/platform, and only requires that you bring pairs of functioning eyes and hands, as well as an understanding of the written language it's "coded" in. The larger ones usually have a glossary to help with the last requirement.
A paper manual is portable; it can function hundreds or thousands of miles from any computer (though getting thousands of miles from a computer is a neat trick these days, at least in the Western hemisphere), or even thrown across the room in a fit of frustration. It's also forgiving, it will probably still be working when you pick it back up after said tantrum!
A paper manual is ergonomic; it can be carried across a room for a consultation with a colleague via an inconveniently-placed phone (if that is an issue), it does not require the installation of "reader" software or hardware unless you need glasses, in which case you *probably* already have them. If you don't need glasses, it won't *make* you need them as quickly (see the comment on contrast ratio above).
A paper manual is more user-friendly; you can flip back and forth between any two pages with great ease, it uses a rugged interface proven in hundreds of years of testing, and can even make you look smarter when sitting on your bookshelf. (provided it's on the right package)
Ok, enough of that, I'm off to get coffee.
-- Searching for Truth, Justice, and the guy who boosted my walled a few years back....
>Do we think auction sites should be liable for >their content? Is this like ISPs being liable for >what users download or read?
There is a difference, legally. An ISP can no more be held accountable for software piracy than the post office can be held accountable for mail fraud, they just pass on data packets, regardless of their content, using what limited (in comparison to the volume of "traffic" they handle) resources in co-operation with law enforcement to deal with the offenses that are so flagrant they can't help but notice them.
On the other hand, Yahoo! is acting as an agent in specific transactions on their auction site, regardless of whether a human being is monitoring each individual one or not, therefore if stolen property is traded through them, they are at the very least liable as accomplices.
As for the point on another thread where someone mentioned that the wording in a sale might imply that what was being sold was a backup service, IIRC most licenses and related law in this area states that the license holder can make their OWN backup copy, but does not make any mention of making backup copies for other people who are also lisence holders. -- Searching for truth, Justice, and the guy who booted my wallet a few years back...
A precedent for it has already been set; L. Ron Hubbard (a.k.a. Phattman) of Dianetics/Scientology fame avoided all sorts of legal issues for a long time by never coming ashore. It's quite possible that INTERPOL or other international LEOs have come up with a strategy for dealing with that sort of chicanery. Based on how much of a nuisance he was, sailing around in plain sight but effectively untouchable, I'd expect so.. --- Searching for Truth, Justice, and the guy who booted my wallet a few years back.
Slashdot Mirror
Ah, apologies.
*reminds self never to post before having coffee....*
I wish someone could have modded this up....
*wipes coffee off the monitor screen*
> Red Hat & Xfree86 usually entirely lock up on me
;P My only plea for mercy is that I use the same monitor/keyboard/mouse for both computers and a switchbox to go back and forth :P)
:D) then I'd be inclined say your problem is a configuration issue. If it's more than one machine, I'd say there is something you're overlooking or some erroneous assumption in your procedure (written or not) for installing Linux.
> and require a reboot at least once a week, and
> xfree86 needs killing at least daily.
Erm... The ONLY time I've had Linux crash is when I compiled the kernel for the wrong processor architecture by accident (duh) and got a Kernel Panic. (told it it was going to be on an Athlon and it was a dual Pentium III system.
(this is about the kernel, not an app, though I've not had many abends in Linux.... of any kind...)
As far as xfree86, I've never had it crash after getting it PROPERLY CONFIGURED, though it sometimes takes four or five hours to do that, and there was an "issue" with a Matrox card once that took me a few days to solve (option HWCursor = "0" is a Good Thing).
The moral of the story is - if it's crashing on you repeatedly, and the only reason I and most people I know have to shut down/reboot Linux boxen is power failure, evacuation of the building, or a lightning strike somehow scrambles the bios chip (I can't afford a UPS at home and power strips apparently aren't worth a damn - Note to anyone building their own systems - Tyan not only makes awesome motherboards, they have a help-desk for end users and will send you a replacement BIOS chip at no cost to you whatsoever, and their tech staff won't treat you like an idiot, either
I did read the whole doc page, and it said it would TRY to recover nicely, but explicitly did not guarantee that it will be able to do so.
;P
Since most people only are on networks which are a served by DHCP when they're in a production environment, it's better to be safe than sorry.
Do try not to be condescending when it's unwarranted.
The verb is "to be," which is one of the few verbs that can be implied in English. The subject would properly be rendered as "This," an indefinite pronoun which, when the subject of an implied "to be," can also be implied.
If you couldn't follow that, then you're not enough of a grammar cop to be criticizing anyone.
Just have the range of IPs that the DHCP server has available to it for use excluded from LaBrea's scanning and you'll be fine. He explains in detail how to do set up ranges of IPs that will be ignored.
(I know I'm not putting this well, I'm tired :P) is if there were some way to combine this set of redirect conditions (which is what I'm currently using on my server - I know the worm doesn't follow them but it keeps the size of my error log down :P):
/scripts/ http://127.0.0.1/
/_vti_bin/ http://127.0.0.1/
/_mem_bin/ http://127.0.0.1/
/c/winnt/ http://127.0.0.1/
/d/winnt/ http://127.0.0.1/
/msadc/ http://127.0.0.1/
/MSADC/ http://127.0.0.1/
/default.ida http://127.0.0.1/
/scrips/, /_vti_bin/, etc. would trigger the "tar baby" effect, but other HTTP requests would go through. That way we could have our Apache web servers and our Tar Pits too. I would LOVE to have one of those.
Redirect permanent
Redirect permanent
Redirect permanent
Redirect permanent
Redirect permanent
Redirect permanent
Redirect permanent
Redirect permanent
within Labrea in such a way that any GET to
--
Searching for Truth, Justice, and the Guy Who Boosted My Wallet a Few Weeks Back....
Quite simply, you'll destroy your eyes reading on-line documentation for long periods of time, the letters are *much* harder to see compared with the stark difference between the white of a paper page and the black of printed text.
A few other points:
A paper manual is customizeable; you can scribble in the margines, highlight important mentions, add to it, photocopy chunks of it and tack them on your wall, or just color the diagrams if you're bored. You can even dog-ear the pages if you are so inclined, leaving a permanent mark. PDF files are set in stone unless you fork over the money for Acrobat or have Illustrator.
A paper manual is a rugged stand-alone piece of equipment; it requires no power, is immune to EMP and can survive most operator errors, functions independently of any OS/platform, and only requires that you bring pairs of functioning eyes and hands, as well as an understanding of the written language it's "coded" in. The larger ones usually have a glossary to help with the last requirement.
A paper manual is portable; it can function hundreds or thousands of miles from any computer (though getting thousands of miles from a computer is a neat trick these days, at least in the Western hemisphere), or even thrown across the room in a fit of frustration. It's also forgiving, it will probably still be working when you pick it back up after said tantrum!
A paper manual is ergonomic; it can be carried across a room for a consultation with a colleague via an inconveniently-placed phone (if that is an issue), it does not require the installation of "reader" software or hardware unless you need glasses, in which case you *probably* already have them. If you don't need glasses, it won't *make* you need them as quickly (see the comment on contrast ratio above).
A paper manual is more user-friendly; you can flip back and forth between any two pages with great ease, it uses a rugged interface proven in hundreds of years of testing, and can even make you look smarter when sitting on your bookshelf. (provided it's on the right package)
Ok, enough of that, I'm off to get coffee.
--
Searching for Truth, Justice, and the guy who boosted my walled a few years back....
>Do we think auction sites should be liable for
>their content? Is this like ISPs being liable for
>what users download or read?
There is a difference, legally. An ISP can no more be held accountable for software piracy than the post office can be held accountable for mail fraud, they just pass on data packets, regardless of their content, using what limited (in comparison to the volume of "traffic" they handle) resources in co-operation with law enforcement to deal with the offenses that are so flagrant they can't help but notice them.
On the other hand, Yahoo! is acting as an agent in specific transactions on their auction site, regardless of whether a human being is monitoring each individual one or not, therefore if stolen property is traded through them, they are at the very least liable as accomplices.
As for the point on another thread where someone mentioned that the wording in a sale might imply that what was being sold was a backup service, IIRC most licenses and related law in this area states that the license holder can make their OWN backup copy, but does not make any mention of making backup copies for other people who are also lisence holders.
--
Searching for truth, Justice, and the guy who booted my wallet a few years back...
A precedent for it has already been set; L. Ron Hubbard (a.k.a. Phattman) of Dianetics/Scientology fame avoided all sorts of legal issues for a long time by never coming ashore. It's quite possible that INTERPOL or other international LEOs have come up with a strategy for dealing with that sort of chicanery. Based on how much of a nuisance he was, sailing around in plain sight but effectively untouchable, I'd expect so..
---
Searching for Truth, Justice, and the guy who booted my wallet a few years back.