Before starting, make sure your tools can be configured to avoid scans of sensitive equipment during work hours. You should know exactly where each server and router is on your network, and run scans against them during maintenance windows, when a crash will not impact the company and the admins are available to bring the systems back up.
I disagree. Crackers will not do you the favor of waiting until convenient times to stress your network. If a security scan brings down a server in the middle of the day, then that server was broken, not the scanner. Repeat: a scanner does not cause breakage - broken applications cause breakage.
We reboot our servers at regular intervals to very that they can bring themselves back up, and so that someone will be available if they can't. This is the same. Do you want to require your DBAs to be in the office at 3am when you're running a security scan, just in case? No, you don't.
To say it once more: if your network scanner crashes a server, then the server is at fault, and not the scanner.
Because I'm too lazy to look it up...
on
More on Global Dimming
·
· Score: 3, Interesting
Could someone explain how we know that less light is reaching the surface now? What accurate instruments were we using 100 years ago that gave us a solid baseline to compare against? Also, how were we accurately measuring solar output, which can be pretty variable?
Is the surface of the earth really receiving less light, or are we just better at measuring it?
Sig: The "HIV==AIDS" hypothesis is the biggest medical fraud in human history. http://www.virusmyth.net/
I find it interesting that people are responding to someone who explicitly states that they're trolling. Don't waste your breath, folks - you have been trolled and the more you argue, the more he laughs.
Move along and debate someone who honestly disagrees with you, and isn't just pulling your strings for the fun of it.
FreeBSD's filesystem has an "immutable" flag. If you set that flag on a file or directory, and set the system's securelevel to a suitably high value, then that file cannot be tampered with except by rebooting the machine. If Linux has a similar facility, that's a nice way to make it impossible for someone to "futz with the syslog configuration".
I fully agree, except that I think this is a strong case for SSH with Kerberos authentication. If you fire a sysadmin, the last thing you want to have to do is to de-authorize them from several hundred machines where they have root access. A centralized authentication system could provide a big payoff in this setup.
Also, I'd pick Subversion (or even CVS) over RCS, since you can create a central server to store all configuration information for every machine. This is extremely nice when you want to clone one the setup of one of your servers to try a clean install of a new version of one of your applications.
This is a failing of UNIX in general, not MacOS in particular.
Actually, that is a failing of particular versions of Unix. From FreeBSD's pf.conf(5) man page:
block out proto { tcp, udp } all pass out proto { tcp, udp } all user { < 1000, dhartmei } keep state
On a {Free,Open,Net?}BSD machine, you can define lists of users that may establish outbound connections. I would imagine that Apple could port pf to Mac OS X and wrap a shiny configurator around it if they really wanted to.
You are exactly correct. At the recommended inflation, the tread of a tire is mostly flat (from side to side). Go under that level, and it becomes slightly concave so that you're riding on the outside edges of the tread. Overinflation make the tread slightly convex so that you're mainly using the middle of the tread.
It might give you slightly better mileage by decreasing contact area (and therefore rolling friction), but it certainly won't increase traction.
It will also cause your tires and suspension (due to increased transmission of road surface defects) to wear faster, and you have to remember that the manufacturing processes for those parts isn't all happy and "green".
And it is not beyond the realms of possibility that MS might sell a piece of GPL software. If they did, that wouldn't stop them being a 'closed source' vendor.
I didn't realize that "closed" and "open" were mutually exclusive. Was SuSe a closed source vendor before they released the source to yast?
If they sell open source products, then they are an open source vendor, in addition to other roles they may have. They are perfectly entitled, both legally and morally, to make a profit from Free software as long as they abide by the rules.
Unlike a lot of you, Linus isn't a Linux zealot. He's said on more than one occasion that Linux/OSS is about making the right tool for the job when one doesn't already exist. It has nothing to do with shoving an ideology down everyone's throat.
And that's perfectly OK, for him. He is free to use whatever tools he wants. However, that doesn't mean that we can't be disappointed that he chose a closed tool with a nasty license, especially since his decision makes for a de-facto Linux development system that is unacceptable to many of us.
Linus is a great guy with a lot of talent, but that doesn't qualify him for sainthood. I think that going with BK was a mistake, and it is my right to believe so regardless of how much I otherwise respect him.
Depends. Did the move to BK come before or after IBM jumped in and started donating huge amounts of code to the kernel, companies started pumping out device drivers, and Linux became a well-known name in IT circles?
I'd be willing to bet that KDE and Gnome have accelerated a lot since Linux moved to BK, but I don't think that anyone would assert that BitKeeper should get the credit.
In short, that move happened at a fixed point in time when a whole lot of other interesting things were starting to happen. Was BK causative or correlative? I'd put money on the latter.
The biggest problem is that due to some twit companies releasing two utterly different cards under the same model name but with a point-bump in the version number, I'm pretty gun shy of buying cards from someplace where I can't easily return them.
Thanks for the other information. If my WLAN didn't account for probably 25% of the wireless networks in my whole city, I'd be pretty interested in high gain antennas.
On a second reading, I'm not sure if that's good enough. If by that, they mean "allow users to write client-side filters to move messages from one IMAP filter to another", then the problem is solved.
However, their wording could also mean "allow users to edit server-side Sieve scripts, and then we don't have to implement client filters", which would be worthless to many of us. First, not all IMAP servers support Sieve. Second, my IMAP setup uses special folders for spam/ham training, which means that I need some sort of client filtering to get the mail into those folders (unless I want to individually drag-and-drop each spam into the spam trainer, which I don't).
Please, oh please, let them be taking the path of "let's do it right" instead of "let's do the bare minimum necessary to advertise that we support this feature". The roadmap could be interpreted either way.
I suppose I see your point, although I still adhere tightly to the idea that it's morally acceptable in every way.
In my personal case, I'd even argue that format-shifting from a closed format to an open one is the same as making an archive copy, since I'm reasonably sure that I'll always be able to play an MP3 or OGG, or at least convert one to the format-du-jour years from now, but I have no expectation that I'll be able to do the same with an encrypted AAC.
I use KDE, so Kontact integrates better with the rest of my desktop than does Evolution. However, this is bound to be good for me, too, since the KDE folks can presumably use this to improve KMail's Exchange support. Oh, to be able to view the company calendar without booting into XP. That would be very, very nice.
Novell, you seriously rock. I know you're doing this for business reasons, but you just bought a lood of goodwill from a bunch of folks in IT departments. Thank you!
OT harp: Now, if KMail would just add IMAP filtering...;-)
Since I wouldn't be old enough to enter a contract, I wouldn't be able to be bound by the terms of the EULA that say I have to be 18. How would that work out?
However, copying to other formats is not obviously fair use.
...in much the same way that converting an RF broadcast into a pattern of magnetic particles on a VHS tape is illegal and not practiced by law-abiding citizens.
How is AAC -> MP3 for personal use inherently different than broadcast television -> VCR for personal use? If anything, it seems like more of a fair use no-brainer, since you've actually purchased (forget the EULA: read all of their advertising) the product, and therefor have more right to use it as you see fit and someone who merely happens to receive a signal in their home - at least, according to any reasonable 3rd-party observer.
If you break the GPL, you are committing copyright infringement. If you use this tool, you may not be committing copyright infringement.
We can and should be upset with people using this to distribute cracked files, but there is no clear reason why using it to, say, play back legitimately purchased files on a Linux machine is morally or legally wrong.
As I mentioned in a previous post, the same is true for their PCMCIA cards. On my Debian laptop, the card was plug-and-play (as much as anything is under Debian, anyway).
I just feel bad for any kid who even remotely buys into his idiocy and dies because of it.
Really, folks, read before you moderate. Is it that hard?
I disagree. Crackers will not do you the favor of waiting until convenient times to stress your network. If a security scan brings down a server in the middle of the day, then that server was broken, not the scanner. Repeat: a scanner does not cause breakage - broken applications cause breakage.
We reboot our servers at regular intervals to very that they can bring themselves back up, and so that someone will be available if they can't. This is the same. Do you want to require your DBAs to be in the office at 3am when you're running a security scan, just in case? No, you don't.
To say it once more: if your network scanner crashes a server, then the server is at fault, and not the scanner.
Is the surface of the earth really receiving less light, or are we just better at measuring it?
I find it interesting that people are responding to someone who explicitly states that they're trolling. Don't waste your breath, folks - you have been trolled and the more you argue, the more he laughs.
Move along and debate someone who honestly disagrees with you, and isn't just pulling your strings for the fun of it.
FreeBSD's filesystem has an "immutable" flag. If you set that flag on a file or directory, and set the system's securelevel to a suitably high value, then that file cannot be tampered with except by rebooting the machine. If Linux has a similar facility, that's a nice way to make it impossible for someone to "futz with the syslog configuration".
Also, I'd pick Subversion (or even CVS) over RCS, since you can create a central server to store all configuration information for every machine. This is extremely nice when you want to clone one the setup of one of your servers to try a clean install of a new version of one of your applications.
That's the rated maximum. My OEM Intrigue tires are rated at 35psi, but you'd be an idiot to keep them there.
Actually, that is a failing of particular versions of Unix. From FreeBSD's pf.conf(5) man page:
On a {Free,Open,Net?}BSD machine, you can define lists of users that may establish outbound connections. I would imagine that Apple could port pf to Mac OS X and wrap a shiny configurator around it if they really wanted to.
It might give you slightly better mileage by decreasing contact area (and therefore rolling friction), but it certainly won't increase traction.
It will also cause your tires and suspension (due to increased transmission of road surface defects) to wear faster, and you have to remember that the manufacturing processes for those parts isn't all happy and "green".
I didn't realize that "closed" and "open" were mutually exclusive. Was SuSe a closed source vendor before they released the source to yast?
If they sell open source products, then they are an open source vendor, in addition to other roles they may have. They are perfectly entitled, both legally and morally, to make a profit from Free software as long as they abide by the rules.
Umm, wouldn't that make them an Open Source vendor, and therefore not a target of Ckwop's complaint?
And that's perfectly OK, for him. He is free to use whatever tools he wants. However, that doesn't mean that we can't be disappointed that he chose a closed tool with a nasty license, especially since his decision makes for a de-facto Linux development system that is unacceptable to many of us.
Linus is a great guy with a lot of talent, but that doesn't qualify him for sainthood. I think that going with BK was a mistake, and it is my right to believe so regardless of how much I otherwise respect him.
I assert that RMS' productivity went up ten-fold since I started using Subversion. Are you going to get upset if someone asks for more proof?
I'd be willing to bet that KDE and Gnome have accelerated a lot since Linux moved to BK, but I don't think that anyone would assert that BitKeeper should get the credit.
In short, that move happened at a fixed point in time when a whole lot of other interesting things were starting to happen. Was BK causative or correlative? I'd put money on the latter.
Thanks for the other information. If my WLAN didn't account for probably 25% of the wireless networks in my whole city, I'd be pretty interested in high gain antennas.
However, their wording could also mean "allow users to edit server-side Sieve scripts, and then we don't have to implement client filters", which would be worthless to many of us. First, not all IMAP servers support Sieve. Second, my IMAP setup uses special folders for spam/ham training, which means that I need some sort of client filtering to get the mail into those folders (unless I want to individually drag-and-drop each spam into the spam trainer, which I don't).
Please, oh please, let them be taking the path of "let's do it right" instead of "let's do the bare minimum necessary to advertise that we support this feature". The roadmap could be interpreted either way.
Thank you for making my day (pathetic, aren't I?).
In my personal case, I'd even argue that format-shifting from a closed format to an open one is the same as making an archive copy, since I'm reasonably sure that I'll always be able to play an MP3 or OGG, or at least convert one to the format-du-jour years from now, but I have no expectation that I'll be able to do the same with an encrypted AAC.
Novell, you seriously rock. I know you're doing this for business reasons, but you just bought a lood of goodwill from a bunch of folks in IT departments. Thank you!
OT harp: Now, if KMail would just add IMAP filtering... ;-)
Since I wouldn't be old enough to enter a contract, I wouldn't be able to be bound by the terms of the EULA that say I have to be 18. How would that work out?
...in much the same way that converting an RF broadcast into a pattern of magnetic particles on a VHS tape is illegal and not practiced by law-abiding citizens.
How is AAC -> MP3 for personal use inherently different than broadcast television -> VCR for personal use? If anything, it seems like more of a fair use no-brainer, since you've actually purchased (forget the EULA: read all of their advertising) the product, and therefor have more right to use it as you see fit and someone who merely happens to receive a signal in their home - at least, according to any reasonable 3rd-party observer.
I'm not, actually, but that would definitely change the legal angle quite a bit.
We can and should be upset with people using this to distribute cracked files, but there is no clear reason why using it to, say, play back legitimately purchased files on a Linux machine is morally or legally wrong.
As I mentioned in a previous post, the same is true for their PCMCIA cards. On my Debian laptop, the card was plug-and-play (as much as anything is under Debian, anyway).