No, that would be calling amatuer hour on my employers.
But I think they'd promptly tell you that they design software and hardware for robots, and to get a girlfriend because you must be coming from a bad place if you have to put people down all the time.
Considering some modernized Japanese toilets include a scented deodoriser, a button for the bidet pressure, air dryer, and have a control panel that wouldn't look out of place in Star Trek,... it's only a matter or time.
Ok, but maybe your bosses are PHBs who don't care if you load the server down with X windows and Gnome. My bosses are senior UNIX geeks with a bankload of experience and the whole O'reilly library at hand.
They want me to do a pile of different servers, starting with a minimal install and then rebuild functionality as needed manually with the rpm command, as well as custom tuning of those packages. We are talking geeky installs here.
If you're just doing the manual anaconda graphical install, that's makes it all pretty damn simple. And I'm sure you could install RedHat easily on twenty thousand servers pretty damn easily if you use a kickstart file, and have a powerful FTP server available to handle the beating it's going to get.
But OK, right. I'm the amateur, what would I know?
I was trying to discuss support issues between hardware and Linux distributions. Not necessary my customer's subjective preference for Debian and apt-get in this case.
And obviously, you have never experienced RPM dependancy hell during an enterprise level install, where documentation creation outlining the install steps is also required.
At the moment in my place of employment, we want to run Debian on some custom hardware (but alas, Debian won't work on it - despite many hack attempts), because we just find RPMs too hard to manage and apt-get + aptitude to ge great.
Employing someone to waste time trying to install Debian on something which cannot guarantee a pay off is not fun, and is a waste of money as well for the customer.
The thing is, the hardware vendor doesn't take Debian seriously (because it's not backed by a company with resources), so there is no driver disk or hardware support.
What I am trying to say is this:- there is a niche here that needs to be filled. There is a need for companies with the ability to back Linux distros, even if just for customer peace of mind. They will pay money for it. So far, only RedHat is being taken seriously commercially IMHO.
There is no "swamped" Linux market, or at least, not in my situation as far as I can tell. Only blimmin' RedHat Linux is supported and will install on our blade server.....
Umm... if these batteries recharge really quickly, and discharge slowly - wouldn't it therefore be possible to use the potential energy of a moving car to charge the battery?
Et voila! A perpertual motion machine! (until the battery karks it)
I work as a sysadmin in a freakin Japanese goverment institute with about 4000+ machines in there.
I have to manage not only the systems analysis, but build new systems, upgrade and patch machines, document them, translate announcements to English, handle system events, and write work reports to superiors. And I have to do all that alone, on their schedule.
Basically they replaced a guy with 17 years of experience (who couldn't hack it anymore) with me with only 2 and a bit years experience. Somehow I am coping because I devised some survival strategies.
Basically, Japanese employers are like spoilt children. They demand too much for too little and they want to have everything done yesterday. They also don't care about whatever you feel because they're paying you (a lousy salary) so they don't have to care.
I can see how this would cause certain salarymen to jump in front of trains.
I don't think it's unusual in Japan for people to overwork and stress out like this because of ridiculous work conditions and greedy employers. Chances are you have been given "mission impossible", and so my advice to you is not to stress out. Take your time, and learn to STALL your project to your own schedule.
It's rude in Japan to say "I can't do this", or "I won't be able to make it on schedule" to your employers because it takes away the warm fuzzy feeling you want to give them (which is more important than your techinical ability). NEVER tell them that the project is a complete mess that you just can't do. You will basically have to spin a web of half-truths to keep your head above water.
Japanese are very group oriented, and you can use that to your advantage so you don't have to take individual blame for anything that goes wrong. Learn to share the blame (i.e. "It was a team failure") rather than incriminate yourself for a mistake you made. The Japanese do this all the time themselves.
If you're not making things on time, blame something else and tell them you're "still checking" the situation ("kakuninn chuu" in Japanese). This confuses the Japanese, and they think that you're taking so long to do the job because you are being "thorough" and perfectionist... something the Japanese like. You can almost do this indefinately to stall things. Also blame other external influences and say "shikataganai" (it cannot be helped) to stall things further.
Also, if you appear anal retentive about checking your work out - you'll impress people. As long as you appear like a perfectionist, you can take all the time you want.
It's a fine balance keeping superiors happy, getting the job done, and not stressing out yourself. Good luck.
P2P is banned outright at my government owned institute. First of all, the IT department has an application server set up to detect P2P applications based on the traffic, regardless of what port they are using.
Here is why it's banned:-
(1) It's a security risk. Most of the time people using P2P applications find themselves targets of port scans and other hack attempts. We really don't need this.
(2) The piracy issue. Sure, you can argue for downloading Linux ISOs over BitTorrent, but let's be real here. When you already have some AMAZING bandwidth, downloading ISOs (And Debian as jigdo files) is quick by FTP or HTTP alone. There's nothing research related that can only be found on BitTorrent. Plus, allowing people to host illegal content becomes a liability for the IT department, and we have enough work to deal with.
(3) The network issue. It hammers the network unneccessarily, and if allowed, it would create a chicken and egg situation for the IT department. As soon as we do an upgrade of the network, more people would use P2P to use up the bandwidth - requiring another upgrade, which more people would then max out. It's too expensive to keep doing this, we already have enough switches that need replacing.
Held Windows at gunpoint, danced around with it in front of the authorities, kicked it in the guts a few times, teased everyone by saying "you'll never get me!", and waged a decade-long seige.... a definte YES.
And if they call bad coding "sabotage", well that's an interesting parallel universe they live in then.
If I'm not wrong, the average.sid file for the C64 takes up about 2K of memory.
The sids must have been pretty small to fit on the RFID.
Some interesting Commodore 64 music links:- The HVSID Collection - Which is the main site for the collection of thousands upon thousands of Commodore 64 sid files. Remix.kwed.org Remixes of Commodore 64 tunes with real and modern synthesized instruments.
I have no problem playing with aptitude from their latest unstable Sarge (it's great BTW), but it makes it very hard for me to recommend Debian on servers to customers when the latest stable release is eons old.
Yes, I know there are ways around this... but let's face it, from a customer point of view it's an small image problem Debian has.
Sure, they can ban the sale to minors in order to prevent children buying games with questionable content..........but they can't stop kids getting these games from P2P, and they can't stop their parents buying it for them.
It handles Japanese quite well, only as long as you don't ssh into your Solaris workstation.
If you ssh into Solaris and get the console, you'll find all of the manpages and other Japanese error messages are illegible.
Assuming that raid become common practice in the future of the internet, one may actually be surprised that P2P apps are trying to work their way out of having their owners IP addresses traced.
I was surprised (but really, should I be?) to see these kinds of projects. Check out the MUTE project here.
RIAA Bastards (Sung to the tune of "Radio Ga Ga" by Queen)
I sit alone and watch the lights, on my PC for several nights. And ev'rything I want to load, I find it on the net, you know
You gave us all those boyband stars. Their CD price -- a total farce. You made 'em sing - which made us cry. We just want all those bands to die
RIAA
You'll just become some background noise, suing groups of girls and boys, who just don't know and just don't care, about your new idea of "fair"
You had your time, you've had the power. You're going to have your final hour
RIAA
All we hear is, RIAA bastards, RIAA sue you, RIAA wankers.
All we hear is, RIAA retards, RIAA blah blah
Peer to peer is new. RIAA no one now needs you!
We taped CDs - we dubbed the stars, off radio for hours and hours. Now we swap files amongst our peers, The tech just changes through the years
Let's hope you leave 'cause you're no friend. Like all good things they come to an end. Don't stick around, as we won't miss you. We're growing tired of all your bullshit
You had your time, you've had the power. You're going to have your final hour
RIAA
All we hear is, RIAA bastards, RIAA screw you, RIAA smacktards.
All we hear is, RIAA wankers, RIAA losers, RIAA ha ha.
All we hear is, RIAA retards, RIAA blah blah
Peer to Peer is new. RIAA, no one now needs you!
RIAA bastards, RIAA bastards, RIAA bastards
RIAA
You had your time you've had the power. You're going to have your final hour
RIAA
employers quite like people with language skills for some unknown reason.
They like us because we not only know computer languages, but human languages as well. It shows you also have social skills and the ability to understand people from otherwise completely different ways of thinking. The ability to communicate effectively with other people is important in tricky situations with users, and when working as a sysadmin in a team of engineers as well.
Actually I work in a Japanese research institute which has a lot of foreign researchers, so they need me to make all the bilingual "System maintenance" notice emails.... and to politely deal with foreign researchers when they have problems, and when they've been naughty and tried to use BitTorrent on our network.
Slashdot Mirror
Foregt about creating a work of art out of old machines. Some of these "creations" look very similar to the desk I actually work on every day.
No, that would be calling amatuer hour on my employers.
But I think they'd promptly tell you that they design software and hardware for robots, and to get a girlfriend because you must be coming from a bad place if you have to put people down all the time.
Considering some modernized Japanese toilets include a scented deodoriser, a button for the bidet pressure, air dryer, and have a control panel that wouldn't look out of place in Star Trek,... it's only a matter or time.
Ok, but maybe your bosses are PHBs who don't care if you load the server down with X windows and Gnome. My bosses are senior UNIX geeks with a bankload of experience and the whole O'reilly library at hand.
They want me to do a pile of different servers, starting with a minimal install and then rebuild functionality as needed manually with the rpm command, as well as custom tuning of those packages. We are talking geeky installs here.
If you're just doing the manual anaconda graphical install, that's makes it all pretty damn simple. And I'm sure you could install RedHat easily on twenty thousand servers pretty damn easily if you use a kickstart file, and have a powerful FTP server available to handle the beating it's going to get.
But OK, right. I'm the amateur, what would I know?
I was trying to discuss support issues between hardware and Linux distributions. Not necessary my customer's subjective preference for Debian and apt-get in this case. And obviously, you have never experienced RPM dependancy hell during an enterprise level install, where documentation creation outlining the install steps is also required.
At the moment in my place of employment, we want to run Debian on some custom hardware (but alas, Debian won't work on it - despite many hack attempts), because we just find RPMs too hard to manage and apt-get + aptitude to ge great.
Employing someone to waste time trying to install Debian on something which cannot guarantee a pay off is not fun, and is a waste of money as well for the customer.
The thing is, the hardware vendor doesn't take Debian seriously (because it's not backed by a company with resources), so there is no driver disk or hardware support.
What I am trying to say is this:- there is a niche here that needs to be filled. There is a need for companies with the ability to back Linux distros, even if just for customer peace of mind. They will pay money for it. So far, only RedHat is being taken seriously commercially IMHO.
There is no "swamped" Linux market, or at least, not in my situation as far as I can tell. Only blimmin' RedHat Linux is supported and will install on our blade server.....
At least someone could sense I was joking. I'm not about to break the laws of physics.
Umm... if these batteries recharge really quickly, and discharge slowly - wouldn't it therefore be possible to use the potential energy of a moving car to charge the battery?
Et voila! A perpertual motion machine! (until the battery karks it)
I'll believe it when I see it in action.
I work as a sysadmin in a freakin Japanese goverment institute with about 4000+ machines in there. I have to manage not only the systems analysis, but build new systems, upgrade and patch machines, document them, translate announcements to English, handle system events, and write work reports to superiors. And I have to do all that alone, on their schedule. Basically they replaced a guy with 17 years of experience (who couldn't hack it anymore) with me with only 2 and a bit years experience. Somehow I am coping because I devised some survival strategies. Basically, Japanese employers are like spoilt children. They demand too much for too little and they want to have everything done yesterday. They also don't care about whatever you feel because they're paying you (a lousy salary) so they don't have to care. I can see how this would cause certain salarymen to jump in front of trains. I don't think it's unusual in Japan for people to overwork and stress out like this because of ridiculous work conditions and greedy employers. Chances are you have been given "mission impossible", and so my advice to you is not to stress out. Take your time, and learn to STALL your project to your own schedule. It's rude in Japan to say "I can't do this", or "I won't be able to make it on schedule" to your employers because it takes away the warm fuzzy feeling you want to give them (which is more important than your techinical ability). NEVER tell them that the project is a complete mess that you just can't do. You will basically have to spin a web of half-truths to keep your head above water. Japanese are very group oriented, and you can use that to your advantage so you don't have to take individual blame for anything that goes wrong. Learn to share the blame (i.e. "It was a team failure") rather than incriminate yourself for a mistake you made. The Japanese do this all the time themselves. If you're not making things on time, blame something else and tell them you're "still checking" the situation ("kakuninn chuu" in Japanese). This confuses the Japanese, and they think that you're taking so long to do the job because you are being "thorough" and perfectionist... something the Japanese like. You can almost do this indefinately to stall things. Also blame other external influences and say "shikataganai" (it cannot be helped) to stall things further. Also, if you appear anal retentive about checking your work out - you'll impress people. As long as you appear like a perfectionist, you can take all the time you want. It's a fine balance keeping superiors happy, getting the job done, and not stressing out yourself. Good luck.
P2P is banned outright at my government owned institute. First of all, the IT department has an application server set up to detect P2P applications based on the traffic, regardless of what port they are using. Here is why it's banned:- (1) It's a security risk. Most of the time people using P2P applications find themselves targets of port scans and other hack attempts. We really don't need this. (2) The piracy issue. Sure, you can argue for downloading Linux ISOs over BitTorrent, but let's be real here. When you already have some AMAZING bandwidth, downloading ISOs (And Debian as jigdo files) is quick by FTP or HTTP alone. There's nothing research related that can only be found on BitTorrent. Plus, allowing people to host illegal content becomes a liability for the IT department, and we have enough work to deal with. (3) The network issue. It hammers the network unneccessarily, and if allowed, it would create a chicken and egg situation for the IT department. As soon as we do an upgrade of the network, more people would use P2P to use up the bandwidth - requiring another upgrade, which more people would then max out. It's too expensive to keep doing this, we already have enough switches that need replacing.
shit that was funny, because it's true.
Microsoft sabotaging Windows? No.
.... a definte YES.
Held Windows at gunpoint, danced around with it in front of the authorities, kicked it in the guts a few times, teased everyone by saying "you'll never get me!", and waged a decade-long seige
And if they call bad coding "sabotage", well that's an interesting parallel universe they live in then.
Some interesting Commodore 64 music links:-
The HVSID Collection - Which is the main site for the collection of thousands upon thousands of Commodore 64 sid files.
Remix.kwed.org Remixes of Commodore 64 tunes with real and modern synthesized instruments.
(Don't hammer their servers!)
I'm off to play "Lazy Jones" (aka ZombieNation)
I have no problem playing with aptitude from their latest unstable Sarge (it's great BTW), but it makes it very hard for me to recommend Debian on servers to customers when the latest stable release is eons old. Yes, I know there are ways around this... but let's face it, from a customer point of view it's an small image problem Debian has.
Sure, they can ban the sale to minors in order to prevent children buying games with questionable content..... .....but they can't stop kids getting these games from P2P, and they can't stop their parents buying it for them.
So in order to join the contest I have to pony up some money for a POWER system... ...aye, there's the rub me laddie.
As long as Jar-Jar dies a horrible, guesome, and painful death in Episode three, it will be worth watching.
It handles Japanese quite well, only as long as you don't ssh into your Solaris workstation. If you ssh into Solaris and get the console, you'll find all of the manpages and other Japanese error messages are illegible.
The movie will be worth seeing as long as Jar-Jar gets hacked to pieces somewhere in the movie. When I see that I will cheer in the theater.
All those sports injuries from playing chess has forced Kasparov to retire.
oh wait.....
Assuming that raid become common practice in the future of the internet, one may actually be surprised that P2P apps are trying to work their way out of having their owners IP addresses traced.
I was surprised (but really, should I be?) to see these kinds of projects. Check out the MUTE project here.
I sit alone and watch the lights, on my PC for several nights. And ev'rything I want to load, I find it on the net, you know
You gave us all those boyband stars. Their CD price -- a total farce. You made 'em sing - which made us cry. We just want all those bands to die
RIAA
You'll just become some background noise, suing groups of girls and boys, who just don't know and just don't care, about your new idea of "fair"
You had your time, you've had the power. You're going to have your final hour
RIAA
All we hear is, RIAA bastards, RIAA sue you, RIAA wankers.
All we hear is, RIAA retards, RIAA blah blah
Peer to peer is new. RIAA no one now needs you!
We taped CDs - we dubbed the stars, off radio for hours and hours. Now we swap files amongst our peers, The tech just changes through the years
Let's hope you leave 'cause you're no friend. Like all good things they come to an end. Don't stick around, as we won't miss you. We're growing tired of all your bullshit
You had your time, you've had the power. You're going to have your final hour
RIAA
All we hear is, RIAA bastards, RIAA screw you, RIAA smacktards.
All we hear is, RIAA wankers, RIAA losers, RIAA ha ha.
All we hear is, RIAA retards, RIAA blah blah
Peer to Peer is new. RIAA, no one now needs you!
RIAA bastards, RIAA bastards, RIAA bastards
RIAA
You had your time you've had the power. You're going to have your final hour
RIAA
Woe to the sysadmins at these places!
employers quite like people with language skills for some unknown reason.
They like us because we not only know computer languages, but human languages as well. It shows you also have social skills and the ability to understand people from otherwise completely different ways of thinking. The ability to communicate effectively with other people is important in tricky situations with users, and when working as a sysadmin in a team of engineers as well.
Actually I work in a Japanese research institute which has a lot of foreign researchers, so they need me to make all the bilingual "System maintenance" notice emails.... and to politely deal with foreign researchers when they have problems, and when they've been naughty and tried to use BitTorrent on our network.