Don't you guys remember a wave power harnessing device that sat at the bottom, and they looked like flaps going back and forth? I went to the ACRE Aussie site with the neat little pictures, but it didn't have it.
Anyhow, my point of this post is to state that the benefits of having a mostly above water based system like the Pelamis (other than the junction on the sea bed) is that maintenance is easy -- it's very accessible. However, it's susceptable to traffic and damage in that regard.
The benefits of being completely submerged, like that sea-bed wave flap device I talked about earlier is that its safe from ships and people screwing around with them; however, maintenance must really blow for something like that.
I think this is a great idea -- hell, there's no energy crisis. We're just too damn content with what we have now. Good post -- even though the idea isn't completely new, the apparatus and its acceptance is.
..this intro to NFS is kinda light for/. Understanding NFS -- I believed I was going to be reading about the gushy internal stuff that goes on but in layman terms, but rather, I found stuff that any *nix admin here on/. has known for years. Don't slip. First, that horrible reference to that horrible Google ad-words article, then this.
Imagine opening up your mailbox at home to free copies of Red Hat Linux 10.0 -- "It's better than ever, 1000 days without a reboot!" Red Hat CDs in your magazines, at your pizza joint, and bundled with your new AOL-HP P5-3500 (maybe if I start that rumor, it just might make the Washington Post).
It's an all out Tekken Tag war with friends and family this evening. People will be coming from far and wide (4 mile radius) to see who is the Tekken Tag Master of 2001 -- that is, the person with the last victory come midnight.
I don't think this had much to do with 2001. What I mean is that its not as if a new version of vi or Emacs is going to come out, and will convince a diehard KWord user to convert.
By the way, favorite distro back in 1995/96, and still my favorite in soon-to-be 2002, Slackware.
My favorite parts of the picture are actually the basketball hoop hanging directly above the workbench, and of course, the rolling monitor stand that promotes bad posture when working on that server its connected to. Man, it looks like my work area. Are we related?
Power supply dies. Power goes out and UPS dies after 30 minutes. Playing shuffle-the-cables at the co-lo facility and you mistakingly unplug the NAS unit. There are still a few non-Microsoft OS related catastrophes that exist, believe it or not. By the way, that last scenario was completely hypothetical. [whistling/twiddling thumbs]
ext3 catches my fancy because there's no ext2 --> ext3 conversion -- you just have to unmount, make a journal file, and remount. reiserfs migration is a challenge for the huge partitions.
Sounds like it's somewhere in the middle of "The New New Thing" and "The Tao of Pooh". In any case, if there's good stuff to be learned without having to suffer through it first hand, it's usually a good read. Thanks for the detailed post/review.
Like so many of you that have posted here, I've been using Slackware for at least five years in the production environment. I've strayed from the distribution when we started ordering pre-fab servers that came with a flavor of RedHat pre-installed in the past few years, but at the end of the day, I just keep coming back -- and what's funny is, I ask myself, "why?"
One reason I think that we Slackware-heads like Slackware so much is because it's about as bare and yet, as fancy as we want an install to go. I don't like GUI installations. At first, I disliked them because they required a mouse (which none of our servers have). Secondly, I disliked them because they used colors -- once, on a Mandrake install, I couldn't tell if an option box was "checked", because the only way to discern this was to know if red or blue meant "selected". I popped out the CD, tossed it in the trash, and popped in Slackware. (very true)
I like to get my hands dirty. Hell, I've never even used RPM before September of this year (on a box, of course, that someone else installed RedHat on). After I build out a new box, I like to break out the Lava soap.
And you know what I like most about Slackware?/etc/rc.d/. I didn't realize how much I liked rc.inet1 and rc.inet2 until I started configuring/etc/sysconfig/network-scripts/ifcfg-eth1:x on a RedHat box -- yikes. I don't need Lava soap after tooling around with RedHat, I need 800mg of Advil.
Recently, I asked for a little support -- asking them if they could tell me if the VA Linux 1000 server could come up after a power-cycle (remote power reboot units used if a server locks up). I would fudge around with it myself, but it's already at the data center, and the next time I go out there, I'd reconfig it.
In any case, the warranty expired last month, so they told me that for $250, they'd answer my question. I asked the lady by e-mail, "Okay -- how about this -- just tell me *IS* this possible? Some motherboards don't have the ability to bypass the soft power switch." She responded saying that it is 100% possible, but it will still cost me $250 if I wanted to find out how.;-)
So what in the fudge is VA doing now anyway, now that they're not selling servers?
Of course we know people are doing it -- but the script doesn't even do any investigative work at all. What if I were to sign up for a newsletter, and then later send it in to SpamCop? Are you telling me that the SpamCop script has some type of intelligent filter to know whether or not my complaint is legitimate or that I did/did-not sign up?
No, we are NOT harrassing people. What about false complaints, Mr. ISP? What about the people who DID sign up -- full proof of hostname/IP match? What do you say then? They have the right to send in some e-mail to a Perl-script-kiddie that yells "abuse@isp1.com" and "abuse@isp2.com", and waste OUR company resources?
You see -- you're grouping in legitmate businesses with casino-viagara-porn-weight-loss-spam-mailers. It's not the same, and your side's demands for double-opt in? Make a law, and we'll obey it. But for now, we're sticking to our "guns" -- and that is, find the real culprit who signed up this person.. because if that was their intent, JUST TO SIGN UP SOMEONE ELSE AND HARRASS SOMEONE ELSE, surely, there lies the possibility that they'll just do it again.
Heck, I'm also guessing that you're also the type to bitch and moan about receiving a confirmation e-mail that you didn't request, right?
I'm not the hypocrite. Let SpamCop run their business -- I'm just looking for other businesses who have fallen victim to half-done investigative work as to who is really responsible for the subscription.
This is not a gun, and we are not killing people. But indeed, if someone took my gun (for which I am a legal gun owner), and illegally used it to hurt someone, no, I am not responsible -- the trigger-puller is responsible. I'm assuming you'd just go ahead and sue the gun manufacturer as well? It is the abuser that should be punished because, you see, all of our terms are clearly stated on our web site.
Listen, not many third-party "I-want-to-use-this-service-to-abuse-some-e-mail-a ddress" people are abusing our service. Nearly ALL of our complaints are from people who have gone to our service, signed up, received a newsletter (because it is clearly stated in our terms that if you do sign up or use our service, you are subscribing to our newsletter) and then complain about it later.
We have the IP addresses and date/time stamps to prove it.
Why are you so emotionally charged about this? I did not slam SpamCop -- after all, they're a for profit business, let them do what they want to do. However, their demands for us to go "double-opt-in" are none of his business, nor yours. As for us "not caring" or "US" being the real villain -- what's all that about?
You can't just bunch all business who broadcast e-mail together. We send out newsletters, usage statistics, and other subscription based e-mails with single-click opt-outs. We store IP addresses of the subscribers. You see, it was solicited, completely and entirely.
If I sent pizzas, magazines, taxis, and C.O.D. merchandise orders to your house -- are you telling me that you would start to bitch and moan about pizza joints, magazine distributors, taxi cab companies, and mail order merchandise houses? Is that who you'd go after? I think not. You'd go after the person who was sending all of these items to you. Now THAT is a far better analogy than a gun.
I don't think that anyone has the right to tell a business how to run things. Granted, if the business is sending outright SPAM (truly unsolicited e-mail where they purchased a list, or gone out and grabbed a bunch of e-mail addresses with web/nntp crawlers), then they should be criticized and/or punished accordingly.
However, if a company wants to use single opt-in, that's their right. If the company maintains subscription lists, IP addresses and/or message headers of the people that subscribed (as we do), to prove WHO subscribed an e-mail address, that should be enough.
There are these "watchdog" organizations out there that "police" SPAM. I have very low opinions about people who write a Perl script that reads in an e-mail header, pulls down all of the ISPs involved, and screams "This is SPAM" to abuse@blah.net and abuse@foo.com. That sawwed-off shot-gun approach is not only inaccurate, it wastes a lot of time for all parties involved if the "watchdog" organization isn't even really looking into things.
One service (SpamCop) constantly accuses our company of sending SPAM. We respond with the IP address or the person who subscribed them to our list, date/time stamp, and the URL of the page that states the conditions of the submission/subscription, but that doesn't matter to them. They just want us to adhere to their demands of double opt-in. Imagine that -- here they have the IP address of the actual perpetrator, date/time stamp -- that's plenty of evidence to find out who the real villian is.
Though I cannot speak about Experian and what they do, I can say that this is a small victory for legitmate businesses that run legitimate services and maintain legitimate mailing lists.
At this time, we're looking for other companies that maintain legitimate e-mail lists/services and have had issues with SpamCop. Specifically, if your company has suffered any downtime, loss of revenue, or any loss of service due to claims made by SpamCop that were false or inaccurate, please contact us via e-mail (neil@whatUseek.com)
See -- the problem was that you went to a well funded company. If you work for a company that didn't take in a dime of VC, started from and continues to work from sweat equity and sweat revenue, you'd still be having fun. True, I'm not driving a Lexus LS-430, but fun, there's plenty of it.
We've graduated from the less harmful nerf games, to the more dangerous, higher velocity hackey-sacks. Crap, if we only had the height, we'd be throwing Jarts (lawn darts) in there. You see -- that is second stage of fun that your dot-bomb company wasn't around to experience. It's slightly more dangerous (doing my Ice Man teeth-bite), but the things you'll put up with for fun and a paycheck...
Big pain in the rump. And just so you know, we have a very recent version (4.33L2) running, and it happened to us as well. The fix -- not sure.. but what I did was this:
su user
mv ~user/Maildir ~usr/Maildir.old
mkdir ~user/Maildir
mkdir ~user/Maildir/new
mkdir ~user/Maildir/tmp
mkdir ~user/Maildir/cur
cp ~usr/Maildir.old/cur/1* ~usr/Maildir/cur/
I did this because we weren't getting ANY of the new messages showing at all. This archives the current Maildir, moves the billion-second messages over and allows you to do some post move reconstruction when you have free time.;-)
I started off with Slackware back in 95 or 96.. I think it was bundled in some other package of CDs. In any case, I guess I may have picked up at least three versions of Slackware from Walnut Creek for $29.99+ per, a bunch of distros from LinuxMall for $1.89 per (including Redhat 6, Redhat 7, Mandrake, Debian, FreeBSD). And most recently, Slackware 8.0 from store.slackware.com for $39.99. No more than a couple hundred bucks.. installed on over 70 servers.. not bad ROI, eh?
With each computer we buy, we always get Windows installed (Dell notebooks primarily). So, it goes with the package.
I, too, have tried to stray from Slackware, but man -- in my opinion, it's just the best damn distribution out there because it doesn't make the presumptions that you want your server with all of the "default" settings.
Unix mail clients have always been my bag. So, thanks Pine for not making me susceptible to such an idiotic virus.
Don't you think it's about time that MS comes out with a freakin' security patch that stops scripts from broadcasting across your entire contact list? This virus isn't original.
My in-box has just been pounded with these e-mails with 200+K attachments (.xls.pif file extension on one or more of them). Well, one good thing comes from this -- you get to see everyone who has you on their contact list.;-)
Oh wait, oh wait -- I have a patch for all of you Outlook users. Stop using it.
--- outlook Mon Jul 23 00:33:57 2001
+++ outlook Mon Jul 23 00:33:59 2001
@@ -1 +1 @@
-Microsoft Outlook
+# Microsoft Outlook
I've read the first book several times, have seen the movie a few times as well -- and man, I think that mini-series really lacked feeling. The story is grand and powerful -- the houses were regal, sinister, advanced, heroic, deplorable.. but in the mini-series I felt like I was watching 90210.
Paul was arrogant, never showing reverence. The dialogue didn't seem to sync with the emotion of the situation -- did these bastards even read the book or watch the movie?
I do not look forward to any mini-series sequels. Leave it up to the big budget houses to make a Dune mega movie with actors and directors that draw you in, because hell, the story is already doing its job.. and Sci-fi Chan did it an injustice the first time around.
Slashdot Mirror
Don't you guys remember a wave power harnessing device that sat at the bottom, and they looked like flaps going back and forth? I went to the ACRE Aussie site with the neat little pictures, but it didn't have it.
Anyhow, my point of this post is to state that the benefits of having a mostly above water based system like the Pelamis (other than the junction on the sea bed) is that maintenance is easy -- it's very accessible. However, it's susceptable to traffic and damage in that regard.
The benefits of being completely submerged, like that sea-bed wave flap device I talked about earlier is that its safe from ships and people screwing around with them; however, maintenance must really blow for something like that.
I think this is a great idea -- hell, there's no energy crisis. We're just too damn content with what we have now. Good post -- even though the idea isn't completely new, the apparatus and its acceptance is.
..this intro to NFS is kinda light for /. Understanding NFS -- I believed I was going to be reading about the gushy internal stuff that goes on but in layman terms, but rather, I found stuff that any *nix admin here on /. has known for years. Don't slip. First, that horrible reference to that horrible Google ad-words article, then this.
This article isn't news for nerds. It's not even news.
..does what we have mean nothing to you? And who is this, this.. Kathleen? |-;
Congrats, you've now spawned a permanent process.
Imagine opening up your mailbox at home to free copies of Red Hat Linux 10.0 -- "It's better than ever, 1000 days without a reboot!" Red Hat CDs in your magazines, at your pizza joint, and bundled with your new AOL-HP P5-3500 (maybe if I start that rumor, it just might make the Washington Post).
It's an all out Tekken Tag war with friends and family this evening. People will be coming from far and wide (4 mile radius) to see who is the Tekken Tag Master of 2001 -- that is, the person with the last victory come midnight.
I don't think this had much to do with 2001. What I mean is that its not as if a new version of vi or Emacs is going to come out, and will convince a diehard KWord user to convert.
By the way, favorite distro back in 1995/96, and still my favorite in soon-to-be 2002, Slackware.
My favorite parts of the picture are actually the basketball hoop hanging directly above the workbench, and of course, the rolling monitor stand that promotes bad posture when working on that server its connected to. Man, it looks like my work area. Are we related?
Power supply dies. Power goes out and UPS dies after 30 minutes. Playing shuffle-the-cables at the co-lo facility and you mistakingly unplug the NAS unit. There are still a few non-Microsoft OS related catastrophes that exist, believe it or not. By the way, that last scenario was completely hypothetical. [whistling/twiddling thumbs]
ext3 catches my fancy because there's no ext2 --> ext3 conversion -- you just have to unmount, make a journal file, and remount. reiserfs migration is a challenge for the huge partitions.
Sounds like it's somewhere in the middle of "The New New Thing" and "The Tao of Pooh". In any case, if there's good stuff to be learned without having to suffer through it first hand, it's usually a good read. Thanks for the detailed post/review.
I stand corrected -- just checked out the web site. These are published in Linux Journal, I believe -- so, I am a devout User Friendly reader. ;-)
//e, and say hello to the Zoom Telephonics 14.4 v32.bis.
Move over Hayes Micromodem
I, for one, am hiding behind my Hayes Micromodem //e at 300 baud. I've never even heard of it.
Like so many of you that have posted here, I've been using Slackware for at least five years in the production environment. I've strayed from the distribution when we started ordering pre-fab servers that came with a flavor of RedHat pre-installed in the past few years, but at the end of the day, I just keep coming back -- and what's funny is, I ask myself, "why?"
/etc/rc.d/. I didn't realize how much I liked rc.inet1 and rc.inet2 until I started configuring /etc/sysconfig/network-scripts/ifcfg-eth1:x on a RedHat box -- yikes. I don't need Lava soap after tooling around with RedHat, I need 800mg of Advil.
One reason I think that we Slackware-heads like Slackware so much is because it's about as bare and yet, as fancy as we want an install to go. I don't like GUI installations. At first, I disliked them because they required a mouse (which none of our servers have). Secondly, I disliked them because they used colors -- once, on a Mandrake install, I couldn't tell if an option box was "checked", because the only way to discern this was to know if red or blue meant "selected". I popped out the CD, tossed it in the trash, and popped in Slackware. (very true)
I like to get my hands dirty. Hell, I've never even used RPM before September of this year (on a box, of course, that someone else installed RedHat on). After I build out a new box, I like to break out the Lava soap.
And you know what I like most about Slackware?
Recently, I asked for a little support -- asking them if they could tell me if the VA Linux 1000 server could come up after a power-cycle (remote power reboot units used if a server locks up). I would fudge around with it myself, but it's already at the data center, and the next time I go out there, I'd reconfig it.
;-)
In any case, the warranty expired last month, so they told me that for $250, they'd answer my question. I asked the lady by e-mail, "Okay -- how about this -- just tell me *IS* this possible? Some motherboards don't have the ability to bypass the soft power switch." She responded saying that it is 100% possible, but it will still cost me $250 if I wanted to find out how.
So what in the fudge is VA doing now anyway, now that they're not selling servers?
Of course we know people are doing it -- but the script doesn't even do any investigative work at all. What if I were to sign up for a newsletter, and then later send it in to SpamCop? Are you telling me that the SpamCop script has some type of intelligent filter to know whether or not my complaint is legitimate or that I did/did-not sign up?
No, we are NOT harrassing people. What about false complaints, Mr. ISP? What about the people who DID sign up -- full proof of hostname/IP match? What do you say then? They have the right to send in some e-mail to a Perl-script-kiddie that yells "abuse@isp1.com" and "abuse@isp2.com", and waste OUR company resources?
You see -- you're grouping in legitmate businesses with casino-viagara-porn-weight-loss-spam-mailers. It's not the same, and your side's demands for double-opt in? Make a law, and we'll obey it. But for now, we're sticking to our "guns" -- and that is, find the real culprit who signed up this person.. because if that was their intent, JUST TO SIGN UP SOMEONE ELSE AND HARRASS SOMEONE ELSE, surely, there lies the possibility that they'll just do it again.
Heck, I'm also guessing that you're also the type to bitch and moan about receiving a confirmation e-mail that you didn't request, right?
I'm not the hypocrite. Let SpamCop run their business -- I'm just looking for other businesses who have fallen victim to half-done investigative work as to who is really responsible for the subscription.
a ddress" people are abusing our service. Nearly ALL of our complaints are from people who have gone to our service, signed up, received a newsletter (because it is clearly stated in our terms that if you do sign up or use our service, you are subscribing to our newsletter) and then complain about it later.
This is not a gun, and we are not killing people. But indeed, if someone took my gun (for which I am a legal gun owner), and illegally used it to hurt someone, no, I am not responsible -- the trigger-puller is responsible. I'm assuming you'd just go ahead and sue the gun manufacturer as well? It is the abuser that should be punished because, you see, all of our terms are clearly stated on our web site.
Listen, not many third-party "I-want-to-use-this-service-to-abuse-some-e-mail-
We have the IP addresses and date/time stamps to prove it.
Why are you so emotionally charged about this? I did not slam SpamCop -- after all, they're a for profit business, let them do what they want to do. However, their demands for us to go "double-opt-in" are none of his business, nor yours. As for us "not caring" or "US" being the real villain -- what's all that about?
You can't just bunch all business who broadcast e-mail together. We send out newsletters, usage statistics, and other subscription based e-mails with single-click opt-outs. We store IP addresses of the subscribers. You see, it was solicited, completely and entirely.
If I sent pizzas, magazines, taxis, and C.O.D. merchandise orders to your house -- are you telling me that you would start to bitch and moan about pizza joints, magazine distributors, taxi cab companies, and mail order merchandise houses? Is that who you'd go after? I think not. You'd go after the person who was sending all of these items to you. Now THAT is a far better analogy than a gun.
I don't think that anyone has the right to tell a business how to run things. Granted, if the business is sending outright SPAM (truly unsolicited e-mail where they purchased a list, or gone out and grabbed a bunch of e-mail addresses with web/nntp crawlers), then they should be criticized and/or punished accordingly.
However, if a company wants to use single opt-in, that's their right. If the company maintains subscription lists, IP addresses and/or message headers of the people that subscribed (as we do), to prove WHO subscribed an e-mail address, that should be enough.
There are these "watchdog" organizations out there that "police" SPAM. I have very low opinions about people who write a Perl script that reads in an e-mail header, pulls down all of the ISPs involved, and screams "This is SPAM" to abuse@blah.net and abuse@foo.com. That sawwed-off shot-gun approach is not only inaccurate, it wastes a lot of time for all parties involved if the "watchdog" organization isn't even really looking into things.
One service (SpamCop) constantly accuses our company of sending SPAM. We respond with the IP address or the person who subscribed them to our list, date/time stamp, and the URL of the page that states the conditions of the submission/subscription, but that doesn't matter to them. They just want us to adhere to their demands of double opt-in. Imagine that -- here they have the IP address of the actual perpetrator, date/time stamp -- that's plenty of evidence to find out who the real villian is.
Though I cannot speak about Experian and what they do, I can say that this is a small victory for legitmate businesses that run legitimate services and maintain legitimate mailing lists.
At this time, we're looking for other companies that maintain legitimate e-mail lists/services and have had issues with SpamCop. Specifically, if your company has suffered any downtime, loss of revenue, or any loss of service due to claims made by SpamCop that were false or inaccurate, please contact us via e-mail (neil@whatUseek.com)
See -- the problem was that you went to a well funded company. If you work for a company that didn't take in a dime of VC, started from and continues to work from sweat equity and sweat revenue, you'd still be having fun. True, I'm not driving a Lexus LS-430, but fun, there's plenty of it.
We've graduated from the less harmful nerf games, to the more dangerous, higher velocity hackey-sacks. Crap, if we only had the height, we'd be throwing Jarts (lawn darts) in there. You see -- that is second stage of fun that your dot-bomb company wasn't around to experience. It's slightly more dangerous (doing my Ice Man teeth-bite), but the things you'll put up with for fun and a paycheck...
Big pain in the rump. And just so you know, we have a very recent version (4.33L2) running, and it happened to us as well. The fix -- not sure.. but what I did was this:
;-)
su user
mv ~user/Maildir ~usr/Maildir.old
mkdir ~user/Maildir
mkdir ~user/Maildir/new
mkdir ~user/Maildir/tmp
mkdir ~user/Maildir/cur
cp ~usr/Maildir.old/cur/1* ~usr/Maildir/cur/
I did this because we weren't getting ANY of the new messages showing at all. This archives the current Maildir, moves the billion-second messages over and allows you to do some post move reconstruction when you have free time.
I started off with Slackware back in 95 or 96.. I think it was bundled in some other package of CDs. In any case, I guess I may have picked up at least three versions of Slackware from Walnut Creek for $29.99+ per, a bunch of distros from LinuxMall for $1.89 per (including Redhat 6, Redhat 7, Mandrake, Debian, FreeBSD). And most recently, Slackware 8.0 from store.slackware.com for $39.99. No more than a couple hundred bucks.. installed on over 70 servers.. not bad ROI, eh?
With each computer we buy, we always get Windows installed (Dell notebooks primarily). So, it goes with the package.
I, too, have tried to stray from Slackware, but man -- in my opinion, it's just the best damn distribution out there because it doesn't make the presumptions that you want your server with all of the "default" settings.
Oh yeah, one more thing. If you've not yet had the privilege of receiving it, just send me your .vcf file. ;-)
Unix mail clients have always been my bag. So, thanks Pine for not making me susceptible to such an idiotic virus.
;-)
Don't you think it's about time that MS comes out with a freakin' security patch that stops scripts from broadcasting across your entire contact list? This virus isn't original.
My in-box has just been pounded with these e-mails with 200+K attachments (.xls.pif file extension on one or more of them). Well, one good thing comes from this -- you get to see everyone who has you on their contact list.
Oh wait, oh wait -- I have a patch for all of you Outlook users. Stop using it.
--- outlook Mon Jul 23 00:33:57 2001
+++ outlook Mon Jul 23 00:33:59 2001
@@ -1 +1 @@
-Microsoft Outlook
+# Microsoft Outlook
I've read the first book several times, have seen the movie a few times as well -- and man, I think that mini-series really lacked feeling. The story is grand and powerful -- the houses were regal, sinister, advanced, heroic, deplorable.. but in the mini-series I felt like I was watching 90210.
Paul was arrogant, never showing reverence. The dialogue didn't seem to sync with the emotion of the situation -- did these bastards even read the book or watch the movie?
I do not look forward to any mini-series sequels. Leave it up to the big budget houses to make a Dune mega movie with actors and directors that draw you in, because hell, the story is already doing its job.. and Sci-fi Chan did it an injustice the first time around.