The money isn't the app it's the services. Create a product and then provide support for it. You provide support and you will not lose your customer base. Nobody that sells software provides any support these days and they wonder why the business model crumbles.
The big punchline will be ease of use for the admins. It is a giant pain in the ass doing scripting for multiple platforms due to varying locations of things. Sure you can spend time doing find and grep to vars in the scripts to make them safer but this move would make a lot of things simpler.
The other point is that Sun is also selling linux and x86 platforms for linux. For the sanity of their support staff going LSB compliant will take some load off. Not to mention aiding the third party app producers. Will take a lot more load off an app vendor's staff now.
The whole argument above about comparing Sparc/Solaris to Linux/Dell is only from those who haven't run the big Sun iron. It will be a while before linux can compete directly with Sparc/Solaris and I'm sure that Sun won't be opposed to linux on their hardware when the reliability and performance equals Solaris on the same hardware. They are selling hardware and support services, I'm sure they really don't care what runs on the hardware if it runs well and they can support it. LSB compliance is a small step on a longer path for a full support solution that will lend to a broader market base.
If there is a serious effort at security at all SSH won't be permitted. Any site that would bother paying $35/seat to essentially proxy AIM will have forced proxying of any other outbound traffic. It is fun when SSH is open though, gotta love the forwarding of your own private squid to avoid the jobsite web proxies.
Camden NJ for anyone who isn't from this area is so disgusting and violent that they felt left out when Detroit was burning the city for Halloween and decided they should do it too a few years ago.
The areas affected are areas where people who have jobs try to live and raise families. Meanwhile, the denizens of Camden proper use these areas as their shopping mall with constant break-ins, car theft and various other assorted means of 'urban' entertainment.
The smallest disruption in radio communications in these areas mean that Tyrone is free to come busting into your bedroom window and do as he pleases. Don't forget, NJ is a gun grabbing state and makes its residents completely dependent on the local police for any maintainence of order. Luckily the 'residents' of Camden don't use the internet because it's all a bunch of words or this would turn into a feeding frenzy without par since the 60's riots their ancestors used to get their TV's.
They use Anvil racks in the music biz, armored 19" racks on wheels. You could easily have one made up to house 16 or so U's of hardware, wire the whole thing into powerstrips so you just need one outlet on a site. Sure it's not as portable as the Tadpole, but it's a hell of a lot less than the $20k or so the Tadpoles go for and it's a lot harder and more obvious to steal a trunk on wheels than a laptop.
With an Anvil rack you could have switches/hubs/servers whatever you wanted. For $20k you can buy a silly amount of Netra X1's and a rack.
Hasn't anyone considered that in addition to the EZ-Pass or similar toll token devices, this is yet another method of vehicle tracking and thus easily adapted for automating speeding tickets?
If you want privacy now and you have a new generation cellphone you already have to power it down completely or you will be tracked via GPS. EZ-Pass was already tested for its ability to trigger automatic speed/radar devices. Now this.
I wish more people would boycott these devices...it won't be long until we all regret them.
An oligopoly will always work. With the automakers sneaking this trash into all of their new models it is a guarantee.
What I hate is the fact they make out the fees as something that should be necessary to pay for the content provided. The truth of it is, it is just gravy on top of the billions in advertising they will make already. It is not all commercial free or it might be worthwhile.
If WINE auto installs mime types of any sort that affect globally used *nix apps, that should be corrected. The biggest festering bleeding problem with Windows is the fact that a mail client will auto-execute anything. If a moron wants to associate an suid WINE to handle VB script attachments viewed in a mutt session let him, but WINE certainly shouldn't be setting up risky associations by default as the article implies.
If the 'victim' setup those mime associations, he should be prevented from breeding.
Did I miss something? In the letter sent to the congressmen there was no substantive argument or pointers to information more clearly defining the GPL, it was merely a pile of rhetoric that didn't give any support for the opposition.
I know too little of the licensing mess, but someone better informed should forward a clearer explanation in opposition to the congressmen involved. If they have no further understanding and just see a complaint, what good will that do. Particularly since obviously they are being well funded to even address this issue. Keep in mind, if they weren't receiving vacations/homes/cars/cash for trying to pass this....would they come up with this idea on their own? These guys are AOL'ers at best as far as their understanding of technology.
We need a platform solid enough to surpass their greed or it will simply pass us by.
I answered my own question reading the details. This puppy has completely variable IF due to all of it being a software engine. This won't mean much to the average Joe, but for a radio enthusiast on paper at least it could be very cool.
The IF in my very ragged terms is what is used to 'mix' with the signal input to create the output. There are 'dead spots' in any radio due to a sort of overlap situation with the fixed or narrowly variable IF and the actual spectrum space. The advantage of completely variable IF is one for the real radio fanatics but it's still a neat innovation. Now whether a radio on a card is 'quiet' enough that it would even matter....this is making me curious enough to hunt one down to check it out.
Oh yeah, used HAM 'HF' rigs are available cheap on ebay and make fun toys and halfway decent shortwave rigs. There are several computer control frontend projects kicking around, compare the models supported and go shopping. SWL (short wave listening) can be a nice diversion.
Well assuming the neighbors didn't mind the gigantic dish in place of their houses.
Also remember, with SETI the whole project centers around the fact that their existing antennae pick up so much data it requires a global effort to process the information. They aren't lacking for the ability to listen, merely to interpret the overwhelming amount of data they already collect.
It will do a bit of both. It covers spectrum up to 30Mhz, in that range there is plain old AM radio, HAM radio, commercial marine, military. There's all sorts of transmission modes in there too; plain voice on AM, voice on SSB, morse code on SSB, FM, data of several types.
One of the things you can do for example is receive weather fax's, you can 'snoop' other forms of data communications as well with add-on accessories. Not sure how the radios on a card work with add-ons or if the software can do it outright inline.
What I found odd was the mention that this was a first of some sort, there have been PC based radios similar to this for a long while, and third party linux frontend support as well. Check out freshmeat, there are other radio frontend controller projects too.
Personally I like having a seperate radio device, it's better for the toy factor and at least a little bit safer as far as picking up static discharges on the antennas, which just creeps me out with antennas that go direct to a PCI card.
You can't blame RPM. RPM is merely a vehicle for installing a package. How an RPM is created is the key. Blame the user that forces the install, blame the RPM creator if they don't have a clean system. Don't blame the vehicle.
An end user needs to simply understand that when you compile a package you are including the base configuration of the system it is built on. If a builder/maintainer of an RPM has a system that is not identical to the user trying to install the RPM, of course you will have dependency issues.
I have never had a single dependency issue with an RPM supplied by the distribution I was using so long as I was trying to install an RPM built for the release version I was using.
Why is it so difficult for people to understand that if they try to install an RPM 'from the wild' they might run into trouble?
The reason.deb's are cleaner most of the time is because they come from a centralized source and are created under fairly rigid standards so they will work on a 'known' base system. A.deb that is not officially maintained is no different than an RPM of similar background.
In a nutshell, use RPM's that were built for the release of the distro you are running and QUIT using --force --no-deps as your normal install routine. RPM bitches about dependencies for a reason, forcing the install is YOUR mistake not the package manager's.
Keep Checking Your Statements
on
Disconnecting
·
· Score: 2, Interesting
It took my father more than two months *after* AOL assured him they would cancel his service for them to stop billing him for it. He had to call back again and argue for more than an hour to be credited...which took them 90days to run through.
What we are talking about here.... is all the know-nothing do gooder liberals that will all line up with their hippie sandals on to protest the 'danger' to their children that having unrestricted access will represent.
I like your idea, maybe in Europe it could work or already is, unfortunately here in the states people have no personal accountability and the city would be sued for the first moron whose unattended child saw someone naked while surfing with mommy's Powerbook.
As long as the setup adheres to the 1W limit and the gain specifications for the antennas there is no issue. The FCC permits this.
The 'limiting' factor that would keep people from exceeding those limits is the PC card itself. If you step up the power at the access point but the cards themselves can't be hyped up, it's just a waste. iow if the access point can 'hit' the card at 5 miles but the card has a short range...
I wonder how hard building a 2.4Ghz brick for the car would be;-).
You run pink noise to setup the crossover points as it is a more balanced representation of the audio spectrum and appropriate for human hearing response. Under pink noise once you deal with it for a while you can hear the peaks in the signal and compensate for them. One can also use a real time spectrum analyzer and setup by the numbers.
It makes sure the power distribution of the rig is even so that when you go to tune the actual EQ to suit the room acoustics you have a balanced starting point as a reference.
Now take white noise and run it through a system and you can shred cones pretty easily as all freq's are pushed at the same level and systems are not generally designed for a signal of that nature.
If you're curious, look for a CD The Great Japanese/American Noise Experiment or similar, basically experimental 'music' done with oscillators and wave form generators. It's a great demo of the dynamic range this type of noise actually has. Just don't turn it up too far on equipment you would like to keep.
1) I like swiveling around and having the whole team right there for any input...really speeds up roll-outs when you can grab the collective knowledge of the team.
The disadvantages.
2) Stuck with the lighting that a suit decides is the proper atmosphere....ugh personally I like a cave as far as lighting goes.
3) Noise level, absolutely hurts productivity while deep in any code or systems logic.
4) Wanderers....the people from other ends of the business who insist on making rounds for smalltalk.
5) Accessibility; Sometimes there are conversations amongst a team that shouldn't be heard by anyone/everyone within earshot. This is particularly important with the systems team for security reasons etc.
My ideal, at least partition areas thoroughly by specialty, developers,systems, designers, etc. .
The section is quite clear to me and is part of the reason I was quite pleased with the changes.
They have relaxed the rules outlawing free use of the service tremendously.
Basically you can do what you please as long as it doesn't disrupt the service of another member or is related to a commercial enterprise. Of course illegal use i.e. batch scanning subnets etc. is disallowed as well.
The old policy was no servers at all.
Unfortunately in NY/NJ area there is a whole class of people determined to get the last penny out of anything they can manage with the assistance of their attorneys. These people will do things like VPN commercial mail services over a residential subscriber line rather than pay like every other company. It is this mentality in general that necessitates these absurd semantics for simple issues. It's killing the country...but that's another topic/forum entirely;-).
Incidentally on this subnet of @home they've capped each connection to a pretty low 10k/s upstream.....max total seems to be about 80-100k upstream. Not sure if that is intended or just another misconfiguration on their end. Downstream typical ftp's are 200kB/s during off-peak to short routes.
Slashdot Mirror
The money isn't the app it's the services. Create a product and then provide support for it. You provide support and you will not lose your customer base. Nobody that sells software provides any support these days and they wonder why the business model crumbles.
The big punchline will be ease of use for the admins. It is a giant pain in the ass doing scripting for multiple platforms due to varying locations of things. Sure you can spend time doing find and grep to vars in the scripts to make them safer but this move would make a lot of things simpler.
The other point is that Sun is also selling linux and x86 platforms for linux. For the sanity of their support staff going LSB compliant will take some load off. Not to mention aiding the third party app producers. Will take a lot more load off an app vendor's staff now.
The whole argument above about comparing Sparc/Solaris to Linux/Dell is only from those who haven't run the big Sun iron. It will be a while before linux can compete directly with Sparc/Solaris and I'm sure that Sun won't be opposed to linux on their hardware when the reliability and performance equals Solaris on the same hardware. They are selling hardware and support services, I'm sure they really don't care what runs on the hardware if it runs well and they can support it. LSB compliance is a small step on a longer path for a full support solution that will lend to a broader market base.
If there is a serious effort at security at all SSH won't be permitted. Any site that would bother paying $35/seat to essentially proxy AIM will have forced proxying of any other outbound traffic. It is fun when SSH is open though, gotta love the forwarding of your own private squid to avoid the jobsite web proxies.
Camden NJ for anyone who isn't from this area is so disgusting and violent that they felt left out when Detroit was burning the city for Halloween and decided they should do it too a few years ago.
The areas affected are areas where people who have jobs try to live and raise families. Meanwhile, the denizens of Camden proper use these areas as their shopping mall with constant break-ins, car theft and various other assorted means of 'urban' entertainment.
The smallest disruption in radio communications in these areas mean that Tyrone is free to come busting into your bedroom window and do as he pleases. Don't forget, NJ is a gun grabbing state and makes its residents completely dependent on the local police for any maintainence of order. Luckily the 'residents' of Camden don't use the internet because it's all a bunch of words or this would turn into a feeding frenzy without par since the 60's riots their ancestors used to get their TV's.
They use Anvil racks in the music biz, armored 19" racks on wheels. You could easily have one made up to house 16 or so U's of hardware, wire the whole thing into powerstrips so you just need one outlet on a site. Sure it's not as portable as the Tadpole, but it's a hell of a lot less than the $20k or so the Tadpoles go for and it's a lot harder and more obvious to steal a trunk on wheels than a laptop.
With an Anvil rack you could have switches/hubs/servers whatever you wanted. For $20k you can buy a silly amount of Netra X1's and a rack.
Hasn't anyone considered that in addition to the EZ-Pass or similar toll token devices, this is yet another method of vehicle tracking and thus easily adapted for automating speeding tickets?
If you want privacy now and you have a new generation cellphone you already have to power it down completely or you will be tracked via GPS. EZ-Pass was already tested for its ability to trigger automatic speed/radar devices. Now this.
I wish more people would boycott these devices...it won't be long until we all regret them.
An oligopoly will always work. With the automakers sneaking this trash into all of their new models it is a guarantee.
What I hate is the fact they make out the fees as something that should be necessary to pay for the content provided. The truth of it is, it is just gravy on top of the billions in advertising they will make already. It is not all commercial free or it might be worthwhile.
If WINE auto installs mime types of any sort that affect globally used *nix apps, that should be corrected. The biggest festering bleeding problem with Windows is the fact that a mail client will auto-execute anything. If a moron wants to associate an suid WINE to handle VB script attachments viewed in a mutt session let him, but WINE certainly shouldn't be setting up risky associations by default as the article implies.
If the 'victim' setup those mime associations, he should be prevented from breeding.
Either way, a correction is needed.
Did I miss something? In the letter sent to the congressmen there was no substantive argument or pointers to information more clearly defining the GPL, it was merely a pile of rhetoric that didn't give any support for the opposition.
I know too little of the licensing mess, but someone better informed should forward a clearer explanation in opposition to the congressmen involved. If they have no further understanding and just see a complaint, what good will that do. Particularly since obviously they are being well funded to even address this issue. Keep in mind, if they weren't receiving vacations/homes/cars/cash for trying to pass this....would they come up with this idea on their own? These guys are AOL'ers at best as far as their understanding of technology.
We need a platform solid enough to surpass their greed or it will simply pass us by.
I answered my own question reading the details. This puppy has completely variable IF due to all of it being a software engine. This won't mean much to the average Joe, but for a radio enthusiast on paper at least it could be very cool.
The IF in my very ragged terms is what is used to 'mix' with the signal input to create the output. There are 'dead spots' in any radio due to a sort of overlap situation with the fixed or narrowly variable IF and the actual spectrum space. The advantage of completely variable IF is one for the real radio fanatics but it's still a neat innovation. Now whether a radio on a card is 'quiet' enough that it would even matter....this is making me curious enough to hunt one down to check it out.
Oh yeah, used HAM 'HF' rigs are available cheap on ebay and make fun toys and halfway decent shortwave rigs. There are several computer control frontend projects kicking around, compare the models supported and go shopping. SWL (short wave listening) can be a nice diversion.
Well assuming the neighbors didn't mind the gigantic dish in place of their houses.
Also remember, with SETI the whole project centers around the fact that their existing antennae pick up so much data it requires a global effort to process the information. They aren't lacking for the ability to listen, merely to interpret the overwhelming amount of data they already collect.
Yes.
It will do a bit of both. It covers spectrum up to 30Mhz, in that range there is plain old AM radio, HAM radio, commercial marine, military. There's all sorts of transmission modes in there too; plain voice on AM, voice on SSB, morse code on SSB, FM, data of several types.
One of the things you can do for example is receive weather fax's, you can 'snoop' other forms of data communications as well with add-on accessories. Not sure how the radios on a card work with add-ons or if the software can do it outright inline.
What I found odd was the mention that this was a first of some sort, there have been PC based radios similar to this for a long while, and third party linux frontend support as well. Check out freshmeat, there are other radio frontend controller projects too.
Personally I like having a seperate radio device, it's better for the toy factor and at least a little bit safer as far as picking up static discharges on the antennas, which just creeps me out with antennas that go direct to a PCI card.
You can't blame RPM. RPM is merely a vehicle for installing a package. How an RPM is created is the key. Blame the user that forces the install, blame the RPM creator if they don't have a clean system. Don't blame the vehicle.
.deb's are cleaner most of the time is because they come from a centralized source and are created under fairly rigid standards so they will work on a 'known' base system. A .deb that is not officially maintained is no different than an RPM of similar background.
An end user needs to simply understand that when you compile a package you are including the base configuration of the system it is built on. If a builder/maintainer of an RPM has a system that is not identical to the user trying to install the RPM, of course you will have dependency issues.
I have never had a single dependency issue with an RPM supplied by the distribution I was using so long as I was trying to install an RPM built for the release version I was using.
Why is it so difficult for people to understand that if they try to install an RPM 'from the wild' they might run into trouble?
The reason
In a nutshell, use RPM's that were built for the release of the distro you are running and QUIT using --force --no-deps as your normal install routine. RPM bitches about dependencies for a reason, forcing the install is YOUR mistake not the package manager's.
It took my father more than two months *after* AOL assured him they would cancel his service for them to stop billing him for it. He had to call back again and argue for more than an hour to be credited...which took them 90days to run through.
Funny how desperate yuppie couples could figure out something that is explicitly warned against as an activity to attract bears.
Yup, bears can smell the scent of sex for long distances and it's one of the things to be wary of in bear country while camping.
Hopefully this will chlorinate the gene pool.
What we are talking about here .... is all the know-nothing do gooder liberals that will all line up with their hippie sandals on to protest the 'danger' to their children that having unrestricted access will represent.
I like your idea, maybe in Europe it could work or already is, unfortunately here in the states people have no personal accountability and the city would be sued for the first moron whose unattended child saw someone naked while surfing with mommy's Powerbook.
Yeah, no way they are using that band. It's 2.4Ghz the CB band runs from 26Mhz-27Mhz.
As long as the setup adheres to the 1W limit and the gain specifications for the antennas there is no issue. The FCC permits this.
The 'limiting' factor that would keep people from exceeding those limits is the PC card itself. If you step up the power at the access point but the cards themselves can't be hyped up, it's just a waste. iow if the access point can 'hit' the card at 5 miles but the card has a short range...
I wonder how hard building a 2.4Ghz brick for the car would be ;-).
FCC 802.11b restrictions
More information
QNX is hardly 'under-underground' its roots are in the embedded systems market, it is a commercial product and has been around for a while.
That's pretty close.
You run pink noise to setup the crossover points as it is a more balanced representation of the audio spectrum and appropriate for human hearing response. Under pink noise once you deal with it for a while you can hear the peaks in the signal and compensate for them. One can also use a real time spectrum analyzer and setup by the numbers.
It makes sure the power distribution of the rig is even so that when you go to tune the actual EQ to suit the room acoustics you have a balanced starting point as a reference.
Now take white noise and run it through a system and you can shred cones pretty easily as all freq's are pushed at the same level and systems are not generally designed for a signal of that nature.
If you're curious, look for a CD The Great Japanese/American Noise Experiment or similar, basically experimental 'music' done with oscillators and wave form generators. It's a great demo of the dynamic range this type of noise actually has. Just don't turn it up too far on equipment you would like to keep.
www.utnereader.com under the society section
Hey, it's all in the phones for a PMP-300.
Take it and try with higher end phones and you'll use it again. The Koss Porta-Pro phones sound fantastic with it, though they look hideous.
The advantages
1) I like swiveling around and having the whole team right there for any input...really speeds up roll-outs when you can grab the collective knowledge of the team.
The disadvantages.
2) Stuck with the lighting that a suit decides is the proper atmosphere....ugh personally I like a cave as far as lighting goes.
3) Noise level, absolutely hurts productivity while deep in any code or systems logic.
4) Wanderers....the people from other ends of the business who insist on making rounds for smalltalk.
5) Accessibility; Sometimes there are conversations amongst a team that shouldn't be heard by anyone/everyone within earshot. This is particularly important with the systems team for security reasons etc.
My ideal, at least partition areas thoroughly by specialty, developers,systems, designers, etc. .
The section is quite clear to me and is part of the reason I was quite pleased with the changes.
;-).
They have relaxed the rules outlawing free use of the service tremendously.
Basically you can do what you please as long as it doesn't disrupt the service of another member or is related to a commercial enterprise. Of course illegal use i.e. batch scanning subnets etc. is disallowed as well.
The old policy was no servers at all.
Unfortunately in NY/NJ area there is a whole class of people determined to get the last penny out of anything they can manage with the assistance of their attorneys. These people will do things like VPN commercial mail services over a residential subscriber line rather than pay like every other company. It is this mentality in general that necessitates these absurd semantics for simple issues. It's killing the country...but that's another topic/forum entirely
Incidentally on this subnet of @home they've capped each connection to a pretty low 10k/s upstream.....max total seems to be about 80-100k upstream. Not sure if that is intended or just another misconfiguration on their end. Downstream typical ftp's are 200kB/s during off-peak to short routes.
"Er... you deserve $113.45, a dented '79 Oldsmobile and a kick in the ass. Now git!" Damnit, God told me I had an exclusive on that deal.