Any statements in this release about future expectations, plans and prospects for the company, including our expectations regarding the future financial performance of the company and other statements containing the words "believes," "anticipates," "plans," "expects," "will" and similar expressions, constitute forward-looking statements within the meaning of the Private Securities Litigation Reform Act of 1995. There are a number of important factors that could cause actual results to differ materially from those indicated by such forward-looking statements. Such factors include: we have a history of operating losses, and we may incur losses in the future; a significant portion of our revenues are derived from a single customer, and a reduction in business with this customer could adversely affect our operating results; adverse changes in domestic and global economic conditions could adversely affect our operating results; changes in exchange rates could adversely affect our results from operations; our common stock may experience extreme market price and volume fluctuations, which may prevent our stockholders from selling our common stock at a profit and could lead to costly litigation against us that could divert our management’s attention; if we fail to implement our business strategy, our financial performance and our growth could be materially and adversely affected; we may not realize all of the sales expected from our backlog of orders and contracts; many of our revenue opportunities are dependent upon subcontractors and other business collaborators, and a reduction in orders stemming from these companies could adversely affect our operating results; our products face intense competition, which could limit our ability to acquire or retain customers; our success is dependent upon attracting and retaining qualified personnel and our inability to do so could significantly damage our business and prospects; and our international operations are subject to risks that we do not face in the U.S., which could have an adverse effect on our operating results. Reference is made to these and other factors discussed in the "Risk Factors" section of the company's most recent quarterly or annual report filed with the Securities and Exchange Commission. In addition, any forward-looking statements included in this press release represent the company's views as of the date of this release. While the company anticipates that subsequent events and developments may cause the company's views to change, the company specifically disclaims any obligation to update these forward-looking statements. These forward-looking statements should not be relied upon as representing the company's views as of any date subsequent to the date this press release is issued.
I have no issue with the police tailing people by whatever means.
I have an issue with the police adding extra weight to my car without me knowing. I have an issue with the police adding electrical equipment to my car without me knowing. I have an issue with police adding radio equipment to my car without me knowing.
I have an issue with the police doing anything to my private property that I haven't approved of, and a judge hasn't approved of, ESPECIALLY since I don't even have to be a suspect.
I'd just like to add my two cents in here. If you are writing a quick and dirty one time script, go nuts with your regex. If your writing something that is going to be used long term, please for the sake of the maintainers just use string functions.
It is a hell of a lot easier to redo one string function than redo a complete regex when the data format changes. Also if you use string functions you can actually do real error reporting when things don't work the way you expect them to.
-Yes the blister packs require a knife or scissors to open. -Yes it is annoying. -Yes if you are clumsy or not paying attention or just plain dumb you might cut yourself or damage the product.
If you screw up, perhaps next time you will be more careful. Consider it a life lesson.
Perhaps huge companies still use Redhat and Novell just for the name, however all of the linux sysadmins I know for smaller companies prefer ubuntu hands down.
Does this explain all the bullshit slashdot articles about cloud this and grid that? I hope this turns into microsoft bob 2.0.
If you run a business, you have to know DAMN well that your data is:
1) private and secure 3) available to your apps 4) backed up
How can you do that if your data is "in the cloud"? The SLA isn't worth the paper that it is written on if your business goes down for a week because something went wrong with "the cloud".
"Good way to be instantly undercut by cheaper labor."
That is not always very easy for the company.
-Perhaps you were the cheap labor, and everyone else costs more -Perhaps there is a time crunch on a project, and the company doesn't have time to hire and train new people -Perhaps you were an asset to the company, aka human capital
If someone else is willing and able to do your job for less money, why hasn't the company hired them already? Responses to the idea of unionizing any industry along the lines of "Just deal with it", or "someone else will take your job" are not valid responses.
Also, I'd like to add that my arguments stand regardless of the threat of outsourcing. If outsourcing is so great, and so inexpensive, why hasn't the company done it already? Further more, while programming jobs can be easily outsourced, other IT jobs like system administration can not be.
As far as not interrupting work, email is better than any other medium because I can choose when to read the message. That is not true if someone calls me, or walks into my cube.
As a sysadmin who is part of a small team that "holds the keys", I find your comment interesting. In most organizations, you don't have to specifically plan for a "hit by a bus test", because it happens all on its own. Don't your employee's take vacations? Don't they ever call in sick? If your employee's have to call the guy on vacation, that is a HUGE HUGE HUGE indicator that there is a problem.
I understand your logic, however I question the reality that a musician would be able to tell any difference. I honestly think its more of a placebo affect. Until I see a scientific study (not from a vendor that selling the crap), I will fail to be convinced of any value.
Now things like lots of channels, or offloading work to the sound card, those things I wont argue against.
I would suggest starting to correlate service failures with denied IT proposals. If you can start to do that, you have a valid point. If you can't, then the management is correct, and you are asking for things you don't need.
1) Listen to the request 2) Politely say, "Sorry but I'm terribly busy at the moment, please email me and I will respond ASAP".
If you do this:
1) You spend less face time with problem users 2) Some users will get in the habit of emailing, which is nice 3) You will have a record of the requests and responses 4) You will work more efficiently because you don't stop working on your current task every time a new task pops in the queue
I've read its possible to get it to work, but it doesn't work out of the box with a standard VNC client. That kind of goes against apples "it just works" philosophy.
The three xServes I've worked on over the years on 2 different KVMs have worked just fine- in fact, better than the HP rackmount gear- this includes high-end Raritan stuff and low-end "iogear" stuff. Maybe you have a crappy KVM, or you haven't configured it properly.
It's possible. On my KVM I have two lights for each computer, one for "is it present", and another for "this is the one selected". Attaching the XServe to my KVM does not make the first light activate, even though it should. I've tested this against known good working ports, with known good working cables...
Then stop whining and fix the problem, chief. Wipe the box and reinstall with a restore (easy to do with Time Machine) and then if that doesn't work, call Apple and have the machine serviced.
So your solution to software bugs is to reinstall the OS? It sounds to me like you have spent too much time maintaining Windows machines.
"You can get a standard VNC client to connect to the built-in VNC server that ships with OSX. It takes some very specific settings, but it can be done. I've done it using TightVNC and UltraVNC on Windows before I finally switched to a Mac on the client side. If you Google around a bit, you should be able to find them."
I'm trying to connect from an Ubuntu machine. I tried for about a day before I gave up. You don't happen to have a link handy do you?
I administer an apple x server at work, and I haven't been impressed.
I'm running ubuntu on a PC, so I can't use the server admin, or workgroup manager tools. Also, apple doesn't come with a standard VNC server, instead it uses VNC with some proprietary shit built in, so I had to install vine server to get a remote desktop. Of course, vine server sucks as well, because I can't get it to start on boot, without logging into the server with either the native server admin tools, or locally with a KVM. Oh wait, the X Serve doesn't play nice with a standard KVM. I have an extra mouse and keyboard setting in my rack just for the X Serve.
Once you manage to get in the damn thing, if you have any sort of complicated setup at all, you simply CAN'T DO it using the server admin tool. I've usually had to bust into the config files just like any other Unix system. Take a look at the SQL section of the Server Admin tool, its a fucking joke. Also, even if you do start to do some things by hand, shit still doesn't work right.
The mailing list / blog / colander stuff is also less than impressive. Why the FUCK should I have to wait 15 minutes for my changes to take affect. It this 1982 or some shit? Some changes seem to take much longer than that as well. I waited a whole day for one of my groups to show up. Why is it that the "recent changes" section of each group shows group emails, even if I turn the mailing list feature off?
Oh yeah, last but not least, the server crashes. It responds to pings, still responds to local terminal input, but anything that requires authentication is dead in the water. So that leaves mail, netbios, ssh, server admin, work group manager, etc etc all dead. I think the LDAP server is crapping out, but I haven't been able to prove it yet. I've had to hard boot the server half a dozen times in the last two weeks.
My last rant. WHAT THE FUCK IS WITH THE QUICK TIME UPDATES, AND THE REQUIRED RESTARTS. Jesus christ, it's like I'm working with windows NT.
I'm also having problems with Leopard. I'm trying to setup a Leopard server as a PDC at work, and the damn thing just doesn't work. The logs are not helpful, are there are no good docs specific to leopard for this software feature. I'll be calling up apple support next week, and if they can't help me get it going, ill be suggesting to my boss that we roll back from leopard.
Slashdot Mirror
Found this on the bottom of the article
Any statements in this release about future expectations, plans and prospects for the company, including our expectations regarding the future financial performance of the company and other statements containing the words "believes," "anticipates," "plans," "expects," "will" and similar expressions, constitute forward-looking statements within the meaning of the Private Securities Litigation Reform Act of 1995. There are a number of important factors that could cause actual results to differ materially from those indicated by such forward-looking statements. Such factors include: we have a history of operating losses, and we may incur losses in the future; a significant portion of our revenues are derived from a single customer, and a reduction in business with this customer could adversely affect our operating results; adverse changes in domestic and global economic conditions could adversely affect our operating results; changes in exchange rates could adversely affect our results from operations; our common stock may experience extreme market price and volume fluctuations, which may prevent our stockholders from selling our common stock at a profit and could lead to costly litigation against us that could divert our management’s attention; if we fail to implement our business strategy, our financial performance and our growth could be materially and adversely affected; we may not realize all of the sales expected from our backlog of orders and contracts; many of our revenue opportunities are dependent upon subcontractors and other business collaborators, and a reduction in orders stemming from these companies could adversely affect our operating results; our products face intense competition, which could limit our ability to acquire or retain customers; our success is dependent upon attracting and retaining qualified personnel and our inability to do so could significantly damage our business and prospects; and our international operations are subject to risks that we do not face in the U.S., which could have an adverse effect on our operating results. Reference is made to these and other factors discussed in the "Risk Factors" section of the company's most recent quarterly or annual report filed with the Securities and Exchange Commission. In addition, any forward-looking statements included in this press release represent the company's views as of the date of this release. While the company anticipates that subsequent events and developments may cause the company's views to change, the company specifically disclaims any obligation to update these forward-looking statements. These forward-looking statements should not be relied upon as representing the company's views as of any date subsequent to the date this press release is issued.
Makes me wonder...
I have no issue with the police tailing people by whatever means.
I have an issue with the police adding extra weight to my car without me knowing.
I have an issue with the police adding electrical equipment to my car without me knowing.
I have an issue with police adding radio equipment to my car without me knowing.
I have an issue with the police doing anything to my private property that I haven't approved of, and a judge hasn't approved of, ESPECIALLY since I don't even have to be a suspect.
If you still want that service just run it over a vpn.
I'd just like to add my two cents in here. If you are writing a quick and dirty one time script, go nuts with your regex. If your writing something that is going to be used long term, please for the sake of the maintainers just use string functions.
It is a hell of a lot easier to redo one string function than redo a complete regex when the data format changes. Also if you use string functions you can actually do real error reporting when things don't work the way you expect them to.
I'd say you are the one dancing around the issue.
-Yes the blister packs require a knife or scissors to open.
-Yes it is annoying.
-Yes if you are clumsy or not paying attention or just plain dumb you might cut yourself or damage the product.
If you screw up, perhaps next time you will be more careful. Consider it a life lesson.
It wasn't a total system lockup then. Also, instead of ssh'ing from another machine if you are using X just press ctl-alt-f1.
Perhaps huge companies still use Redhat and Novell just for the name, however all of the linux sysadmins I know for smaller companies prefer ubuntu hands down.
2 percent off due to human error, and most likely zero percent off tallying error. I betcha that compares pretty damn well to our system.
"cloud storage done right....."
One of the major arguments against it is that you don't know if its done right or not.
Does this explain all the bullshit slashdot articles about cloud this and grid that? I hope this turns into microsoft bob 2.0.
If you run a business, you have to know DAMN well that your data is:
1) private and secure
3) available to your apps
4) backed up
How can you do that if your data is "in the cloud"? The SLA isn't worth the paper that it is written on if your business goes down for a week because something went wrong with "the cloud".
Maybe they could starting fixing the noun-verb vs verb-noun problems instead.
"Good way to be instantly undercut by cheaper labor."
That is not always very easy for the company.
-Perhaps you were the cheap labor, and everyone else costs more
-Perhaps there is a time crunch on a project, and the company doesn't have time to hire and train new people
-Perhaps you were an asset to the company, aka human capital
If someone else is willing and able to do your job for less money, why hasn't the company hired them already? Responses to the idea of unionizing any industry along the lines of "Just deal with it", or "someone else will take your job" are not valid responses.
Also, I'd like to add that my arguments stand regardless of the threat of outsourcing. If outsourcing is so great, and so inexpensive, why hasn't the company done it already? Further more, while programming jobs can be easily outsourced, other IT jobs like system administration can not be.
Ever have someone that sends an email and then calls just to say that they sent an email?
I don't miss that job.
As far as not interrupting work, email is better than any other medium because I can choose when to read the message. That is not true if someone calls me, or walks into my cube.
As a sysadmin who is part of a small team that "holds the keys", I find your comment interesting. In most organizations, you don't have to specifically plan for a "hit by a bus test", because it happens all on its own. Don't your employee's take vacations? Don't they ever call in sick? If your employee's have to call the guy on vacation, that is a HUGE HUGE HUGE indicator that there is a problem.
I understand your logic, however I question the reality that a musician would be able to tell any difference. I honestly think its more of a placebo affect. Until I see a scientific study (not from a vendor that selling the crap), I will fail to be convinced of any value.
Now things like lots of channels, or offloading work to the sound card, those things I wont argue against.
I would suggest starting to correlate service failures with denied IT proposals. If you can start to do that, you have a valid point. If you can't, then the management is correct, and you are asking for things you don't need.
When a problem user comes to you:
1) Listen to the request
2) Politely say, "Sorry but I'm terribly busy at the moment, please email me and I will respond ASAP".
If you do this:
1) You spend less face time with problem users
2) Some users will get in the habit of emailing, which is nice
3) You will have a record of the requests and responses
4) You will work more efficiently because you don't stop working on your current task every time a new task pops in the queue
User: "My computer is broken."
IT: "What's wrong?"
User: "I can't access Myspace"
IT: "We were asked to block it by "
User: "Oh."
"Dtrace ported from Solaris for developers, and a bunch of other dev tools and new APIs"
You mean the broken Dtrace?
http://developers.slashdot.org/article.pl?sid=08/01/22/2156244&from=rss
Oop's I should have previewed, I screwed up some of the html tags.
Xserve, running OS X Server.
My Mistake. I don't have the apple naming conventions down yet.MacOS X Server does in fact come with a standard VNC server. You need to enable it and set a password.
Incorrect.http://www.realvnc.com/pipermail/vnc-list/2006-September/055897.html
I've read its possible to get it to work, but it doesn't work out of the box with a standard VNC client. That kind of goes against apples "it just works" philosophy.
The three xServes I've worked on over the years on 2 different KVMs have worked just fine- in fact, better than the HP rackmount gear- this includes high-end Raritan stuff and low-end "iogear" stuff. Maybe you have a crappy KVM, or you haven't configured it properly.
It's possible. On my KVM I have two lights for each computer, one for "is it present", and another for "this is the one selected". Attaching the XServe to my KVM does not make the first light activate, even though it should. I've tested this against known good working ports, with known good working cables...Then stop whining and fix the problem, chief. Wipe the box and reinstall with a restore (easy to do with Time Machine) and then if that doesn't work, call Apple and have the machine serviced.
So your solution to software bugs is to reinstall the OS? It sounds to me like you have spent too much time maintaining Windows machines."You can get a standard VNC client to connect to the built-in VNC server that ships with OSX. It takes some very specific settings, but it can be done. I've done it using TightVNC and UltraVNC on Windows before I finally switched to a Mac on the client side. If you Google around a bit, you should be able to find them."
I'm trying to connect from an Ubuntu machine. I tried for about a day before I gave up. You don't happen to have a link handy do you?
I administer an apple x server at work, and I haven't been impressed.
I'm running ubuntu on a PC, so I can't use the server admin, or workgroup manager tools. Also, apple doesn't come with a standard VNC server, instead it uses VNC with some proprietary shit built in, so I had to install vine server to get a remote desktop. Of course, vine server sucks as well, because I can't get it to start on boot, without logging into the server with either the native server admin tools, or locally with a KVM. Oh wait, the X Serve doesn't play nice with a standard KVM. I have an extra mouse and keyboard setting in my rack just for the X Serve.
Once you manage to get in the damn thing, if you have any sort of complicated setup at all, you simply CAN'T DO it using the server admin tool. I've usually had to bust into the config files just like any other Unix system. Take a look at the SQL section of the Server Admin tool, its a fucking joke. Also, even if you do start to do some things by hand, shit still doesn't work right.
See one of my bug reports here.
http://macosx.com/forums/mac-os-x-server/298314-samba-shares-hfs-extended-attributes.html
The mailing list / blog / colander stuff is also less than impressive. Why the FUCK should I have to wait 15 minutes for my changes to take affect. It this 1982 or some shit? Some changes seem to take much longer than that as well. I waited a whole day for one of my groups to show up. Why is it that the "recent changes" section of each group shows group emails, even if I turn the mailing list feature off?
Oh yeah, last but not least, the server crashes. It responds to pings, still responds to local terminal input, but anything that requires authentication is dead in the water. So that leaves mail, netbios, ssh, server admin, work group manager, etc etc all dead. I think the LDAP server is crapping out, but I haven't been able to prove it yet. I've had to hard boot the server half a dozen times in the last two weeks.
My last rant. WHAT THE FUCK IS WITH THE QUICK TIME UPDATES, AND THE REQUIRED RESTARTS. Jesus christ, it's like I'm working with windows NT.
I'm also having problems with Leopard. I'm trying to setup a Leopard server as a PDC at work, and the damn thing just doesn't work. The logs are not helpful, are there are no good docs specific to leopard for this software feature. I'll be calling up apple support next week, and if they can't help me get it going, ill be suggesting to my boss that we roll back from leopard.