I have a totally silent fanless/diskless machine at work and it's so quiet that i can hear everyone in the adjoining offices. Kinda like having my laptop for a bit of background noise.
Now it'd be nice to have a silent system at home, but i usually have music on when i'm working so either way it's good.
We simply don't have the bandwith right now to do everything over wireless. The only way we're ever likely the have the bandwidth we need is to keep moving into even higher frequency ranges.
Unfortunately as the frequency goes up the signal is less likely to bend around obstaces and work well indoors.
Plus new wire research can have implications for long distance carriers and short connections inside your computer, since those things cant really go wireless either.
A nice intelligent choice with WinNT was the "Press Alt-Ctl-Delete" to login.
Since applications shouldn't be able to hijack that combination it adds additionaly security.
You can have a lot of fun with micking login boxes. Back when I was in uni we'd screw around with each others laptops. I got a terminal window on a friends machine and aliaed the su command to a perl script which would prompt for a password, send the password to my webserver, tell the user it was wrong, and then unalis the command so the next try would go to the real su.
Easy to do, but you'd have to be very on top of things to spot it.
But JDS2 is available on Linux and i'm sure that JDS3 will be out shortly.
I'm not sure how the driver question is even an issue. Perhaps for home users tinkering with solaris, but if you are buying thousands of desktops for an enterprise deployment then you buy hardware that works with the OS you want to use.
In the enterprise the goals are entirely different.
Installation doesn't need to be graphical, it should be as automated as humanly possible. In the proper environment you can install solaris using nothing but the network and bios.
Applications should be updated remotely (or launch from a netmount), users shouldn't be installing/uninstalling or you'll create a support nightmare.
Enterprise linux seems a whole lot closer than desktop linux, and they aren't the same.
It is not an operating system and strangely enough you can use JDS on top of both linux and solaris. Which make pretty good sense since end users probably can't tell the different between the two OSs.
I'm not certain, but i thought intels HT processors still only had one execution unit. They just have two fetch and decode processes and fast context switching between them.
Sure this 8 core chip won't be good for everything. But when you've got a lot of similar processes in some server environment then it should do very well.
I've got employment in multiple countries, different residency statuses, a change in martial status, interest from investments in multiple countries, profit from my own business... i'll be filing 20-30 pages this year, though h&r block taxcut is worth the $20 to me.
Yeah only yesterday did i find a way to get KDE running at work. For the last 18 months i've been doing my day to day work on gnome and found it really cumbersome. Not windows cumbersome, but still denting my productivity.
I find gnomes load/save dialogs to be far less efficient that KDE's. In any kde app i can open up files on remote servers using fish://servername.domain and it does magic with ssh.
Kate and cervisia are both really cool. I can't even find a syntax highlighting editor as standard in my employers gnome distro.
Admittedly their gnome distro seems pretty old to me, but i'm running kde 3.1 which i'm sure is equally dated.
I've always thought i was the logical analytical type... but who knows.
Also kde seems like a dream to develop for. KDevelop is probably the best OS ide i've seen (maybe eclipse is slightly ahead) and the kde apis are incredibly clean and well thought out. My brief adventures with developing gnome stuff suggest it's not the same.
All the phones my wife and I have had with t-mobile in the last 3 years have had it.
However i had a verizon phone before that which could only text message on certain networks.
It's been a feature of GSM networks since they were created in the early 90s (iirc) but some US networks were pretty slow to catch on. Perhaps there's something cultural about europe where people don't like to talk in lots of places... resturants in the US certainly don't seem out of bounds:(
In most of europe cellphones are essentially premuim rate numbers. Unlike the US where the cellphone holder pays for every minute, europeans place the cost burden on the person making the call.
Typically these rates aren't too bad, but when you start calling from one network to another they can get VERY high. In the UK I would pay close to 1$US/minute to call from orange -> tmobile.
Text messages are generally very cheap and practical. Plus they are better for communicating certain types of information since you have a record of it. Not to mention the privacy issue of being able to text when you are in a meeting at work or in a resturant.
On top of that you can IM with people on their computers.
Radiation drops off in some sort of inverse cubed relationship, so unless you are right next to a transmitter it's going to have very little effect on you.
Holding a cellphone an inch from your brain is way worse than being 40ft from a tower.
Slashdot Mirror
In both cases the answer is probably "a dead version" :)
I have a totally silent fanless/diskless machine at work and it's so quiet that i can hear everyone in the adjoining offices. Kinda like having my laptop for a bit of background noise.
Now it'd be nice to have a silent system at home, but i usually have music on when i'm working so either way it's good.
I've only got 256mb of ram on my laptop and kde 3.3 is perfectly usable.
Gets a little sluggish if i fire up eclipse, but it's still usable.
We simply don't have the bandwith right now to do everything over wireless. The only way we're ever likely the have the bandwidth we need is to keep moving into even higher frequency ranges.
Unfortunately as the frequency goes up the signal is less likely to bend around obstaces and work well indoors.
Plus new wire research can have implications for long distance carriers and short connections inside your computer, since those things cant really go wireless either.
If you could identify the company that was calling you it'd be lots of fun to reroute their calls back to their inbound sales lines :)
Tie up two of their people talking to each other while they figure it out.
Very true.
But bear in mind that this does mean that any userspace remote shell exploit can now be turned into a root exploit.
But a malicious hacker could alias both /bin/su and su leaving cautious users vulnerable.
I just tried
/bin/su="echo you suck"
alias
and it hurt my feelings
I said that it "shouldn't" be possible.
Just because it wasn't well implemented doesn't make it a bad idea.
A nice intelligent choice with WinNT was the "Press Alt-Ctl-Delete" to login.
Since applications shouldn't be able to hijack that combination it adds additionaly security.
You can have a lot of fun with micking login boxes. Back when I was in uni we'd screw around with each others laptops. I got a terminal window on a friends machine and aliaed the su command to a perl script which would prompt for a password, send the password to my webserver, tell the user it was wrong, and then unalis the command so the next try would go to the real su.
Easy to do, but you'd have to be very on top of things to spot it.
But JDS2 is available on Linux and i'm sure that JDS3 will be out shortly.
I'm not sure how the driver question is even an issue. Perhaps for home users tinkering with solaris, but if you are buying thousands of desktops for an enterprise deployment then you buy hardware that works with the OS you want to use.
In the enterprise the goals are entirely different.
Installation doesn't need to be graphical, it should be as automated as humanly possible. In the proper environment you can install solaris using nothing but the network and bios.
Applications should be updated remotely (or launch from a netmount), users shouldn't be installing/uninstalling or you'll create a support nightmare.
Enterprise linux seems a whole lot closer than desktop linux, and they aren't the same.
JDS is a DESKTOP... it's a gnome variant.
It is not an operating system and strangely enough you can use JDS on top of both linux and solaris. Which make pretty good sense since end users probably can't tell the different between the two OSs.
I'm not certain, but i thought intels HT processors still only had one execution unit. They just have two fetch and decode processes and fast context switching between them.
Sure this 8 core chip won't be good for everything. But when you've got a lot of similar processes in some server environment then it should do very well.
But i think they are leading the industry (in sales at least) of small desktop machines.
It's always nice when that happens :)
You'll have to spim me to death before i'll add another pointless word to the english language :)
Does sound pretty cool in french sentances, but NO.
It's trivially easy to remove the tivo drm and playback on linux. I'm sure a nicely packaged utility will come out for doing it soon.
Sounds good for you.
I've got employment in multiple countries, different residency statuses, a change in martial status, interest from investments in multiple countries, profit from my own business... i'll be filing 20-30 pages this year, though h&r block taxcut is worth the $20 to me.
Thanks, i'll give that a shot next time i'm using gnome.
Yeah only yesterday did i find a way to get KDE running at work. For the last 18 months i've been doing my day to day work on gnome and found it really cumbersome. Not windows cumbersome, but still denting my productivity.
I find gnomes load/save dialogs to be far less efficient that KDE's. In any kde app i can open up files on remote servers using fish://servername.domain and it does magic with ssh.
Kate and cervisia are both really cool. I can't even find a syntax highlighting editor as standard in my employers gnome distro.
Admittedly their gnome distro seems pretty old to me, but i'm running kde 3.1 which i'm sure is equally dated.
I've always thought i was the logical analytical type... but who knows.
Also kde seems like a dream to develop for. KDevelop is probably the best OS ide i've seen (maybe eclipse is slightly ahead) and the kde apis are incredibly clean and well thought out. My brief adventures with developing gnome stuff suggest it's not the same.
I'd have to concur.
My employer defaults to a gnome desktop as did my university, and i've run kde on all my own systems.
It may just be a preference, but i find i'm a lot more productive on a kde system than a gnome one.
All the phones my wife and I have had with t-mobile in the last 3 years have had it.
:(
However i had a verizon phone before that which could only text message on certain networks.
It's been a feature of GSM networks since they were created in the early 90s (iirc) but some US networks were pretty slow to catch on. Perhaps there's something cultural about europe where people don't like to talk in lots of places... resturants in the US certainly don't seem out of bounds
In most of europe cellphones are essentially premuim rate numbers. Unlike the US where the cellphone holder pays for every minute, europeans place the cost burden on the person making the call.
Typically these rates aren't too bad, but when you start calling from one network to another they can get VERY high. In the UK I would pay close to 1$US/minute to call from orange -> tmobile.
Text messages are generally very cheap and practical. Plus they are better for communicating certain types of information since you have a record of it. Not to mention the privacy issue of being able to text when you are in a meeting at work or in a resturant.
On top of that you can IM with people on their computers.
Radiation drops off in some sort of inverse cubed relationship, so unless you are right next to a transmitter it's going to have very little effect on you.
Holding a cellphone an inch from your brain is way worse than being 40ft from a tower.