Such biting wit. You're obviously a bitter, humourless old man. I pray your child doesn't end up like you. You're not getting a rise out me, no matter how childish your remarks. Good bye.
PS -- your "joke" still sucked. Remember, this is slashdot. Stating the obvious is modded "insightful" here. People say stupid shit in earnest. And you gave no reason to suspect you're not a moron. My joke got a rise out of you. That was sweet.
You were kidding when you said NYC was huge? I totally missed the context, because that "joke" was not funny. If you call that kidding, I fear for your children. You wouldn't happen to be an accountant or engineer, would you?
If the firewall is another easy layer of protection, they why not use it?
I didn't say that he shouldn't use a firewall. I said that his internal security procedures shouldn't depend on a firewall. There's a difference.
Imagine this scenario. A fortress has an inner wall and an outer wall. But the inner wall will fail if the outer wall is breached. It effectively only has one wall. There are two ways to harden this: you can either make the outer wall very strong, or you can make it so the inner wall doesn't depend on the outer wall, so that you actually have two independent layers of security.
My suggestion was that if you finds yourself slacking with regards to security procedures, you've effectively eliminated the inner wall. If the outer wall is breached, so is the inner one, by virtue of the fact that you're slacking. If the benefits of slacking (with respect to productivity, convenience, etc.) are sufficient, you should just harden the firewall and ditch the internal security processes. If maintaining security is a serious issue, you should do your damn job and implement the security processes. The fact that you have a firewall is no excuse for being sloppy, and sloppiness will bite you in the ass when the firewall fails.
So you see the firewall failing as inevitable - but can't fathom the possiblity of the server security itself ever being breached? What is wrong with this picture?
We have a firewall so that we CAN be a little sloppy inside if needed. It's the balance between security and usability.
If you find yourself being sloppy because you have a firewall installed, I suggest you re-evaluate your security model. Evaluate the points you're slacking on and figure out if you really need that layer of defense. If you don't, get rid of it -- it's clearly an inconvenience. If you do, stop using the firewall as a crutch. It will fail at some point, and your lapse will bite you in the ass.
The problem isn't remembering passwords, but remembering which password works with which login. If you have 20 logins and 20 passwords, there are on the order of 20! ways to mess up and compromise your other passwords.
I have used Gentoo. I realize that it is a perfectly viable distribution, and have not rejected it out of hand. I strongly considered ditching Debian in favor of Gentoo recently, but decided against it. My needs -- a lightweight PPC distro with only what I need installed on it -- are served just as well with Debian as they would have been with Gentoo.
However, I question the validity of the distinction you make, considering that Gentoo's biggest feature in this regard removes functionality (compared to a binary distro) for slight performance benefits. I'm of course referring to USE flags here. To wit, a given Debian package already does what I need, and possibly more. Why should I compile it myself for slight performance benefits unless that performance is what I seek?
Red Hat and Debian came up with their own package management systems. The issue is that Linux software is designed to be modular -- for instance, programmers take advantage of libraries so that they don't have to replicate code. But this creates a dependency. You need to have the library installed before you can use software that depends on it. Package management systems figure out what a software package depends on and installs that automatically.
The apt suite is Debian's package management system. Actually, I'm not sure if Red Hat came up with RPM or not. RPM.org isn't immediately clear on that point. But Red Hat is the distribution most strongly associated with RPM. I wish I could offer a comparison, but I couldn't offer a fair one. I tried Red Hat a few years ago and fell into "dependency hell," which is when a package manager can't figure out what needs to be installed. But this was several years ago. From what I gather, RPM is much better now. I've had no reason to switch from Debian though, so I haven't tried it since. Still, apt is nice.:-)
Strictly speaking, "ricer" is a racist term for asian youths who extensively modify their cars. The term has been picked up other uses to mean people who obsessively customize to gain minimal performance benefits. Gentoo is a source based distribution (for the most part) -- as such, the user must compile the software he plans on using. Gentoo was designed to facilitate easy optimization for your hardware/needs during the compile phase. This tends to cause much obsessiveness among its users.
I don't know what your goals are for Linux, but for desktop use, it would be hard to go wrong with Ubuntu. Debian is great for just about everything, but ideally you'd have some more experience (or enough patience to RTFM enough to ask smart questions). There are obviously other great distributions. Once you figure out what your needs are, check out http://www.distrowatch.com/ to help you pick a distribution.
Most of the distros you mentioned are designed to fill a particular niche. Ubuntu is designed as a user friendly Debian-based distro (meaning, it uses apt-get and not RPMs or some other scheme). Gentoo is for the ricers. Suse and Redhat are for the enterprise. Mandriva is an easy to use RPM based distro. Yellow Dog is a lame RPM based distro for PPC machines. The Brazilian, Chinese, Japanese, and German distros are for people who speak Portuguese, Chinese, Japanese, and German, respectively. Caldera is dead. See, they all fill a niche.
I like Sarge, but I've never used Slack. I've used it for about a year now. apt-get really is a great bit of software. Packages are designed to install and configure themselves intelligently, if not optimally. As long as you're not a pansy about typing into the command line, everything just works. But you can still tweak/install from source if you'd like. The default installation is not as slim as I'd like -- it weighs in at about 350 MB if you don't select any packages other than those "required" by the system. You can trim it if you'd like.
Regardless of the reputation the community has on/., it's terrific. lists.debian.org is a great resource. Smart questions are usually answered by curteous developers/users within an hour.
Enough raving about debian. Having never tried Slack, I can't say how they compare, but I think it's clear I'd recommend Sarge.
People disagree on what is "self-evident." Is it self-evident that black people are lazy? People used to think so. Is it self-evident that gays couples shouldn't be married? A lot of people think so now. Is it self-evident that a thing can't be both a particle and a wave? Sure, but it's flat out wrong. If your aim is to convince someone of a claim, you're going to have to persuade them to agree to each of your "axioms."
People use analogies because the structure of one situation is similar (analogous!) to that of another. Thus reasoning about one situation can be applied to another. There is nothing wrong with using well developed analogies, and analogies can be used to promote tremendous insight into a problem.
Regarding your claim that logic isn't easy, it is not apparent, except so far as your faulty post proves your point. You simply stated bare opinion without any supporting argument.
Yeah, all was going well until we tried using mysql to hold a 100 mb database. The kernel panicked and we lost 15 years worth of data. The company just couldn't recover from such a stunning blow. I was fired for suggesting Linux, and my boss said he would make me unemployable with bad references forever. All in all, I don't think Linux belongs in the work place.
Slashdot Mirror
It's a shame, really, that you're right. Your post has given me a great idea for a book. You're going in the acknowledgements.
Such biting wit. You're obviously a bitter, humourless old man. I pray your child doesn't end up like you. You're not getting a rise out me, no matter how childish your remarks. Good bye.
You're obviously an illiterate. Good bye.
Care to make any more assumptions about me?
PS -- your "joke" still sucked. Remember, this is slashdot. Stating the obvious is modded "insightful" here. People say stupid shit in earnest. And you gave no reason to suspect you're not a moron. My joke got a rise out of you. That was sweet.
You were kidding when you said NYC was huge? I totally missed the context, because that "joke" was not funny. If you call that kidding, I fear for your children. You wouldn't happen to be an accountant or engineer, would you?
I didn't say that he shouldn't use a firewall. I said that his internal security procedures shouldn't depend on a firewall. There's a difference.
Imagine this scenario. A fortress has an inner wall and an outer wall. But the inner wall will fail if the outer wall is breached. It effectively only has one wall. There are two ways to harden this: you can either make the outer wall very strong, or you can make it so the inner wall doesn't depend on the outer wall, so that you actually have two independent layers of security.
My suggestion was that if you finds yourself slacking with regards to security procedures, you've effectively eliminated the inner wall. If the outer wall is breached, so is the inner one, by virtue of the fact that you're slacking. If the benefits of slacking (with respect to productivity, convenience, etc.) are sufficient, you should just harden the firewall and ditch the internal security processes. If maintaining security is a serious issue, you should do your damn job and implement the security processes. The fact that you have a firewall is no excuse for being sloppy, and sloppiness will bite you in the ass when the firewall fails.
Your understanding of what I wrote.
If you find yourself being sloppy because you have a firewall installed, I suggest you re-evaluate your security model. Evaluate the points you're slacking on and figure out if you really need that layer of defense. If you don't, get rid of it -- it's clearly an inconvenience. If you do, stop using the firewall as a crutch. It will fail at some point, and your lapse will bite you in the ass.
We have hydrogen gas installations? Do you have to go to an industrial chemical supplier to buy your fuel?
The first thing I thought of after reading your question was the suicide booths from the pilot episode.
The problem isn't remembering passwords, but remembering which password works with which login. If you have 20 logins and 20 passwords, there are on the order of 20! ways to mess up and compromise your other passwords.
However, I question the validity of the distinction you make, considering that Gentoo's biggest feature in this regard removes functionality (compared to a binary distro) for slight performance benefits. I'm of course referring to USE flags here. To wit, a given Debian package already does what I need, and possibly more. Why should I compile it myself for slight performance benefits unless that performance is what I seek?
The apt suite is Debian's package management system. Actually, I'm not sure if Red Hat came up with RPM or not. RPM.org isn't immediately clear on that point. But Red Hat is the distribution most strongly associated with RPM. I wish I could offer a comparison, but I couldn't offer a fair one. I tried Red Hat a few years ago and fell into "dependency hell," which is when a package manager can't figure out what needs to be installed. But this was several years ago. From what I gather, RPM is much better now. I've had no reason to switch from Debian though, so I haven't tried it since. Still, apt is nice. :-)
Strictly speaking, "ricer" is a racist term for asian youths who extensively modify their cars. The term has been picked up other uses to mean people who obsessively customize to gain minimal performance benefits. Gentoo is a source based distribution (for the most part) -- as such, the user must compile the software he plans on using. Gentoo was designed to facilitate easy optimization for your hardware/needs during the compile phase. This tends to cause much obsessiveness among its users.
I don't know what your goals are for Linux, but for desktop use, it would be hard to go wrong with Ubuntu. Debian is great for just about everything, but ideally you'd have some more experience (or enough patience to RTFM enough to ask smart questions). There are obviously other great distributions. Once you figure out what your needs are, check out http://www.distrowatch.com/ to help you pick a distribution.
Most of the distros you mentioned are designed to fill a particular niche. Ubuntu is designed as a user friendly Debian-based distro (meaning, it uses apt-get and not RPMs or some other scheme). Gentoo is for the ricers. Suse and Redhat are for the enterprise. Mandriva is an easy to use RPM based distro. Yellow Dog is a lame RPM based distro for PPC machines. The Brazilian, Chinese, Japanese, and German distros are for people who speak Portuguese, Chinese, Japanese, and German, respectively. Caldera is dead. See, they all fill a niche.
I like Sarge, but I've never used Slack. I've used it for about a year now. apt-get really is a great bit of software. Packages are designed to install and configure themselves intelligently, if not optimally. As long as you're not a pansy about typing into the command line, everything just works. But you can still tweak/install from source if you'd like. The default installation is not as slim as I'd like -- it weighs in at about 350 MB if you don't select any packages other than those "required" by the system. You can trim it if you'd like.
/., it's terrific. lists.debian.org is a great resource. Smart questions are usually answered by curteous developers/users within an hour.
Regardless of the reputation the community has on
Enough raving about debian. Having never tried Slack, I can't say how they compare, but I think it's clear I'd recommend Sarge.
?
I think you misspelled "Hindenberg."
Good idea, AC. Thanks for the suggestion. I'll do it once it's TeXified.
Yeah, you can't play cock rock with a mechanical cock.
You must be an mcse.
Eh, Freescale manufactures G3's and G4's. IBM never made those -- Motorola did.
Yep. Look into VPNs.
Your script is suffering from feature-itis. It's starting to sound like Dupe Nukem Forever.
Read that sentence again. He gave a presentation to some people. Afterwards, he told reporters about it. Literacy isn't a bad thing, you know.
People use analogies because the structure of one situation is similar (analogous!) to that of another. Thus reasoning about one situation can be applied to another. There is nothing wrong with using well developed analogies, and analogies can be used to promote tremendous insight into a problem.
Regarding your claim that logic isn't easy, it is not apparent, except so far as your faulty post proves your point. You simply stated bare opinion without any supporting argument.
I'm just kidding. I would never recommend linux in the work place. ;-)
Yeah, all was going well until we tried using mysql to hold a 100 mb database. The kernel panicked and we lost 15 years worth of data. The company just couldn't recover from such a stunning blow. I was fired for suggesting Linux, and my boss said he would make me unemployable with bad references forever. All in all, I don't think Linux belongs in the work place.