Well, I for one, hail our long-time rich-boy overlords!
I'm in Germany, on leave, and have had more than my/. two-drink minimum. I'll comment on how evil and brain dead this SC ruling is later, but the guy who pointed out that public has effectively changed to public or private in the 5th amendment already stated the nature of my gripe.
Web servers have a tendency to be compromised by scripts/executables running on other machines. IIS also doesn't go out to the web clicking willy-nilly on ad infested websites, but has in the past been affected by things like Code Red and its variants.
I also once demonstrated how a web browser could be used to destroy an IIS server that didn't have the directory traversal flaw patched.
Any version of MacOS/X isn't actually 64 bit code, or not too much of it. It just uses some addressing extensions to be able to use more than 4 gigabytes RAM, but nothing else.
That's largely because the PowerPC spec is 64-bit. all of the processors Apple has used up until the G5 were merely using the 32-bit subset of a 64-bit architecture. For joe sixpack, the difference is semantic. At any rate, the important stuff that still needs to migrate to 64-bit is all in UI space. As of tomorrow, the most current release of OSX will, for all intents and purposes, have all of the back-end 64-bit safe. You're comparing different methodologies of migrating from two different architectures to two different architectures. I am also going to point out that there is but one build of the kernel for MacOS at this point, and you get your OSX with or without server tools. now for windows you have multiple different builds for architecture and purpose of the machine. I see no Tao in that way of doing things.
Also, last I checked, Wine was in no way a "virtual machine", it was an EXE/DLL format loader that provided the services of reimplemented Windows procedures or loading/linking of Win32 system dll's to a win32 app on a non-Windows platform. Throw in something also about bug-for-bug compatibility.
all quite true. however, apple was in no way obligated to even release the x86 version of darwin, much less maintain it. further, i imagine that there was a bit of kernel level reworking involved in the source. As for Star Trek having anything to do with the current release of MacOS, I think I'd have an easier time trying to claim a connection between MS Windows v1.0 design or source and IBM System/360's.;)
They also have ported their OS to x86. Twice, in fact. The first time was in the early '90's, with the Star Trek project, which culminated in System 7 booting on x86 and a huge internal conundrum, and was killed because Apple is, first and foremost, a hardware company. Star Trek was also never released to the general public, although it would be really interesting to see the source for it...
Darwin is the second port of MacOS to x86, albeit this version is stripped down to just the core OS. My guess is, its x86 port was done to insure that the underlying OS core would port to different architectures. On the bright side, most of the rest of OS X should be relatively easy to port from unoptimized source code for the rest of the system...
Some of that has to do with the way Mac binaries are made, some of that has to do with the differences between G4 and G5.
First off, Motion probably runs as a "fat binary" -- when you click on the icon, it loads an executable compiled for your architecture, be it G4 or G5. It's one of the nicer innovations to come out of NeXT, although a NeXT fat binary could also target NeXT on x86 or any other architecture that could run NeXTStep natively. This is merely "kewl" until you think about the architectural differences between the G4 and G5...
The G5 can address 16 exabytes of space vs the G4's 4GB. It makes an enormous difference when dealing with insanely large data sets, like DV or complex GIS data, and directly manipulating them in addressable memory (granted, a lot of it is actually in swap, but at least you can address it directly from swap). The G4, dealing with more than 4GB of data, would have to write data to temporary files, load them (frequently into swap), and have easily three times the number of disk accesses of the 64-bit version of the same application. I won't even digress into the pipelining differences between the two, or the impact Altivec vs. non-Altivec code has on apps like this...
In any case, for the scientific, engineering, video, and graphics design markets where high processing power and portability are highly desirable, a G5 based laptop would be exceptional. Only problem is melting the aluminum chassis during heavy processor loads...;)
The same FS search capability was in BeOS many moons before that. In fact, BeOS's greatest accomplishment, IMO, was their filesystem. It was a true 64-bit journalled filesystem with some metadata search capability when FAT32 was just getting widespread. It was nice, but I'm personally looking forward to the Apple implementation of the search feature set. BTW, WinFS got canned for Longhorn, last I checked, supposedly so that MS could release only a year later than planned.
Programs like Serv-U and VNC (I am quite sure that there are others misused for spyware, I'm just no longer dealing with it daily) are exploited by spyware writers because they add features/functionality cheaply. Nobody writing malware really cares about violating rhinosoft's license, or that VNC was not intended to run surreptitiosly. They care that they can add ftp functionality or remote desktop viewing capabilities to their crap with the only cost being a little time to customize serv-u, or familiarization with VNC's API.
The reason that the anti-spyware lists them is that there are some ungodly number of machines with these programs being abused to exploit a user. It's just a shame that generally good software is more abused than used...
I knew a SGM once who insisted that it was "HUA, acronym, infantry, Head Up Ass!" He was a tanker, btw.
From my own observations, guys were playing the games as an escape from reality, so things like KOTOR were popular if we were anywhere near where we could have a console. Once we got to our second home-away-from-home south of Baghdad, it was pretty much limited to GameBoys and laptops. BTW, the most popular GameBoy title for quite a while was the Sims...
Granted, I haven't checked on what other automagic source massagers do in a while, but I would imagine that there are none that do what you're describing to the point of being actually useful. What's useful falls into a few basic categories, namely WHY did this get written, and WHO do I blame for this crap, anyway. the first being generally more useful than the second, unless you're playing the cover-your-ass game. Most modern IDE's will try to fill in the second for you in header blocks or string definition files, but considering how hard it can be to go back to uncommented code a few weeks later and figure out what the hell you were thinking, I seriously doubt that anyone's got software that allows the computer to figure that out for you.
Considering that this guy has his copy of XP running on a Virtual PC image--sandboxed on a Mac (read BSD environment on a mach core)-- I think he's just denying that he's got it...
Right now, there are no jobs in the army that don't turn into "acting infantry" in the right place at the right time (Afghanistan, Iraq, not too sure about what's going on right now at the "Horn of Africa" aka Somalia). I would like to point out that MPs do a whole lot more than what most people think, and a Combat Support MP section packs almost as much firepower as a dismount infantry section, and goes to almost as many unpleasant places. When I got extended with 1AD earlier this year, I saw an MP company make the trip from where they were to where we were not less than 1-2 times a week, which had a particularly nasty IED Alley in between.
BTW, I also wouldn't necessarily recommend going for a desk job rather than the Infantry. I've found it so far to be a bit more honest and direct than any IT job I've ever held, but the IT skills make it hard for me to stay in a line unit.
a la Pleasantville? It's simple on stills in any reasonably featured photo editor. probably a time consuming PITA on film, though, but the principle would still be the same.
Split video into frames, copy the frames, change mode to b/w, change mode back to color, add alpha channel, add layer, paste the original as the background layer, and 'erase' the areas on the upper (b/w) layer to show color, flatten image, export to frame. Lather, rinse, and repeat about 30 times for each second of video.
like I said, very time consuming by hand, but maybe there's a tool to automate it. In any case, there's a tutorial for doing this to a still on gimp.org, and I don't imagine it would be significantly different for video frames. YMMVG
Yeah, remember Spyglass? They sold their Mosaic sources to MSFT for $50k plus a royalty on sales of the Microsoft branded web browser. How large was their last royalty check, again?
Since Final Cut can handle MPEG-2 editing. I think the lack of editing support of MPEG-2 in all of the iApps may simply be a method of discouraging piracy of copyrighted materials. It kind of makes sense if you think about dvd studio pro/motion/final cut pro being targeted towards studios, or whomever the studios contract for development of the DVD version of a flick.
OK, your management isn't hot on linux because they can't sue anybody if it doesn't work. I'm not familiar with VM/ESA's licensing agreements, but I can't name a single vendor that produces a product that their licensing claims is useful for anything, or that will indemnify if the software is a complete piece of crap. Nothing else in the US can be sold with the same disclaimers against liability as software because of the Consumer Protection Act. You can sue the vendor if you buy a lamp that has a defect that causes your house to burn down. You can't sue your vendor if their software loses data, infringes on someone else's patents and you get pulled into a liability suit, or their OS can't stay up for more than a week without hard-crashing.
Now, I'm going to go out on a limb here and guess that you're in a shop that already has at least one z390 available, or that your company has a lot of cash to burn. The reason I am inclined to this opinion is that a nice, shiny new z390 costs about $50K USD. Having a partition added to an existing z390 costs more than my car and my wife's car put together. In either case, there is still a real cost per cycle of computing on that platform that even a PHB can see. Find out what IBM is providing license wise under VM/ESA that they don't provide under their licensing agreement with RedHat. Then study the costs of the migration to linux. since any mainframe OS has monthly licensing costs (last I checked, which I will concede was more than a couple of years ago), long-term migration to OSS on the OS side will eventually come out on top dollar for dollar. It also can't hurt to point out that IBM seems to have concluded that linux is the direction for all of their server-class and mainframe machines in the long term.
As an aside, for those of you reminding this guy about the MS SQL 7/2k licensing issues, this case has been in court for about 3 years, and everybody who is about to get hosed on patent licensing was told by MS's PR dept. that they didn't have a thing to worry about. Part of what the customers are getting nailed to the wall on is the > 2 1/2 years that patent licensing has been a known issue where they didn't talk to the patent owners and acquire the appropriate licensing for their copy of MSSQL. In any case, the indemnification argument could work incredibly well as an argument to move away from MS on the smaller servers, but you are going to have to do some homework to get anything done about the mainframes.
Icelandic naming convention (short summary):
male child: father's first name + possessive 's' + son
female child: father's first name + possessive 's' + dottir
If dad's a deadbeat/unknown, use mother's first name instead of father's.
There are also subtle mutations of names involved. You want great detail on that, learn Icelandic. For an example of how it all works, Tryggvi and his wife Brunhild have a son that they name Thorvald. The child is named Thorvald Tryggvasson. Thorvald gets Gudrun knocked up and skips town on the nearest trawler, leaving no forwarding address. When the child is born (let's say it's a girl), she will have the last name Gudrunsdottir. 18 years later, young Ms. Gudrunsdottir (let's call her Rannveig) is grown up. She finds out she's pregnant after partying an entire weekend with a bunch of sailors on shore leave from NAS Keflavik, and can't remember who specifically is in the daddy candidate pool. Her child would have the last name of either Rannveigsson or Rannveigsdottir.
As an interesting and somewhat related side note, Icelandic phone books list name, address, phone number, and occupation. They also have kept concise records of descent since the Age of the Saga Writers (c. 1200ad).
Try holding your hands clasped in front of you. I wouldn't want to get caught leaning too far to the right, but you may find putting it on your right wrist will alleviate the leftist leanings.
Ah, the joys of American political jokes. Compassionate conservatism, a Democratic party political platform, time off from presidential campaigning...
Slashdot Mirror
Well, I for one, hail our long-time rich-boy overlords!
I'm in Germany, on leave, and have had more than my /. two-drink minimum. I'll comment on how evil and brain dead this SC ruling is later, but the guy who pointed out that public has effectively changed to public or private in the 5th amendment already stated the nature of my gripe.
Web servers have a tendency to be compromised by scripts/executables running on other machines. IIS also doesn't go out to the web clicking willy-nilly on ad infested websites, but has in the past been affected by things like Code Red and its variants.
I also once demonstrated how a web browser could be used to destroy an IIS server that didn't have the directory traversal flaw patched.
That's largely because the PowerPC spec is 64-bit. all of the processors Apple has used up until the G5 were merely using the 32-bit subset of a 64-bit architecture. For joe sixpack, the difference is semantic. At any rate, the important stuff that still needs to migrate to 64-bit is all in UI space. As of tomorrow, the most current release of OSX will, for all intents and purposes, have all of the back-end 64-bit safe. You're comparing different methodologies of migrating from two different architectures to two different architectures. I am also going to point out that there is but one build of the kernel for MacOS at this point, and you get your OSX with or without server tools. now for windows you have multiple different builds for architecture and purpose of the machine. I see no Tao in that way of doing things.
Also, last I checked, Wine was in no way a "virtual machine", it was an EXE/DLL format loader that provided the services of reimplemented Windows procedures or loading/linking of Win32 system dll's to a win32 app on a non-Windows platform. Throw in something also about bug-for-bug compatibility.
I think you forgot Zero Cool... been a while since I watched that comedy, tho...
all quite true. however, apple was in no way obligated to even release the x86 version of darwin, much less maintain it. further, i imagine that there was a bit of kernel level reworking involved in the source. As for Star Trek having anything to do with the current release of MacOS, I think I'd have an easier time trying to claim a connection between MS Windows v1.0 design or source and IBM System/360's. ;)
They also have ported their OS to x86. Twice, in fact. The first time was in the early '90's, with the Star Trek project, which culminated in System 7 booting on x86 and a huge internal conundrum, and was killed because Apple is, first and foremost, a hardware company. Star Trek was also never released to the general public, although it would be really interesting to see the source for it...
Darwin is the second port of MacOS to x86, albeit this version is stripped down to just the core OS. My guess is, its x86 port was done to insure that the underlying OS core would port to different architectures. On the bright side, most of the rest of OS X should be relatively easy to port from unoptimized source code for the rest of the system...
Some of that has to do with the way Mac binaries are made, some of that has to do with the differences between G4 and G5.
First off, Motion probably runs as a "fat binary" -- when you click on the icon, it loads an executable compiled for your architecture, be it G4 or G5. It's one of the nicer innovations to come out of NeXT, although a NeXT fat binary could also target NeXT on x86 or any other architecture that could run NeXTStep natively. This is merely "kewl" until you think about the architectural differences between the G4 and G5...
The G5 can address 16 exabytes of space vs the G4's 4GB. It makes an enormous difference when dealing with insanely large data sets, like DV or complex GIS data, and directly manipulating them in addressable memory (granted, a lot of it is actually in swap, but at least you can address it directly from swap). The G4, dealing with more than 4GB of data, would have to write data to temporary files, load them (frequently into swap), and have easily three times the number of disk accesses of the 64-bit version of the same application. I won't even digress into the pipelining differences between the two, or the impact Altivec vs. non-Altivec code has on apps like this...
In any case, for the scientific, engineering, video, and graphics design markets where high processing power and portability are highly desirable, a G5 based laptop would be exceptional. Only problem is melting the aluminum chassis during heavy processor loads... ;)
Don't forget Maya, Lightwave, and pretty much all other 3d modellers on the market for the mac...
The same FS search capability was in BeOS many moons before that. In fact, BeOS's greatest accomplishment, IMO, was their filesystem. It was a true 64-bit journalled filesystem with some metadata search capability when FAT32 was just getting widespread. It was nice, but I'm personally looking forward to the Apple implementation of the search feature set. BTW, WinFS got canned for Longhorn, last I checked, supposedly so that MS could release only a year later than planned.
Programs like Serv-U and VNC (I am quite sure that there are others misused for spyware, I'm just no longer dealing with it daily) are exploited by spyware writers because they add features/functionality cheaply. Nobody writing malware really cares about violating rhinosoft's license, or that VNC was not intended to run surreptitiosly. They care that they can add ftp functionality or remote desktop viewing capabilities to their crap with the only cost being a little time to customize serv-u, or familiarization with VNC's API.
The reason that the anti-spyware lists them is that there are some ungodly number of machines with these programs being abused to exploit a user. It's just a shame that generally good software is more abused than used...
I knew a SGM once who insisted that it was "HUA, acronym, infantry, Head Up Ass!" He was a tanker, btw.
From my own observations, guys were playing the games as an escape from reality, so things like KOTOR were popular if we were anywhere near where we could have a console. Once we got to our second home-away-from-home south of Baghdad, it was pretty much limited to GameBoys and laptops. BTW, the most popular GameBoy title for quite a while was the Sims...
As far as I know, the more useful tools out there do things like restructure your written code for readability or automagically generate documentation from specially formatted comments.
Granted, I haven't checked on what other automagic source massagers do in a while, but I would imagine that there are none that do what you're describing to the point of being actually useful. What's useful falls into a few basic categories, namely WHY did this get written, and WHO do I blame for this crap, anyway. the first being generally more useful than the second, unless you're playing the cover-your-ass game. Most modern IDE's will try to fill in the second for you in header blocks or string definition files, but considering how hard it can be to go back to uncommented code a few weeks later and figure out what the hell you were thinking, I seriously doubt that anyone's got software that allows the computer to figure that out for you.
Just my .013 Euro...
Considering that this guy has his copy of XP running on a Virtual PC image--sandboxed on a Mac (read BSD environment on a mach core)-- I think he's just denying that he's got it...
Right now, there are no jobs in the army that don't turn into "acting infantry" in the right place at the right time (Afghanistan, Iraq, not too sure about what's going on right now at the "Horn of Africa" aka Somalia). I would like to point out that MPs do a whole lot more than what most people think, and a Combat Support MP section packs almost as much firepower as a dismount infantry section, and goes to almost as many unpleasant places. When I got extended with 1AD earlier this year, I saw an MP company make the trip from where they were to where we were not less than 1-2 times a week, which had a particularly nasty IED Alley in between.
BTW, I also wouldn't necessarily recommend going for a desk job rather than the Infantry. I've found it so far to be a bit more honest and direct than any IT job I've ever held, but the IT skills make it hard for me to stay in a line unit.
a la Pleasantville? It's simple on stills in any reasonably featured photo editor. probably a time consuming PITA on film, though, but the principle would still be the same.
Split video into frames, copy the frames, change mode to b/w, change mode back to color, add alpha channel, add layer, paste the original as the background layer, and 'erase' the areas on the upper (b/w) layer to show color, flatten image, export to frame. Lather, rinse, and repeat about 30 times for each second of video.
like I said, very time consuming by hand, but maybe there's a tool to automate it. In any case, there's a tutorial for doing this to a still on gimp.org, and I don't imagine it would be significantly different for video frames. YMMVG
Couldn't you have used that valuable opportunity to shout "first post!"?
Yeah, remember Spyglass? They sold their Mosaic sources to MSFT for $50k plus a royalty on sales of the Microsoft branded web browser. How large was their last royalty check, again?
Since Final Cut can handle MPEG-2 editing. I think the lack of editing support of MPEG-2 in all of the iApps may simply be a method of discouraging piracy of copyrighted materials. It kind of makes sense if you think about dvd studio pro/motion/final cut pro being targeted towards studios, or whomever the studios contract for development of the DVD version of a flick.
Holy $H|^!!! a rational comment on /. -- i think we need to all stop and prepare to meet our maker, for surely the end is near!
this is why they still speak of varangians in whispers of hushed terror here in the middle east. we of icelandic descent are just plain crazy...
If it's any consolation, I'd have probably done the same thing by now, lord knows I have enough time between patrols. I just don't have the hardware.
you will find the humble icelander in a bar sitting next to the honest man.
You forgot to mention that Pedro is the only act in town, since he killed off all of the other local competition...
Just put the gun down...
OK, your management isn't hot on linux because they can't sue anybody if it doesn't work. I'm not familiar with VM/ESA's licensing agreements, but I can't name a single vendor that produces a product that their licensing claims is useful for anything, or that will indemnify if the software is a complete piece of crap. Nothing else in the US can be sold with the same disclaimers against liability as software because of the Consumer Protection Act. You can sue the vendor if you buy a lamp that has a defect that causes your house to burn down. You can't sue your vendor if their software loses data, infringes on someone else's patents and you get pulled into a liability suit, or their OS can't stay up for more than a week without hard-crashing.
Now, I'm going to go out on a limb here and guess that you're in a shop that already has at least one z390 available, or that your company has a lot of cash to burn. The reason I am inclined to this opinion is that a nice, shiny new z390 costs about $50K USD. Having a partition added to an existing z390 costs more than my car and my wife's car put together. In either case, there is still a real cost per cycle of computing on that platform that even a PHB can see. Find out what IBM is providing license wise under VM/ESA that they don't provide under their licensing agreement with RedHat. Then study the costs of the migration to linux. since any mainframe OS has monthly licensing costs (last I checked, which I will concede was more than a couple of years ago), long-term migration to OSS on the OS side will eventually come out on top dollar for dollar. It also can't hurt to point out that IBM seems to have concluded that linux is the direction for all of their server-class and mainframe machines in the long term.
As an aside, for those of you reminding this guy about the MS SQL 7/2k licensing issues, this case has been in court for about 3 years, and everybody who is about to get hosed on patent licensing was told by MS's PR dept. that they didn't have a thing to worry about. Part of what the customers are getting nailed to the wall on is the > 2 1/2 years that patent licensing has been a known issue where they didn't talk to the patent owners and acquire the appropriate licensing for their copy of MSSQL. In any case, the indemnification argument could work incredibly well as an argument to move away from MS on the smaller servers, but you are going to have to do some homework to get anything done about the mainframes.
Icelandic naming convention (short summary):
male child: father's first name + possessive 's' + son
female child: father's first name + possessive 's' + dottir
If dad's a deadbeat/unknown, use mother's first name instead of father's.
There are also subtle mutations of names involved. You want great detail on that, learn Icelandic. For an example of how it all works, Tryggvi and his wife Brunhild have a son that they name Thorvald. The child is named Thorvald Tryggvasson. Thorvald gets Gudrun knocked up and skips town on the nearest trawler, leaving no forwarding address. When the child is born (let's say it's a girl), she will have the last name Gudrunsdottir. 18 years later, young Ms. Gudrunsdottir (let's call her Rannveig) is grown up. She finds out she's pregnant after partying an entire weekend with a bunch of sailors on shore leave from NAS Keflavik, and can't remember who specifically is in the daddy candidate pool. Her child would have the last name of either Rannveigsson or Rannveigsdottir.
As an interesting and somewhat related side note, Icelandic phone books list name, address, phone number, and occupation. They also have kept concise records of descent since the Age of the Saga Writers (c. 1200ad).
yes, it's a little offtopic, but what the hell...
Try holding your hands clasped in front of you. I wouldn't want to get caught leaning too far to the right, but you may find putting it on your right wrist will alleviate the leftist leanings.
Ah, the joys of American political jokes. Compassionate conservatism, a Democratic party political platform, time off from presidential campaigning...