On the whole I think yours is a good scheme, albeit with some tweaking.
- ISO standard Country codes (3 characters)
What's wrong with 2 Character ISO standard Country codes? I live in the UK, and no one over here associates themselves with GBR. You might on the very odd occasion see that on a car sticker, no where else.
- Site number within country (1 digit, we only need one)
Good idea, but you should use 2 in case your company ever grows. 10 offices nationally isn't very much.
- O/S NT based, LX based, MC based, A4 for AS/400
Not necessary. I've dealt with hundreds of corporate customers over the past couple of decades and have never seen one where the OS type is reflected in the hostname.
Having said that, I've just scanned back over most of the customer hostnames I've had to connect to over the past decade or so (I have a list) and most of them seem to start with either a contraction of the company name, site name, or function name.
His point about a clean code base is that it lowers the bar for new developers to join the project. By comparison, OOo internals are supposed to be a nightmare maze of twisty little passages and difficult to learn.
This was the reason why Apple originally chose KDE's KHTML source code over Mozilla's Gecko. Clean, lean, code that was easy to understand, debug and extend. The fruits of that we see today in Safari and Webkit.
Hacker sites also publish instructions for a "do-it-yourself GPS jammer that can have a range of up to several hundred feet. Keep in mind this is not an easy hack; a bachelor's in electrical engineering seems like a prerequisite." The parts can be obtained at shopping-mall electronics retailers.
Why would anyone want to do that on such a large scale? That's just being nasty. I seriously hope that anyone who gets caught using such a device gets a mandatory prison sentence. After all, if you're belting out that kind of power, you're gonna be easy to track and locate.
Spot on. If you download the sources, there's a README file in the advfs_gen3_src_v1 directory that says: This directory includes the source code for a second generation implementation of AdvFS, including the kernel modules, commands and utilities.
This is the code that was ported to HP-UX. It is functionally complete and went through fairly extensive functional and stress testing. However, it should be considered beta quality and so you may spot bugs. It is recommended that you review the design documentation which is also available at this site as it will guide you through the major subsystems.
This code will not build on HP-UX because it requires a specialized build environment. HP-UX users are discouraged from attempting to build or use this code on HP-UX as it will not be supported by HP.
So it made the port ok. But it was a very lucrative deal between HP and Veritas over VxFS and their Cluster Silesystem that killed it. Money talks, and Veritas must've been crapping themselves that HP were about to walk away in favour of something better and home grown.
Though why anyone would want to use Veritas Cluster Filesystem considering the whopping price tag that comes with it, is beyond me.
It doesn't have the Merkle tree and the associated error-detection properties of ZFS though.
Also, AdvFS (or PolyFS, as I could swear it was called in the beginning - though Google can't seem to any record of it) had a pretty bad reliability record in its earlier days, at least bad enough that its unreliability still was mentioned in DEC Open Systems Support when I visited there in 2000.. (by which stage Tru64 clearly was on life-support).;)
It was pretty flakey around Tru64 v4, but got a major re-write for Tru64 v5 which cleared up the problems and made it very stable after that. Today, it's the most stable filesystem I've ever used. And you're right about the Poly stuff. There was a marketing drive which fortunately didn't last very long where they tried to brand it as the Polyserve filesystem, then it got changed. Even Polyserve was an improvement on its birth name, the MegaSafe Filesystem. You can still see remnants of that in the Tru64 kernel config file: its the options MSFS line that triggers inclusion of AdvFS into the kernel. The word MegaSafe also crops up all over the source tree too. Go take a look;-)
Ah, now I understand what you meant. I just SSH'd into a headless Mac Mini I have and tried it. It kicks out the message:
pebbles: ~ $ osascript -e 'tell app "ARDAgent" to do shell script "whoami"' _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
Then after a timeout delay it returns with an error:
23:47: execution error: ARDAgent got an error: Connection is invalid. (-609)
So someone has to be logged into the Desktop at the same time the command is issued (even if issued remotely) and I'm guessing that the account the remote user is logged into probably has to be the same account the desktop user is using.
So Xserve servers should be immune to this via SSH, unless someone else is actively using Remote Desktop at the same time. Interesting!
You can do this either by logging in normally and opening up a Terminal window to get a shell prompt; or by logging in remotely using remote desktop & opening a Terminal window to get a shell prompt; or by logging in remotely using SSH to get a shell prompt.
The latter doesn't need any desktop login on OS X at all. Could be done from a Linux box, or even a Windows box using Putty. Providing "remote login" is enabled in System Prefs on the Mac of cause and the remote user has access to a local account.
I used to work in Unix Support for a large multi-national. Had loads of customers ring in with cock ups over the years. Some of them were silly, like a developer with root access typing rogue spaces where they shouldn't be. e.g: "chmod -R me / foobar". Conversations always started like "OMG I own the whole system, HELP!". Others were more obtuse, like a world renowned news reporting organisation who allowed one of their developers to install a very important database in his own account. System management got outsourced to Singapore, he then left the company, so Singapore deleted his account. We were left trying to reconstruct was was left from a dd image copy of the disk.
Another one I remember (about 20 years ago) was where one customer had systems that would crash at about 10am every monday morning. After a very long trouble shooting experience (i.e. months) the cause was found to be a delivery lorry that arrived every monday morning. He would back up to the loading bay, where some rubber bumpers (fenders) had been installed. He had the habit of stopping the lorry when he banged into the bumpers. Unfortunately this sent a shock wave through the building sufficient to cause some of the disks in the computer room throw a hissy fit and park their heads in the middle of whatever I/O they were doing.
In the early 90's I found myself having to pick up SCO Unix support for my sin's. Thankfully it only lasted 4 years. Two specific customer incidents I remember from that time. One was a call from a hospital who's system seemed in a right state. The guy was panicing, so I cut short my usual trouble shooting routine, got in the car and drove down there. Took one look at the system, typed ^D and then left after it'd finished booting to multi-user. Taught me a lesson; embarrassed the hell out of the customer and I never heard from him again.
The second was more interesting. I had a customer in the MoD at HMS Dolphin in Gosport. A number of their systems would crash simultaneously at certain times during the week. There was no real pattern to when, but when one of them went, they all did. I couldn't find the problem. No common denominators. Power monitors didn't show anything. Nothing. That was until one day the customer was staring out the window when the systems crashed. He remembered seeing one of the warships leaving the harbor and sailing right past his window. He also remembered seeing the ship starting its RADAR as it went past; and as the beam swept the computer room, all the systems crashed. The fix: a snotty email dictating that captains don't start their radar until they've cleared the harbor and made it out to sea.
I could go on typing for another hour straight with stories like this that either I've seen, or have happened to friends/colleagues:-)
The court's ruling makes clear the legal rights given to al Qaida members today should exceed those provided to the Nazis during World War II," Graham said. "Our nation is at war. It's truly unfortunate the Supreme Court did not recognize and appreciate that fact."
The two scenarios are completely different. During the 2nd World War is was blinding obvious who the enemy was, as a few million of them wore distinctive uniforms and pointed guns at you. In Iraq however most look exactly the same as the civilians. So who is he, or anyone else to decide who is and who is not an Al Qaida member without some form of unbiased review of the evidence? That's the whole point of giving them the right to trial.
With out a doubt some of the detainees are Al Qaida. But it's also very clear from the testimonies of many who've been detained without charge for years before being released without explanation, that many are also not Al Qaida; were not involved in any military action, and should never have been sent there in the first place.
Given that the U.S. military and government are not prepared to give these people fair justice. A court of law is totally the right choice in a modern, civilized western world.
Not to disagree with you, just wanted to point out that this law is not popular in Britain
Funny that, but watching the TV news a couple of days ago (I think it was Channel 4) a report pointed to polls performed by he newpapers that collectively returned a ~65% majority vote in favour by the british public.
I don't agree with this law either. But you and I are clearly in the minority.
I too moved from Linux & Windows Desktops to Mac OS X some years ago. Now while I love working with OS X, you know what I miss the most? Being able to ssh into one of my Macs and fire up a single application I want to work on while directing the display for that app back to my desktop.
Instead I have to do a full remote desktop login to the box hosting the app I want, just like in the Windows world. It's a waste of time, resources and network bandwidth. And compared to displaying single app as X does, it's slow.
If anything, Quartz needs to take a leaf out of X's book, not the other way round.
I've tried playing around with the Eeee PC, and while I can see the appeal, the GUI experience is a bit sucky. Gnome as is, just wasn't designed with a screen that small in mind, and it shows with the amount of real estate consumed by control buttons and what not in proportion to the data.
What's needed is a kind of minimalist mode, where contol buttons and menus don't get in the way, but can be exposed easily and intuitively as they're required. That's going to be a lot of very hard work.
Redoffice 4.0 beta new UI is really intuitive and useful. The "Live Preview" function is great and should definitively be adopted in OOo after 3.0. Though slower than OOo 3.0 beta, RedOffice runs at an acceptable speed on my old harware. I also hope they will release a Linux version soon.
RedOffice shows a possible way OOo could develop in the future. However, the chinese writing is extremely compact and allows RedOffice's exceptional menu structure. It remains doubtfoul that the user interface could be translated in other languages without major changes in its layout.
The screenshots don't really do KDE 4 development justice. Go to Youtube and search for "KDE Commit-Digest". Change the sort order to Date Added and then scan down the list for interesting looking additions.
Plasma Containments, Issue 85 (Parts 1 & 2) are some of my favourites.
I wonder how many people view the Dilbert site from their Phone, and whether they bothered to check their web logs before making this move.
Ever since I got my iPhone last December I've been using it to view Dilbert every morning. Part of my ritual before I get out of bed, to help me wake up. But this new site design has got to be the most mobile unfriendly load of crock I've ever seen.
Someone on the Dilbert forums pointed to the daily comic strip being served up from Yahoo ( http://news.yahoo.com/comics/dilbert ) so I'll be giving that a try instead.
I doubt it'll take much longer for all three to get taken over
Well at the end of day two both the Windows and Ubuntu systems are still unhacked. This is really embarrassing for Apple and quite a worry for OS X users. That includes me BTW as I have 3 x Mac OS X systems.
I'm also pretty sure that the hack wasn't about getting root level access, just access to a user account from outside caused by the user doing something they would normally do on the internet. And the bottom line is that this is how virtually ALL Windows malware finds its way onto PCs. And the user account is where all the juicy data is anyway!
So today, all OS X users can breath a sigh of relief that we're not yet a big enough target for hackers to pay much attention to. Or for sure we'd be in trouble!
I look forward to finding out what the details of this hack were, after Apple have fixed it and the info is released. I wonder if it's got anything to do with some of the dumb choices that Apple make for default OOTB security settings on OS X. Like: "Allow all incoming connections" on the Firewall, and automatically "Open safe files after downloading" in Safari. The latter is particularly stupid. Safe files are only safe until someone finds a way to make them un-safe. Then 90% of your entire user base who don't disable this are screwed! Someone at Apple should get fired for making that decision!
Somehow I doubt that the lack of Java, or any other additional language, browser, etc is going to hinder or limit the explosion of applications available for the iPhone. A year down the road from now your average iPhone user will be drowning in choice.
Those of you who won't buy an iPhone because of this, frankly aren't Apple's target market. And anyone who's been following the iPhone from the start shouldn't be in the least surprised that the iPhone SDK is presented in a gilded cage. Apple have tried to keep a grip of iron on this platform from the start. There's no way they're going to willingly allow people to hack at the guts of the iPhone using tools that Apple can't vet and cleanse in advance. That's life !
You'll just have to wait for the 2.0 jailbreak, and then hack your own apps onto the iPhone that way.
Firmware upgrades are usually bug fixes, not functionality enhancements. The former is like fixing the plumbing because it wasn't built quite right in the first place, and you wouldn't expect to pay for faulty goods. The latter is like adding an extension to the back of your house, and that costs!
It may not be YOUR idea of open source, but it's still open source none the less. And providing it retains relevance on new hardware, it will never die.
Personally I've never used it, but after reading this thread I think I'll fire up VMware and give it a try. I come from an Ultrix & Tru64 background which were/are heavily influenced by BSD, so many of the concepts are familiar to me.
It should be fun. And isn't that what much of Open Source is all about.
You're correct, but you're also missing the point a bit. Until now, spammers have had to rely on human assistance to translate captchas. It doesn't stop them, but it does slow them down somewhat. If spammers develop a software method to reliably translate captchas (and it will only get better over time) then the speed at which they are able to generate successful intrusions will increase, which is worse for everyone else.
So the battle must be fought on as many fronts as possible. And captcha solutions must improve to keep pace with new attacks. The 3-D captcha solution linked to elsewhere on this discussion looks like the best one I've seen to date.
Slashdot Mirror
On the whole I think yours is a good scheme, albeit with some tweaking.
What's wrong with 2 Character ISO standard Country codes? I live in the UK, and no one over here associates themselves with GBR. You might on the very odd occasion see that on a car sticker, no where else.
Good idea, but you should use 2 in case your company ever grows. 10 offices nationally isn't very much.
Not necessary. I've dealt with hundreds of corporate customers over the past couple of decades and have never seen one where the OS type is reflected in the hostname.
Having said that, I've just scanned back over most of the customer hostnames I've had to connect to over the past decade or so (I have a list) and most of them seem to start with either a contraction of the company name, site name, or function name.
His point about a clean code base is that it lowers the bar for new developers to join the project. By comparison, OOo internals are supposed to be a nightmare maze of twisty little passages and difficult to learn.
This was the reason why Apple originally chose KDE's KHTML source code over Mozilla's Gecko. Clean, lean, code that was easy to understand, debug and extend. The fruits of that we see today in Safari and Webkit.
I'm guessing the moron who modded you Offtopic has never heard of Schrodinger's Cat
From TFA:
Why would anyone want to do that on such a large scale? That's just being nasty. I seriously hope that anyone who gets caught using such a device gets a mandatory prison sentence. After all, if you're belting out that kind of power, you're gonna be easy to track and locate.
Spot on. If you download the sources, there's a README file in the advfs_gen3_src_v1 directory that says:
This directory includes the source code for a second generation
implementation of AdvFS, including the kernel modules, commands
and utilities.
This is the code that was ported to HP-UX. It is functionally
complete and went through fairly extensive functional and stress
testing. However, it should be considered beta quality and so
you may spot bugs. It is recommended that you review the
design documentation which is also available at this site
as it will guide you through the major subsystems.
This code will not build on HP-UX because it requires a
specialized build environment. HP-UX users are discouraged
from attempting to build or use this code on HP-UX as it will
not be supported by HP.
So it made the port ok. But it was a very lucrative deal between HP and Veritas over VxFS and their Cluster Silesystem that killed it. Money talks, and Veritas must've been crapping themselves that HP were about to walk away in favour of something better and home grown.
Though why anyone would want to use Veritas Cluster Filesystem considering the whopping price tag that comes with it, is beyond me.
It doesn't have the Merkle tree and the associated error-detection properties of ZFS though.
Also, AdvFS (or PolyFS, as I could swear it was called in the beginning - though Google can't seem to any record of it) had a pretty bad reliability record in its earlier days, at least bad enough that its unreliability still was mentioned in DEC Open Systems Support when I visited there in 2000.. (by which stage Tru64 clearly was on life-support). ;)
It was pretty flakey around Tru64 v4, but got a major re-write for Tru64 v5 which cleared up the problems and made it very stable after that. Today, it's the most stable filesystem I've ever used. And you're right about the Poly stuff. There was a marketing drive which fortunately didn't last very long where they tried to brand it as the Polyserve filesystem, then it got changed. Even Polyserve was an improvement on its birth name, the MegaSafe Filesystem. You can still see remnants of that in the Tru64 kernel config file: its the options MSFS line that triggers inclusion of AdvFS into the kernel. The word MegaSafe also crops up all over the source tree too. Go take a lookSo someone has to be logged into the Desktop at the same time the command is issued (even if issued remotely) and I'm guessing that the account the remote user is logged into probably has to be the same account the desktop user is using.
So Xserve servers should be immune to this via SSH, unless someone else is actively using Remote Desktop at the same time. Interesting!
You can do this either by logging in normally and opening up a Terminal window to get a shell prompt; or by logging in remotely using remote desktop & opening a Terminal window to get a shell prompt; or by logging in remotely using SSH to get a shell prompt.
The latter doesn't need any desktop login on OS X at all. Could be done from a Linux box, or even a Windows box using Putty. Providing "remote login" is enabled in System Prefs on the Mac of cause and the remote user has access to a local account.
Your Manager wouldn't happen to be the PHB from Dilbert would he?
I used to work in Unix Support for a large multi-national. Had loads of customers ring in with cock ups over the years. Some of them were silly, like a developer with root access typing rogue spaces where they shouldn't be. e.g: "chmod -R me / foobar". Conversations always started like "OMG I own the whole system, HELP!". Others were more obtuse, like a world renowned news reporting organisation who allowed one of their developers to install a very important database in his own account. System management got outsourced to Singapore, he then left the company, so Singapore deleted his account. We were left trying to reconstruct was was left from a dd image copy of the disk.
:-)
Another one I remember (about 20 years ago) was where one customer had systems that would crash at about 10am every monday morning. After a very long trouble shooting experience (i.e. months) the cause was found to be a delivery lorry that arrived every monday morning. He would back up to the loading bay, where some rubber bumpers (fenders) had been installed. He had the habit of stopping the lorry when he banged into the bumpers. Unfortunately this sent a shock wave through the building sufficient to cause some of the disks in the computer room throw a hissy fit and park their heads in the middle of whatever I/O they were doing.
In the early 90's I found myself having to pick up SCO Unix support for my sin's. Thankfully it only lasted 4 years. Two specific customer incidents I remember from that time. One was a call from a hospital who's system seemed in a right state. The guy was panicing, so I cut short my usual trouble shooting routine, got in the car and drove down there. Took one look at the system, typed ^D and then left after it'd finished booting to multi-user. Taught me a lesson; embarrassed the hell out of the customer and I never heard from him again.
The second was more interesting. I had a customer in the MoD at HMS Dolphin in Gosport. A number of their systems would crash simultaneously at certain times during the week. There was no real pattern to when, but when one of them went, they all did. I couldn't find the problem. No common denominators. Power monitors didn't show anything. Nothing. That was until one day the customer was staring out the window when the systems crashed. He remembered seeing one of the warships leaving the harbor and sailing right past his window. He also remembered seeing the ship starting its RADAR as it went past; and as the beam swept the computer room, all the systems crashed. The fix: a snotty email dictating that captains don't start their radar until they've cleared the harbor and made it out to sea.
I could go on typing for another hour straight with stories like this that either I've seen, or have happened to friends/colleagues
With out a doubt some of the detainees are Al Qaida. But it's also very clear from the testimonies of many who've been detained without charge for years before being released without explanation, that many are also not Al Qaida; were not involved in any military action, and should never have been sent there in the first place.
Given that the U.S. military and government are not prepared to give these people fair justice. A court of law is totally the right choice in a modern, civilized western world.
I don't agree with this law either. But you and I are clearly in the minority.
I too moved from Linux & Windows Desktops to Mac OS X some years ago. Now while I love working with OS X, you know what I miss the most? Being able to ssh into one of my Macs and fire up a single application I want to work on while directing the display for that app back to my desktop.
Instead I have to do a full remote desktop login to the box hosting the app I want, just like in the Windows world. It's a waste of time, resources and network bandwidth. And compared to displaying single app as X does, it's slow.
If anything, Quartz needs to take a leaf out of X's book, not the other way round.
I've tried playing around with the Eeee PC, and while I can see the appeal, the GUI experience is a bit sucky. Gnome as is, just wasn't designed with a screen that small in mind, and it shows with the amount of real estate consumed by control buttons and what not in proportion to the data.
What's needed is a kind of minimalist mode, where contol buttons and menus don't get in the way, but can be exposed easily and intuitively as they're required. That's going to be a lot of very hard work.
The screenshots don't really do KDE 4 development justice. Go to Youtube and search for "KDE Commit-Digest". Change the sort order to Date Added and then scan down the list for interesting looking additions.
Plasma Containments, Issue 85 (Parts 1 & 2) are some of my favourites.
Aren't you asking in the wrong place? Why would anyone who's made a successful career break from IT be hanging around on Slashdot?
From what I can tell its dick heads like you that don't like what's on offer who should STFU and go do your own coding.
I wonder how many people view the Dilbert site from their Phone, and whether they bothered to check their web logs before making this move.
Ever since I got my iPhone last December I've been using it to view Dilbert every morning. Part of my ritual before I get out of bed, to help me wake up. But this new site design has got to be the most mobile unfriendly load of crock I've ever seen.
Someone on the Dilbert forums pointed to the daily comic strip being served up from Yahoo ( http://news.yahoo.com/comics/dilbert ) so I'll be giving that a try instead.
I'm also pretty sure that the hack wasn't about getting root level access, just access to a user account from outside caused by the user doing something they would normally do on the internet. And the bottom line is that this is how virtually ALL Windows malware finds its way onto PCs. And the user account is where all the juicy data is anyway!
So today, all OS X users can breath a sigh of relief that we're not yet a big enough target for hackers to pay much attention to. Or for sure we'd be in trouble!
I look forward to finding out what the details of this hack were, after Apple have fixed it and the info is released. I wonder if it's got anything to do with some of the dumb choices that Apple make for default OOTB security settings on OS X. Like: "Allow all incoming connections" on the Firewall, and automatically "Open safe files after downloading" in Safari. The latter is particularly stupid. Safe files are only safe until someone finds a way to make them un-safe. Then 90% of your entire user base who don't disable this are screwed! Someone at Apple should get fired for making that decision!
Somehow I doubt that the lack of Java, or any other additional language, browser, etc is going to hinder or limit the explosion of applications available for the iPhone. A year down the road from now your average iPhone user will be drowning in choice.
Those of you who won't buy an iPhone because of this, frankly aren't Apple's target market. And anyone who's been following the iPhone from the start shouldn't be in the least surprised that the iPhone SDK is presented in a gilded cage. Apple have tried to keep a grip of iron on this platform from the start. There's no way they're going to willingly allow people to hack at the guts of the iPhone using tools that Apple can't vet and cleanse in advance. That's life !
You'll just have to wait for the 2.0 jailbreak, and then hack your own apps onto the iPhone that way.
Firmware upgrades are usually bug fixes, not functionality enhancements. The former is like fixing the plumbing because it wasn't built quite right in the first place, and you wouldn't expect to pay for faulty goods. The latter is like adding an extension to the back of your house, and that costs!
It may not be YOUR idea of open source, but it's still open source none the less. And providing it retains relevance on new hardware, it will never die.
Personally I've never used it, but after reading this thread I think I'll fire up VMware and give it a try. I come from an Ultrix & Tru64 background which were/are heavily influenced by BSD, so many of the concepts are familiar to me.
It should be fun. And isn't that what much of Open Source is all about.
LOL
You're correct, but you're also missing the point a bit. Until now, spammers have had to rely on human assistance to translate captchas. It doesn't stop them, but it does slow them down somewhat. If spammers develop a software method to reliably translate captchas (and it will only get better over time) then the speed at which they are able to generate successful intrusions will increase, which is worse for everyone else.
So the battle must be fought on as many fronts as possible. And captcha solutions must improve to keep pace with new attacks. The 3-D captcha solution linked to elsewhere on this discussion looks like the best one I've seen to date.