I admit I'm relatively new (13 months to my credit) to this, but I happen to expect that a "stable" release is actually compilable. Why are we worried about compiling on weird systems for QA if nobody even bothers to test them on a normal one?
For me, anything I try to say to myself gets interrupted by irrational whining about how it should've been different. So the easiest thing to do is just not think about it, by doing something else enjoyable. I've always liked a good book.
If you stretch the point slightly, GIF animations using the "combine" method of changing frames use alpha compositing--the alpha is just binary on/off, but it's still transparency, and it's being composited since frame N's data is composited with frame N-1 (which may have itself been composited from an earlier image).
I'm sorry, I'm just really struggling very hard to try grasp this somewhat common notion that sex (or even nudity for that matter) is bad.
The underlying problem is that "sex" is too broad a category. Intercourse itself is neither inherently good or bad; it is circumstance that defines this. If you want children, it's not bad. On the other hand, I know of nobody who would say the rape was good, not even the guy. Yet both come from the same fundamental act, which is one tiny part of the sex category.
Add as many layers as you can think of to your security. For instance, I've set up/etc/profile so that it runs lastb|grep `id -un` for the user at login time. This lets the user see all failed logins and what time the attempt was made. When/var/run/btmp gets big enough, logrotate moves it and invokes a script to mail me the old one. A common variation on this is to print out a message, "There have been 35 failed attempts since your last successful login."
I think beyond a certain point, password strength is a joke. If passwd(1) is set up to disallow the usual variations on a username and dictionary attacks, the attacker will either have to either get lucky and find a user with a relatively weak password, or get ahold of/etc/shadow (in which case you'd have more serious problems to worry about...)
But did he *know* about the bullying?
on
Sean In The Middle
·
· Score: 1
To take action, you first have to notice.
My parents wouldn't (didn't) know if I were suicidal. I told them she was raped the day after I found out, and I get "Well, you seemed a little emotional last night, but I didn't think it was anything that bad." These are the people who have been living with me for nineteen years.........
The sorta same thing happened with the 386SX/DX and the 486SX/DX bit.
Error! The 486DX was an SX with an integrated FPU. (Actually, early SX's were DX's with a defective FPU disabled--Intel was selling trash.) And the 487SX "FPU" was a 486DX with an odd pinout that turned off your 486SX, similar to the OverDrives (Pentium core.)
But you're right wrt 386SX=16bit and 386DX=32bit busses.
Speaking of overheating... get a real mobo
on
Pentium IV study
·
· Score: 1
From the Asus A7V manual, page 45: "Beep: High frequency beeps when system is working Meaning: CPU overheated, system operating at a reduced frequency"
Open systems tend to have more bugs found and fixed but closed systems have far fewer exploits found -- they're about the same.
Think of OpenBSD and Windows NT, then say that again.
Security isn't so much a question of open vs. closed, but the underlying techniques behind the development. If you're always pushing for neat toys (ASP [a poisonous snake]) over fixing things (formatting string bugs), you'll end up with more holes, regardless of whether the end product is open or closed.
Getting back to encryption, would you trust my algorithm? I can't tell you what it is; you just have to trust me that it's "secure".
The general opinion of Average Joe is, "Why would they bother to listen to
me?"
If there's millions of people using cell phones, then A. Joe will assume
the expense of listening to his particular one is not worth the benefit, and
not care. Like how one of my friends has Windows shares on computers with
DSL--and no firewall. "Oh, there's so many other computers, what are they
going to do with mine?" And since his parents, not him, will be going to jail
if kiddie porn shows up, he doesn't care.
So I don't see how this ad is going to affect anyone.
There are some cases where the host of a site must be liable for it's content.
Kinda scary... if someone breaks into my (hypothetical) Windoze box and leaves stuff there, am I liable for it? Guilty until proven innocent... worse, what if they encrypted it? How can someone tell whether I'm hiding it or I just don't know it?
DOS boot disks are not the sort of thing you carry around in your purse...
Oh, sure, now they tell me... I carry DOS floppies with System Analyzer [shareware]--that's the only program that's ever seen my system as a Duron. Very nice.
I HATE info. It isn't
intelligent enough to
pay any attention to
the size of the display
(or gnu or redhat
prerendered the pages)
so that everything
is still wrapped to
80 columns.
Man, on the other hand, wraps properly to fill all 132 columns. Just like HTML. (Hail Curses!)
Back before I moved to Lynx, I had images disabled in Netscrape.
"Onvia.com. Work. Wisely." is probably the most effective ad I saw, because
all the others were "Click Here!"
IIRC, 72 Hz is considered the lowest flicker-free frequency. Personally, I can catch my console flickering only in my peripheral and only when the screen is solidly colored (like with ntsysv), and that's 68 Hz. X is fine at 75 Hz, and horrendous at 60 Hz.
You answered your question: it takes money to send out paper junk mail.
You can't just write one letter, address it to thousands of people, and have
the Post Office make and deliver all those copies.
I've had RH7.0 since October, and the only thing I have ever had trouble
compiling/running is stuff from their "sources" (xxxx.src.rpm). Everything
I've downloaded (blade, LAME, kernels 2.4.0-test11 and 2.4.1, e2fsprogs,
modutils 2.4.2, etc.) works perfectly fine. Even the pre-built (and
statically linked) gpart worked, for which my partition table is eternally
thankful....
Re:What is wrong with US DSL? Apathy.
on
DSL Woes
·
· Score: 1
It's the "who cares, customers just complain" attitude, I think.
It's much cheaper just to piss off the whiners so they'll leave than to
fix their problem. Word of mouth takes a little time to spread, in which the
big corporations can have such rock-bottom prices that it attracts a large
number of customers from ISPs who have good service. So those ISPs have to
cut costs, and it drags everything down to the lowest common denominator.
For some strange reason, your car analogy
reminds me of a certain company from Redmond. The
road owner company can work on traffic monitoring
technology to help drivers pick the fastest
route, but this feature is only found in
Microcars....
Slashdot Mirror
I admit I'm relatively new (13 months to my credit) to this, but I happen to expect that a "stable" release is actually compilable. Why are we worried about compiling on weird systems for QA if nobody even bothers to test them on a normal one?
For me, anything I try to say to myself gets interrupted by irrational whining about how it should've been different. So the easiest thing to do is just not think about it, by doing something else enjoyable. I've always liked a good book.
If you stretch the point slightly, GIF animations using the "combine" method of changing frames use alpha compositing--the alpha is just binary on/off, but it's still transparency, and it's being composited since frame N's data is composited with frame N-1 (which may have itself been composited from an earlier image).
I'm sorry, I'm just really struggling very hard to try grasp this somewhat common notion that sex (or even nudity for that matter) is bad.
The underlying problem is that "sex" is too broad a category. Intercourse itself is neither inherently good or bad; it is circumstance that defines this. If you want children, it's not bad. On the other hand, I know of nobody who would say the rape was good, not even the guy. Yet both come from the same fundamental act, which is one tiny part of the sex category.
Add as many layers as you can think of to your security. For instance, I've set up /etc/profile so that it runs lastb|grep `id -un` for the user at login time. This lets the user see all failed logins and what time the attempt was made. When /var/run/btmp gets big enough, logrotate moves it and invokes a script to mail me the old one. A common variation on this is to print out a message, "There have been 35 failed attempts since your last successful login."
I think beyond a certain point, password strength is a joke. If passwd(1) is set up to disallow the usual variations on a username and dictionary attacks, the attacker will either have to either get lucky and find a user with a relatively weak password, or get ahold of /etc/shadow (in which case you'd have more serious problems to worry about...)
To take action, you first have to notice.
My parents wouldn't (didn't) know if I were suicidal. I told them she was raped the day after I found out, and I get "Well, you seemed a little emotional last night, but I didn't think it was anything that bad." These are the people who have been living with me for nineteen years.........
The sorta same thing happened with the 386SX/DX and the 486SX/DX bit.
Error! The 486DX was an SX with an integrated FPU. (Actually, early SX's were DX's with a defective FPU disabled--Intel was selling trash.) And the 487SX "FPU" was a 486DX with an odd pinout that turned off your 486SX, similar to the OverDrives (Pentium core.)
But you're right wrt 386SX=16bit and 386DX=32bit busses.
From the Asus A7V manual, page 45: "Beep: High frequency beeps when system is working Meaning: CPU overheated, system operating at a reduced frequency"
So, how do you foresee Intel dominating the platform war?
Remember when Intel was the unstoppable giant and everyone thought AMD was going to go belly-up?
Open systems tend to have more bugs found and fixed but closed systems have far fewer exploits found -- they're about the same.
Think of OpenBSD and Windows NT, then say that again.
Security isn't so much a question of open vs. closed, but the underlying techniques behind the development. If you're always pushing for neat toys (ASP [a poisonous snake]) over fixing things (formatting string bugs), you'll end up with more holes, regardless of whether the end product is open or closed.
Getting back to encryption, would you trust my algorithm? I can't tell you what it is; you just have to trust me that it's "secure".
The general opinion of Average Joe is, "Why would they bother to listen to me?"
If there's millions of people using cell phones, then A. Joe will assume the expense of listening to his particular one is not worth the benefit, and not care. Like how one of my friends has Windows shares on computers with DSL--and no firewall. "Oh, there's so many other computers, what are they going to do with mine?" And since his parents, not him, will be going to jail if kiddie porn shows up, he doesn't care.
So I don't see how this ad is going to affect anyone.
There are some cases where the host of a site must be liable for it's content.
Kinda scary... if someone breaks into my (hypothetical) Windoze box and leaves stuff there, am I liable for it? Guilty until proven innocent... worse, what if they encrypted it? How can someone tell whether I'm hiding it or I just don't know it?
DOS boot disks are not the sort of thing you carry around in your purse...
Oh, sure, now they tell me... I carry DOS floppies with System Analyzer [shareware]--that's the only program that's ever seen my system as a Duron. Very nice.
(The purse in my case is strictly notional.)
Go ahead. Just _try_ tab completion or ad[vV]anced.{glob,pattern}s on MICROS~1.
Also, Linux lowercases 8.3 names, but VFAT ones are case-sensitive. So 8.3 is inherently superior (I'd like my Amiga back, please.)
I HATE info. It isn't
intelligent enough to
pay any attention to
the size of the display
(or gnu or redhat
prerendered the pages)
so that everything
is still wrapped to
80 columns.
Man, on the other hand, wraps properly to fill all 132 columns. Just like HTML. (Hail Curses!)
Back before I moved to Lynx, I had images disabled in Netscrape. "Onvia.com. Work. Wisely." is probably the most effective ad I saw, because all the others were "Click Here!"
If they merely ignore us, we'll end up with the inet equivalent of Dilbert.
IIRC, 72 Hz is considered the lowest flicker-free frequency. Personally, I can catch my console flickering only in my peripheral and only when the screen is solidly colored (like with ntsysv), and that's 68 Hz. X is fine at 75 Hz, and horrendous at 60 Hz.
You answered your question: it takes money to send out paper junk mail. You can't just write one letter, address it to thousands of people, and have the Post Office make and deliver all those copies.
grep ssh /etc/services
Next to be sued: Red Hat, Debian, Slackware, et al. for not clearly labeling SSH as a trademark.
I've had RH7.0 since October, and the only thing I have ever had trouble compiling/running is stuff from their "sources" (xxxx.src.rpm). Everything I've downloaded (blade, LAME, kernels 2.4.0-test11 and 2.4.1, e2fsprogs, modutils 2.4.2, etc.) works perfectly fine. Even the pre-built (and statically linked) gpart worked, for which my partition table is eternally thankful....
It's the "who cares, customers just complain" attitude, I think.
It's much cheaper just to piss off the whiners so they'll leave than to fix their problem. Word of mouth takes a little time to spread, in which the big corporations can have such rock-bottom prices that it attracts a large number of customers from ISPs who have good service. So those ISPs have to cut costs, and it drags everything down to the lowest common denominator.
For some strange reason, your car analogy reminds me of a certain company from Redmond. The road owner company can work on traffic monitoring technology to help drivers pick the fastest route, but this feature is only found in Microcars....
I call any toll-free-to-me numbers they're dumb enough to give out and leave lengthy monologues about not wishing to receive spam.
If everybody did this, phone bills would convince real companies not to spam.
The only problem I see with reprogramming is the heat output. What happens when dnetc and the GIMP get into reconfiguration wars?