Even in the US most of the telco's I've seen now have a webpage where you can send SMS messages to any phone on their network for free and without limit.
All it needs is a program that does contious HTTP POSTS to that form and you have a DoS to one or more phones.
If you are on a phone contract where you pay for incomming SMS this could really hurt financially. As an ex-pat Brit I still find it hard to come to terms with paying for incoming calls to a mobile phone in the US.
It was NEVER the first entry, it was the default entry which wasn't necessarily first. The defaults were always no destructive in all OpenLook applications I used. OpenLook != OpenWindows (OpenLook is the look and fell of the GUI OpenWindows is Sun's shippent of that look and feel together with an X server and other stuff).
You could easily change this behaviour from the properties menu.
Also which button is the root menu usually on ?
Err the right one so this was consistancy. Remeber that OpenLook's history predates anything of CDE, or KDE, or GNOME and Microsoft Windows.
It is not just about licenesing but also about the choice of programing environment. My understanding is that KDE pretty much forces C++ onto you. That is fine if everything is only ever built with on compiler which is using the same revision of the C++ ABI and interepretation of the standard. For Sun customers that wouldn't work because the Sun compilers and gcc and others all get used on Solaris by different groups of people for diffrent reasons.
Note this is my personal interpretation and is not to be taken as an official Sun position.
Into the case without turning screws Most Sun machines (except the current lowend Ultra 5/10).
FireWire Sun Blade 1000
Optical Mouse Sun was doing optical mice back in the 80's.
Giving up CRT in favour of LCD Bad idea, you need both to properly cover the market, this has been hashed out on/. many many times each have their benifits but currently neither does everything for everyone.
BTW Sun has LCD screens for standalone use and
a SunRay integrated into an LCD screen.
The article appears to be saying that this will be interoperability at the server level which I believe is actually better than having the client know how to talk to multiple different servers.
Clients like jabber are fine if you don't mind having accounts on every service but why should you need to ? You don't need to have a different email account to send mail to some one at AOL if you have Yahoo so why should I need multiple IM accounts.
The only reason I have a hotmail account is to chat to other people that use Microsoft IM if I could do that from AOL or Yahoo or something else of my choice it would be great progress and I might acutally use IM a bit more.
Where they already have encrypted digital broadcast TV ! (OnDigital), though at the moment I don't believe there is copy protection it is just encryption to make sure only those people who payup get it. The next logical step for the UK of course is to link the "free"[1] channels to your TV license.
[1] There really is no such thing as free (as in beer) TV in the UK because if you own equipment capable of recieving any broadcast or satelite TV then you need to pay the TV license. Not paying isn't an option they will get you and they have the technology to find you....
The discussion is completely off topic but I feel I have to comment anyway:
I would very strongly disagree that http can do
everything that ftp can do. ftp is a general purpose file transfer program that provides a lot of the functionality that you get from ls,cp,rm but between two machines. It provides authentication, separate data and control channels and heaps more stuff. http is simple and stupid and thats why it is so widely used. http is very poor at file transfer - it can't do restarts.
Red Light cameras are very popular in the UK, most intersections in London have red light cameras. There are also bus lane cameras (UK doesn't have car pool lanes yet).
When I moved to California I was shocked to see the number of people who jump red lights (and I'm not talking about right turn on red - these are mainly left over busy intersections) and I quickly realised it is because of the lack or red light cameras.
I understand that some states in the US belive these aren't legal - I don't understand why that can be the case you were clearly breaking the law and in many cases intentionally doing it. What is unconstitutional about getting caught by a device rather than a policeman ?
This is my stock answer for why static linking is a bad idea it is written with Solaris in mind but applies equally well to an UNIX like system and to Windows systems as well.
Static linking reduces the overhead when the program is started up, mainly because relocations and some other start-up activities are done at compile time.
However, static linking is generally discouraged. Here are some reasons :
Static linking prevents libc_psr.so.1 from working for platform specifics. This library automatically enables dynamically linked programs from linking in platform specific versions of various library routines which are optimized for a particular platform.
Static linking greatly increases working set size and disk footprint.
Statically linked executables are NOT necessarily binary compatible between releases - the Sun Application Binary Guarantee does not apply to statically linked programs.
eg. statically linked programs that use libsocket will failed if compiled on 2.5.1 or less and run on 2.6 or later.
Patches to system libaries for bug fixes and performance enhancements are not automatically picked up by the application. This is most important for library based security fixes.
Some debugging libraries/tools will fail to work properly.
eg. malloc debugging.
Localistation via setlocale(3c) / gettext(3c) is not supported when libc is statically linked.
When to use static linking
The binary is critical to system operation when in single user-mode either for the startup of the OS or for disaster recovery.
Statically linking a private (internal) libarary is okay.
Don'ts
Statically link against libc
Statically link against libdl
glibc which is what Linux uses for C runtime is under LGPL not GPL. LGPL specifically allows the linking. The virtualdub code being used in the Vidomi case is under GPL not LGPL.
The only proof that there was classified data on the laptop is the media reports. Don't trust everything you read in the media.
The other thing to note is the classification scheme has a class called "unclassfied" which means that the data doesn't contain anything sensitive but it is still classified in the scheme
You haven't understood the article. In the case of Linux, Linus is not liable because he as no on going control of what the user actually does with the product. That is the clear and simple distinction between a Service like Napster and a Product like the Linux Kernel.
The pictures on the California highspeed rail site are actually of a EuroStar.
The DMCA is a US specific law that does not apply outside of the US.
This case is about a Japanese based company and Australian law - so how does DMCA have any impact ?
You need either an SSN or a copy of the standard letter the department issues saying you aren't intitled to have one.
You then go into the DMV checks INS records cycle,
mine took 2 months.
Even in the US most of the telco's I've seen now have a webpage where you can send SMS messages to any phone on their network for free and without limit.
All it needs is a program that does contious HTTP POSTS to that form and you have a DoS to one or more phones.
If you are on a phone contract where you pay for incomming SMS this could really hurt financially. As an ex-pat Brit I still find it hard to come to terms with paying for incoming calls to a mobile phone in the US.
It was NEVER the first entry, it was the default entry which wasn't necessarily first. The defaults were always no destructive in all OpenLook applications I used. OpenLook != OpenWindows (OpenLook is the look and fell of the GUI OpenWindows is Sun's shippent of that look and feel together with an X server and other stuff).
You could easily change this behaviour from the properties menu.
Also which button is the root menu usually on ?
Err the right one so this was consistancy. Remeber that OpenLook's history predates anything of CDE, or KDE, or GNOME and Microsoft Windows.
It is not just about licenesing but also about the choice of programing environment. My understanding is that KDE pretty much forces C++ onto you. That is fine if everything is only ever built with on compiler which is using the same revision of the C++ ABI and interepretation of the standard. For Sun customers that wouldn't work because the Sun compilers and gcc and others all get used on Solaris by different groups of people for diffrent reasons.
Note this is my personal interpretation and is not to be taken as an official Sun position.
Into the case without turning screws
/. many many times each have their benifits but currently neither does everything for everyone.
Most Sun machines (except the current lowend Ultra 5/10).
FireWire
Sun Blade 1000
Optical Mouse
Sun was doing optical mice back in the 80's.
Giving up CRT in favour of LCD
Bad idea, you need both to properly cover the market, this has been hashed out on
BTW Sun has LCD screens for standalone use and
a SunRay integrated into an LCD screen.
As for the DOS thing... If a program can handle wildcards, you can just do
;-)
program *.x
just like UNIX, since DOS is a UNIX copy cat.
Not quite true. In UNIX systems the expansion of
the wildcard is performed by the shell before
executing the program.
In DOS the program does the interpretation of
the wildcard itself.
Quite a fundamental difference since most UNIX programs don't understand wildcards at all but it looks like they do because the shell is powerful.
Personally I prefer zsh over any other shell
The IETF is already working on it:
h tm l
http://www.ietf.org/html.charters/impp-charter.
The article appears to be saying that this will be interoperability at the server level which I believe is actually better than having the client know how to talk to multiple different servers.
Clients like jabber are fine if you don't mind having accounts on every service but why should you need to ? You don't need to have a different email account to send mail to some one at AOL if you have Yahoo so why should I need multiple IM accounts.
The only reason I have a hotmail account is to chat to other people that use Microsoft IM if I could do that from AOL or Yahoo or something else of my choice it would be great progress and I might acutally use IM a bit more.
Or you could move to the UK
Where they already have encrypted digital broadcast TV ! (OnDigital), though at the moment I don't believe there is copy protection it is just encryption to make sure only those people who payup get it. The next logical step for the UK of course is to link the "free"[1] channels to your TV license.
[1] There really is no such thing as free (as in beer) TV in the UK because if you own equipment capable of recieving any broadcast or satelite TV then you need to pay the TV license. Not paying isn't an option they will get you and they have the technology to find you....
It is for this exact reason that libc (and other key libraries) and kernel modules on Solaris can have platform specific optimized versions.
/usr/lib/libc.so.1 but at run time some of the functions actually get run out of: /usr/platform/`arch`/lib/libc_psr.so.1
eg: My program links against
The `arch` in this case isn't limited to sun4c,sun4m,sun4u,sun4u-us3
but can actually be a fully platform spec like SUNW,Ultra-Enterprise-10000
The discussion is completely off topic but I feel I have to comment anyway:
I would very strongly disagree that http can do
everything that ftp can do. ftp is a general purpose file transfer program that provides a lot of the functionality that you get from ls,cp,rm but between two machines. It provides authentication, separate data and control channels and heaps more stuff. http is simple and stupid and thats why it is so widely used. http is very poor at file transfer - it can't do restarts.
Solaris 8 shipped with rpm2cpio ;-)
Red Light cameras are very popular in the UK, most intersections in London have red light cameras. There are also bus lane cameras (UK doesn't have car pool lanes yet).
When I moved to California I was shocked to see the number of people who jump red lights (and I'm not talking about right turn on red - these are mainly left over busy intersections) and I quickly realised it is because of the lack or red light cameras.
I understand that some states in the US belive these aren't legal - I don't understand why that can be the case you were clearly breaking the law and in many cases intentionally doing it. What is unconstitutional about getting caught by a device rather than a policeman ?
This is my stock answer for why static linking is a bad idea it is written with Solaris in mind but applies equally well to an UNIX like system and to Windows systems as well.
Static linking reduces the overhead when the program is started up, mainly because relocations and some other start-up activities are done at compile time.
However, static linking is generally discouraged. Here are some reasons :
Static linking prevents libc_psr.so.1 from working for platform specifics. This library automatically enables dynamically linked programs from linking in platform specific versions of various library routines which are optimized for a particular platform.
Static linking greatly increases working set size and disk footprint.
Statically linked executables are NOT necessarily binary compatible between releases - the Sun Application Binary Guarantee does not apply to statically linked programs.
eg. statically linked programs that use libsocket will failed if compiled on 2.5.1 or less and run on 2.6 or later.
Patches to system libaries for bug fixes and performance enhancements are not automatically picked up by the application. This is most important for library based security fixes.
Some debugging libraries/tools will fail to work properly.
eg. malloc debugging.
Localistation via setlocale(3c) / gettext(3c) is not supported when libc is statically linked.
When to use static linking
The binary is critical to system operation when in single user-mode either for the startup of the OS or for disaster recovery.
Statically linking a private (internal) libarary is okay.
Don'ts
Statically link against libc
Statically link against libdl
I have a PSX -> USB adaptor so making a USB -> PSX shouldn't be too hard...
My adaptor and a copy of Bleem is the only way I can play US PSX games without getting my UK PSX chipped.
glibc which is what Linux uses for C runtime is under LGPL not GPL. LGPL specifically allows the linking. The virtualdub code being used in the Vidomi case is under GPL not LGPL.
Interesting since for me Netscape 4.x was rendering it properly and IE (what ever is included in WindowsME) was showing it all in italics !
The only proof that there was classified data on the laptop is the media reports. Don't trust everything you read in the media.
The other thing to note is the classification scheme has a class called "unclassfied" which means that the data doesn't contain anything sensitive but it is still classified in the scheme
There is already an "Open" standard in development by the IMPP working group at IETF.
;-)).
And whats more if you look at the authors on the drafts then you will clearly seem Microsoft listed.
I know a lot of people here like to bash Microsoft of keeping stuff to themselves but with IM they are playing the game (or should that be GAIM
Actually software is generally not sold as a product, you normally only get a license to use.
You haven't understood the article. In the case of Linux, Linus is not liable because he as no on going control of what the user actually does with the product. That is the clear and simple distinction between a Service like Napster and a Product like the Linux Kernel.
When encryption is outlawed only the countries that really have free speech will have it not the one that thinks it does ;-)
All fine except that the source for most versions of PGP is available for viewing.