I don't want an argument over terms here, but I think your generalization of a competent sysadmin does not fit in here. I can really throw in a handful of acronyms of which I think a sysadmin should be aware of in my line of work that you don't, and I'm sure you can do the same for whatever field you're specialized in. But that wouldn't make either of us incompetent sysadmins. (btw my job description doesn't say sysadmin either).
The point is: many readers here who might be interested in the Linux Terminal Server Project don't give the GGGGGP's post a second thought because they don't recognize the acronym - which from my POV is nowhere near to being ubiquitous technology like virtualization, and if people don't pick up hints like this never will be.
Would you expect participants in a discussion about board design to spell out ASIC and FPGA?
No, but xzvf admitted himself that he was posting slightly off-topic and therefore should not expect that everyone is familiar with it. LTSP is not the topic at hand, virtualization is. I agree with HateBreeder.
While display resolution must be a major factor in power consumption, in my opinion the whole issue started back when VGA designers and game designers began thinking: "Hey, we can offload that processing to the GPU!" (if there even was the concept of 'GPU' back then).
Ever since, the complexity and features of these GPUs has increased tremendously, obviously resulting in higher scene complexity and better looking games/graphics. But man... Those chips need to be fed.
I don't know if there is any such thing as 'demand for scene complexity' beyond the "Oooh! Shiny!" factor, but if there is you can't hold the GPU manufacturers responsible for jumping that market.
When I was doing consulting/engineering services for SMB, the documentation I made was modeled after the actual OSI model.
So, you start with Layer 8, which is a basic description of your company's services, needs and requirements of the network, technical contacts, third parties involved in the network (security, telephony, ISP, hardware suppliers, specialized software) and their contracts.
Layer 7: Document the applications in use and how they are 'connected'. Create a global picture of what applications exist in the network, how they are connected, any dependencies on specific versions (e.g. frameworks, Java versions, databases, etc). Then, create a separate section for each 'application' that details the configuration of that application. E.g. the Active Directory gets its own section where you describe the domain name, relevant domain controllers, OU structure, blabla. For your web servers, document the site names, devices/servers responsible for the service, references to other documentation. Garnish with screen shots. Repeat for all applications.
Layer 6 may be hard to document because it's not always transparent, but include things like special software languages, broker services or anything sitting between your network and applications.
Layer 5, in a Windows-based network, should include documentation on the NT session security and compatibility level (authentication and signing requirements, if any).
Layer 4 should mention the transport protocols in use in your network (don't forget things like telephony), and any special settings made to the TCP/IP protocol stack required to make stuff work. Firewall access rules fit in this section nicely.
Layer 3 should include the addressing and routing schemes for your network. Server/distribution/access subnets, printer subnets, DHCP scopes, DNS servers, VPN connectivity, etc should all be described in this section.
Layer 2 should include the switch configuration documentation, VLAN configuration, frame types in use (again, don't forget telephony and wireless networks).
Layer 1 should include a building plan, documentation/certification of cabling infrastructure, patch cabinet documentation, maybe things like power infrastructure, physical access control. Sure you can make up the other stuff applicable to your network.
This is the global picture. The detailed configuration information for each server and device in the network should of course be noted, but that kind of information is useless without the big picture (which explains WHY the device has been configured thus).
I also never include security related information in generic documentation. A list of credentials should be stored safely in a separate document that sits in your boss' safe.
A lot of commenters in this thread are bound to be native Dutch speakers, doing quite a good job at expressing themselves in English. Now, I would like to see YOU try in any other foreign languague, mister Coward, preferably Dutch. See how well your grammar sticks.
ms, to the larger part, makes money from the programs and products they sell that run on windows machines.
I call BS. Couldn't find any more recent figures, but from http://www.microsoft.com/msft/earnings/FY07/earn_rel_q4_07.mspx I gather that in 2007, MS made a total revenue of $26B in the Client and Server division, and a measly $16B in the Business division (and I assume their server applications belong there). You also didn't bother to read TFS which explains nicely why pirated versions cause headaches. You, sir, earn zero points.
You must have used a retail disc on an OEM product key, or a generic OEM install disc on a DELL/HP/whatever branded OEM product key. Yeah, those are different. The activation challenge is not "25 sets of 5 random characters", it's 30 characters. Learn how to spell, it's a useful skill, and not just to activate XP. See http://en.wikipedia.org/wiki/NATO_phonetic_alphabet
So, instead of trolling, you could also consider phone activation to be a service for [expletive] who lose the recovery media that came with their computer, or didn't bother do make any.
The way I see it, they've produced exactly two games over the last five years, according to WP (Prey and some variants of Duke Nukem). Nothing to do with being nice to your employees. The bottom line is that just two releases won't keep your business in business. Which probably boils down to management issues, yeah.
Ooh, I could listen to my ass all day. The only country I'm aware of that uses the word Saloon is the UK. And yes, the majority of Europeans call it a sedan.
Listen, I was not implying that Sedan is the only word in use, I was challenging the GP's statement that Europeans call this type of car a saloon.
Look at the Wiki page for Sedan and check the articles for the different languages.
The Dutch, Czech, Finnish, Danish, Greek, Turkish, Romanians, Spanish and a host of other languages call it a Sedan.
The French and Italians call it a Berline/Berlina.
The Germans and a few other languages call it a Limousine.
The article I linked to is mainly about hot adding memory, indeed, because this seems to me to be the most appealing type of RAM adjustments. However, the Static Resource Affinity Table mentioned is also capable of hot-removing memory.
The problem of the missing data from a removed module might actually not be a problem. I suspect that the type of hardware that supports hot addition and removal of RAM also supports the use of spare memory and memory mirroring.
Slashdot Mirror
I don't want an argument over terms here, but I think your generalization of a competent sysadmin does not fit in here. I can really throw in a handful of acronyms of which I think a sysadmin should be aware of in my line of work that you don't, and I'm sure you can do the same for whatever field you're specialized in. But that wouldn't make either of us incompetent sysadmins. (btw my job description doesn't say sysadmin either).
The point is: many readers here who might be interested in the Linux Terminal Server Project don't give the GGGGGP's post a second thought because they don't recognize the acronym - which from my POV is nowhere near to being ubiquitous technology like virtualization, and if people don't pick up hints like this never will be.
Would you expect participants in a discussion about board design to spell out ASIC and FPGA?
No, but xzvf admitted himself that he was posting slightly off-topic and therefore should not expect that everyone is familiar with it.
LTSP is not the topic at hand, virtualization is. I agree with HateBreeder.
While display resolution must be a major factor in power consumption, in my opinion the whole issue started back when VGA designers and game designers began thinking: "Hey, we can offload that processing to the GPU!" (if there even was the concept of 'GPU' back then).
Ever since, the complexity and features of these GPUs has increased tremendously, obviously resulting in higher scene complexity and better looking games/graphics. But man... Those chips need to be fed.
I don't know if there is any such thing as 'demand for scene complexity' beyond the "Oooh! Shiny!" factor, but if there is you can't hold the GPU manufacturers responsible for jumping that market.
Also, the telephone set he's using must predate the AT command set by at least 60 years.
When I was doing consulting/engineering services for SMB, the documentation I made was modeled after the actual OSI model.
So, you start with Layer 8, which is a basic description of your company's services, needs and requirements of the network, technical contacts, third parties involved in the network (security, telephony, ISP, hardware suppliers, specialized software) and their contracts.
Layer 7: Document the applications in use and how they are 'connected'. Create a global picture of what applications exist in the network, how they are connected, any dependencies on specific versions (e.g. frameworks, Java versions, databases, etc). Then, create a separate section for each 'application' that details the configuration of that application. E.g. the Active Directory gets its own section where you describe the domain name, relevant domain controllers, OU structure, blabla. For your web servers, document the site names, devices/servers responsible for the service, references to other documentation. Garnish with screen shots. Repeat for all applications.
Layer 6 may be hard to document because it's not always transparent, but include things like special software languages, broker services or anything sitting between your network and applications.
Layer 5, in a Windows-based network, should include documentation on the NT session security and compatibility level (authentication and signing requirements, if any).
Layer 4 should mention the transport protocols in use in your network (don't forget things like telephony), and any special settings made to the TCP/IP protocol stack required to make stuff work. Firewall access rules fit in this section nicely.
Layer 3 should include the addressing and routing schemes for your network. Server/distribution/access subnets, printer subnets, DHCP scopes, DNS servers, VPN connectivity, etc should all be described in this section.
Layer 2 should include the switch configuration documentation, VLAN configuration, frame types in use (again, don't forget telephony and wireless networks).
Layer 1 should include a building plan, documentation/certification of cabling infrastructure, patch cabinet documentation, maybe things like power infrastructure, physical access control. Sure you can make up the other stuff applicable to your network.
This is the global picture. The detailed configuration information for each server and device in the network should of course be noted, but that kind of information is useless without the big picture (which explains WHY the device has been configured thus).
I also never include security related information in generic documentation. A list of credentials should be stored safely in a separate document that sits in your boss' safe.
Hope this helps.
I think this would only actually be a problem if anyone used LIVE search.
I've used it once, but after 300ms I decided to look it up in a book.
A lot of commenters in this thread are bound to be native Dutch speakers, doing quite a good job at expressing themselves in English. Now, I would like to see YOU try in any other foreign languague, mister Coward, preferably Dutch. See how well your grammar sticks.
I wasn't contesting any spelling mistakes. Spelling a word using a phonetic alphabet across the phone is an entirely different subject, no?
ms, to the larger part, makes money from the programs and products they sell that run on windows machines.
I call BS. Couldn't find any more recent figures, but from http://www.microsoft.com/msft/earnings/FY07/earn_rel_q4_07.mspx I gather that in 2007, MS made a total revenue of $26B in the Client and Server division, and a measly $16B in the Business division (and I assume their server applications belong there). You also didn't bother to read TFS which explains nicely why pirated versions cause headaches. You, sir, earn zero points.
Her husband doesn't trust anyone without a company name on the side of their truck to do anything
Plug the live wire from the mains to the ON/OFF switch
That will probably get him into a nice, big van with company stickers on the side. The company being the "$STATE Correctional Facilities".
You must have used a retail disc on an OEM product key, or a generic OEM install disc on a DELL/HP/whatever branded OEM product key. Yeah, those are different. The activation challenge is not "25 sets of 5 random characters", it's 30 characters. Learn how to spell, it's a useful skill, and not just to activate XP. See http://en.wikipedia.org/wiki/NATO_phonetic_alphabet
So, instead of trolling, you could also consider phone activation to be a service for [expletive] who lose the recovery media that came with their computer, or didn't bother do make any.
Don't forget to see Burn After Reading for an example of how to get killed in the process. Hilarious.
The way I see it, they've produced exactly two games over the last five years, according to WP (Prey and some variants of Duke Nukem). Nothing to do with being nice to your employees. The bottom line is that just two releases won't keep your business in business. Which probably boils down to management issues, yeah.
For any value of FrameMaker.
You ever tried to get any work done on a 20 year old 14-inch EGA monitor?
If work consists of WP4 or playing Prince of Persia, hell yeah.
Haah, I'd never thought I'd see an argument about floppy drives backfire so badly. That musta hurt.
I'm off to find a floppy drive, take a picture of it and build a shrine.
"There is nothing more helpless and irresponsible than a man in the depths of a Terabit ethernet binge".
No, seriously. What a foresight these guys at IEEE have. They've run out of single-letter standards already.
Ooh, I could listen to my ass all day.
The only country I'm aware of that uses the word Saloon is the UK. And yes, the majority of Europeans call it a sedan.
Listen, I was not implying that Sedan is the only word in use, I was challenging the GP's statement that Europeans call this type of car a saloon.
Look at the Wiki page for Sedan and check the articles for the different languages.
The Dutch, Czech, Finnish, Danish, Greek, Turkish, Romanians, Spanish and a host of other languages call it a Sedan.
The French and Italians call it a Berline/Berlina.
The Germans and a few other languages call it a Limousine.
Nope, saloon is British English. Europeans just call it a sedan.
But a mime never has to say he's sorry.
But they will succeed in January 2076. The proof is right there on the Internets!
http://fallout.wikia.com/wiki/Timeline#2076
The article I linked to is mainly about hot adding memory, indeed, because this seems to me to be the most appealing type of RAM adjustments. However, the Static Resource Affinity Table mentioned is also capable of hot-removing memory.
The problem of the missing data from a removed module might actually not be a problem. I suspect that the type of hardware that supports hot addition and removal of RAM also supports the use of spare memory and memory mirroring.
Which will work, as a matter of fact, given the proper hardware: http://www.microsoft.com/whdc/system/pnppwr/hotadd/hotaddmem.mspx
Wouldn't that make a 3d model required to be presented to the input instead just a 2d one?
Mission Impossible, anyone?
...and on the seventh day, He exited from Append mode.