Oh, and I mean on the server side. NFS on the client side is ok.
Surely you're insane. Let me give you an example of NFS shafting me on the client side. I manage a small group of Linux boxes for a physics research group. Some of the users requested a "shared directory" which would appear on all the machines and be readable/writable by everyone.
So I make a 1gb image file on one of the machines, format and mount it loopback, export it on NFS, and mount it on the other machines.
For about a week, no problem. Then a user I didn't know had root access deleted the image file. Whoops. Every machine required a reboot to get ps, top, df, etc. working right again. Fixing the server didn't help, umount -f didn't help. This may not be a big deal for some users, but these machines routinely run ~1 week number crunching jobs.
This kind of problem is simply not acceptable in such an important and standard app. I'm now forced to use Samba despite its lack of UNIX permissions.
OLD LISTER: I know you're there, because when I was your age, I saw me at my age... telling you... what I'm about to tell you. You've got to tell you... when you get to be me. ...
RIMMER: What about me? What happens to me?
LISTER: He can't hear us, Rimmer. He's from the future.
RIMMER: Ah, but if I ask you now, you can remember it, and when you get to be him, you can tell me.
RIMMER: Lister, it *has* happened. You can't change it, any more than you can change what you had for breakfast yesterday.
LISTER: Hey, it hasn't happened, has it? It has "will have going to have happened" happened, but it hasn't actually "happened" happened yet, actually.
RIMMER: Poppycock! It will be happened; it shall be going to be happening; it will be was an event that could will have been taken place in the future. Simple as that. Your bucket's been kicked, baby.
OK, this web site, despite being a great idea, sucks. It's utterly unusable in Galeon, Konqueror and lynx, and only useable in Netscape 4 if you edit the GET URL and replace all the spaces with "%20". While it's obviously designed to work with IE, has anyone managed to get anywhere with anything available on Linux?
But just yesterday we started looking into replacing our commercial database engine with MySQL. Lo and behold, for our commercial use, we have to pay for it.
Look a little bit harder next time. MySQL is available under the GPL, which does not distinguish between commercial and non-commercial use. From the MySQL web site:
MySQL is available for free under the GNU General Public Licence (GPL). Commercial licences are sold to users who prefer not to be restricted by the GPL terms.
Also, prebuilt binaries of the so-called "MySQL Classic" are only available under the commercial license, but if you can't be bothered to build it from source, you must not be very serious about using it.
On the other hand, a lot of really good paranoia scifi stories have not panned out. In the 40s and 50s there was a whole lot of apocalyptic and post-apocalyptic literature written, from the good (Canticle for Leibowitz) to the not-so-good (Alas, Babylon). The stuff is scary and convincing because at the time it was being written, nuclear war was a very real possibility.
It's certainly possible that humanity could destroy itself and/or the world with any one of hundreds of new technologies, but the odds are worse than they were in the days of the Cuban missile crisis, and we pulled through that one. Maybe you should check the Doomsday Clock next time, folks.
This sort of shit is why you should read the computer use policy of a university before deciding to enroll. I also work for IT at a university, and I spend a fair amount of time making sure that no one including us has any more private information about people than is absolutely necessary. There are still schools out there determined not to take an authoritarian view of computing, and it's worth your time to track one down.
This thing is fantastic. It's amazing the things you can fit into 50 megs - basically every command line program you'd want except Emacs and man pages, plus minimal X support.
For a really quality experience, modify the image to boot to a win95 boot disk image with stuff like fdisk and format, and include loadlin and NTFS dos drivers on the image. You can then use it to fix just about any system. Best of all, it still fits on a credit card sized CD that I keep in my wallet.
You're forgetting about Birdman vs. Wesley Willis. There's a movie I'd pay to see:
Birdman caught me on his property
He saw me trespassing his real estate
He reached into his pocket for a pistol
He came after me and pistol-whipped my behind
Birdman beat me to a pulp
He gave me a yell-down war hell ride
He told me that he was going to kill me if I don't get off his real estate
He gave five minutes to get in my Bronco and hit the rookie road
At 10:00 PM, I drove my Bronco back to Birdman's real estate
I jumped over his fence after dark
I picked up a brick and shattered Birdman's window pane
Birdman sighted me doing it and reached for his pistol
Suddenly, I jumped back in my Bronco and took off like O. J. Simpson
I'm not necessarily saying that people have no excuse for not teaching themselves command line - it takes a certain kind of person to want to approach that kind of a challenge. But there are excellent resources out there for people who aren't so much into learning by doing.
The vast majority of computer users on the planet want nothing to do with CLIs, grep or awk....it's a pain in the ass for Joe Average PC User.
You are correct. Note I also said "anyone who considers himself a power user owes it to himself to learn some command line."
This debate is akin to me saying that anyone who can't shift a straight cut racing gearbox without using the clutch is plain lazy. Although the fact that I can do this is probably indicative of the fact that I am a better driver than 95% of the people out there, but this helps me not one bit when I am stuck in 5 mph Manhattan traffic with the rest of the world.
That's not a very fitting analogy. While it's true that many CLI benefits aren't useful for most people, I find a CLI very helpful even for day-to-day tasks, such as renaming large numbers of files. As for the last part, I would say that the fact you can shift without the clutch probably means you are a worse driver than 95% of the people out there.
Sure someone can learn ls, mv, cp, rm, really quick. But things like grep, awk, etc. Require a lot more.
Er... if you say so. Personally, I'd think that anyone who can remember cp <source> <destination> can remember grep <pattern> <files>. Of course awk is going to take longer to learn, since it's a Turing complete programming language, but you can get a lot done with <some command producing columns of output> |awk '{print $<which row of output>}'
It'll take a while to learn, sure, but it's worth it if you need that functionality.
The only excuses for not learning the command line are laziness or (misplaced) intimidation. Anyone willing to put forth a miniscule amount of effort can learn enough command line to accomplish certain tasks faster than with a GUI.
I'm not saying everyone should use a command line, because certainly GUIs are useful and have their place. But really anyone who considers himself a power user owes it to himself to learn some command line.
None of the Redhat 7.x series are vulnerable. To quote from the advisory:
OpenSSH supports the SKEY and BSD_AUTH authentication options. These are
compile-time options. At least one of these options must be enabled
before the OpenSSH binaries are compiled for the vulnerable condition to
be present.
Both of these options are disabled unless specifically enabled with when configure is run. None of the Redhat 7.x OpenSSH spec files mention anything about BSD auth or SKey support, and so I conclude that they are not vulnerable.
Sure, as it turns out, nukes served as an effective deterant to war and possibly prevented a significant number of deaths. However, the amount of risk associated with nukes is mind-boggling. What would the world be like had Kennedy ordered nuclear strikes during the missle crisis? Nukes were seriously considered for use during Vietnam, where they would arguably have led to a full-scale nuclear war. These are just two incidents which our government has let slip - think of how many more there have been that our government or the USSR have successfully kept under wraps.
As it turns out, nukes might arguably have been good for humanity, but at the cost of how many close calls? And of course, the possibility of nuclear war is far from over. As more countries develop nuclear weapons, there will be more and more chance of an lunatic or terrorist getting ahold of one.
For those of you too lazy to go to Google, here's a link to the Antec cases page. There's also a mixed review here, with some better pictures. In agreement with the article, 2/3 of their product lines come in either black or grey. I actually think the grey looks better, though - the black ones look too much like the new Dells for me.
I think the poster was going for a McLuhen-esque reference. Marshall McLuhen was a media and culture guru in the 60s, 70s and 80s, and according he and his supporters (including the guys over at Wired before it sucked), the medium is the message. And while McLuhen was partially about freaking out the squares and psychedelia, he was also a lot more than that. Turn off your computers and go read The Medium is the Massage or Understanding Media. Had Flash been around in his day, I'm sure he would have been thrilled about it and probably been involved in its gaining acceptance as more than just another stupid advertising ploy.
Why there will never be a time machine
on
Time Travel
·
· Score: 3, Insightful
Say someone in the future develops a time machine using some newly discovered way of exploiting a loophole in the laws of physics. Such a machine would almost certainly be used to travel into the past. And yet in the present, no time travelers from the future have been observed.
I have much more faith in the possibility that a time machine is impossible to construct than the possibility that all time travelers in the future will be so careful that no one will notice them.
Indeed. I'm constantly surprised how much stuff the LNX-BBC guys can fit in ~50 megs. Except for emacs and man pages, the image has pretty much anything you could reasonably ask for. Personally, I hacked the iso to boot to win95 dos rather than isolinux, then added loadlin and ntfsdos to the filesystem. All the same great Linux functionality, and now I can use it to fix win9x boxes and bypass security on NT/2k boxes. I never leave home without it.
Slashdot Mirror
Surely you're insane. Let me give you an example of NFS shafting me on the client side. I manage a small group of Linux boxes for a physics research group. Some of the users requested a "shared directory" which would appear on all the machines and be readable/writable by everyone.
So I make a 1gb image file on one of the machines, format and mount it loopback, export it on NFS, and mount it on the other machines.
For about a week, no problem. Then a user I didn't know had root access deleted the image file. Whoops. Every machine required a reboot to get ps, top, df, etc. working right again. Fixing the server didn't help, umount -f didn't help. This may not be a big deal for some users, but these machines routinely run ~1 week number crunching jobs.
This kind of problem is simply not acceptable in such an important and standard app. I'm now forced to use Samba despite its lack of UNIX permissions.
RIMMER: What about me? What happens to me?
LISTER: He can't hear us, Rimmer. He's from the future.
RIMMER: Ah, but if I ask you now, you can remember it, and when you get to be him, you can tell me.
RIMMER: Lister, it *has* happened. You can't change it, any more than you can change what you had for breakfast yesterday.
LISTER: Hey, it hasn't happened, has it? It has "will have going to have happened" happened, but it hasn't actually "happened" happened yet, actually.
RIMMER: Poppycock! It will be happened; it shall be going to be happening; it will be was an event that could will have been taken place in the future. Simple as that. Your bucket's been kicked, baby.
OK, this web site, despite being a great idea, sucks. It's utterly unusable in Galeon, Konqueror and lynx, and only useable in Netscape 4 if you edit the GET URL and replace all the spaces with "%20". While it's obviously designed to work with IE, has anyone managed to get anywhere with anything available on Linux?
The yellow face, it burns us. Stay in your dank cave and guard your precious.
I think maybe he mistook Slashdot for Memepool.
Look a little bit harder next time. MySQL is available under the GPL, which does not distinguish between commercial and non-commercial use. From the MySQL web site:
MySQL is available for free under the GNU General Public Licence (GPL). Commercial licences are sold to users who prefer not to be restricted by the GPL terms.
Also, prebuilt binaries of the so-called "MySQL Classic" are only available under the commercial license, but if you can't be bothered to build it from source, you must not be very serious about using it.
It's certainly possible that humanity could destroy itself and/or the world with any one of hundreds of new technologies, but the odds are worse than they were in the days of the Cuban missile crisis, and we pulled through that one. Maybe you should check the Doomsday Clock next time, folks.
This sort of shit is why you should read the computer use policy of a university before deciding to enroll. I also work for IT at a university, and I spend a fair amount of time making sure that no one including us has any more private information about people than is absolutely necessary. There are still schools out there determined not to take an authoritarian view of computing, and it's worth your time to track one down.
For a really quality experience, modify the image to boot to a win95 boot disk image with stuff like fdisk and format, and include loadlin and NTFS dos drivers on the image. You can then use it to fix just about any system. Best of all, it still fits on a credit card sized CD that I keep in my wallet.
Birdman caught me on his property He saw me trespassing his real estate
He reached into his pocket for a pistol
He came after me and pistol-whipped my behind
Birdman beat me to a pulp
He gave me a yell-down war hell ride
He told me that he was going to kill me if I don't get off his real estate
He gave five minutes to get in my Bronco and hit the rookie road
At 10:00 PM, I drove my Bronco back to Birdman's real estate
I jumped over his fence after dark
I picked up a brick and shattered Birdman's window pane
Birdman sighted me doing it and reached for his pistol
Suddenly, I jumped back in my Bronco and took off like O. J. Simpson
Truly, an artist beyond comparison.
I'm not necessarily saying that people have no excuse for not teaching themselves command line - it takes a certain kind of person to want to approach that kind of a challenge. But there are excellent resources out there for people who aren't so much into learning by doing.
You are correct. Note I also said "anyone who considers himself a power user owes it to himself to learn some command line."
This debate is akin to me saying that anyone who can't shift a straight cut racing gearbox without using the clutch is plain lazy. Although the fact that I can do this is probably indicative of the fact that I am a better driver than 95% of the people out there, but this helps me not one bit when I am stuck in 5 mph Manhattan traffic with the rest of the world.
That's not a very fitting analogy. While it's true that many CLI benefits aren't useful for most people, I find a CLI very helpful even for day-to-day tasks, such as renaming large numbers of files. As for the last part, I would say that the fact you can shift without the clutch probably means you are a worse driver than 95% of the people out there.
Er... if you say so. Personally, I'd think that anyone who can remember
cp <source> <destination>
can remember
grep <pattern> <files>.
Of course awk is going to take longer to learn, since it's a Turing complete programming language, but you can get a lot done with
<some command producing columns of output> |awk '{print $<which row of output>}'
It'll take a while to learn, sure, but it's worth it if you need that functionality.
The only excuses for not learning the command line are laziness or (misplaced) intimidation. Anyone willing to put forth a miniscule amount of effort can learn enough command line to accomplish certain tasks faster than with a GUI.
I'm not saying everyone should use a command line, because certainly GUIs are useful and have their place. But really anyone who considers himself a power user owes it to himself to learn some command line.
Or judging from the going rate of VA stock lately, the "got no green" lantern.
Er... the .spec file is the part of the source RPM that details how the package is built.
It's still broken, but at least now it'll tell you they don't work together rather than just breaking.
OpenSSH supports the SKEY and BSD_AUTH authentication options. These are compile-time options. At least one of these options must be enabled before the OpenSSH binaries are compiled for the vulnerable condition to be present.
Both of these options are disabled unless specifically enabled with when configure is run. None of the Redhat 7.x OpenSSH spec files mention anything about BSD auth or SKey support, and so I conclude that they are not vulnerable.
It still beats the one I have now... 486-66 with no battery at all. The good news is the extra space gives me a place to store my ethernet dongle.
or 1,789.15 Euro
or 2,613.96 Canadian
or 3,018.88 Australian
Cheaper than I expected, really. Anyone else remember the days when any decent laptop ran you at least $3,000 US?
wget -O -
As it turns out, nukes might arguably have been good for humanity, but at the cost of how many close calls? And of course, the possibility of nuclear war is far from over. As more countries develop nuclear weapons, there will be more and more chance of an lunatic or terrorist getting ahold of one.
For those of you too lazy to go to Google, here's a link to the Antec cases page. There's also a mixed review here, with some better pictures. In agreement with the article, 2/3 of their product lines come in either black or grey. I actually think the grey looks better, though - the black ones look too much like the new Dells for me.
I think the poster was going for a McLuhen-esque reference. Marshall McLuhen was a media and culture guru in the 60s, 70s and 80s, and according he and his supporters (including the guys over at Wired before it sucked), the medium is the message. And while McLuhen was partially about freaking out the squares and psychedelia, he was also a lot more than that. Turn off your computers and go read The Medium is the Massage or Understanding Media. Had Flash been around in his day, I'm sure he would have been thrilled about it and probably been involved in its gaining acceptance as more than just another stupid advertising ploy.
Say someone in the future develops a time machine using some newly discovered way of exploiting a loophole in the laws of physics. Such a machine would almost certainly be used to travel into the past. And yet in the present, no time travelers from the future have been observed.
I have much more faith in the possibility that a time machine is impossible to construct than the possibility that all time travelers in the future will be so careful that no one will notice them.
Indeed. I'm constantly surprised how much stuff the LNX-BBC guys can fit in ~50 megs. Except for emacs and man pages, the image has pretty much anything you could reasonably ask for.
Personally, I hacked the iso to boot to win95 dos rather than isolinux, then added loadlin and ntfsdos to the filesystem. All the same great Linux functionality, and now I can use it to fix win9x boxes and bypass security on NT/2k boxes. I never leave home without it.