That's great, but I don't have 2GB of RAM and I will not build my hardware around my operating system. If the operating system will not work with my hardware, it won't work for me.
But in the future, you -will- have 2GB of RAM. I'm not saying that linux is the big deal, it just happens to be the first that has been configured to run without installing. And running without installing -is- a big deal, that's my point.
Yes, you have your "special" hardware that you will never let go of. But as hardware gets cheaper, for a large part of the rest of the world, zero-install starts to make sense, especially when it fits comfortably into RAM.
Linux is great. I won't deny that the LiveCDs that I've used are great. But I can't keep my optical drive occupied forever by my OS. That's why we have hard drives...
Funny you should mention that. I recently rebuilt my system after a mobo failure, and I built it with 2GB of RAM.
When I initially built it, I fired up a KNOPPIX CD to test the system out. Since I had so much RAM, I used the "toram" option to copy the CD into memory (took an extra 2.5 minutes at boot), so the DVD burner would be freed up. Wow. What a great way to run!
My system is on a UPS and rarely gets rebooted anyway, I'm starting to think this might be viable for longer-term than just testing. Zero install could be the future of the OS.
It might not be all things to all people, but it is getting closer. For the most popular purposes (web/email/images/music/dvd's*), it works now.
...the future looks bright with no specialist software engineers with all development being done by unqualified developers who have no incentive to do it properly.
For example: Apache, Linux, Java, Perl, Python, MySQL?
I've managed both Apache and IIS, and there is no doubt in my mind that the Apache developers are far from unqualified, and definitely had some sort of incentive to do it properly.
Software support can be a non-issue with many of these apps. As long as you have all of the features you need, these systems are very stable because they are very mature.
The underlying OS is not changing, so if the features are not changing, that stability can be counted on.
Old DOS apps are incredibly -fast- on new(er) hardware.
I don't know that the open source aspect is a big sell (although it is nice, it isn't Free, only free), but free is pretty good too.
In the corporate/government environment, it is great to have the Solaris name/reputation available for free.
While I see more and more acceptance of Linux, there is still some level of cowboy/zealotry image associated with it.
Perceptions: Linux == t-shirt, Solaris == shirt and tie.
I'm personally for FOSS, but in some environments, it is good to be able to quickly and cheaply put up say, a sendmail server without the perceived stigma attached to FOSS. It is a way to save money and get the job done while staying under the corporate radar.
What's more, it doesn't actually do much for the security anyway: if someone hands random people their password then you're pretty much screwed anyway - people aren't going to wait until after the password change to try and use that password.
Periodic password changes help limit the window of exploitation.
That's not to say that you aren't royally screwed in some situations (ie., root password/privelige escalation), but in other situations it can really help limit the damage. You don't ever really know if someone else has your password.
Password changes exploit the fact that it often takes time to leverage a compromised password into useful exploitation.
Yes, the users are the primary problem (the point of TFA!).
It's all about using layered defense to incrementally raise the bar of entry.
Mercora's parent company pays the labels a rights fee for each song the service streams.
Also from the FA
Currently, Mercora makes its money by letting you purchase the music that you're listening to through Amazon, as well as posting unobtrusive Google-supplied ads to the application.
Satisfied now? Got karma envy? Moderate instead of bitching about it.
A random sample of music on my system would put Dead Kennedies next to Phillip Glass next to James Brown next to Keith Jarrett, etc....
Some songs just don't play well with others.
Maybe for Windows then, but that still doesn't cover Linux...
Why not? We are talking about a license for a codec. They got their money for a license for a codec. Doesn't matter what I'm running, I paid for a license when I bought my sound card.
So the Frauenhofer seal on the box meant nothing? Even if it isn't hardware encoding (although I definitely got the impression it did), doesn't paying for the software bundle still put me in the position of having paid for my license?
I have a SB Live! card that has hardware mp3 decoding built-in, but the linux drivers support it. I assume I paid for a license as part of the purchase price of the card. I feel no qualms about using LAME, etc. and in fact they are doing a great service to those of us who already paid but are unable to use that capablility on our OS of choice...
any competent person in the field will tell you that they ARE NOT PASSWORDS and SHOULD NEVER BE USED AS PASSWORDS
I agree, but I have experienced a similar situation (fortunately nothing as sensitive as medical records), and you would not believe the pressure there was to use a public ID as a password.
Everyone was pushing for the path of least resistance, which is rarely a secure path.
Funny thing is, all of the potential "problems" that were brought up as justification for developing an insecure system never really materialized. Do The Right Thing, and it will work out fine.
I'm pretty sure you will be modded to oblivion. Speak the truth in the Apple section of/. at the peril of your karma (been there, done that, this is my last post in the Apple section)...
Slashdot Mirror
That's great, but I don't have 2GB of RAM and I will not build my hardware around my operating system. If the operating system will not work with my hardware, it won't work for me.
But in the future, you -will- have 2GB of RAM. I'm not saying that linux is the big deal, it just happens to be the first that has been configured to run without installing. And running without installing -is- a big deal, that's my point.
Yes, you have your "special" hardware that you will never let go of. But as hardware gets cheaper, for a large part of the rest of the world, zero-install starts to make sense, especially when it fits comfortably into RAM.
Linux is great. I won't deny that the LiveCDs that I've used are great. But I can't keep my optical drive occupied forever by my OS. That's why we have hard drives...
Funny you should mention that. I recently rebuilt my system after a mobo failure, and I built it with 2GB of RAM.
When I initially built it, I fired up a KNOPPIX CD to test the system out. Since I had so much RAM, I used the "toram" option to copy the CD into memory (took an extra 2.5 minutes at boot), so the DVD burner would be freed up. Wow. What a great way to run!
My system is on a UPS and rarely gets rebooted anyway, I'm starting to think this might be viable for longer-term than just testing. Zero install could be the future of the OS.
It might not be all things to all people, but it is getting closer. For the most popular purposes (web/email/images/music/dvd's*), it works now.
*With libdvdcss added after boot...
Been there, done that, got the t-shirt! #:-)
For example: Apache, Linux, Java, Perl, Python, MySQL?
I've managed both Apache and IIS, and there is no doubt in my mind that the Apache developers are far from unqualified, and definitely had some sort of incentive to do it properly.
Dang, where are the mod points when you need them?!
Software support can be a non-issue with many of these apps. As long as you have all of the features you need, these systems are very stable because they are very mature.
The underlying OS is not changing, so if the features are not changing, that stability can be counted on.
Old DOS apps are incredibly -fast- on new(er) hardware.
Some observations:
I don't know that the open source aspect is a big sell (although it is nice, it isn't Free, only free), but free is pretty good too.
In the corporate/government environment, it is great to have the Solaris name/reputation available for free.
While I see more and more acceptance of Linux, there is still some level of cowboy/zealotry image associated with it.
Perceptions: Linux == t-shirt, Solaris == shirt and tie.
I'm personally for FOSS, but in some environments, it is good to be able to quickly and cheaply put up say, a sendmail server without the perceived stigma attached to FOSS. It is a way to save money and get the job done while staying under the corporate radar.
So what are you advocating?
No password changes? Ever?
Dictionary passwords?
No passwords?
You are right, the problem is the uneducated or uncaring user. Secure systems are inherently pain in the ass to use securely and maintain securely.
Change your password regularly.
...
What's more, it doesn't actually do much for the security anyway: if someone hands random people their password then you're pretty much screwed anyway - people aren't going to wait until after the password change to try and use that password.
Periodic password changes help limit the window of exploitation.
That's not to say that you aren't royally screwed in some situations (ie., root password/privelige escalation), but in other situations it can really help limit the damage. You don't ever really know if someone else has your password.
Password changes exploit the fact that it often takes time to leverage a compromised password into useful exploitation.
Yes, the users are the primary problem (the point of TFA!).
It's all about using layered defense to incrementally raise the bar of entry.
Damn! I finally RTFA, now I'm evil...
A Linux distribution contains hundreds to thousands of programs.
A Windows distribution contains a handful of programs.
Huh? Maybe I'm too dense to figure out the interface, but I wasn't able to "choose a country". Informative? I don't think so....
OK, not to descend into an endless bitching match, but I did RTFA before I posted. I just didn't get all the way to the final paragraph, my bad.
I didn't post an uninformed opinion, the part I didn't read from the article I posed as a question. To promote discussion. OK?
As far as being a "little kiddie", I was punching cards before you were probably even glint in your father's eye!
Mercora's parent company pays the labels a rights fee for each song the service streams.
Also from the FACurrently, Mercora makes its money by letting you purchase the music that you're listening to through Amazon, as well as posting unobtrusive Google-supplied ads to the application.
Satisfied now? Got karma envy? Moderate instead of bitching about it.
According to the article, they pay the royalty fees, although it doesn't say where the money is coming from. Hmmm....
A random sample of music on my system would put Dead Kennedies next to Phillip Glass next to James Brown next to Keith Jarrett, etc.... Some songs just don't play well with others.
Maybe for Windows then, but that still doesn't cover Linux...
Why not? We are talking about a license for a codec. They got their money for a license for a codec. Doesn't matter what I'm running, I paid for a license when I bought my sound card.
So the Frauenhofer seal on the box meant nothing? Even if it isn't hardware encoding (although I definitely got the impression it did), doesn't paying for the software bundle still put me in the position of having paid for my license?
...The linux drivers -don't- support it...
I have a SB Live! card that has hardware mp3 decoding built-in, but the linux drivers support it. I assume I paid for a license as part of the purchase price of the card. I feel no qualms about using LAME, etc. and in fact they are doing a great service to those of us who already paid but are unable to use that capablility on our OS of choice...
any competent person in the field will tell you that they ARE NOT PASSWORDS and SHOULD NEVER BE USED AS PASSWORDS
I agree, but I have experienced a similar situation (fortunately nothing as sensitive as medical records), and you would not believe the pressure there was to use a public ID as a password.
Everyone was pushing for the path of least resistance, which is rarely a secure path.
Funny thing is, all of the potential "problems" that were brought up as justification for developing an insecure system never really materialized. Do The Right Thing, and it will work out fine.
I'm pretty sure you will be modded to oblivion. Speak the truth in the Apple section of /. at the peril of your karma (been there, done that, this is my last post in the Apple section)...
I don't know that I would expect them to export .swf, but why not import? It's an open spec.
Will Pages be MS Word compatible?
More importantly, will it be OO.O compatible?
Actually, BMI will come knocking.