Re:Obligatory SNL Quote
on
They Killed Ken!
·
· Score: -1, Redundant
Sean: "What's the different between your mother and a mallard with a cold?" Alex: "What?" Sean: "One's a sick duck, I don't remember the rest, but your mother's a whore!"
The client side comes stock on NT, 2k Pro and Server*, XP Pro and 2k3 Server*. However the MS RDP client is downloadable for free from their site.
The server side only comes stock on NT,2k, and 2k3 Servers, not the workstation OSs. And even then, you have get a single "stock" license, so no more than one connection at a time unless you shell out some bucks.
So, I just read a few of Mr. PWCX's additions to the maillists and I've come to think he's a being a real asshole. At the very first mention of removing his hook he goes balistic and threatens to remove all his work. He's probably only doing it now because he threatened he would in the first place.
And so, yet again, the person left with the most suckage is the average linux user. The kernel team is a hair bit restrictive, driver devs morph into uber-elitist pricks and yank their code, and people are left with less or poor hardware support.
After reading the rant^H^H^H^Hexplaination, it seems like the current two-part design is a product of Phillips still wanting to protect it's IP. There's enough open source code to get the cams working, but if you realy want all the wiz-bang you'll need their proprietary binary module.
If I were Phillips, I'd be pretty pissed. They have a product whos inner workings they, understandably, don't want to fully release just yet. There's enough code out there to drive the cams with pure open-source, but they've also been kind enough to provide a binary only interface to take advantage of more features.
It's kinda like:
Phillips: "We want to provide you with functionality, but we also have obligations to our internals and share holders, so we'll do what we can and meet you half way."
Kernel team: "Yeah, all that time we talk about wanting better hardware support? We were just fucking with you. Go home and die."
I understand the reason the hook was taken out of the kernel, and I can fully appreciate the intentions of doing so, but regardless of the technicalities, what kind of message does this send to Phillips, and, more importantly, other companies like it now and in the future?
..at some place like Applebees and watch the waitstaff work. Every person active on the floor has a badge with a magstrip that's attached to a ripcord on their belt. Every time they need to use a register they have to swipe their card for access, and when they walk away I'm sure they're required to logoff. It's all touchscreen and the units seem to update very quickly (screen refresh, zero wait time, etc...). I'd bet the whole system is tightly controled and transactions are tied back to exact individual employees. If it can be done in the food industry I'm sure it can be adapted to your set of goals. It might be a challenge to get things to work this fast in a webapp environment though.
There have been other posts suggesting different styles of keyfob wireless access that authenticate you when you approach the machine, but the Applebees scenario also shows how that wouldn't work. During a lunch or dinner rush those places can get crowded and there's potential for multiple waitstaff to be standing close to a register. It would be a tricky and overcomplex game for the machine to try to decide which person to pay attention to.
Since the article is about speed, and just incase the magstrip cards aren't fast enough for you, you could use the same method but switch to proximity RFID tags. I know RFID has been a buzzword lately, but don't forget that's what Exxon has been using in their "Tigerpass" (or whatever they're called) fobs for a long time now. No swiping, just hold it within an inch or two and you're good to go. RFID security passes are usually accompanied by a secondary confirmation that you actually do want gain access, something like a fullscreen button that you have to tap immediately after passing your badge. It helps keep the system from being activated or a user logging on simple by being to near the console.
Also, I don't and never have worked at Applebees. This is just what I've noticed on the last trip or two.
Ok, I'm a little less than impressed by how it walks. Essentially it's waddling, putting it's center of gravity over one "pad" (or foot), moving the other, and then moving the COG to the other pad. Admittedly, this is a decent hack, and it does work.
Stand up, lift up your left foot, and lean to your left without putting down your left foot. It's obsurdly obvious you'll fall down because your center of gravity has shifted to much. This method does work for the robot, and it's not a "hack", because it's the exact same way you walk. It may not be that graceful, but the basic procedure we all use is being mirrored.
Since it's clear that this thing likely its tethered to it's controller...
You're unimpressed with the way it walks, so you've watched the clip on the page. Yet, you've watched the clip on the page and somehow missed completely that it wasn't tethered to anything at all?
I wonder if it would be possible to put more servos in controlling the angle of the pad. Then the pad comes down, and the unit senses if it's tipping, and corrects.
Congratulations. You just described fairly exactly how it works already.
In theory this should produce less waddling, and more realistic walking, right?
Since your theory is how it currently opperates, I'm going to guess the answer is.. no.
It's an excerpt from the opening paragraph of Frozen Journey by Philip K. Dick. I think it first appeared in Playboy in the early 80's, but now it's part of a collection of stories in I Hope I Shall Arive Soon.
It's an excerpt from the opening paragraph of Frozen Journey by Philip K. Dick. I think it first appeared in Playboy in the early 80's, but now it's part of a collection of stories in I Hope I Shall Arive Soon.
This was/not/ the official first flight to attempt winning the X-Prize. It was a test flight just like the last one, only this one made it to regulation altitude.
We ran SUSE Email Server III for just under a year before I finally decided I'd had enough and rolled my own platform.
The LDAP server started dieing multiple times a day due to corruption. After double checking local hardware and configs we knew it was a problem when handfuls of other people started reporting the same thing to the maillists. They didn't provide a way to rebrand the interface and instisted on placing links to their homepage (hardcoded to German) in a very annoying place on every users Inbox.
It was an interesting experience, but my homebrew postfix virtual domain server has been going for 8 months solid now with no problems. And I didn't have to spend $1G on it either.
If you've got the know-how, save the money and build your own.
This is pointless and repetitive, but I'm bored so you win.
- It's time consuming to install. Time is money. Companies don't like spending money if they don't have to.
There are so many rebuttals to this, it really only shows your inexperience with the distro and in some regards sysadmining. Any experienced Gentoo GRP installer will tell you that you can have a fully installed system up and running in the same ammount of time it takes to install something like Fedora. Granted, that's a desktop focused install, but it helps make the point.
Aside from that, if you're doing OS deployment (desktop or server) and you're still doing things by hand, then you may have greater issues. At the very least you could keep a standardized install in a chroot environment and deploy with rsync. Does your boss know that? Doesn't sound like you did.
- emerge doesn't do dependency checking when removing packages. For example, if I accidentally remove libc instead of glibc (for example), I've just fscked myself.
"Our systems are down because our sysadmin just removed libc from one of the boxes." "WTF? Don't we pay him because he's supposed to be smarter then that?" You see where that's headed? Yes, safeguards are nice, and there are a few that aren't quite in place, but you're telling us you're competent and can't help yourself from removing libc?
- there doesn't appear to be any significant review process as Debian and RedHat has in terms of stability - Debian in particular. For instance: Someone used the fact that gentoo only requires the updating of the source code to update all gentoo machines. This isn't a good thing - it doesn't allow for a sufficient review of the code to make sure that there aren't serious problems with it. Contrast that to the armies of reviewers that debian has - even to the relatively new packages which are currently in sarge.
Gentoo has distfiles mirrors which hold the sources referenced by the portage tree. Rsync mirrors handle distribution of the portage tree to end users. To make a new package available, a new or updated ebuild must be created that matches the machines arch type and mask. The ebuild, sources, patches, and other associated files are all MD5'd before addition to the tree. When a user chooses to install a packag everything is checked for consistancy. This process has saved Gentoo users a few times, such as the nmap source poisoning that happened a while back.
As far as code review, Gentoo has so far been successful using a peer/community review system. Packages are initially added as testing. or "soft masked". Once there is suffecient reason to believe there are no problems it is bumped to stable.
My personal experience with gentoo is...
Gentoo isn't an easy distro, and especially not easy to use correctly and effeciently, but the payoff is huge once you get there. It's a bit odd that most Linux users like Linux for it's power, configurability, and in some cases its complexity. Gentoo offers all of those on a new scale and suddenly people aren't interested in taking advantage of it. Don't put yourself down for not figuring the whole thing out right away.
I'd likely not want to work with someone that's so reckless to put such an untested system as gentoo in a critical role.
I'm using Gentoo at several sites for proxy services, web services and virtual domain mail hosting. It's unfortunate that we couldn't work together because you're willing to ignore my skills in sight of my chosen platform. By the note on the front of your homepage it appears you "happen to be looking for a job" so luckily you're not the decision making just yet.
Slashdot Mirror
Sean: "What's the different between your mother and a mallard with a cold?"
Alex: "What?"
Sean: "One's a sick duck, I don't remember the rest, but your mother's a whore!"
Let's imagine you had a clue what you talking about...
You could've made it easier on yourself and just said "I've never used this stuff so I have NFC what I'm talking about."
To clarify the parent a little,
The client side comes stock on NT, 2k Pro and Server*, XP Pro and 2k3 Server*. However the MS RDP client is downloadable for free from their site.
The server side only comes stock on NT,2k, and 2k3 Servers, not the workstation OSs. And even then, you have get a single "stock" license, so no more than one connection at a time unless you shell out some bucks.
How many other webcam companies let another guy write a prorietary driver under an NDA?
I can't think of any.
Realative to the situation, it is a big deal.
Repling to my own post, yeah, yeah..
So, I just read a few of Mr. PWCX's additions to the maillists and I've come to think he's a being a real asshole. At the very first mention of removing his hook he goes balistic and threatens to remove all his work. He's probably only doing it now because he threatened he would in the first place.
And so, yet again, the person left with the most suckage is the average linux user. The kernel team is a hair bit restrictive, driver devs morph into uber-elitist pricks and yank their code, and people are left with less or poor hardware support.
Fuckin' crazy.
After reading the rant^H^H^H^Hexplaination, it seems like the current two-part design is a product of Phillips still wanting to protect it's IP. There's enough open source code to get the cams working, but if you realy want all the wiz-bang you'll need their proprietary binary module.
If I were Phillips, I'd be pretty pissed. They have a product whos inner workings they, understandably, don't want to fully release just yet. There's enough code out there to drive the cams with pure open-source, but they've also been kind enough to provide a binary only interface to take advantage of more features.
It's kinda like:
Phillips: "We want to provide you with functionality, but we also have obligations to our internals and share holders, so we'll do what we can and meet you half way."
Kernel team: "Yeah, all that time we talk about wanting better hardware support? We were just fucking with you. Go home and die."
I understand the reason the hook was taken out of the kernel, and I can fully appreciate the intentions of doing so, but regardless of the technicalities, what kind of message does this send to Phillips, and, more importantly, other companies like it now and in the future?
..at some place like Applebees and watch the waitstaff work. Every person active on the floor has a badge with a magstrip that's attached to a ripcord on their belt. Every time they need to use a register they have to swipe their card for access, and when they walk away I'm sure they're required to logoff. It's all touchscreen and the units seem to update very quickly (screen refresh, zero wait time, etc...). I'd bet the whole system is tightly controled and transactions are tied back to exact individual employees. If it can be done in the food industry I'm sure it can be adapted to your set of goals. It might be a challenge to get things to work this fast in a webapp environment though.
There have been other posts suggesting different styles of keyfob wireless access that authenticate you when you approach the machine, but the Applebees scenario also shows how that wouldn't work. During a lunch or dinner rush those places can get crowded and there's potential for multiple waitstaff to be standing close to a register. It would be a tricky and overcomplex game for the machine to try to decide which person to pay attention to.
Since the article is about speed, and just incase the magstrip cards aren't fast enough for you, you could use the same method but switch to proximity RFID tags. I know RFID has been a buzzword lately, but don't forget that's what Exxon has been using in their "Tigerpass" (or whatever they're called) fobs for a long time now. No swiping, just hold it within an inch or two and you're good to go. RFID security passes are usually accompanied by a secondary confirmation that you actually do want gain access, something like a fullscreen button that you have to tap immediately after passing your badge. It helps keep the system from being activated or a user logging on simple by being to near the console.
Also, I don't and never have worked at Applebees. This is just what I've noticed on the last trip or two.
Ok, I'm a little less than impressed by how it walks. Essentially it's waddling, putting it's center of gravity over one "pad" (or foot), moving the other, and then moving the COG to the other pad. Admittedly, this is a decent hack, and it does work.
Stand up, lift up your left foot, and lean to your left without putting down your left foot. It's obsurdly obvious you'll fall down because your center of gravity has shifted to much. This method does work for the robot, and it's not a "hack", because it's the exact same way you walk. It may not be that graceful, but the basic procedure we all use is being mirrored.
Since it's clear that this thing likely its tethered to it's controller...
You're unimpressed with the way it walks, so you've watched the clip on the page. Yet, you've watched the clip on the page and somehow missed completely that it wasn't tethered to anything at all?
I wonder if it would be possible to put more servos in controlling the angle of the pad. Then the pad comes down, and the unit senses if it's tipping, and corrects.
Congratulations. You just described fairly exactly how it works already.
In theory this should produce less waddling, and more realistic walking, right?
Since your theory is how it currently opperates, I'm going to guess the answer is.. no.
It's an excerpt from the opening paragraph of Frozen Journey by Philip K. Dick. I think it first appeared in Playboy in the early 80's, but now it's part of a collection of stories in I Hope I Shall Arive Soon.
It's an excerpt from the opening paragraph of Frozen Journey by Philip K. Dick. I think it first appeared in Playboy in the early 80's, but now it's part of a collection of stories in I Hope I Shall Arive Soon.
The DVD is being released on Sept. 14 of this year. Here's the cover art.
It has it's own homepage
Direct link to the trailer (quicktime).
There's a second comparison page here
I saw the enhanced trailer for it not to long ago.
Dock N Talk
...when it was called Citrix.
This was /not/ the official first flight to attempt winning the X-Prize. It was a test flight just like the last one, only this one made it to regulation altitude.
Look a little harder.
That's right. Fuck creativity, you're all about the money.
We ran SUSE Email Server III for just under a year before I finally decided I'd had enough and rolled my own platform.
The LDAP server started dieing multiple times a day due to corruption. After double checking local hardware and configs we knew it was a problem when handfuls of other people started reporting the same thing to the maillists. They didn't provide a way to rebrand the interface and instisted on placing links to their homepage (hardcoded to German) in a very annoying place on every users Inbox.
It was an interesting experience, but my homebrew postfix virtual domain server has been going for 8 months solid now with no problems. And I didn't have to spend $1G on it either.
If you've got the know-how, save the money and build your own.
I found a picture of the new TechTV staff
Sorry. I just didn't understand that you disliked all Israelis.
This is pointless and repetitive, but I'm bored so you win.
- It's time consuming to install. Time is money. Companies don't like spending money if they don't have to.
There are so many rebuttals to this, it really only shows your inexperience with the distro and in some regards sysadmining. Any experienced Gentoo GRP installer will tell you that you can have a fully installed system up and running in the same ammount of time it takes to install something like Fedora. Granted, that's a desktop focused install, but it helps make the point.
Aside from that, if you're doing OS deployment (desktop or server) and you're still doing things by hand, then you may have greater issues. At the very least you could keep a standardized install in a chroot environment and deploy with rsync. Does your boss know that? Doesn't sound like you did.
- emerge doesn't do dependency checking when removing packages. For example, if I accidentally remove libc instead of glibc (for example), I've just fscked myself.
"Our systems are down because our sysadmin just removed libc from one of the boxes." "WTF? Don't we pay him because he's supposed to be smarter then that?" You see where that's headed? Yes, safeguards are nice, and there are a few that aren't quite in place, but you're telling us you're competent and can't help yourself from removing libc?
- there doesn't appear to be any significant review process as Debian and RedHat has in terms of stability - Debian in particular. For instance: Someone used the fact that gentoo only requires the updating of the source code to update all gentoo machines. This isn't a good thing - it doesn't allow for a sufficient review of the code to make sure that there aren't serious problems with it. Contrast that to the armies of reviewers that debian has - even to the relatively new packages which are currently in sarge.
Gentoo has distfiles mirrors which hold the sources referenced by the portage tree. Rsync mirrors handle distribution of the portage tree to end users. To make a new package available, a new or updated ebuild must be created that matches the machines arch type and mask. The ebuild, sources, patches, and other associated files are all MD5'd before addition to the tree. When a user chooses to install a packag everything is checked for consistancy. This process has saved Gentoo users a few times, such as the nmap source poisoning that happened a while back.
As far as code review, Gentoo has so far been successful using a peer/community review system. Packages are initially added as testing. or "soft masked". Once there is suffecient reason to believe there are no problems it is bumped to stable.
My personal experience with gentoo is...
Gentoo isn't an easy distro, and especially not easy to use correctly and effeciently, but the payoff is huge once you get there. It's a bit odd that most Linux users like Linux for it's power, configurability, and in some cases its complexity. Gentoo offers all of those on a new scale and suddenly people aren't interested in taking advantage of it. Don't put yourself down for not figuring the whole thing out right away.
I'd likely not want to work with someone that's so reckless to put such an untested system as gentoo in a critical role.
I'm using Gentoo at several sites for proxy services, web services and virtual domain mail hosting. It's unfortunate that we couldn't work together because you're willing to ignore my skills in sight of my chosen platform. By the note on the front of your homepage it appears you "happen to be looking for a job" so luckily you're not the decision making just yet.
Dan had a screenshot of his desktop that featured Tux waving an Israeli flag. I guess that can be considerd "on" the Gentoo site.
Somehow I believe if it was something like a Canadian flag you wouldn't have thought twice about it.
# emerge -u world
And you're done.