A while back I had to deal with a similiar problem of everything but port 80 being blocked. They did have a proxy server where I could connect to port 80. Doing some very evil things I managed to hack ing up a copy of SSH on a server and the client to do something like this..
Connect to port 80 of the SSH server:
Send GET / HTTP/1.0
The hacked up SSH server ends up sending..
HTTP/1.0 Okay
SSH-1.5-1.2.25
And then the SSH transaction proceeded as normal...I dunno if this would work with all proxy software, but if its just a simple port blocker, you might not even need to do this, just talk on port 80...
If anybody wants the patches for my hacked up ssh server let me know...
Well one solution to the problem of each station needing its own frequency is what is called DAMA mode in the ham radio world. Basically it works like this, the main node(our default gateway) is the one who decides when a station can send data. The reason for this is the fact that all of the end points can hear the hub, but not all of the end points can hear each other transmit. Obviously one could see how collisions could become a problem. DAMA also should allow you to keep any one station from hogging all of the bandwidth.
Of course this doesn't prevent people from trying to jam the station, but if your using something like spread spectrum, this too isn't much of an issue.
I know out here in Northern Virginia, there is a major shortage of qualified people for all of the tech jobs here. I think the last number I heard about the number of tech positions open was something like 10000 or so(I could be wrong though, so don't quote me). Regardless, companies here will hire damn near anybody to do the work, if you know what your doing. Degrees seem to matter less and less(not saying they won't help you if your are compentent). I know this personally, as I've been Unix Admin professionally for 2 years now and I'm making 70k a year, all without any sort of degree...
One thing the x86 architecture has going for it is the fact that it probably ends up having some of the smallest executables out there. Have any of you ever compared the size of a sparc binary versus an x86 binary. Often times the x86 binary ends up being half the size. And I'm sure that the instruction set for IA-64 will result in similiar sized binaries to that of the sparc and the alpha. Say what you will about CISC instructions, but it does make for a bit smaller memory footprint as far as memory resident code goes...
It seems like a lot of people are missing Miguel's point. He is not saying that you *must* do it this way, he is just saying that this is just one way of doing it, a way that he feels is better.
What I see as one of the points here is that a lot of people are wasting a lot of time by writing a bunch of support code for their application because they are not reusing code. How this hurts us is the fact that this time could be used more effectively on working on the logic of the application, rather than rewriting yet another html parser or whatever.
I know on a few pieces of software I have written I ended up using glib, because there are just so many nifty functions that programmers are constantly rewriting. And I can see his point after using what is still a fairly lowlevel interface.
Also, as far as a lot of people saying, well we have pipes and that's all we'll ever need is just silly. I mean yes, pipes are neat, but god damn, how do you really expect to write anything complex and have it be relatively fast when your swishing data via pipes and firing off a bunch of new processes via fork().
Modularity is really the key to have a extensible OS. Linux to some extent is modular, but not really. Take a look at the HURD for example, from the design viewpoint, its a beautiful kernel. Sure microkernels are a bit slower than a monolithic kernel at this point, but what difference does say a 3% performance hit matter.
Code sharing and reuse is really what open source programs should be about. There should be common APIs and interfaces. Lets let go of some of the baggage that has accumlated with us over the years and stop trying to be a UNIX workalike and do something innovative. Linux and GNU are really the standards that the rest of the Unix community are trying to live up to now, we should show a bit of leadership here.
A lot really depends on the band. If they are being excessive while touring, well then no they aren't going to make money. Also a lot of artists tend to record their CDs on credit from the record label, so they need to pay back the record label first, which is often why touring is so necessary.
But some musicians still actually enjoy touring. These are the people who are not in it for the money, but for the love creating music. In general I tend not to care for most major label performers because a lot of them don't have the passion for the music, but are doing it because it is their meal ticket. It is possible to make a comfortable living off of your music and not be on a major label. Sure you might not get rich, but thats not the reason why your doing it. Its the same sort of argument used to defend Free Software(free in the GNU sense, not beer sense). People who write free software do it because they love what they do, not because they want to get filthy rich. The ones who want to be filthy rich end up working for M$, and we all know what sort of quality software they produce...
Here is an idea for the napster folks...have all the major record labels send lists of there artists to napster as artists not to be on napster. Doing a search of all users trading those files and ban them...Lets see how well napsters business does then, as I think they would find that they have no users.
I understand that Napster claims to be providing a file sharing service, but lets be realistic here, there is music piracy going on, they know it, we know it, and they of course are scared shitless to do a damn thing about it. Why? They make money on it. Take away all of the artists on the major lables from Napster and you'll have what left? Maybe a few thousand mp3s of unsigned artists or artists who allow their music to be traded in this fashion.
If more artists and record labels got a clue and realized that this didn't hurt sales, but help them. Then maybe this would work.
Here is a way to put the whole thing in perspective for the slashdot community.
Lets say you write some program that you spent weeks working on and you license it under the GPL. Would you really want MS taking your software, violating the GPL and shipping your code out with the latest version of Windows? I think not...
Perhaps a better way of exchange emails would be through the use of stenography(hiding the content in other data). Send images of your pets(not the images of course) back and forth via email and have a light discussion in the email, when you both know that the real content is in the image itself.
And to be on the safe side encrypt your message before running it through a stenograhy tool, so there won't be a big glaring header saying, "hey..look at me..i'm hiding something".
One of the main reasons why mp3 won't kill the CD is that with an mp3 you'd don't get the cover art and the liner notes that you typically get with the CD. Maybe if the record labels would stop to realize that what they are selling is not just the music, but the packaging and the print artwork as well. I mean sure I could download a whole album off of napster and burn it to CD, but its just not the same as having the artwork there in front of me.
Maybe the record labels should focus on adding more value into each CD and stop focusing on napster.
Well, they might have owned it in the past, but openoffice.org seems to be owned buy Sun at this point, but its nameservers do point to caldera's name servers....
Well if your not encrypting your mail, its like sending out only postcards. If you wanted things private, you would put your message in a nice envelope and mail it that way...
Email isn't really all that different, it just seems that we all expect our postcards to be completely private.
8. No corrupt union taking a cut of your pay to conduct political activities you don't agree with.
Actually, I've always felt that the tech industry would greatly benefit from a union. Lets say that your asshole boss cans you for some petty reason, 9 times out of 10 your not going to have much of a recourse. At least with a union around you'd have somebody to report the incident. This way people wouldn't be as likely to get pushed into working insane hours etc... Of course I am a bit biased growing up in a part of the US where unions are very important to the workers.
3) always have a functional caller id box setup on your home phone in case your boss tries to call.
I always take the policy of once I've left work, I am not longer working. If they want me to work more than that, damnit they are going to pay me. Of course being a consultant one can demand this a bit more.
Of course this doesn't mean I don't use computers at home, its just that I work on things not related to work, at all.
Also another tip is, when going into a job, remember that *everything* is negotiable, especially if your not in dire need of getting a job immediately. For example, demands things like having an office with a window and not being stuck in a cube etc. If they want you bad enough they'll working with you on your demands.
The 2.2.x series is hitting a road block, basically they realized that they foobared the VM in 2.2.0 and are realizing its going to be a major pain in the ass to fix. That doesn't mean that the 2.4.x series are going to be crap.
Yes, lets all use algorithms that we don't know if they have been proven or not that will solve the problem, not. Of course no cryptosystem is completely secure, but thats not the question that should be asked. The real question is, is this cryptosystem secure enough for the task at hand. PGP is general is secure enough for most tasks(like all those X rated emails you send to your girlfriend that you don't want the System Admin reading). Sure its very well possible that PGP can be cracked by the right person under the right conditions, but what are your odds of running across that person? As for an unpublished algorithm, you can not be sure of the risks involved because, for all you know that algorithm could have a backdoor in it.
1. postgreSQL support transactions and MySQL doesn't (at least not yet) 2. postgreSQL supports stored procedures take your pic of pl/perl, pl/pgsql, and pl/tcl to write them in. 3. postgreSQL supports finer grained locks on the database. MySQL only really supports locks on the table level. 4. postgreSQL has subselects and views. 5. Don't forget goodies like triggers and foreign keys.
Of course the trade off is that mysql tends to be a bit faster on reads and writes, but then again I've heard mysql described as a sql interface to a filesystem, so....
Now how about support for stored procedures and a decent procedural language to go with it as well.
You must realize that interprocess communicator is rather slow and expensive and having to fire off ten queries to do something is kind of silly when you could just rewrite a procedure and store it in the database and execute that with a single statement from the database client.
Re:What disappoints me...
on
Mattel Spyware
·
· Score: 1
But I should say this: People who have no interest in programming and hacking independent of making money, who just go to college and get an IT degree but otherwise couldn't care less about computers or technology and their impact, will probably never be nearly as skilled as those who truly love it and spend their free time doing it as well. If this is what you meant, then I agree with you.
This was exactly the point I was trying to make. I mean I personally don't object to getting a CS degree or whatever, but I know that there is a backlash against the clueless people who try to do jobs they aren't qualified for. I guess I was just being a bit to general:)
Re:What disappoints me...
on
Mattel Spyware
·
· Score: 1
So your saying that it ought to be required to be a programming profession, you must have a BS in something like Computer Science? Come on you have got to be serious. I consider myself to be a good C programmer(and a have decent pl/sql programmer) and I haven't had one day of formal training in anything. Yes, lets raise the bar so that you can only program professionally if you have a degree, that way all programmers have the same stupid mindset that professors drill into the heads of students. You realize that in the IT industry there is a major backlash against people coming out of colleges with degrees, because they haven't learned a damn think useful. It is these programmers who I writing the crap software like this, not the self taught ones...
Re:Largest Independent Label Joins RIAA vs. Napste
on
Napster Wars
·
· Score: 1
It figures that TVT would turn around and file suit against Napster. They are just as bad for fucking over artists as any other major label. Remember when Trent Reznor had a very long drawn out lawsuit against them to get out of his contract with them? Also, TVT did a pretty damn good job of scaring pretty much every artist from Wax Trax! records when they bought them out. TVT is no better than the big guys...
Well hell what would be fun is, in the contents of the packets your sending, put something in the packet about whatever your cause of the week is, the just claim that you were excersing your right to free speech. Yeah, that'll work...not
Slashdot Mirror
A while back I had to deal with a similiar problem of everything but port 80 being blocked. They did have a proxy server where I could connect to port 80. Doing some very evil things I managed to hack ing up a copy of SSH on a server and the client to do something like this..
Connect to port 80 of the SSH server:
Send GET / HTTP/1.0
The hacked up SSH server ends up sending..
HTTP/1.0 Okay
SSH-1.5-1.2.25
And then the SSH transaction proceeded as normal...I dunno if this would work with all proxy software, but if its just a simple port blocker, you might not even need to do this, just talk on port 80...
If anybody wants the patches for my hacked up ssh server let me know...
Try doings a 'host -l slashdot.org' and you'll see that the DNS servers are setup to allow zone transfer to anywhere...
Well one solution to the problem of each station needing its own frequency is what is called DAMA mode in the ham radio world. Basically it works like this, the main node(our default gateway) is the one who decides when a station can send data. The reason for this is the fact that all of the end points can hear the hub, but not all of the end points can hear each other transmit. Obviously one could see how collisions could become a problem. DAMA also should allow you to keep any one station from hogging all of the bandwidth.
Of course this doesn't prevent people from trying to jam the station, but if your using something like spread spectrum, this too isn't much of an issue.
I know out here in Northern Virginia, there is a major shortage of qualified people for all of the tech jobs here. I think the last number I heard about the number of tech positions open was something like 10000 or so(I could be wrong though, so don't quote me). Regardless, companies here will hire damn near anybody to do the work, if you know what your doing. Degrees seem to matter less and less(not saying they won't help you if your are compentent). I know this personally, as I've been Unix Admin professionally for 2 years now and I'm making 70k a year, all without any sort of degree...
One thing the x86 architecture has going for it is the fact that it probably ends up having some of the smallest executables out there. Have any of you ever compared the size of a sparc binary versus an x86 binary. Often times the x86 binary ends up being half the size. And I'm sure that the instruction set for IA-64 will result in similiar sized binaries to that of the sparc and the alpha. Say what you will about CISC instructions, but it does make for a bit smaller memory footprint as far as memory resident code goes...
It seems like a lot of people are missing Miguel's point. He is not saying that you *must* do it this way, he is just saying that this is just one way of doing it, a way that he feels is better.
What I see as one of the points here is that a lot of people are wasting a lot of time by writing a bunch of support code for their application because they are not reusing code. How this hurts us is the fact that this time could be used more effectively on working on the logic of the application, rather than rewriting yet another html parser or whatever.
I know on a few pieces of software I have written I ended up using glib, because there are just so many nifty functions that programmers are constantly rewriting. And I can see his point after using what is still a fairly lowlevel interface.
Also, as far as a lot of people saying, well we have pipes and that's all we'll ever need is just silly. I mean yes, pipes are neat, but god damn, how do you really expect to write anything complex and have it be relatively fast when your swishing data via pipes and firing off a bunch of new processes via fork().
Modularity is really the key to have a extensible OS. Linux to some extent is modular, but not really. Take a look at the HURD for example, from the design viewpoint, its a beautiful kernel. Sure microkernels are a bit slower than a monolithic kernel at this point, but what difference does say a 3% performance hit matter.
Code sharing and reuse is really what open source programs should be about. There should be common APIs and interfaces. Lets let go of some of the baggage that has accumlated with us over the years and stop trying to be a UNIX workalike and do something innovative. Linux and GNU are really the standards that the rest of the Unix community are trying to live up to now, we should show a bit of leadership here.
A lot really depends on the band. If they are being excessive while touring, well then no they aren't going to make money. Also a lot of artists tend to record their CDs on credit from the record label, so they need to pay back the record label first, which is often why touring is so necessary.
But some musicians still actually enjoy touring. These are the people who are not in it for the money, but for the love creating music. In general I tend not to care for most major label performers because a lot of them don't have the passion for the music, but are doing it because it is their meal ticket. It is possible to make a comfortable living off of your music and not be on a major label. Sure you might not get rich, but thats not the reason why your doing it. Its the same sort of argument used to defend Free Software(free in the GNU sense, not beer sense). People who write free software do it because they love what they do, not because they want to get filthy rich. The ones who want to be filthy rich end up working for M$, and we all know what sort of quality software they produce...
Here is an idea for the napster folks...have all the major record labels send lists of there artists to napster as artists not to be on napster. Doing a search of all users trading those files and ban them...Lets see how well napsters business does then, as I think they would find that they have no users.
I understand that Napster claims to be providing a file sharing service, but lets be realistic here, there is music piracy going on, they know it, we know it, and they of course are scared shitless to do a damn thing about it. Why? They make money on it. Take away all of the artists on the major lables from Napster and you'll have what left?
Maybe a few thousand mp3s of unsigned artists or artists who allow their music to be traded in this fashion.
If more artists and record labels got a clue and realized that this didn't hurt sales, but help them. Then maybe this would work.
Here is a way to put the whole thing in perspective for the slashdot community.
Lets say you write some program that you spent weeks working on and you license it under the GPL. Would you really want MS taking your software, violating the GPL and shipping your code out with the latest version of Windows? I think not...
and I can spell too :) That should be steganography
Perhaps a better way of exchange emails would be through the use of stenography(hiding the content in other data). Send images of your pets(not the images of course) back and forth via email and have a light discussion in the email, when you both know that the real content is in the image itself.
And to be on the safe side encrypt your message before running it through a stenograhy tool, so there won't be a big glaring header saying, "hey..look at me..i'm hiding something".
One of the main reasons why mp3 won't kill the CD is that with an mp3 you'd don't get the cover art and the liner notes that you typically get with the CD. Maybe if the record labels would stop to realize that what they are selling is not just the music, but the packaging and the print artwork as well. I mean sure I could download a whole album off of napster and burn it to CD, but its just not the same as having the artwork there in front of me.
Maybe the record labels should focus on adding more value into each CD and stop focusing on napster.
Um...what about Unix in general? Last I checked AT&T was a US company. Don't forget the weirdos at Berkeley either
Well, they might have owned it in the past, but openoffice.org seems to be owned buy Sun at this point, but its nameservers do point to caldera's name servers....
Well if your not encrypting your mail, its like sending out only postcards. If you wanted things private, you would put your message in a nice envelope and mail it that way...
Email isn't really all that different, it just seems that we all expect our postcards to be completely private.
Of course I am a bit biased growing up in a part of the US where unions are very important to the workers.
3) always have a functional caller id box setup on your home phone in case your boss tries to call.
I always take the policy of once I've left work, I am not longer working. If they want me to work more than that, damnit they are going to pay me. Of course being a consultant one can demand this a bit more.
Of course this doesn't mean I don't use computers at home, its just that I work on things not related to work, at all.
Also another tip is, when going into a job, remember that *everything* is negotiable, especially if your not in dire need of getting a job immediately. For example, demands things like having an office with a window and not being stuck in a cube etc. If they want you bad enough they'll working with you on your demands.
The 2.2.x series is hitting a road block, basically they realized that they foobared the VM in 2.2.0 and are realizing its going to be a major pain in the ass to fix. That doesn't mean that the 2.4.x series are going to be crap.
Yes, lets all use algorithms that we don't know if they have been proven or not that will solve the problem, not. Of course no cryptosystem is completely secure, but thats not the question that should be asked. The real question is, is this cryptosystem secure enough for the task at hand. PGP is general is secure enough for most tasks(like all those X rated emails you send to your girlfriend that you don't want the System Admin reading). Sure its very well possible that PGP can be cracked by the right person under the right conditions, but what are your odds of running across that person? As for an unpublished algorithm, you can not be sure of the risks involved because, for all you know that algorithm could have a backdoor in it.
2) Differences between postgress and MySQL.
1. postgreSQL support transactions and MySQL doesn't (at least not yet)
2. postgreSQL supports stored procedures take your pic of pl/perl, pl/pgsql, and pl/tcl to write them in.
3. postgreSQL supports finer grained locks on the database. MySQL only really supports locks on the table level.
4. postgreSQL has subselects and views.
5. Don't forget goodies like triggers and foreign keys.
Of course the trade off is that mysql tends to be a bit faster on reads and writes, but then again I've heard mysql described as a sql interface to a filesystem, so....
Now how about support for stored procedures and a decent procedural language to go with it as well.
You must realize that interprocess communicator is rather slow and expensive and having to fire off ten queries to do something is kind of silly when you could just rewrite a procedure and store it in the database and execute that with a single statement from the database client.
So your saying that it ought to be required to be a programming profession, you must have a BS in something like Computer Science? Come on you have got to be serious. I consider myself to be a good C programmer(and a have decent pl/sql programmer) and I haven't had one day of formal training in anything. Yes, lets raise the bar so that you can only program professionally if you have a degree, that way all programmers have the same stupid mindset that professors drill into the heads of students. You realize that in the IT industry there is a major backlash against people coming out of colleges with degrees, because they haven't learned a damn think useful. It is these programmers who I writing the crap software like this, not the self taught ones...
It figures that TVT would turn around and file suit against Napster. They are just as bad for fucking over artists as any other major label. Remember when Trent Reznor had a very long drawn out lawsuit against them to get out of his contract with them? Also, TVT did a pretty damn good job of scaring pretty much every artist from Wax Trax! records when they bought them out. TVT is no better than the big guys...
Buy UUNet stock when MCIWorldcom decides to divest in UUNet.
Well hell what would be fun is, in the contents of the packets your sending, put something in the packet about whatever your cause of the week is, the just claim that you were excersing your right to free speech. Yeah, that'll work...not